Dynamic Itinerary Generation
How a tour operator generated itineraries from trip templates in Zoho Writer, plus a Creator-based quote viewer that replaced static PDF itineraries with a branded interactive experience.
Client details generalized to protect confidentiality.
Operators assembling itinerary documents by hand for every booking, where each document is a copy of a previous one with details swapped.
The Challenge
Every itinerary was built by copying a prior document and editing the details. On a multi-day trip with accommodation, transfers, and activities per day, that meant dozens of edits per booking and a real chance of leaving a previous client’s detail in the document. Clients received a static PDF, so any change meant reissuing the whole file and hoping they opened the newest version rather than the one already in their inbox.
The Solution
Trip Templates as the Source
Itinerary content is held as reusable template components rather than living inside past documents.
- Template library per trip type
- Day and activity components
- Supplier detail pulled from records
- Template versioning
Dynamic Document Generation
The itinerary generates from the trip record and its subform data with no manual assembly.
- Writer merge from trip and subform data
- Day-by-day sections generated from lines
- Conditional inclusion by trip content
- Regeneration retains prior versions
Interactive Quote Viewer
Clients view a branded interactive itinerary instead of a PDF attachment, so the version they see is always current.
- Creator-hosted HTML viewer
- Branded layout with imagery
- Always renders current trip data
- Shareable link per trip
Change Handling
An itinerary change updates what the client sees rather than requiring a reissued document.
- Viewer reads live trip data
- Change log visible to the agent
- Notification on material change
- PDF export retained for those who want it
Apps in This Solution
Zoho CRM
Zoho Writer
Zoho Creator
Under the Hood Technical detail
- Template Components
- Itinerary content is componentized by day and activity rather than stored as whole documents. Whole-document templates get copied and edited, which reintroduces the original problem in a slightly tidier form.
- Viewer Over Attachment
- The interactive viewer reads live trip data, so there is no stale version circulating. This solved a support problem as much as a design one, since clients arriving with an outdated itinerary was a recurring source of confusion at check-in.
- PDF Still Available
- A PDF export remains for clients who want a file, particularly for offline travel. Removing it entirely would have been cleaner and would have failed the actual use case of someone on a flight.
- Version Retention
- Regenerating an itinerary keeps prior versions rather than overwriting, which matters when a client references what they were originally sent.
- Notable Constraint
- Suppliers provide detail in inconsistent formats and some of it arrives as free text. Free-text notes are supported per day rather than forcing every element into structured fields, since forcing structure onto genuinely unstructured supplier notes is how agents end up working outside the system.
The Results
- Itineraries generate from trip data rather than being assembled by hand.
- Clients always see the current itinerary rather than a stale attachment.
- Prior versions are retained for reference when a client queries a change.
Building Every Itinerary by Hand?
We have automated itinerary and document generation for travel operators. Tell us what your client documents look like today.