AI guest messaging for Bedloop agencies
When a guest writes in Bedloop, your team answers there, not TravelPal. It connects with an API user, a login for other software, that you create yourself.
One Bedloop connection works in both directions. Each item is explained below.
What TravelPal reads from Bedloop
Rental agencies in Spain and Latin America use Bedloop, and the company counts 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. It keeps the door opening code and key numbers on the booking. TravelPal drops those fields before the concierge sees anything. So it cannot read one out to the wrong guest. It answers from the name, address, capacity, floor area, your check-in and check-out times, and photos.
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 has no definition in the table. So TravelPal raises a booking in that state with your team. It does not guess the nearest state.
Where a booking came from, in your own words
Bedloop keeps the list of booking origins inside your account, and your team can name the rows. So the source on a booking is whatever you called it. TravelPal reads those names. It treats Airbnb, Booking.com, Expedia and Vrbo as those channels. It leaves a name it does not know without a label. It does not file it under the nearest one.
The customer record, reused across stays
A Bedloop guest has a customer record that carries from one booking to the next. Bedloop's customer types also include one for a recurring guest. So a returning guest arrives already linked to their history. The concierge knows from 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.
The chat is filed under the booking number
Bedloop files a conversation under the booking, with the messages inside it. It publishes no way to list chats or to find one by guest. So TravelPal goes through your bookings to reach them. It puts each chat in order, 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 and nightly prices stay in Bedloop
TravelPal does not read availability or nightly prices from Bedloop. Bedloop names no currency anywhere in its API. Paid extras are priced from your own price list, the way upsells work everywhere else.
What TravelPal writes back to Bedloop
Here is what TravelPal sends through Bedloop today, and what it leaves to your team.
One way to send, and it is the guest's own chat
Bedloop has a single send, and it posts into the chat already attached to the booking. The API has no email, SMS or WhatsApp send. So every message sent through Bedloop lands in the one place your team already reads. There is no other channel to check.
Your team answers each Bedloop guest chat
TravelPal cannot tell which Bedloop lines a guest wrote, so it sends no alert. Your team answers in Bedloop.
The guest opens the conversation
Bedloop documents a reply and no way to start a chat. So the first message comes from the guest. Every booking still gets its own private guest link. Your team can put that link in the check-in message you already send: see how that works.
A paid extra goes to your team, not the booking
The guest pays your price on their own link. The sale is emailed to your team. It carries the stay, the unit and the amount. TravelPal does not edit Bedloop's booking record.
Connected in four steps
You create the access details yourself, inside Bedloop. TravelPal does the rest itself.
Create the API user in Bedloop
In the Bedloop portal, go to Settings, then API, then Create User. Bedloop shows the password once, so copy it right then. If you lose it, create another API user. There is no partner form and no approval wait.
Confirm which host your account answers on
Bedloop's public reference documents its test host only. So TravelPal asks you for your host and does not assume one. A short message to Bedloop confirms the host your live account uses. A wrong host would read a test account and not your properties. That is why the host is a field on the connect screen and not a default.
Paste the host, username and password
Bedloop trades that password for a token each time TravelPal connects. A mistyped password costs one refused connection. You do not need to switch anything else on inside Bedloop. That one API user covers the listing reads and the send.
Confirm the timezone with your units
A Bedloop listing has no timezone. So your team sets it for each property during setup. TravelPal does not guess one from an address. The timezone drives quiet hours, scheduled messages and check-in timing. Your units then import in the background, with their photos. Bedloop keeps photos as records of their own and not on the listing.
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 Bedloop connection will not do
Know the limits of Bedloop before you turn anything on. Every property management system has its own limits. TravelPal works inside them, not around them.
Nothing TravelPal does edits the booking
Bedloop's booking update asks for a status along with whatever you change. It publishes two values for that status, but a booking can come back in eight. So moving a guest's arrival time could also confirm a booking that was only provisional. For that reason TravelPal writes no times and no dates at all. The booking's notes box is one field that overwrites and is not a log. So TravelPal puts nothing of its own there, and what your team typed stays. Sale notes, and anything held for a person, go to your team as a message and an email.
No calendar blocks
A block created through Bedloop comes back with no identifier. So there would be no reliable way to find it again and free the night. TravelPal does not create one.
Bedloop does not push, so TravelPal sweeps
Bedloop publishes no push events. So TravelPal picks up new bookings, changed bookings and new guest messages on a sweep. A sweep is a check that TravelPal repeats. It does not see them the second they arrive. Bedloop's change feed is dated by the day, so each sweep reads that whole day again. Nothing is lost, but it arrives on a schedule and not instantly.
Who wrote an older message is not stated
Bedloop marks the direction of a message with one field that its reference never defines. So TravelPal will not guess which side of the chat an old message came from. It does not file your team's past words as property facts. Bedloop also does not tell TravelPal when your team replies. So TravelPal cannot see a reply your team already wrote. It does not answer in Bedloop, because it never interrupts your team.
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.
Bedloop integration FAQ
Do I need Bedloop's permission to connect TravelPal?
No. You create the API user yourself in the Bedloop portal. Go to Settings, then API, then Create User. Then you paste it into TravelPal. One thing is worth a short message to Bedloop: which host your live account uses. Their public reference documents only the test host. TravelPal asks for the host and does not assume it.
Can TravelPal message a Bedloop guest before the guest writes?
Not through Bedloop. Bedloop's send posts into a chat that already exists, and it documents no way to open one. So TravelPal never starts a Bedloop chat. Every booking still gets its own private guest link. Your team can put that link in the check-in message you already send. That is how a guest reaches the concierge first.
Will TravelPal change my Bedloop bookings?
No. It never edits a Bedloop booking. Bedloop's booking update asks for a status along with any change and publishes two values for it. 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. TravelPal does not offer a paid late checkout on a booking that came from Bedloop.
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 use?
TravelPal connects to 33 property management systems. Below are the systems closest to Bedloop in how widely they are used.
Updated
Bedloop is a trademark of its owner. TravelPal is not affiliated with or endorsed by Bedloop.