These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Tour Operator Software
- Features
- Bookings
Bookings
Enquiries, reservations and confirmed departures.
OverviewDepartures this month×
Tour Operator Software · Bookings
New
Departures this month
Tour bookings
| Id | Package | Customer | Departure date | Traveler count | Status | |
|---|---|---|---|---|---|---|
| IDD-127 | TP-3385 | CUS-146 | 12 Nov | 21 | Enquiry | |
| IDD-307 | TP-8617 | CUS-159 | 03 Nov | 16 | Reserved | |
| IDD-188 | TP-5154 | CUS-079 | 26 Oct | 17 | Confirmed | |
| IDD-589 | TP-8941 | CUS-040 | 15 Oct | 33 | Completed | |
| IDD-663 | TP-7313 | CUS-151 | 31 Oct | 15 | Enquiry |
6 of 6 records
IDD-127Tour bookings · TB-41560
EnquiryPackageTP-3385
CustomerCUS-146
Departure date12 Nov
Traveler count21
What you can do
From an enquiry to a confirmed departure
A tour booking records which package a customer wants, the departure date and how many travellers are coming. It moves along one path: enquiry, reserved, confirmed and completed. Failures, rejections and cancellations are recorded as their own outcomes with a reason, rather than as edits that erase what was planned. That keeps the pipeline honest: you can see how many enquiries became confirmed departures and why the others did not.
Bookings are captured by the dispatcher through a form that validates the whole booking first: the package and customer must exist, and a booking already submitted from the same source is rejected rather than entered twice. The person recording the booking is taken from their login.
How the work is organized
The dispatcher takes and confirms bookings; the operations manager follows the departure calendar.
- One path. Bookings move from enquiry to reserved, confirmed and completed, never skipping a step.
- Reasons kept. Cancellations and rejections carry their reason.
- No duplicates. A repeated submission from the same source is rejected.
What to agree during setup
Agree what moves a booking from enquiry to reserved (a deposit, a signed form) and from reserved to confirmed. Agree your cancellation reasons and who can cancel. Decide how group bookings are recorded: one booking with the traveller count, or one per family. Prepare examples of an enquiry that never books, a confirmed group, a duplicate booking from a partner channel and a late cancellation.
Check the handoff on an actual case
A travel agent sends the same booking request twice through their channel. The first becomes an enquiry for six travellers on the coastal tour; the second is rejected as a repeat. The dispatcher reserves it when the deposit arrives and confirms it a week before departure. The departures list shows six confirmed travellers on that date, and the dispatcher can plan the vehicle accordingly.
What your team sees
- Booking pipeline — Enquiries, reservations and confirmations by package.
- Departures this month — Bookings departing in the next thirty days.
Follow the work through
- Booking to departure: From enquiry to a confirmed departure.
Plan integrations with booking channels.
What it keeps track of
Data model- Tour bookings
- Customer bookings against a tour package with departure and travelers.
- Tour packages
- Sellable tour packages built on an operational trip record.
- Parties
- Customers, carriers and providers the operator trades with.
Who uses it
Permissions- Dispatcher
- , Operations Manager.
- The dispatcher takes bookings; the operations manager follows departures.
Set up Tour Operator Software your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.