Named in Grant Thornton's 100 Ones to Watch 2026, their list of hospitality, retail and travel technology companies. See the list

Guest messaging for Cloudbeds.

We read your Cloudbeds bookings and send each guest what they need, from the welcome to the door code.

We connect to Cloudbeds through its own API, with an access key your property admin creates. Every booking, whichever channel it came from, gets a welcome in your voice, and the details your team keeps on the reservation reach the guest at the right moment.

Tell us what you run. Nothing to prepare.
What we readReservations from every channel, guest details, room assignments and status
What we write backNotes on the reservation for your team
Where your team sees itOn the reservation in Cloudbeds, and in one inbox for replies
What we need from youAn access key from your Cloudbeds admin, created in a few minutes on the call
Your Cloudbeds, connected

What we read, and what we write back.

We read

  • New and changed reservations, from every channel
  • Guest details: name, phone, email and country, so numbers are formatted properly for WhatsApp
  • The room or unit assigned, and the details your team keeps with it
  • Reservation status, checked again just before any message that depends on it
  • Transactions and the balance on the reservation

We write back

  • Notes on the reservation for your team
  • Extras added to the reservation, with Cloudbeds' own pay-by-link so payments run through the gateway you already use
The details that matter

The right door code, even after a room move.

Where your team keeps a unit's details on the booking, such as which lodge or pod it is and its door code, we read them and send them in the day-before message. If the guest is moved, we check the booking again before sending, so they get the new code.

OTA guests

Booked through an OTA, reached anyway.

OTA bookings often arrive with a relay email address. Where the phone number is real, we use it. Where it is missing, we ask for it at the first touch. A guest who holds two bookings back to back is treated as one stay, so they get one welcome.

Worth knowing

The honest detail.

Running it on your own

If you look after the property yourself, guests get answers from what you have approved, and only what needs you reaches your phone.

Rooms by any name

Lodges, pods, cottages or rooms: we read what the unit is called on the booking and use your names in every message.

Questions hotels ask

How do you connect to Cloudbeds?

Through Cloudbeds' own API, with an access key your property admin creates in the Cloudbeds settings. We walk you through it on the kick-off call, and it takes a few minutes.

Do you work with OTA bookings in Cloudbeds?

Yes. Where the phone number on an OTA booking is real, we use it. Where it is missing, we ask for it at the first touch, and a guest with back-to-back bookings is treated as one stay.

Can guests pay through Cloudbeds?

Yes. We can use Cloudbeds' own pay-by-link, so payments run through the gateway you already have, or our payment provider if you prefer.

We run lodges, pods or cottages. Does that work?

Yes. Unit names, door codes and arrival details are read from the booking and sent when the guest needs them, whatever you call your rooms.

Do guests need an app?

No. Guests reply in the channel already on their phone: WhatsApp, SMS, email or the others your guests use.

What does it cost?

It is priced on the property and billed monthly, so you only pay for what you have us build. You get two months in the operation, rolling, before any annual commitment.

Built around your hotel. Managed by us.

What are your guests trying to do that is harder than it should be?

Bring us the action, the brand, the awkward systems and the operational reality. We will shape the message for each channel and build the easiest route through them.

Show us where guests get stuck. Nothing to prepare. Sometimes the honest answer is that you do not need us.