Forty bookings behind one departure
Look behind a single eight-day departure and you find a lot of small bookings: two included dinners, a winery lunch, a boat trip, three museum timed entries, a cable car, a local guide, a coach for four days and a transfer at each end. Each was requested by email, some by a booking form on the supplier's site, one by phone.
Some confirmed at once. The winery replied "yes, fine" without the date. The boat company has not replied at all. The museum sent an automated confirmation for the wrong time slot. Your operations person keeps a checklist in a spreadsheet and chases on Friday afternoons, when she has time, which in May she does not.
The work is in the loose ends
Requesting services is not the hard part. The hard part is knowing, across every departure, what is confirmed, what is provisional and what has been missed, when confirmations arrive in a dozen formats into a shared inbox.
- Confirmations are emails, PDFs, booking reference texts and phone calls.
- The checklist for each departure is rebuilt by hand from the itinerary.
- Replies do not always quote your reference or the date.
- Chasing depends on someone reading the checklist at the right time.
- Changes to passenger numbers need re-confirming with the suppliers that care.
Unconfirmed services are found at the worst moment
A boat trip that was never confirmed is discovered by the tour leader on the quay. A restaurant that was told twenty guests when there are now twenty-four has laid the wrong table. A timed entry at the wrong hour means rearranging the day. The tour leader improvises, the passengers notice, and the office spends the next morning apologising.
In the office, confirmation chasing crowds out other work during the busiest months, and it is the kind of task where a missed item is invisible until it goes wrong.
A confirmation tracker that chases for you
We build a tracker that knows every service on every departure and follows each one to a confirmed state.
- Each tour itinerary lists the services it needs per day. When a departure is created, its service checklist is created from the itinerary, with the supplier, date, time and number.
- Requests go to suppliers from templates, including your reference, the date and the passenger count, by email or through the supplier's own booking form where needed.
- Replies arriving in the operations inbox are matched to the service by reference, supplier and date. An AI step reads the reply and proposes a status (confirmed, needs changes, declined), and a person accepts it with one click.
- Services still unconfirmed after a set time are chased automatically, and after a second reminder they go to a person to phone.
- When passenger numbers change beyond a threshold you set, the suppliers who care about numbers get an update and the service goes back to awaiting confirmation.
- Each departure shows a single status: all confirmed, or a short list of what is still open.
| Service state | What happens |
|---|---|
| Requested | Waiting for reply, reminder scheduled |
| Reply received | Matched and proposed status shown for approval |
| Confirmed | Stored with the supplier's reference |
| No reply after reminders | Passed to a person to phone |
| Numbers changed | Supplier updated, awaiting re-confirmation |
Operations with only the exceptions left
The operations person starts the day with a list, not an inbox: four replies to approve, two suppliers to phone, one numbers change sent out overnight. Departures leaving in the next fortnight all show confirmed except one boat trip, which is now a phone call rather than a surprise.
The tour leader sees the same confirmed list with supplier references and contact numbers, so on the day there is no question of whether the booking exists.
Signs supplier confirmations are slipping
- Confirmations are tracked in a spreadsheet rebuilt for each departure.
- You chase suppliers when you have time rather than on a schedule.
- Tour leaders have found services that were never confirmed.
- Passenger number changes are not always passed to restaurants.
- Confirmation replies arrive in a shared inbox nobody fully owns.