Tourpaq
Accommodation and travel Ticketing and booking systems
When a customer books a trip with you, the booking is in Heyloyalty the next morning. The integration is built by Tourpaq and runs once a day. It picks up the bookings created or changed since the last run, so a trip that is cancelled is updated too. Only customers who have said yes to the newsletter in Tourpaq are created as members. The booking itself is stored as tracking data on the customer.
What can you do with it?
-
Without the integration
The guests call. Where are the documents, what should they pack, how do they get in from the airport. The answers are the same every time, but they cannot be sent in advance if nobody knows who travels when. Here the departure date sits on the contact, and the email can go out by itself.
-
Before departure
Send the practical things before the customer travels: what to pack, how to get in from the airport, and what is open at the destination. The timing follows the departure date. The data arrives overnight, so the flow has to sit a few days out and not on the day itself.
-
Welcome home
Once the return date has passed, you know. Send a thank you and ask for a review while the trip is still fresh, and suggest the next one based on where they have just been.
-
Destination and hotel
Country, resort and hotel come with every booking. A family that has been to the same resort three years running should not get the same email as someone who tries a new place each time.
-
Length of the trip
The duration is calculated from the departure and return dates. A long weekend and three weeks are two different decisions for the customer, and they do not take the same follow-up.
-
Trips that were cancelled
If a customer cancels, the booking changes status at the next synchronisation. You can keep them out of the flows that speak to someone about to travel, so nobody gets an email about looking forward to a trip they have cancelled.
The data you work with
About the customer
- First name and last name
- Email address
- Sign-up date: the booking date is used as the permission date
- Source: always set to TourPaq
About the trip
- Booking number and booking date
- Departure date and return date
- Duration: the number of days between departure and return
- Destination, country and resort
- Departure airport as an IATA code
- Hotel code and room type
- The salesperson on the booking
- Status: bought or cancelled, and it is updated if the trip is cancelled later
Requirements
- Booking system with TourPaq
- Premium license or higher
- An active email list and Tracking integration in Heyloyalty
Consent and GDPR
Only customers subscribed to the newsletter in Tourpaq are created as members in Heyloyalty. The rest do not come across. The booking date comes with them as the sign-up date, so the consent can be dated.
It is your responsibility that the data in Tourpaq was collected correctly and lawfully.
Setup
The integration is built by Tourpaq and is set up together with them. You need an active email list and the tracking integration switched on in Heyloyalty. The synchronisation runs at night, once a day, so it can take up to a day from a booking being created until it is in Heyloyalty. Tourpaq can send a number of custom fields, but which codes mean what is agreed per customer and has to be written down for your setup.