Using the Document Starter Kit

A key function of Kaptio Travel (KT) is to facilitate the delivery of branded documents from multi-day tour operators and their customers. To allow for maximum flexibility of the document setup and branding, Kaptio provides this Documents Starter Kit which contains a base setup of documents with code examples, which can either be used as-is or used as a foundation/examples for custom documents.

This document provides specifications of what, when and how data is made available for Documents for delivery to the customer as well as provides detailed insight into where key data is stored in the Kaptio system and how it’s applied within the Document Starter Kit

General Business Flow

An example of the high-level business flow describing document generation in Kaptio is described below.

The content manager has a wide range of configuration options when it comes to documents. Each channel defines which document types it uses (currently labelled Stages) and one or more document templates can be defined for each document type. These are used to define which data to pull into a document and the behaviour of documents, such as actions presented to customers on the document, expiration date and email template used to deliver the document.

All documents can be presented as online documents and/or PDF.

When generating a document, an example business flow is as follows:

An Agent or direct customer contacts a sales consultant to create a trip and produce one or more itineraries
The sales consultant composes a trip and one or more itineraries.
The sales consultant manually generates an Itinerary Document (Proposal) which will pull in content articles from services, locations and other relevant entities, and data defined for the document type and channel based on the selected Template. Supported document types are:
- Proposal
- Booking Confirmation
- Amendment
- Travel Documents
- Cancellation
The sales consultant modifies the Itinerary Document as needed.
The sales consultant publishes the Itinerary Document and sends it to the customer via the built-in Email Composer
The customer reviews the proposals and is given several standard options: 1. Reject the proposal; 2. Get back to the sales consultant with an additional question(s) and 3. Accept the proposal and select the option to BOOK.
When options 1 or 2 are selected notification is sent to the sales consultant and the status of the Itinerary is updated accordingly
When option 3 is selected the booking conversion process is triggered.
Kaptio provides multiple ways to convert the itinerary to a booking (manual by a sales consultant or automated through the customer book option). In both cases, Kaptio Travel will produce a payment schedule based on configured business rules. The customer will be requested to make a deposit payment. Receiving the payment (automated or manual) triggers the creation of an Itinerary Document (Booking Confirmation) and its automatic delivery to the customer via Email.
When the travel start date draws near, the Sales Consultant, Operational Support Staff or an automated process will generate an Itinerary Document (Travel documents), containing all vital information needed while travelling and deliver it to the customer via Email.
If the Itinerary is cancelled, an Itinerary Document (Cancellation) is created (automated or manual) showing any cancellation fees that apply and delivered to the customer via Email.

Example Document

To help visualize the resulting documents, here is a short demo of an example online document:

https://share.getcloudapp.com/YEukyqmd

Kaptio Data Model

To understand the content generation process it is useful to have a high-level understanding of the underlying Kaptio Travel data model. For detailed object descriptions and relationships see Kaptio Developer Doc (see https://docs.kaptioapis.com/ ) and the standard Salesforce Object Modeler/Schema builder.

The High-Level Entity Relationship Diagram below provides a high-level overview of the objects relevant to Documents.