Between the deposit and the flight home, a traveler on a multi-day trip receives invoices, reminders, questionnaires, forms, and final documents, and sends information back that operations depends on. This guide explains that exchange, what a guest portal and communications engine have to do, and how Tourcube handles both sides.
A tour operator guest portal is a branded website where a traveler sees their own trip: dates, balance, documents released by the operator, forms to complete, and a way to pay. It is the guest-facing side of the booking record. Traveler communications are the staged emails and documents the operator sends as the trip approaches, and the portal is where most of them land.
Both are part of tour operator software rather than separate products, for a simple reason: everything the guest sees is a view of the booking. The balance is the booking's schedule, the documents are generated from its segments, and the forms write back into it. A portal that is not built on the booking record is a second copy of the trip that has to be kept in step by hand.
Guest communication on a multi-day trip is a sequence, not a message. Each stage has something going out and, often, something coming back.
Confirmation and invoice, generated from the booking with the payment schedule on it. The guest portal opens for the traveler.
Pre-trip questionnaire, health and waiver forms, and traveler information forms go out. What comes back, such as dietary needs, medical notes, emergency contacts, and passport details, is captured into the booking and later into the manifests. How manifests are produced →
Upcoming and overdue payment reminders, then payment acknowledgments as receipts land. Where a card profile is stored, the final payment charges automatically on its date. How receivables work →
A pre-trip reminder, then the final documents: the detailed itinerary, pre-departure information, and final details, released to the portal when the operator is ready. Itinerary documents, explained →
The guide has the guest list and documents in their own portal; the traveler has the trip specialist and trip leader contacts in theirs.
A welcome-home message and a trip evaluation, with the results recorded on the client record for references and the next trip. Where evaluations go →
SUMMIT TRAILSCtrl K?✨Support RequestLog Out| Recipient | Booking | Last Stage Sent | Status | ||
|---|---|---|---|---|---|
| ☑ | Carter, James & Anne | 197101 | jcarter@example.com | Pre-Trip Reminder · 05/12 | Ready |
| ☑ | Bennett, Sarah | 197115 | s.bennett@example.com | Pre-Trip Reminder · 05/12 | Ready |
| ☐ | Holloway, Daniel | 197128 | — | — | No email |
The Pax Communications panel on a Tourcube departure: choose the document stage and sender, build the recipient list for the whole date, and see each booking's last stage sent and whether it is ready.
Operators send the same kinds of document to every traveler on a date, so the useful unit is the departure, not the individual email. In Tourcube the Communications panel is a generation engine: pick a document stage, choose the sending user, and build the recipient list for the entire departure in one pass, with per-booking status showing who last received what.
Some of the sequence above should run itself. Payment reminders, acknowledgments, form chase, welcome-home messages, and evaluation requests are predictable, and an operator with hundreds of travelers a season should not be sending them by hand. Other messages, such as a final-documents email from the trip developer, should read as though a person sent them, because one did.
A guest portal is a view of the booking under the operator's brand. The traveler sees the trip and its dates, who is traveling and whether the booking is paid in full, the trip specialist and trip leader, the documents that have been released, the forms to complete, and a secure way to pay against the live balance. Because it reads from the record, it is never out of date.
The Tourcube guest portal for one booking: dates, travelers, contacts, balance, and the documents released so far, all read from the booking record.
The information travelers return is not paperwork for a file. A dietary restriction becomes a line on the rooming list a hotel receives. An emergency contact and a medical note become part of the manifest a guide carries. A passport number becomes a passport manifest. The system has to capture these into the booking and pass them to the documents that need them, and it has to show operations who has not yet responded.
Passenger waivers and traveler information forms are automated and captured digitally, per passenger, on the booking.
Forms and PTQ are managed on the departure, so the set of questions fits the trip, and a guest forms status report shows completion across the date.
Reminders go out automatically until a form is returned, without a coordinator keeping a list.
What travelers enter flows into rooming lists, manifests, and portal documents without being retyped. Documents from live data →
The guide portal is the field counterpart of the guest portal. A guide or trip leader sees the departures they are assigned to, upcoming and past, with the guest list and guest details, every departure document and report, and a place to upload required forms and expense reports. The documents are the ones generated from the departure's bookings, so the manifest in the guide's hands matches the one in the office.
A tour operator guest portal is a branded website where a traveler sees their own trip: dates, balance, documents released by the operator, forms to complete, and a way to pay. It is the guest-facing side of the booking record, drawn live from it rather than copied.
Guests log in to a portal that is tied to their booking. In Tourcube the portal is branded as yours, mobile-friendly, and shows booking details, forms, documents, and secure payment for that traveler's trip.
From your staff. Tourcube sends communications from specific users or booking-contextual roles, such as the trip developer on the booking, not from a do-not-reply address, and each message is logged on the booking.
Yes. Documents are released on your schedule by document stage, and the booking carries release controls for final documents and guest portal forms. Until a stage is released the guest does not see it.
Health, waiver, and preference forms, passenger waivers, and traveler information forms, captured digitally into the booking. Pre-trip questionnaires are managed on the departure, and a guest forms status report shows who has completed what.
Yes. Agents get portal access for their clients' bookings, with optional guest-price suppression for wholesalers.
Yes. Tourcube provides a branded, mobile-friendly guest portal for booking details, documents, forms, and secure payments, a communications engine that generates staged documents per departure, rules-based automated emails and form chase, and a guide portal for the departures a guide is assigned to.
These guides explain how multi-day tour operations work and what software should do about it. Start with the overview, or go straight to the part of the business you are thinking about.
Tell us what you send travelers today and what you wish came back on its own. We will show you the portal and the communications engine in the actual product.
Book a demo