Which login was that booking under?
A client rings to ask what time their transfer picks them up. It sounds simple. The transfer was booked through one company's site, the hotel through a bed bank, the flights through a consolidator, and the tour operator for the second week has its own portal. You have a password manager full of supplier logins, if you are lucky, or a notebook of them if you are not.
You search your inbox for the client's surname, find three confirmation emails and a reference number, log into the transfer company's site, and find the pickup time. Five minutes for a thirty-second answer. Multiply by every call, and by every booking where the client's name is spelled differently in each system.
Why a trip lives in so many places
| Component | Where the booking lives | Reference style |
|---|---|---|
| Package | Tour operator agent site | Operator booking number |
| Flights | Consolidator or airline | Airline booking reference |
| Hotel only | Bed bank or hotel direct | Bed bank or hotel reference |
| Transfers | Transfer company site | Voucher number |
| Cruise | Cruise line portal | Cruise booking number |
Dynamic and tailor-made trips, which are where independent agents shine, spread across the most suppliers. Nothing ties those references together except your memory and your inbox.
What scattered references cost
Every client question takes longer than it should. Errors creep in when you look at the wrong booking. Covering for a colleague, or letting someone cover for you, is hard because only the person who booked knows where everything is. And when something changes with one supplier, you might not think to check the related components elsewhere.
One booking record for every trip
- Each trip has a single record with the client, passengers, dates and every component.
- Each component holds its supplier, supplier reference, status, amount, payment state and a direct link to the booking on the supplier's site where one exists.
- Confirmation emails forwarded to a booking inbox are read, and supplier, reference, dates and times are extracted and added to the right trip, with anything uncertain queued for you.
- Key details, such as flight times, hotel address and transfer pickup times, are shown on the trip summary, so most client questions are answered without logging in anywhere.
- Search works across clients, passengers, supplier references and destinations.
- Where a supplier offers an API for booking status, we pull it; where they do not, the record is updated from their emails.
Supplier logins themselves stay in a proper password manager. We do not store supplier passwords in the booking system.
Answering 'what time is my pickup' in seconds
When a client rings, you search their name and the trip summary shows every component, reference and key time. If you need to go to the supplier's site, the direct link takes you there. A colleague covering for you can answer the same question without asking you where anything is.
Take a three-centre trip: flights from a consolidator, two hotels from different bed banks and a rail pass. Each confirmation email is forwarded to the booking inbox and matched to the trip. The summary lists all five references and the key times. A month later, when the client asks which station their train leaves from, the answer is on the summary.
It also provides the foundation for most other improvements: balance reminders, document tracking, schedule change checks and commission reconciliation all work better once every component lives in one record.
Is this your daily login marathon?
- You log into several supplier sites to answer one client question.
- Booking references are found by searching your inbox.
- Only the person who made a booking knows where everything is.
- Client names are spelled differently across supplier systems.
- You keep supplier logins in a notebook or spreadsheet.