Loyalist × Cloudbeds

Cloudbeds stays land on the same guest record as that person's restaurant visits, so a hotel guest who eats in the dining room is one relationship rather than two. Notes move in both directions, which means a preference recorded at dinner can reach the front desk.

How it works

A hotel and its restaurant usually know different halves of the same guest. Cloudbeds reservations arrive in Loyalist with the arrival and departure, the room, and the charges posted against the stay, and they join whatever that person’s restaurant history already holds. Notes travel the other way too: a note written in Loyalist can be added to the Cloudbeds guest and removed again, so something learned over dinner can be waiting at check-in.

Key benefits

  • A stay and a dinner reservation belong to the same person. The guest in room 12 who ate in the restaurant on Tuesday is one record, so the hotel and the restaurant stop describing that guest to each other from memory.
  • Notes move in both directions. A preference recorded by the restaurant can be added to the Cloudbeds guest and removed again later, which is how something learned at dinner reaches the front desk without anyone relaying it by hand.
  • Charges posted to a stay are visible on the profile. What a guest spent during the stay comes across with the reservation, so their value is the whole visit rather than only what they signed for in the dining room.
  • Returning guests are recognised across both sides. Someone on their fourth stay who always eats in on the first night is legible as exactly that, which is the kind of thing that makes a returning guest feel known rather than processed.

Frequently asked questions

Do a hotel guest and a restaurant guest end up as one record?

Where their details line up, yes. That overlap is usually larger than either system suggests on its own, and joining it is normally the reason for connecting the two in the first place.

Can a note written in Loyalist reach the front desk?

Yes. A note can be added to the Cloudbeds guest and later removed, so a preference the restaurant learned is visible to the people checking that guest in rather than staying on the restaurant’s side.

Does spend from the stay come across?

Charges posted against the reservation arrive with it, so what a guest was worth over a stay is part of the record. For a property where the restaurant and the rooms are run as one business, that is the number that matters.

Last updated

More Integrations

See all integrations

Get started with Loyalist.

If your hospitality group is looking to supercharge your data, we’d love to chat.

Book a Demo