AI guest messaging for Beds24
TravelPal answers Beds24 guests in their Airbnb, Booking.com, Vrbo or Expedia thread. Direct guests get a private link.
One Beds24 connection works in both directions. Each item is explained below.
What TravelPal reads from Beds24
Beds24 is used in more than 150 countries, by the company's own count. One account often holds buildings in several of them. They range from whole homes to hostel dorms and hotel room classes.
Room types become your properties
In Beds24, a property holds room types. Each room type becomes one property in TravelPal. TravelPal names it for both the property and the room type. So a forty-room site does not show up as forty listings called Double Room. The address, the location description, your directions and the house rules come across. So do the check-in window and the check-out time. So do the minimum and maximum stay and how many people it sleeps. The AI answers from all of it. Beds24 does not send property or room pictures over its API. So every image in your guidebook is one you add.
Bookings, including the ones nobody has acknowledged
Beds24 marks a live booking that the host has not yet acknowledged as new. It returns these in the same list as the confirmed ones. TravelPal treats both as a guest who is arriving. It treats a request or an inquiry as still pending. A booking with the black status is how a Beds24 host blocks dates. It is not a guest. TravelPal leaves it alone: no greeting, no guest link and no messages.
The booking is the thread
Beds24 keeps no separate conversation record. Messages are stored under the booking id. The notes your team left sit in the same list beside them. TravelPal reads all of it before it answers. So when it joins a stay halfway, it sees your own notes and not just the newest line.
Language, currency and what the guest has been charged
A Beds24 booking carries the guest's language as a two-letter code. The concierge uses it from the first message, so it does not open in English. Currency is kept on the property and not on the booking. TravelPal reads the currency from the property that owns the room. So it never quotes a price in the wrong currency. Invoice lines arrive typed as a charge or a payment. The ones a person typed in by hand are marked as such.
What TravelPal writes back to Beds24
Every message goes out through Beds24, never around it. So your Beds24 inbox shows exactly what each guest was told.
Beds24 hands the answer to the channel
A reply goes to Beds24, and Beds24 passes it to the channel that owns the booking. An Airbnb guest reads it inside Airbnb, and a Booking.com guest reads it inside Booking.com. Vrbo and Expedia guests read it inside Vrbo and Expedia. The booking in Beds24 then shows the same thread the guest saw. That is the route the reply took.
Notes your team sees and your guest does not
Beds24 has a note source that is never delivered to the guest, and TravelPal writes to it. On a channel booking, what the guest bought goes onto the booking itself. So does any question the AI holds for a person. Your team finds it where they already work, not in a tool they must remember to open. Beds24's message route does not cover direct bookings. For those, the same note reaches your team inside TravelPal. A note stays as written once it is saved.
Arrival time, and nights added to a direct booking
A paid early check-in writes the arrival time onto the Beds24 booking. An added night changes the booking dates for real. Beds24 checks availability when a booking is made, not when it is changed. So TravelPal reads those nights first, and it refuses the write if it cannot read them. TravelPal moves only a booking that Beds24 marks as direct. It leaves a channel booking as it is. It also leaves alone a booking typed in by hand with the channel blank. A blank channel does not prove a direct booking. TravelPal reads your Beds24 calendar and puts nothing into it. Only a booking's own dates change your availability.
One of the ten custom fields, the one you pick
Every Beds24 booking has custom1 through custom10, with a thousand characters each. TravelPal sells paid extras at your own prices. It writes the guest link or the sold paid extra into the field you choose. It refuses any other field name and does not send it. Beds24 accepts an unknown key without an error and then drops it.
Connected in four steps
You create the access details yourself, inside Beds24. TravelPal does the rest itself.
Make an invite code in Beds24
Go to Settings, then Marketplace, then API. Create an invite code with the bookings, bookings-personal, inventory and properties scopes. Pick all four now. The scopes are fixed when the code is made, and adding one later means making a second code. Nobody at Beds24 has to approve you before you reach this screen.
Trade the code for the token TravelPal keeps
The invite code lasts 24 hours. You trade it once for a refresh token. The refresh token is the credential. The code is not, and neither is the 24-hour access token that comes back beside it. Setup does the exchange with you. If Beds24 will not answer to the token, it is rejected while you are still on the call. Beds24 keeps a refresh token alive while it is in use. It retires one left unused for 30 days. So a working connection never needs a second code.
Add the header on every property
Go to Settings, then Properties, then Access, then Booking webhooks. Paste the custom header TravelPal gives you. A booking alert that reaches us then carries your own secret. One that does not is turned away. Beds24 keeps this setting per property. A property you add next month needs the same line.
Room types import, then time zones
Each room type arrives as its own property. Every booking on it then opens its own private guest link. Next, set the time zone for each property inside TravelPal. Beds24 keeps one time zone on the account and none on a property. One account can hold buildings in several countries.
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 Beds24 connection will not do
Know the limits of Beds24 before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Inside Beds24, only channel guests can be reached
Beds24's message send works only on a booking that came from an online travel agent. Beds24 has no email or SMS send to fall back on. So Airbnb, Booking.com, Vrbo and Expedia guests are answered in their thread. A direct guest is answered on the private guest link that comes with their booking, never inside Beds24. Dates pulled in from an iCal feed have no guest and no thread behind them. TravelPal will not try to send a message for those dates.
A late checkout cannot be written onto the booking
A Beds24 booking has a field for the arrival time and none for departure. A paid early check-in updates the booking itself. A paid late checkout reaches your team and your cleaning schedule through TravelPal. The booking in Beds24 keeps the checkout time it was made with.
New messages are found by looking, not by being told
Beds24's booking alert fires when a booking is made. It also fires on a big change, such as the status, the arrival, the departure or the room. A new guest message is not one of those events. Beds24 also counts API use in credits over a five minute window. The count covers your whole account and is shared with every other tool you have connected. So TravelPal checks for new messages on a paced schedule that leaves those other tools room to work.
A listing here is a room type, which can hold more than one unit
If a room type is one place to sleep, a TravelPal property is the unit the guest booked. Some room types cover several identical units, such as a dorm bed or a hotel room class. Those stays share one record. Beds24 does not name the single units over its API. Anything that assumes one party in a unit at a time needs a person to check it there.
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.
Beds24 integration FAQ
Can I make the Beds24 invite code myself, or does someone have to approve it?
You make it yourself, and nobody has to approve it. Go to Settings, Marketplace, API, and put the bookings, bookings-personal, inventory and properties scopes on the code. You trade it once for a refresh token and paste that token into TravelPal. The Marketplace organization name on the connect screen is only for Beds24 integration partners. It stays blank on a normal account.
How does TravelPal reach my direct guests on Beds24?
On their own guest link, not in Beds24. The Beds24 message send is for bookings from an online travel agent. Beds24 has no email or SMS send. A direct guest gets a private link with their booking and talks to the concierge there. TravelPal can still act on that booking from the link. For example, it can move the dates when the guest buys an extra night.
Where do I see what the AI told a Beds24 guest?
On the booking. Every channel reply goes out through Beds24, not around it. So the thread on the booking is the record of what that guest was told. Beds24 has a note type that it never delivers to a guest. TravelPal writes there what sold and anything held for a person. Conversations on a direct booking happen on the guest link and are kept in TravelPal.
What happens to the bookings I use to block dates?
Nothing. A Beds24 host blocks dates by making a booking with the black status. Beds24 returns those in the same list as real bookings. TravelPal recognizes them and leaves them alone: no guest link, no greeting and no messages. Bookings still marked new, because nobody has acknowledged them, are treated as real arrivals. That is what they are.
Not the system you use?
TravelPal connects to 33 property management systems. Below are the systems closest to Beds24 in how widely they are used.
Updated