Hospitable guest messaging, answered in the booking thread
TravelPal connects to Hospitable with a token you approve yourself, then answers each guest in the thread their booking already has, whether that booking came from Airbnb, Vrbo, Booking.com, Agoda, or Hospitable Direct. It reads your properties, your calendar, and the whole of each booking's single thread, then sells early check-in and late checkout at your prices and writes the sold time onto the reservation, on channel bookings as well as direct ones. When somebody on your team answers in the Hospitable inbox, TravelPal sees it and steps back.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Hospitable
Hospitable is run by hosts themselves, more than 24,000 of them by Hospitable's own count, from a single rental up to a full portfolio, and it is the host who approves this connection rather than an account manager.
Properties become the answer set
Names, addresses, amenities, capacity, the space overview, guest access, neighborhood notes, and your check-in and check-out times arrive from Hospitable and become what the AI answers from. House rules arrive as the switches you actually set in Hospitable, pets allowed or not and the rest, alongside any extra rules you typed in yourself, so nobody rewrites them into sentences you never wrote.
Reservations, in Hospitable's own status words
A booking reaches TravelPal when it is created and again when it changes, and a window of existing stays is imported at the start. Hospitable separates an accepted booking from a request and from a checkpoint, so a guest who has not actually booked is not set up as an arriving stay. Owner stays are flagged as owner stays in Hospitable and are treated as the owner's, which keeps a deposit request or an upgrade pitch away from the person who owns the unit.
The conversation is the reservation
A Hospitable stay has one thread, and TravelPal reads all of it, oldest message first, before it says anything. The booking reference it quotes back to a guest is the one Hospitable shows you and the channel shows them, not an internal record number.
Your own team's replies arrive too
Hospitable reports messages in both directions and labels what sent each one, which separates a person typing in the inbox from Hospitable's own scheduled messages. So when your team steps into a thread, TravelPal stands down and leaves it with them, and a scheduled arrival message does not get mistaken for a colleague.
What TravelPal writes back
Every message goes out through Hospitable, never around it, so your own inbox shows exactly what each guest was told.
Replies in the booking's own thread
There is one rail on Hospitable and the reservation picks it: the reply lands in the Airbnb, Vrbo, Booking.com, Agoda, or Hospitable Direct thread the guest wrote in. Every reply goes out as plain text, which is the only form a Hospitable send takes, so nothing ever reaches a guest with stray markup in it. Teams weighing the two can read the TravelPal and Hospitable comparison.
Sold time changes, one field at a time
A paid early check-in or late checkout is written onto the Hospitable reservation as a time, and Hospitable accepts that from a connected app on channel bookings as well as direct ones. Each field is written on its own, so a sold checkout time cannot disturb a check-in time your team set a minute earlier. This is how the upsells land in the system your cleaners read.
Calendar holds we never claim as ours
Where a sale needs a night held, TravelPal writes the hold into your Hospitable calendar. Hospitable accepts the write and applies it in the background without naming the nights it changed, so TravelPal never treats a block as its own to clear later. Your maintenance blocks stay exactly where your team put them.
Connected in four steps
The credentials are yours to create inside Hospitable. TravelPal does the rest itself.
Approve TravelPal, or make your own token
Two ways in and both are yours: approve the connection at auth.hospitable.com when we send the link, or create a Personal Access Token in your own account at my.hospitable.com/apps/api-access. There is nothing for Hospitable's team to switch on and no partner application in between.
Leave the property permission checked
The approval screen lists what TravelPal may see. The property permission is the one that matters: a reservation that arrives without its property attached cannot be matched to a unit, and a full portfolio then looks empty.
Paste the token into TravelPal
A Personal Access Token does not expire. An approved connection renews itself, and the renewal lapses after 90 days of silence, so a connection nobody has used for three months takes one more approval. TravelPal proves the token with one read of your own account before anything imports, so a wrong paste costs you nothing but a retry.
Properties and stays import
Your properties become the units TravelPal answers for, and every reservation from then on gets its own private guest link. There is nothing else to fill in inside Hospitable: its own guidance is that these notices are not set up in your account at all, so bookings and messages start arriving the moment the token 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 Hospitable connection will not do
Every property management system draws its own lines, and the ones Hospitable draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
No team-only note on a Hospitable reservation
The reservation carries a single notes box, and anything written into it replaces what was there before. TravelPal therefore does not write there at all, so your team's own notes survive. Sale notes, and anything the AI holds back for a person, reach your team channel and your email, and the notes box on the reservation stays whatever your team last typed into it.
Extra nights stay with your team
Hospitable takes check-in and checkout time changes from a connected app, and keeps date changes to reservations your team created by hand. An added night is therefore not sold through this connection: TravelPal answers the question, quotes nothing it cannot deliver, and hands the thread to your team to finish.
One rail, and it is the booking thread
Hospitable's API exposes no email or SMS route, so every guest is reached where they booked and nowhere else. If somebody stops reading the channel inbox, reaching them another way is a call your team makes, from the contact details already on the reservation.
Sends are paced to Hospitable's published ceilings
Hospitable publishes them plainly: 50 messages in any five minutes for a connected app, and two a minute on any one reservation. TravelPal queues to those numbers instead of pushing past them, which is invisible in a normal conversation and shows up as a short wait when a whole arrival day writes in at once. Reading a stay's past messages sits under the same per-reservation ceiling, so the first import of your history lands over hours rather than minutes.
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.
Hospitable integration FAQ
Do I need Hospitable's permission to connect TravelPal?
No. You approve the connection yourself at auth.hospitable.com, or create a Personal Access Token in your own account at my.hospitable.com/apps/api-access and paste it into TravelPal. There is no partner application and no approval queue at Hospitable between you and a working connection.
Will TravelPal reply over my team in the Hospitable inbox?
No. Hospitable reports messages in both directions and labels what sent each one, so the moment a person on your team answers a thread, TravelPal stands down and leaves it with them. It also tells your team's typing apart from Hospitable's own scheduled messages, so a scheduled arrival message does not silence the concierge for no reason.
Can TravelPal add a night to a Hospitable booking?
No. Hospitable keeps date changes from a connected app to reservations your team created by hand, so an added night is a person's job. Paid early check-in and late checkout do write back as times on the reservation, on channel bookings and direct bookings alike, and your cleaning schedule reads the real time.
Which channels does the Hospitable connection cover?
Whatever you run through Hospitable: Airbnb, Vrbo, Booking.com, Agoda, calendars synced by iCal, and Hospitable Direct. Each guest is answered in the thread their own booking already has, because that is the single route Hospitable's API offers, and your team sees every word of it in the Hospitable inbox.
Updated