AI guest messaging for Beds24
TravelPal answers your Beds24 guests inside the booking they made: in the channel's own thread for Airbnb, Booking.com, Vrbo and Expedia, and on a private link for a direct booking. It runs on one Beds24 credential, the refresh token an invite code is traded for, and reads your properties and the room types inside them, your bookings, the invoice lines on those bookings, the guest's language and your availability, and it sells upgrades at your own prices. Beds24 also carries a note the guest never receives, so what sold, and anything the AI holds for a person, is parked on the booking where your team is already looking.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Beds24
Beds24 is run from more than 150 countries by the company's own count, often by hosts whose one account holds buildings in several of them, from whole-home rentals to hostel dorms and hotel room classes.
Room types become your properties
Beds24 holds a property that contains room types, and each room type becomes one property in TravelPal, named for both so a forty-room site does not arrive as forty listings called Double Room. The address, the location description, your directions, the house rules, the check-in window, the check-out time, minimum and maximum stay and how many people it sleeps all come across and become what the AI answers from. Beds24 does not return 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 the host has not yet acknowledged as new, and returns it in the same list as the confirmed ones. TravelPal treats both as a guest who is arriving, and treats a request or an inquiry as still pending. A booking with the black status is how a Beds24 host blocks dates rather than a guest, so it is left alone: no greeting, no guest link, no messages.
The booking is the thread
Beds24 keeps no separate conversation record: messages hang off the booking id, and the notes your team has left sit in that same list beside them. TravelPal reads all of it before it answers, so a stay it joins halfway through is handled with your own notes in view rather than from the newest line alone.
Language, currency and what the guest has been charged
A Beds24 booking carries the guest's language as a two-letter code, and the concierge uses it from the first message rather than opening in English. Currency sits on the property and not on the booking, so a figure is read from the property that owns the room and never quoted in the wrong one. Invoice lines arrive typed as a charge or a payment, with the ones a person keyed in by hand marked as such.
What TravelPal writes back
Every message goes out through Beds24, never around it, so your own 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, so an Airbnb guest reads it inside Airbnb, a Booking.com guest inside Booking.com, and Vrbo and Expedia guests in theirs. The booking in Beds24 then shows the same thread the guest saw, because 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 and any question the AI holds for a person goes onto the booking itself, so your team finds it where they are already working instead of in a tool they have to remember to open. Beds24's message route does not cover direct bookings, so for those the same note reaches your team inside TravelPal. A note, once written, stays as written.
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 is a real date change, and Beds24 runs its availability check when a booking is made rather than when one is changed, so TravelPal reads those nights itself first and refuses the write if it cannot read them. Only a booking Beds24 marks as direct is moved: a channel booking is left as it stands, and so is one keyed in by hand with the channel left blank, because a blank channel is not proof of a direct booking. TravelPal reads your Beds24 calendar and puts nothing into it, so nothing but a booking's own dates moves your availability.
One of the ten custom fields, the one you pick
Every Beds24 booking carries custom1 through custom10, a thousand characters each. TravelPal writes the guest link or the sold upgrade into the one you nominate, and refuses any other field name rather than sending it, because Beds24 accepts an unknown key without complaint and then drops it.
Connected in four steps
The credentials are yours to create inside Beds24. TravelPal does the rest itself.
Make an invite code in Beds24
Settings, then Marketplace, then API. Create an invite code with the bookings, bookings-personal, inventory and properties scopes, and 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 and is exchanged once, for a refresh token. That token is the credential: not the code, and not the 24-hour access token that comes back beside it. Onboarding does the exchange with you, and a token Beds24 will not answer to is rejected while you are still on the call. Beds24 keeps a refresh token alive for as long as it is in use and retires one left unused for 30 days, so a working connection never needs a second code.
Add the header on every property
Settings, then Properties, then Access, then Booking webhooks. Paste the custom header TravelPal gives you, so a booking alert that reaches us carries your own secret and one that does not is turned away. Beds24 keeps that setting per property, so a property you add next month needs the same line.
Room types import, then time zones
Each room type arrives as its own property, and every booking on it from then on opens its own private guest link. Then set the time zone per property inside TravelPal: Beds24 keeps one time zone on the account and none on a property, and one account can hold buildings in several countries.
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 Beds24 connection will not do
Every property management system draws its own lines, and the ones Beds24 draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Inside Beds24, only channel guests can be reached
Beds24's message send works on a booking that came from an online travel agent, and the system carries no email or SMS send to fall back on. So Airbnb, Booking.com, Vrbo and Expedia guests are answered in their thread, and a direct guest is answered on the private guest link their booking gets, never inside Beds24. Dates pulled in from an iCal feed carry no guest and no thread behind them at all, and TravelPal will not try to message one.
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, while 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 and when something significant changes on it, such as the status, the arrival, the departure or the room. A new guest message is not one of those events. Beds24 also meters its API in credits over a five minute window, counted across your whole account and shared with every other tool you have connected to it, so TravelPal looks 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
Where one room type is one place to sleep, a property in TravelPal is exactly the unit the guest booked. Where a room type covers several identical units, a dorm bed or a hotel room class, those stays share one record, because Beds24 does not name the individual units over its API. Anything that assumes one party in a unit at a time wants a human eye on it there.
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.
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. Settings, Marketplace, API, with 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 for Beds24 integration partners only and 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 that came from an online travel agent, and the system has no email or SMS send. A direct guest gets a private link with their booking and talks to the concierge there, and TravelPal can still act on that booking from it, including moving 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 rather than around it, so the thread on the booking is the record of what that guest was told, and the note type Beds24 never delivers to a guest is where what sold and anything held for a person is written. 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, and Beds24 returns those in the same list as real reservations. TravelPal recognizes them and leaves them alone: no guest link, no greeting, no messages. Bookings still marked new because nobody has acknowledged them yet are treated as real arrivals, because that is what they are.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest Beds24 in how widely they are used.
Updated