AI guest messaging for BookingPal channels
TravelPal connects to BookingPal and answers guests in the channel conversations BookingPal relays back: Airbnb, Booking.com, Vrbo, and Expedia. Connect it only if BookingPal's own dashboard is the screen your team works in every day. If your units are pushed into BookingPal from a property management system that holds your reservations and your inbox, connect that system instead, because that is where the booking and the thread are owned.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from BookingPal
BookingPal is the distribution layer under rental brands and property management companies that sell through Marriott Homes and Villas, Google Travel, Hyatt, and Amex Travel alongside the big booking sites, a network BookingPal puts at more than 100,000 properties.
Bookings announce themselves
BookingPal sends a notice the moment a booking is made, changed, or canceled, and that notice carries the booking itself rather than a pointer to one, so nothing has to be fetched back before the guest is greeted. Every delivery echoes the key BookingPal issued your account, which is how TravelPal knows it is yours and turns away anything that is not. A cancel notice is the one place BookingPal states that a booking has ended, so TravelPal treats it as final and stops writing to that guest.
Reservations read back one unit at a time
BookingPal answers with the bookings for a single unit rather than a list across your portfolio, so TravelPal sweeps unit by unit to catch anything a notice missed. Each booking brings the channel it came from, the guest's own confirmation code from that channel, the dates, and the party size as adults plus children. BookingPal calls a booking confirmed or fully paid once the guest is coming and provisional while it is still an inquiry, so an inquiry is never handled as a stay. The accommodation fare arrives with no currency stated anywhere on the record, so TravelPal shows the figure exactly as BookingPal gives it and puts no currency on it.
The channel conversation, and the stay it belongs to
Threads arrive with the channel they came from and with every message already on them, ordered oldest first, so the concierge has read the conversation in the order it happened before it says anything. Each thread names the reservation it belongs to, and that is the only way a message is tied to a stay: BookingPal issues no guest identity of its own, so somebody who books twice arrives as two separate stays until TravelPal matches them from what it knows.
What BookingPal says about a guest, and what it does not
The name arrives as one comma-separated string, and which half is the surname is not consistent from booking to booking, so TravelPal repeats it exactly as BookingPal supplies it rather than guessing. There is no language field on a BookingPal booking, so the first reply follows the language the guest actually wrote in. The address on a booking is sometimes the channel's own relay rather than the person's, which is one more reason nothing here is sent by email.
What TravelPal writes back
Every message goes out through BookingPal, never around it, so your own inbox shows exactly what each guest was told.
Replies land in the channel conversation
BookingPal has one send and it is the thread itself, so an Airbnb guest is answered inside Airbnb and a Booking.com guest inside Booking.com. There is no email, SMS, or WhatsApp path through BookingPal, and TravelPal will not fall back to one even when the booking carries an address, because that address is as likely to be the channel's relay as the person's.
Every line you write reaches the guest
BookingPal relays every message on a thread onward to the channel, so there is nowhere on it to leave a line for your own staff: it would travel out to the guest's Airbnb or Booking.com conversation. TravelPal writes no such line into BookingPal. Anything meant for your staff, a recorded sale or a question it is holding for a person, is raised with your team away from BookingPal entirely.
Nothing else in BookingPal is touched
Messages are the only thing TravelPal puts into BookingPal. It creates no units, changes no rates, and writes no availability, because the system that pushes your inventory into BookingPal re-pushes it on its own schedule and would quietly undo anything written from this side.
Connected in four steps
BookingPal switches API access on for your account, and TravelPal does the rest itself.
Ask BookingPal to switch partner access on
There is no self-serve key and no developer signup screen: BookingPal gives out access through its partner program. One email or call to your BookingPal account manager starts it, and the technical side of that program is ours to handle. Ask them for the API host issued to your account, including any version path and with no trailing slash.
Paste the four values into TravelPal
The API host, the partner key that authorizes the connection, and your own BookingPal login email and password. TravelPal checks them against your account on the spot, so a wrong one is caught while you are still on the screen.
Have BookingPal point reservation notices at TravelPal
BookingPal sets those deliveries up on its own side rather than leaving it to you, and gives your account a unique key it echoes inside every one. Paste that key in as well. Until it is there every delivery is turned away, which is the safe default rather than an error.
Match your units once
Your properties come from the system that pushes them into BookingPal, and each BookingPal unit is paired with one of them during onboarding. After that, a guest on that unit is answered on whichever of the four channels they booked through, and the price is the same whether a unit sells on one channel or five.
The dashboard shows the connection the whole way: connected, last sync, and any error in plain words. The rest of going live is covered in what onboarding involves.
What the BookingPal connection will not do
Every property management system draws its own lines, and the ones BookingPal draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Your unit list cannot come from BookingPal
BookingPal takes units in from the system that owns them and offers no way to read them back out, so TravelPal cannot build your property list from it. Your properties come from your own system of record, which you will find on the integrations list, and each BookingPal unit is paired with one of them at setup. A unit added later needs that same one-time pairing before its guests are answered.
A sale does not move the BookingPal booking
BookingPal has no way to write a change onto a reservation, so a paid late checkout does not shift the departure time on the BookingPal record. Upsells are still sold at your prices and recorded against the stay, and your team is told, but the time change is made in the system that owns the booking.
Four channels carry a guest thread
Airbnb, Booking.com, Vrbo, and Expedia conversations come back through BookingPal, and those are the guests TravelPal answers. BookingPal also distributes to Marriott Homes and Villas, Google Travel, Hyatt, and Amex Travel, and a stay booked on one of those is left with your team rather than answered down a route TravelPal cannot confirm reaches the guest.
Bookings are announced, messages are not
A new or changed booking reaches TravelPal the moment BookingPal sends the notice. Nothing announces a guest message, so BookingPal threads are re-read on a schedule and a reply follows that pass rather than the keystroke. The same gap runs the other way: when one of your team types in the BookingPal inbox nothing reaches TravelPal, so a thread is handed over on the quiet hours and rules you set rather than on anything BookingPal tells us.
Where the AI is not sure, it stops and asks your team rather than guessing. That is the same on every system: see the guardrails.
BookingPal integration FAQ
Do I need BookingPal to switch something on before TravelPal can connect?
Yes. BookingPal gives out API access through its partner program rather than from a self-serve screen, so it starts with one email or call to your BookingPal account manager. They issue the API host and the partner key that authorizes the connection, and the technical side of their program is ours to handle. You supply your own BookingPal login and the notification key they hand you.
My reservations live in a property management system and BookingPal only distributes my units. Which one should I connect?
Connect the system where your reservations and your guest inbox actually live. BookingPal is a distribution layer, so connecting it reaches the same units with an extra party in between, and it cannot give TravelPal your unit list. BookingPal is the right connection when BookingPal's own dashboard is the screen your team works in. Our integrations page lists every system we connect to.
Which channels can TravelPal answer on through BookingPal?
Airbnb, Booking.com, Vrbo, and Expedia. Those conversations are relayed back through BookingPal and TravelPal replies inside them, so the guest never leaves the channel they booked on. A stay booked on any other channel BookingPal distributes to is left with your team.
Can TravelPal change a BookingPal reservation?
No. The connection reads bookings and conversations and sends guest messages. A sold upgrade is charged at your price and recorded against the stay, and your team applies the change in the system that owns the booking. TravelPal also leaves rates and availability alone, because your own system re-pushes both into BookingPal.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest BookingPal in how widely they are used.
Updated