AI guest messaging for Guesty
TravelPal plugs into your Guesty account with an API key and answers guest messages in the same threads your team already works in. It reads your listings, reservations, and live calendar, sells upgrades at your prices, and writes every change back onto the reservation in Guesty.
Every reply lands in Guesty, so your team sees everything.
Messages TravelPal sends go out through Guesty, never around it. Airbnb guests are answered in their Airbnb thread, everyone else through Guesty email, and a sold upsell is recorded as an internal note in the thread and written onto the reservation itself.
The flat $25 per unit per month includes this integration; connecting Guesty is never an extra charge.
Late checkout sold and paid, $60. Planned departure moved to 4:00 PM on the reservation.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Guesty
The listing content your team already maintains in Guesty becomes the corpus the AI answers from. Nothing to re-enter, nothing to keep in two places.
Listings become properties
Name, address, photos, amenities, check-in and check-out times, house rules. Listings re-sync automatically, with no manual work.
Reservations become stays
Guest name, email, phone, booking channel, party size, dates, and status. Only confirmed bookings get a guest surface; a cancellation revokes the guest's link.
Real-time webhooks
Bookings, changes, cancellations, and guest messages arrive the moment they happen, signature-verified; a retried webhook never double-processes.
The conversation itself
Guest threads mirror into TravelPal, so the AI reads the same conversation your team sees and builds a profile of the guest from what they write. Threads with property owners are never mirrored.
Live rates and availability
Prices, availability, and minimum nights come from the Guesty calendar at the moment of the quote; nothing on the quote path is cached.
Folio payments
Payments your team records on the reservation folio are read back automatically, so an upsell paid through the booking platform completes itself.
What TravelPal writes back
Everything the AI does shows up where your team already looks: the Guesty thread, the reservation, and the calendar.
Guest replies, through Guesty
Every message goes out through your Guesty account, never around it: Airbnb guests in their Airbnb thread, everyone else through Guesty email.
Sold time changes, on the reservation
A sold early check-in or late checkout moves the reservation's planned arrival or departure in Guesty, so crews see the real time. Verified live.
Extra nights as real date changes
On direct bookings, an added night is a real date change that Guesty validates against availability, so an extension can never overbook.
Calendar blocks that protect the night
When an early arrival consumes the prior night, TravelPal blocks that night so it cannot be double-sold, and releases it on undo.
Sale notes in the thread
Every confirmed upsell is recorded as an internal note on the guest's Guesty conversation, visible to your team and never to the guest.
Your templates, their guest link
TravelPal writes the reservation's id into a custom field, so your Guesty message templates can carry each guest's TravelPal link.
And when TravelPal replies on its own, you hold the gates:
Connected in four steps
The only thing you create in Guesty is the key. TravelPal does the rest itself.
Create an API key in Guesty
In Guesty: Settings, then Integrations, then API. Create an Open API key: a client ID and a secret.
Paste it into TravelPal
TravelPal validates the credentials against Guesty immediately and rejects bad ones on the spot.
The webhook registers itself
TravelPal registers its webhook in your Guesty account and fetches the signing secret on its own. Nothing else to configure in Guesty.
Listings import in the background
Properties appear without further action, and from then on every new reservation gets its guest link automatically.
The dashboard shows the connection the whole way. The rest of going live is covered in what onboarding involves.
What it will not do
The integration is deliberate about what stays out of the AI's hands.
A code is sent only when your team put that exact code on file; codes are never pulled out of listing data.
Your house manual is never overwritten by a sync and wins on any disagreement.
Guesty integration FAQ
What property management companies ask before they connect the Guesty account they already run. On something else? Every other system has its own page in the list of connections.
Does TravelPal replace the Guesty inbox?
No. Every message TravelPal sends goes out through Guesty, never around it, so your team's own inbox shows exactly what each guest was told. Guest threads mirror into TravelPal too, so both sides always read the same conversation.
What do I have to set up inside Guesty?
One thing: create an Open API key under Settings, Integrations, API. Paste the client ID and secret into TravelPal, which validates them on the spot, registers its own webhook, and fetches the signing secret itself. The listing import then starts in the background.
Can TravelPal change reservations in Guesty?
Yes, for what a guest actually bought. A sold early check-in or late checkout moves the reservation's planned arrival or departure time, and an extra night on a direct booking is a real date change that Guesty validates against availability. Date changes on channel-owned bookings are refused, and the guest is pointed to the channel's own change flow.
Which booking channels does the integration cover?
Whatever channels you run in Guesty: Airbnb, VRBO, Booking.com, and direct bookings flow in with their reservations. Airbnb guests are messaged in their Airbnb thread; everyone else is reached through Guesty email, which threads in your inbox and outlives the stay.
What happens if I disconnect?
Disconnecting disables the integration, and webhook traffic is ignored from then on. Reconnecting later is safe: TravelPal refuses to create duplicate webhook subscriptions.
Updated