Hospitable guest messaging, answered in the booking thread
TravelPal answers Hospitable guests in the thread their booking already has. It sells early check-in and late checkout, and stops when your team answers in the Hospitable inbox.
One Hospitable connection works in both directions. Each item is explained below.
What TravelPal reads from Hospitable
Hosts run Hospitable themselves. Hospitable counts more than 24,000 of them, from one rental up to a full portfolio. The host approves this connection, not an account manager.
Properties become the answer set
Hospitable sends names, addresses, amenities, capacity, the space overview, guest access and neighborhood notes. It also sends your check-in and check-out times. These details become what the AI answers from. House rules come as the switches you set in Hospitable, such as pets allowed or not. Any extra rules you typed come too. 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. A window of existing stays is imported at the start. Hospitable keeps an accepted booking apart from a request and from a checkpoint. So a guest who has not booked is not set up as an arriving stay. Owner stays are marked as owner stays in Hospitable, and TravelPal treats them as the owner's. That keeps a deposit request or a paid extra offer away from the person who owns the unit.
The conversation is the reservation
A Hospitable stay has one thread. TravelPal reads all of it, oldest message first, before it says anything. The booking reference it gives a guest is the one Hospitable shows you. The channel shows the guest the same one. It is not an internal record number.
Your own team's replies arrive too
Hospitable reports messages in both directions and labels what sent each one. That tells a person typing in the inbox apart from Hospitable's own scheduled messages. When your team steps into a thread, TravelPal stops and leaves it with them. A scheduled arrival message is not mistaken for a colleague.
What TravelPal writes back to Hospitable
Every message goes out through Hospitable, never around it. So your Hospitable inbox shows exactly what each guest was told.
Replies in the booking's own thread
Hospitable has one route, and the booking picks it. The reply goes to the Airbnb, Vrbo, Booking.com, Agoda, or Hospitable Direct thread where the guest wrote. Every reply goes out as plain text, which is the only form a Hospitable send takes. So no guest sees stray formatting symbols. To compare the two products, read the TravelPal and Hospitable comparison.
Sold time changes, one field at a time
TravelPal sells early check-in and late checkout at your prices. The paid time is written onto the Hospitable reservation. Hospitable accepts this from a connected app on channel bookings and on direct bookings. Each field is written on its own. A sold checkout time cannot change 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
When a sale needs a night held, TravelPal writes the hold into your Hospitable calendar. Hospitable accepts the write and applies it in the background. It does not name the nights it changed. So TravelPal never treats a block as its own to clear later. Your maintenance blocks stay where your team put them.
Connected in four steps
You create the access details yourself, inside Hospitable. TravelPal does the rest itself.
Approve TravelPal, or make your own token
You have 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. Hospitable's team does not need to switch anything on. There is 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 cannot be matched to a unit. Then a full portfolio looks empty.
Paste the token into TravelPal
A Personal Access Token does not expire. An approved connection renews itself. The renewal lapses after 90 days of silence. A connection nobody used for three months needs one more approval. TravelPal tests the token with one read of your own account before anything imports. A wrong paste costs you only a retry.
Properties and stays import
Your properties become the units TravelPal answers for. Every reservation from then on gets its own private guest link. You fill in nothing else inside Hospitable. By Hospitable's own guidance, these notices are not set up in your account at all. So bookings and messages start arriving the moment the token 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 Hospitable connection will not do
Know the limits of Hospitable before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
No team-only note on a Hospitable reservation
The reservation has a single notes box, and anything written into it replaces what was there before. So TravelPal does not write there at all, and your team's own notes stay safe. Your team gets sale notes in a message and an email. Anything the AI holds back for a person arrives the same way. The notes box 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. It keeps date changes for reservations your team created by hand. So an added night is not sold through this connection. TravelPal answers the question and quotes nothing it cannot deliver. It then leaves the thread for your team to finish.
One route, and it is the booking thread
Hospitable's API has no email or SMS route. So every guest is reached where they booked, and nowhere else. If a guest stops reading the channel inbox, your team decides how to reach them another way. The contact details are already on the reservation.
Sends are paced to Hospitable's published limits
Hospitable publishes them: 50 messages in any five minutes for a connected app. On any one reservation, the limit is two messages a minute. TravelPal queues to those numbers and does not push past them. In a normal conversation you will not see this. You will see a short wait when a whole arrival day writes in at once. Reading a stay's past messages falls under the same per-reservation limit. So the first import of your history takes hours, not minutes.
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.
Hospitable integration FAQ
Do I need Hospitable's permission to connect TravelPal?
No. You approve the connection yourself at auth.hospitable.com. Or you 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. When a person on your team answers a thread, TravelPal stops 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 for 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. This works on channel bookings and direct bookings alike. 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. That is the only route Hospitable's API offers. Your team sees every word of it in the Hospitable inbox.
Updated