Travel booking management software
that doesn't live in five different places.
The booking is in a spreadsheet. The passports are in Dropbox. The supplier confirmation is in someone's inbox. The 'oh and they want a sea view' note is in a WhatsApp group. The departure is on Tuesday. Pick your favourite source of truth and cross your fingers.
Or move every booking to one record that holds everything — passengers, suppliers, payments, documents and notes — and stop the daily scramble.
No credit card. Cancel any time.
Where your bookings actually live right now
Take the next booking on your sheet. Try to gather every piece of information about it in one place, in under two minutes. We'll wait.
The shared spreadsheet
Row 147, columns A through AB. Some cells are red because somebody used red to mean 'urgent'. Some are red because Excel auto-formatted negative numbers. Nobody is quite sure which.
The Dropbox folder
Twelve subfolders, each containing 'final_v3', 'final_v3_REAL', 'use_this_one' and 'do_not_use'. The real e-ticket is in one of them. Probably.
The WhatsApp group
Client mentioned a nut allergy in a voice note at 8:43pm on a Tuesday. The note is between forty-seven other messages and a meme. Somebody listened to it. Maybe.
The consultant's head
Only one person knows that Mrs Patel always wants a ground-floor room because her knee. They're on annual leave next week. The booking departs in nine days.
The email thread
Forty-three messages, four participants, two suppliers, one client. Somewhere in there is the agreed pickup time. Search 'transfer' returns thirty-eight hits.
The Post-it note
'Henderson — call re. balance'. Stuck to the monitor. Three weeks old. The Hendersons departed last Friday. You hope it was important.
One record. Everything attached.
Every booking in travelCRM is a single, complete record. Passengers, suppliers, payments, documents, notes, status — all in one place, all visible to the people who need to see them.
Passengers as first-class records
Each passenger has their own profile — name, passport number and expiry, date of birth, dietary requirements, room preferences, frequent flyer numbers. Edit one passenger without touching the others. GDPR-compliant by design.
Replaces: a 'pax details' tab in a spreadsheet.
Multi-supplier components
A booking can include flights, accommodation, transfers, excursions, insurance — each with its own supplier, reference number, cost, confirmation status and option-release date. Edit one component without rebuilding the whole booking.
Replaces: separate trackers per supplier, per booking.
Payment schedule and history
Deposit due, balance due, late fees, refunds — all tracked against the booking. See exactly what's been paid, what's owed and when it's due. No more 'have we invoiced this?' moments at month end.
Replaces: cross-referencing the bank statement against the booking sheet.
Document hub
Tickets, vouchers, supplier confirmations, passports, insurance certificates — uploaded directly to the booking record, encrypted at rest, retrievable from a phone in three taps when the client phones from a departure lounge.
Replaces: Dropbox, Google Drive, 'check your downloads folder'.
Threaded internal notes
Every booking has a notes thread. 'Client wants sea view.' 'Confirmed nut allergy with supplier.' 'Mother-in-law travelling separately — separate invoice required.' Visible to the team, searchable, time-stamped.
Replaces: WhatsApp groups, sticky notes, 'I think Sarah mentioned…'
Status workflow
Quote, confirmed, documents pending, invoiced, paid, departed, returned, commission due, commission received. Every booking sits in a status; you filter by status to see what needs your attention today, not in the weekly meeting.
Replaces: colour-coded spreadsheet rows.
Why a generic CRM is the wrong shape
HubSpot, Pipedrive, Salesforce — they model the world as a 'deal' with one customer, one product, one price. A travel booking has six suppliers, eight passengers, three payment instalments, and a commission only payable eleven months later. You can torture HubSpot into approximating it, but you'll be building custom objects forever.
travelCRM models the booking the way agencies actually think about it. The data shape is right out of the box. No custom field configuration. No three-month implementation. No consultancy fee.
What's in every plan
- ✓Unlimited bookings, passengers and suppliers
- ✓Multi-component booking structure
- ✓Per-passenger profile with passport storage
- ✓Document hub per booking, encrypted
- ✓Threaded internal notes
- ✓Status workflow with custom states
- ✓Role-based access and audit trail
- ✓CSV import, REST API, white-label customer portal
Questions agencies actually ask before switching
Can I import my existing bookings from a spreadsheet?
+
Yes. CSV import covers contacts, bookings, suppliers and supplier rates. Most agencies migrate active bookings only — anything already departed and paid usually stays in the old spreadsheet until it's archived. We've written importers for the common formats (the typical 30-column 'master tracker' that most agencies keep) and we can help shape your file if it's unusual. No migration consultancy fee.
How does it handle a single booking with multiple passengers and suppliers?
+
A booking is a parent record with passengers as linked sub-records (each with their own passport details, dietary requirements and traveller notes) and components as linked sub-records (flights, hotels, transfers, excursions, insurance — each with its own supplier, reference and cost). You can edit a single passenger's details without touching the others, and you can add or remove components after confirmation without re-creating the booking.
What about group bookings — 30+ passengers, multiple rooming combinations?
+
Group bookings work the same way as individual bookings, just with more passenger rows. You can attach a rooming list, set per-passenger payment status (which is genuinely useful when half the group has paid and half hasn't), and produce a group manifest for the supplier. We've had agencies run school groups of 80+ on the same architecture.
Is it mobile-friendly? Our consultants travel a lot.
+
Yes — the app is fully responsive. Look up a booking from a phone at an airport, update a passport detail, send a document to a client, mark a deposit received. We don't have a native iOS or Android app yet (the mobile web version is more useful than most native apps would be), but it's on the roadmap.
Who can see what? Some bookings are sensitive.
+
Role-based access controls. Consultants see their own bookings by default; managers see everything in their team; directors see the agency. You can mark a booking as restricted so only specific users can open it (VIP clients, staff personal travel, anything sensitive). Audit trail logs every view and edit, so you know who looked at what.
Does it support multiple consultants working on the same booking?
+
Yes. Bookings can have a primary owner and additional collaborators. When a colleague edits, you see the change live. When somebody's on annual leave, their bookings can be reassigned in bulk to cover. Internal notes thread by booking — no more 'I think Sarah said something about this in an email last week' moments.
One booking. One record. Everything attached.
Two weeks free. No credit card. Import your active bookings in an afternoon. Get your evenings back.
Start your trial →Got a tricky booking shape? Ask us if it fits →