AI guest messaging for Uplisting
TravelPal answers your Uplisting guests in the thread they already wrote in, and every send names the channel it goes out on, so an Airbnb guest is answered inside Airbnb and nothing slips out on a rail that thread does not carry. It reads your properties, bookings, threads, and calendar, sells upgrades at your prices, and moves the time change onto the booking without disturbing anything else on it. Uplisting switches API access on for your account first, which is one email to your account manager.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Uplisting
Uplisting is UK-founded and says more than 2,000 property management companies run on it, mostly mixed books of Airbnb, Booking.com, Vrbo, and direct bookings priced in the property's own currency rather than in dollars.
Properties, under the name your team uses
Uplisting's nickname for a unit, the one your own staff recognize on an ops card, is the name TravelPal works from, along with the address, photos in the order you set them, amenities, capacity, and your check-in and check-out times. Each property carries its own time zone, so a checkout reminder goes out at the right local hour rather than at head office's.
Bookings, with the code the guest can quote
Uplisting pushes a booking the moment it is created, updated, or removed, and each delivery carries its own id, so one that gets retried is not counted twice. The channel comes with it, and so does that channel's own reservation code, the number already sitting in the guest's Airbnb or Booking.com email, rather than Uplisting's internal booking number. Fees, upsells, charges, and tax lines arrive with it in the currency on the booking.
The thread the guest actually used
A booking in Uplisting can carry more than one thread, one for each channel the guest has used, and TravelPal works in the one with the most recent activity. Every thread Uplisting publishes hangs off a booking, a booking request, or a guest inquiry, so there is no owner-side thread for a guest reply to land in by mistake. The history comes across oldest message first, so a stay is picked up 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 strips it before the stay reaches the AI, along with 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. More on that in how we handle safety.
What TravelPal writes back
Every message goes out through Uplisting, never around it, so your own 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, and it refuses a channel the thread has not enabled. So an Airbnb guest is answered inside Airbnb, a Booking.com guest inside Booking.com, a Vrbo guest inside Vrbo, and a guest with no channel thread by email. SMS stays a deliberate choice for your team, because Uplisting charges you for each one.
A sold time change moves one field
A late checkout or early check-in bought at your own prices moves the arrival or departure time on the Uplisting booking. Uplisting accepts a partial change, so that one field moves and everything else your team put on the booking stays exactly where it was. Cleaning reads the real time off Uplisting instead of a note somebody has to spot.
Extra nights, on the bookings Uplisting calls direct
An added night is a real date change. Uplisting requires the new dates to be free and publishes no way to force them, and TravelPal does not work around that: if the calendar says no, the guest is told no. A booking keyed in inside Uplisting is not one Uplisting calls direct, so its dates are left to your team, and channel bookings are pointed at the channel's own change flow.
Availability, one night at a time
Where a sale needs a night off the market, TravelPal names that night in the Uplisting calendar your channels already sync from. It moves availability and nothing else: the day rate, the minimum stay, and the closed-for-arrival and closed-for-departure flags on that day stay as your team set them.
Connected in four steps
Uplisting switches API access on for your account, and TravelPal does the rest itself.
Ask Uplisting to switch API access on
There is no key to create in your dashboard. Uplisting's partner desk at partner@uplisting.io registers the integration against your account, which is one email or one call to your account manager. Ask for the partner client ID in the same message if you want TravelPal stamping a custom attribute on your bookings.
Approve TravelPal from your own account
Once you are registered, you approve the access in the browser, once: your properties, your bookings, your calendar, and messaging. Include offline access in the same approval and the connection keeps itself alive rather than sending you back through that screen every hour.
Add the account's API key as well
Uplisting keeps event subscriptions on its older key, so the connection takes that one too. With it in place, TravelPal subscribes itself to bookings created, updated, and removed, and to new messages. Nothing else has to be configured inside Uplisting, and a wrong paste is rejected on the spot and costs nothing but a retry.
Every property comes across
Uplisting publishes no archived flag on a property, so the whole account arrives and you switch off anything you do not want TravelPal answering for. Every booking from then on gets a guest link of its own. The rest of the flow is on how it works.
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 Uplisting connection will not do
Every property management system draws its own lines, and the ones Uplisting draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Uplisting's own automated messages stand the concierge down
Uplisting tells TravelPal when a message leaves your side, but not who sent it. A message from your side is therefore read as one of your people taking the thread over, which is the safe reading and the one we keep, so an Uplisting automated message silences TravelPal on that stay. Automated messages are a per-booking switch in Uplisting, so they get turned 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 carries one note field, and a write to it replaces whatever was there, so TravelPal will not use it as a scratchpad. Sale notes and anything held for a person reach your team in your own channel and by email instead.
A held night is accepted first and applied second
Uplisting takes a calendar change and applies it shortly after, typically in under a minute by its own reference, so TravelPal reports the hold as accepted rather than as done and re-reads the calendar when a night has to be gone right now. Uplisting also ignores a calendar write for a date already past, so TravelPal refuses those outright rather than claiming a block that never happened.
A booking names no guest
Uplisting carries the guest's name, email, and phone on the booking, but no identity that follows a person from one booking to the next. Its thread search will take a guest id and no booking carries one, so that route has nothing to feed it, and a returning guest is matched from their own details and history instead. Language works the same way: Uplisting records the language of a message, not of a guest, so the reply follows what the guest actually writes in.
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.
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: their partner desk at partner@uplisting.io registers the integration against your account, and after that you approve TravelPal yourself from a browser sign-in. Ask for the partner client ID in the same email if you want TravelPal writing a custom attribute onto your bookings.
Why does the Uplisting connection ask for two credentials?
Because Uplisting keeps event subscriptions on the account's older API key, and 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, and guests would be waiting on the next sweep instead of on 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 and goes quiet on that stay. Automated messages switch off per booking in Uplisting, and turning them off on the stays TravelPal runs is part of onboarding.
Which channels does the Uplisting connection reach?
Airbnb, Booking.com, and Vrbo inside their own threads, plus email and SMS. Uplisting requires every send to name its channel and 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 per message.
Updated