AI guest messaging for Uplisting
TravelPal answers your Uplisting guests in the thread they wrote in. Every reply names its channel, and Uplisting switches API access on for your account first.
One Uplisting connection works in both directions. Each item is explained below.
What TravelPal reads from Uplisting
Uplisting was founded in the UK. It says more than 2,000 property management companies use it. Most have a mix of Airbnb, Booking.com, Vrbo, and direct bookings. These are priced in each property's own currency instead of dollars.
Properties, under the name your team uses
TravelPal uses the nickname Uplisting gives each unit, the one your own staff know from an ops card. It also reads the address and the amenities. It reads the photos in the order you set them. It reads the capacity and your check-in and check-out times. Each property has its own time zone. So a checkout reminder goes out at the right local hour, not at your head office's hour.
Bookings, with the code the guest can quote
Uplisting sends a booking the moment it is created, updated, or removed. Each delivery has its own id, so one that is sent again is not counted twice. The channel comes with it, and so does that channel's own reservation code. That is the number already in the guest's Airbnb or Booking.com email, not Uplisting's internal booking number. Fees, paid extras, charges, and tax lines arrive too, in the currency on the booking.
The thread the guest actually used
One booking in Uplisting can have more than one thread, one for each channel the guest has used. TravelPal works in the thread with the most recent activity. Every thread Uplisting publishes belongs to a booking, a booking request, or a guest inquiry. So there is no owner-side thread where a guest reply could land by mistake. The history comes in with the oldest message first. So TravelPal picks up the stay where the guest left it.
The door code stops at the door
Uplisting puts the guest's lock code on every booking read and every booking event. TravelPal removes it before the stay goes to the AI. It also removes the payment handle on the booking and the address of your own direct-booking site. So none of the three can be repeated to anybody. Read more in how we handle safety.
What TravelPal writes back to Uplisting
Every message goes out through Uplisting, never around it. So your Uplisting inbox shows exactly what each guest was told.
Replies that name their channel
Uplisting will not take a message that does not say which channel it goes out on. It also refuses a channel the thread has not enabled. So an Airbnb guest is answered inside Airbnb. Booking.com guests get their answer inside Booking.com. A Vrbo guest is answered inside Vrbo. A guest with no channel thread is answered by email. SMS stays a choice for your team, because Uplisting charges you for each one.
Each sale is emailed to your team
TravelPal sells the extras you price yourself, like a damage waiver or an extra clean, at your own prices, on the guest's own page. Each sale is emailed to your team, so nobody has to find it in Uplisting. On a booking that came from Uplisting, early check-in and late checkout are not sold. TravelPal also changes no arrival or departure time on it.
Extra nights go to your team, not onto the booking
TravelPal moves no dates on an Uplisting booking. When an Uplisting guest asks for another night, your team gets the request and the dates. Your team checks the calendar and makes the change in Uplisting. A guest who booked on a channel is pointed to the channel's own change flow.
Connected in four steps
Uplisting turns on API access for your account. TravelPal does the rest itself.
Ask Uplisting to switch API access on
There is no key for you to create in Uplisting. Its partner desk at partner@uplisting.io registers the integration against your account. That takes one email, or one call to your account manager. Ask for the partner client ID in the same message.
Approve TravelPal from your own account
After you are registered, you approve the access once in the browser. It covers your properties, your bookings, your calendar, and messaging. Include offline access in the same approval. Then the connection stays on by itself, and you are not sent back to that screen every hour.
Add the account's API key as well
Uplisting keeps event subscriptions on its older key, so the connection needs that key too. With it, TravelPal subscribes itself to bookings created, updated, and removed, and to new messages. Nothing else has to be set up inside Uplisting. A wrong paste is rejected at once and costs only a retry.
Every property comes across
Uplisting publishes no archived flag on a property, so the whole account comes across. You switch off any property you do not want TravelPal to answer for. From then on, every booking gets its own guest link. The rest of the flow is on how it works.
TravelPal shows the connection at every step: connected, last update, and any error in plain words. To see the other setup steps, read what onboarding involves.
What the Uplisting connection will not do
Know the limits of Uplisting before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Uplisting's own automated messages stand the concierge down
Uplisting tells TravelPal when a message leaves your side, but it does not say who sent it. So TravelPal reads any message from your side as one of your people taking over the thread. That is the safe reading, and we keep it. An automated message from Uplisting therefore silences TravelPal on that stay. Automated messages are a switch for each booking in Uplisting. Turn them off on the stays TravelPal runs.
The booking's note field is not a place for your team
Every message channel Uplisting offers reaches the guest: SMS, email, and the Airbnb, Booking.com, and Vrbo threads. The booking has one note field, and a write to it replaces whatever was there. So TravelPal does not use it for notes. Sale notes reach your team in your own channel and by email instead. So does anything held for a person.
No availability is read and no night is blocked
TravelPal does not quote availability from your Uplisting calendar, and it never holds a night in it. A guest who asks for a night goes to your team instead.
A booking names no guest
Uplisting keeps the guest's name, email, and phone on the booking. It has no identity that follows one person from one booking to the next. Its thread search takes a guest id. No booking carries one, so that route has nothing to use. For this reason, TravelPal does not recognize a returning guest on Uplisting. Uplisting records the language of a message, not of a guest. So the reply is in the language the guest writes in.
When TravelPal's AI is not sure, it stops and asks your team instead of guessing. This rule is the same on every system: see the safety guardrails.
Uplisting integration FAQ
Do I need Uplisting's permission before connecting TravelPal?
Yes, and it is one email. Uplisting publishes no self-serve API key. Its partner desk at partner@uplisting.io registers the integration against your account. After that, you approve TravelPal yourself with a browser sign-in. Ask for the partner client ID in the same email.
Why does the Uplisting connection ask for two credentials?
Uplisting keeps event subscriptions on the account's older API key. The approval you click through does not carry them. The approval covers your properties, your bookings, your calendar, and messaging. So the connection takes the older key as well. Without it, nothing would reach TravelPal the moment a booking or a message changes. Guests would wait for the next scheduled check instead of getting an answer.
Will Uplisting's automated messages clash with TravelPal?
Yes, they will silence it. Uplisting reports an outbound message without saying who sent it. So TravelPal reads any message from your side as one of your people taking over. TravelPal then goes quiet on that stay. Uplisting has a switch for automated messages on each booking. Turning them off on the stays TravelPal runs is part of setup.
Which channels does the Uplisting connection reach?
It covers Airbnb, Booking.com, and Vrbo inside their own threads, plus email and SMS. Uplisting requires every send to name its channel, and it refuses a channel the thread has not enabled. So a guest is answered where they wrote and nowhere else. SMS is left for your team to choose, since Uplisting charges for each message.
Updated
Uplisting is a trademark of its owner. TravelPal is not affiliated with or endorsed by Uplisting.