AI guest messaging for Bedloop agencies
TravelPal connects to Bedloop with an API user you create in your own portal, then answers guests inside the Bedloop thread they wrote in. It reads your listings, your bookings and the status Bedloop gave each one, your customer records, and availability across every rate. Bedloop's send is a reply, so the guest starts the conversation and the concierge carries it from there.
One connection, running both ways. Every item on it is detailed below.
What TravelPal reads from Bedloop
Bedloop is the system behind rental agencies in Spain and Latin America, on a base the company puts at more than 33,000 properties.
Listings, minus the things a guest must not be told
Bedloop keeps the wifi network and password, the intercom number and the key number on the unit, and the door opening code and key numbers on the booking. Those fields are dropped before anything reaches the concierge, so there is no way for it to read one out to the wrong guest. Name, address, capacity, floor area, your check-in and check-out clock, and photos are what it answers from.
Bookings, in Bedloop's own status words
Bedloop's published table has eight states: Confirmed, Pre Booking, Provisional, On Request, Cancelled, Abandonate, No Show and Virtual. Only Confirmed starts a conversation. Pre Booking, Provisional and On Request wait. Cancelled, Abandonate and No Show stop it. Virtual sits in the table with no definition beside it, so a booking in that state is raised with your team instead of guessed into the nearest neighbor.
Where a booking came from, in your own words
Bedloop keeps the list of booking origins inside your account and lets your team name the rows, so the source on a reservation is whatever you called it. TravelPal reads those names, takes Airbnb, Booking.com, Expedia and Vrbo as the channels they are, and leaves a name it does not know unlabeled rather than filing it under the nearest one.
The customer record, reused across stays
A Bedloop guest has their own customer record that carries from one booking to the next, and Bedloop's own customer types include one for a recurring guest. So a returning guest arrives already joined to their history, and the concierge knows on the first line that this is not their first stay with you. Bedloop returns no phone number and no language on a read, so the concierge takes the language from the guest's own message and answers in the thread, never by text.
The thread hangs off the booking number
Bedloop files a conversation under the booking, with the messages nested inside it, and publishes no way to list threads or to find one by guest. TravelPal walks your bookings to reach them, and orders each thread oldest message first, because Bedloop states no order of its own. A stay that is three days into its conversation arrives with all three days attached.
Availability, agreed across every rate
Bedloop reports availability per rate plan, and one unit commonly carries several rates. TravelPal counts a night as free only when every rate that mentions it says so, because offering a night somebody already booked is the worse mistake. Nightly prices are not read: Bedloop names no currency anywhere in its API, so upsells are quoted from your own price list, the way upsells work everywhere else.
What TravelPal writes back
Every message goes out through Bedloop, never around it, so your own inbox shows exactly what each guest was told.
One rail, and it is the guest's own thread
Bedloop has a single send, and it posts into the thread already attached to the booking. There is no email, SMS or WhatsApp send in the API, so every answer lands in the one place your team already reads and there is no side channel to check.
Only a thread Bedloop proves is the guest's
TravelPal replies only where Bedloop marks the thread as belonging to that reservation and names the customer on it. A booking can carry more than one thread, and Bedloop documents no order for them, so anything TravelPal cannot prove is the guest's is left for your team rather than answered into on a guess.
The guest opens the conversation
Bedloop documents a reply and no way to start a thread, so the first message belongs to the guest. Every reservation still gets its own private guest link, and your team can put that link in the check-in message you already send: see how that works.
A sold upgrade reaches your team, not the booking
The guest pays at your price on their own link, and the sale goes to your team channel and by email with the stay, the unit and the amount on it. Bedloop's booking record is not edited, so the late checkout your cleaners see is the one your team enters.
Connected in four steps
The credentials are yours to create inside Bedloop. TravelPal does the rest itself.
Create the API user in Bedloop
Bedloop portal, then Settings, then API, then Create User. Bedloop shows the password once, so copy it there and then; if it goes missing, create another API user. There is no partner form and no approval queue in front of you.
Confirm which host your account answers on
Bedloop's public reference documents its test host only, so TravelPal asks you for your host rather than assuming one. One short message to Bedloop confirms the host your live account is served from. A wrong host would read a test account instead of your portfolio, which is exactly why it is a field on the connect screen and not a default.
Paste the host, username and password
Bedloop trades that password for a token every time TravelPal connects and publishes no daily budget on those tokens, so a mistyped password costs one refused connection and nothing else. There is nothing further to switch on inside Bedloop: that one API user carries the listing reads, the availability reads and the send.
Confirm the timezone with your units
A Bedloop listing carries no timezone, so your team sets it per property during onboarding rather than TravelPal inferring one from an address. It drives quiet hours, scheduled messages and check-in timing. Your units then import in the background, with the photos Bedloop keeps as records of their own rather than on the listing itself.
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 Bedloop connection will not do
Every property management system draws its own lines, and the ones Bedloop draws are worth knowing before you switch anything on. TravelPal works inside them rather than around them.
Nothing TravelPal does edits the booking
Bedloop's booking update asks for a status alongside whatever you are changing and publishes two values for that status, while a booking can come back in eight. Moving a guest's arrival time could therefore also confirm a booking that was only provisional, so TravelPal writes no times and no dates at all. The booking's notes box is a single field that overwrites rather than a log, so nothing of ours is parked there and what your team typed stays; sale notes and anything held for a person reach your team channel and your email instead.
No calendar blocks
A block created through Bedloop comes back without an identifier, so there would be no dependable way to find it again and release the night. TravelPal does not create one. Where a sale needs a night held, your team holds it in Bedloop and the concierge sells against what the calendar then says.
Bedloop does not push, so TravelPal sweeps
Bedloop publishes no push events, so new bookings, changed bookings and new guest messages are picked up on a sweep rather than the second they land, and its change feed is dated by the day, so each sweep re-reads that whole day. Nothing is lost, but it arrives on a cadence rather than instantly.
Who wrote an older message is not stated
Bedloop marks a message's direction with a single field its reference never defines, so TravelPal will not guess which side of the thread an old message came from. It does not file your team's past words as property facts, and it does not fall silent because a colleague happened to type. A thread reaches a person because your rules and your quiet hours say so, which you set yourself, and never because that one field was read the wrong way round.
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.
Bedloop integration FAQ
Do I need Bedloop's permission to connect TravelPal?
No. You create the API user yourself in the Bedloop portal, under Settings and then API and then Create User, and paste it into TravelPal. The one thing worth a short message to Bedloop is which host your production account is served from, because their public reference documents only the test host and TravelPal asks for the host rather than assuming it.
Can TravelPal message a Bedloop guest before the guest writes?
Not through Bedloop. Bedloop's send posts into a thread that already exists and documents no way to open one, so the concierge replies rather than knocks. Every reservation still gets its own private guest link, and your team can put that link in the check-in message you already send, which is how a guest reaches the concierge first.
Will TravelPal change my Bedloop bookings?
No. It writes guest replies and nothing else. Bedloop's booking update asks for a status alongside any change and publishes two values for it, while a booking can come back in eight, so a write meant only to move an arrival time could confirm a booking that was still provisional. A sold late checkout goes to your team to apply, with what the guest paid alongside it.
How are upsells priced if Bedloop shows no currency?
Your prices live in TravelPal and the guest pays there. Bedloop names no currency anywhere in its API and its booking totals come back as plain numbers, so TravelPal never restates a fare it cannot read. What it reports is what was sold, at the price you set.
Not the system you run?
TravelPal connects to 33 property management systems. These are the ones nearest Bedloop in how widely they are used.
Updated