AI guest messaging and upsells for Lodgify
TravelPal connects to Lodgify with one API key. It answers guests in their Airbnb, Booking.com, or Vrbo thread. Guests who booked on your own Lodgify website get an email.
One Lodgify connection works in both directions. Each item is explained below.
What TravelPal reads from Lodgify
Lodgify is used by vacation rental companies. They take bookings on their own Lodgify website, and on Airbnb, Booking.com, Vrbo, and Expedia.
Your properties, with their address and map position
TravelPal reads each property's name, address, city, and map position. A property counts as closed only when Lodgify marks it not active. So a unit is never dropped because one field is empty.
Bookings announce themselves, and a sweep catches the rest
Lodgify tells TravelPal when a booking is new or changed, and when a guest writes. TravelPal does not trust the short notice alone. It reads the booking or the thread again from Lodgify, so it always works from the full record. It also re-reads bookings Lodgify has changed since the last check, which picks up anything a notice missed. A booked stay is a stay. A tentative or open one waits. A declined or canceled one closes the stay.
Every booking names where it came from
Lodgify records the source on each booking. It is Airbnb, Booking.com, Vrbo, Expedia, or your own Lodgify website. A booking you entered by hand counts as direct. That source decides where the guest is answered. It is also why a channel guest is never contacted outside the channel.
The guest, their party, and their times
TravelPal reads the guest's name, email, phone, and language from the booking. It reads how many people are coming, the arrival and departure times the guest planned, and the currency of the booking. So the first reply can go out in the guest's own language.
The whole thread, in time order
Each booking has one message thread in Lodgify. TravelPal reads all of it before it says anything, and puts it back in time order. Lodgify marks every message as from the guest or from your side. So TravelPal sees a reply your team types in Lodgify when it reads the thread.
What TravelPal writes back to Lodgify
Every message goes out through Lodgify, never around it. So your Lodgify inbox shows exactly what each guest was told.
Replies in the channel thread
A guest who booked on Airbnb, Booking.com, or Vrbo is answered in the thread they already use. Lodgify pushes the reply into that channel for us. Your own Lodgify inbox holds the same conversation.
Email for direct and Expedia guests
A booking from your own website, or one entered by hand, has no channel thread. Lodgify does not push to Expedia either. So these guests are answered by email, and only when Lodgify holds an address for them. If there is no address, TravelPal does not send. The send is recorded as failed, not as a reply the guest read.
A closed thread is refused, not ignored
Lodgify can close a thread so that it takes no more messages. TravelPal reads the thread before every send. If it is closed, the send is stopped and recorded as failed. A message is never handed to Lodgify only to be dropped.
Each send is checked after it goes
Every message TravelPal sends carries its own id. That is how TravelPal finds its own messages in the thread later. Lodgify reports how each message went out and whether it was delivered. TravelPal reads that report, and logs any message Lodgify marks as failed.
Connected in four steps
You create the access details yourself, inside Lodgify. TravelPal does the rest itself.
Copy your API key from Lodgify
In Lodgify, open Settings, then Public API. Copy the key shown there. It is the only key TravelPal needs. You do not need to ask Lodgify for anything.
Paste it into TravelPal
TravelPal checks the key right away by reading your properties. If the key is wrong, you see a refusal on the connect screen. You do not get a connection that succeeds and imports nothing.
TravelPal turns on the booking notices itself
TravelPal asks Lodgify to send it a notice when a booking changes or a guest writes. Each notice is signed with its own secret, and TravelPal checks the signature before it acts. If you disconnect, TravelPal removes these notices from your account.
Properties import, and every booking gets a guest link
Your properties become units. Every booking after that, from any source Lodgify carries, gets its own private guest link.
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 Lodgify connection will not do
Know the limits of Lodgify before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Lodgify has no note that only your team sees
Every message on a Lodgify booking can reach the guest. So TravelPal does not invent a private note there. Sale notes and anything held for a person reach your team by email and in your own channel.
What a guest buys reaches your team, not the booking
TravelPal does not change Lodgify bookings or block nights on your Lodgify calendar. A late checkout that is sold is priced, paid, and recorded on the stay. It is handed to your team with the time on it. See how upsells are sold.
A returning guest is not joined across bookings
Lodgify does not give a guest one id that stays the same from booking to booking. So TravelPal does not join a returning guest's stays through Lodgify.
Lodgify's booking number is not read to the guest
The number Lodgify files a booking under is not the confirmation code the guest got from Airbnb or Booking.com. So TravelPal never reads it to a guest as their reservation number.
Questions before a booking are left to you
A message on an enquiry, before anyone has booked, has no stay behind it. TravelPal does not answer it. It stays in your Lodgify inbox for your team.
The door code is never read
Lodgify keeps a door code on each booking. TravelPal removes it from every booking it reads, before anything else sees it. It is never stored and never logged.
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.
Lodgify integration FAQ
Does Lodgify have to switch anything on before TravelPal can connect?
No. The key is in your own Lodgify account, under Settings, then Public API. Copy it and paste it into TravelPal. That one key covers reading your bookings and sending replies. TravelPal then turns on the booking notices itself.
Which channels does the Lodgify connection cover?
The sources Lodgify carries. Guests from Airbnb, Booking.com, and Vrbo are answered in that channel's thread. Guests who booked on your own Lodgify website, or whose booking you entered by hand, are answered by email. Expedia guests are answered by email too. Email works where Lodgify holds an address for the guest.
Will my team still see what guests were told?
Yes. Every reply is posted through Lodgify, so your own Lodgify inbox holds the same conversation the guest holds. Anything meant only for your side is not in that thread, because a guest can see every message on a Lodgify booking. Sale notes and anything held for a person reach your team by email and in your own channel.
Can TravelPal change a Lodgify booking?
No. TravelPal reads Lodgify bookings and sends messages on them. It does not edit them. A late checkout that a guest buys is sold at your price and recorded on the stay. It is handed to your team with the time on it.
Updated
Lodgify is a trademark of its owner. TravelPal is not affiliated with or endorsed by Lodgify.