A loyal passenger rings, and nobody recognises her
Mrs Patel has travelled with you six times over ten years. She rings to ask about next year's programme. The new member of staff finds three records under her name, one with an old address, one created for a group booking through her walking club, and one from last year. None shows her dislike of early starts, her preference for a ground floor room, or the complaint she made (and you resolved) about a hotel in Seville.
She is polite about it, but she mentions that she had to explain everything again. She had expected you to know her.
History is split across records and systems
Repeat history is lost for ordinary reasons. The booking system was changed a few years ago and old bookings are in an archive. Group bookings created new traveller records. Preferences and feedback were kept in notes, emails and a spreadsheet.
- Duplicate traveller records from different bookings and systems.
- Old bookings held in a previous system or an archive export.
- Preferences stored as notes on individual bookings, not on the person.
- Feedback and complaints kept separately from the traveller.
- No quick way to see which of your tours they have not yet taken.
Regulars feel like strangers
Repeat travellers are the heart of most specialist operators. They book early, they recommend you and they forgive the occasional problem because they know you. Treating them like new customers wastes that. Staff also miss easy opportunities: suggesting the tour a regular has not done yet, or offering a returning traveller a date before the brochure goes public.
Mistakes repeat, too. If a traveller's past issues or needs are not visible, you can put them back in the room they complained about.
One traveller record with the whole story
We build a traveller record that brings history together and keeps it current.
- Traveller records from your current booking system, older system exports and spreadsheets are loaded and matched. Likely duplicates are found by name, date of birth, email, phone and address, and a person confirms each merge.
- Past bookings from all sources are attached to the single record: tours, dates, room types, who they travelled with.
- Preferences are held on the person rather than the booking: room location, dietary needs, sharing preferences, pace, and anything else you choose to record.
- Feedback, complaints and their resolution are linked, so staff see them before making suggestions.
- The record shows tours in your programme that the traveller has not yet taken, grouped by the types of tours they have booked before.
- When staff open a new booking or answer a call, the traveller's summary is shown, through a small add-on to your booking system or a lookup screen.
- Travellers can be tagged for early previews of new tours, under the marketing permissions they have given.
| What staff can see | Where it came from |
|---|---|
| Every past tour | Current and previous booking systems |
| Room and dietary preferences | Moved from booking notes to the person |
| Past feedback and complaints | Survey replies and office records |
| Travel companions | Linked bookings |
| Tours not yet taken | Programme compared with history |
When a regular calls now
Mrs Patel rings. Her record opens with her six tours, her ground floor room preference, a note about early starts and the resolved Seville complaint. The member of staff suggests the new Puglia tour, which has a relaxed pace and which she has not done, and offers a date before it goes on general sale. Her room preference is copied to the new booking automatically.
Across the business, you can finally see how many of your travellers are returning, and which tours bring people back.
Keeping records clean becomes part of normal work. When a new booking arrives with details that match an existing traveller, staff are prompted to link it rather than creating another duplicate.
Is repeat history getting lost?
- Regular travellers have several records in your system.
- Old bookings are in a previous system nobody opens.
- Preferences are stored on bookings, not on the traveller.
- Staff cannot see past complaints when taking a new booking.
- You cannot easily list tours a regular has not taken.