AI agents for Cloudbeds hotels

How Visito works with Cloudbeds

Cloudbeds is your PMS. It owns your inventory, your rates, your reservations, and the channel manager that syncs you to Booking.com, Expedia, Airbnb, Hostelworld, and the rest of your distribution. It's the system of record for everything happening at your hotel.

Visito is the AI agent layer for guest messaging. It talks to your guests on WhatsApp, Instagram, Facebook Messenger, and your website chat if you use one. It uses your hotel's policies, FAQs, and live Cloudbeds data to answer them accurately and, when they're ready, to book them.

The two products solve different problems. Cloudbeds doesn't talk to guests on WhatsApp. Visito doesn't run your front desk. The integration is the bridge between them. This is the same pattern Cloudbeds describes in their own guide on AI-powered messaging for direct bookings, where Visito is their partner of choice for this category.

How the integration connects

The connection is two-way and real-time via the Cloudbeds API. No batching, no nightly sync.

What Visito reads from Cloudbeds:

• Live room availability
• Live rates and pricing rules
• Room types and inventory
• Existing reservation details for every booked guest
• Guest data tied to those reservations

That last point is worth pausing on. Cloudbeds is the system of record for reservations from every source, which means reservations synced in from Booking.com, Expedia, Airbnb, Hostelworld, and your other OTAs are all visible to Visito the same way direct bookings are. That matters for how the Support Agent and Guest Engagement Agent work, which we'll get to.

What Visito writes back to Cloudbeds:

• New reservations created by the AI Booking Agent in chat, with name, dates, room type, guest count, and payment status

The hotel side of the connection is one-click OAuth from the Visito dashboard, authorized through your Cloudbeds login. No developer needed. Visito is a certified Cloudbeds marketplace partner and the integration takes under 30 minutes to set up end to end.

The four Visito agents

Visito for Cloudbeds is four distinct agents working together. Each one owns part of the guest conversation lifecycle, all powered by the same Cloudbeds connection.

1. AI Booking Agent

The Booking Agent turns a guest message into a confirmed reservation in Cloudbeds. There are two flows, and you can run either or both depending on where you want bookings to close.

Flow A: Quote in chat, book on Cloudbeds.

The agent reads live rates and availability from Cloudbeds, replies in the conversation with options that match the guest's dates and party size, and sends a direct link to your Cloudbeds booking engine to complete the booking. Cloudbeds handles checkout and payment.

This flow is the right default for hotels with a strong Cloudbeds booking engine setup who want the booking to close on their existing engine. The guest still gets a fast, accurate quote in WhatsApp or Instagram, but the actual transaction stays on Cloudbeds where you control branding, terms, and the checkout flow.

Flow B: Visito Checkout, end-to-end in chat.

The same conversation, but the booking closes inside the chat itself. This flow is called Visito Checkout. The agent generates a unique payment link tied to the quoted reservation. The guest pays by card without leaving WhatsApp, Instagram, or Messenger. The moment payment clears, the reservation is created in Cloudbeds with all the right fields populated. Funds settle to the hotel's connected bank account on the standard processor schedule. The guest gets a confirmation on WhatsApp and email.

Flow B is the right choice when you want zero friction. The guest never has to switch apps, fill in a booking form, or re-enter their dates. The whole transaction happens in one thread.

Hotels can run both flows. A common pattern: Flow A for rooms (keep the booking engine, which is already tuned and converting), and the Upsells Agent for add-ons (more on Upsells next).

Conecta Glamping, an eco-retreat in Mexico with 140,000 Instagram followers, runs Visito on WhatsApp and Instagram with Cloudbeds underneath. They automated 95%+ of guest messages and saw a 30%+ increase in direct bookings. Real-time pricing and availability in chat meant guests could go from question to confirmed reservation without ever leaving the conversation. Paola Espinosa, co-founder, puts it this way:

2. Upsells Agent

Rooms aren't the only thing your hotel sells. Airport transfers, late checkout, breakfast, spa treatments, tours, day passes, equipment rental, parking, anything you'd normally close at the front desk or over email. The Upsells Agent handles all of it in chat.

The mechanics are the same as Visito Checkout. A guest asks about an airport transfer (or the agent offers one based on rules you've set). Visito quotes the price, sends a unique payment link, takes payment, and writes the booked add-on into the Visito dashboard. Funds settle to the hotel's bank account.

Two important details about how Upsells differs from the Booking Agent:

• No real-time inventory check. You define what services are available and at what price, and the agent sells against that. There's no live availability sync the way there is for rooms.
• Fulfillment stays with your team. The Upsells Agent captures the transaction. Your staff sees the booked add-on in the Visito dashboard with all the details (guest name, room, flight number for a transfer, preferred time, anything else you've configured) and arranges the actual service. The chat closes the sale. The team delivers it.

The operational logic worth understanding: hotels using Flow A of the Booking Agent (rooms book on the Cloudbeds engine) often still run the Upsells Agent for add-ons. The Cloudbeds booking engine doesn't sell airport transfers or spa treatments. The chat is the natural place to capture them, especially when the guest is already in conversation about their stay. A guest who's already messaging you about their reservation is a much easier yes on a transfer than the same guest after check-in.

3. Support Agent

The Support Agent answers guest questions in real time across every channel, in 100+ languages. It handles two kinds of questions, and the second one is where it pulls ahead of generic chatbots.

General hotel questions. Check-in and checkout times, breakfast hours, parking, pet policy, cancellation rules, amenities, distance to the airport, anything you've loaded into the hotel's FAQ and policies. The agent replies in the language the guest wrote in, immediately.

Booking-specific questions, answered with real reservation context. When a booked guest messages the hotel (about their check-in time, a change to their dates, what's included in their reservation, billing, anything reservation-specific), the agent recognizes the guest, pulls their reservation details from Cloudbeds, and answers with the right context. The agent knows the guest has a confirmed reservation, what dates they're booked for, what room type, what they've paid, and any notes on the booking.

Because Cloudbeds is the source of truth for every reservation regardless of source, this works the same way for direct bookings and for OTA bookings. A guest who booked on Booking.com and then messages the hotel on WhatsApp gets the same contextual answers as a guest who booked direct.

The agent escalates to a human when it should. Complaints, complex modifications, VIP requests, group bookings, anything outside its scope. You configure the handoff rules, and when an escalation happens, your team sees the full conversation, not a summary.

Blue Apple Beach, a boutique hotel and beach club on Tierra Bomba Island near Cartagena and a certified B Corp with 64,000+ Instagram followers, runs Visito on WhatsApp and Instagram with Cloudbeds underneath. They automated 70% of routine guest questions. The part-time front desk, which used to spend most of the day typing the same answers about day passes, transfers, and dining, now focuses on hosting onsite guests. Portia Hart, the founder, frames the impact this way:

4. Guest Engagement Agent

The Guest Engagement Agent handles outbound messaging on WhatsApp. Two flows:

Branded booking confirmations. Every confirmed reservation in Cloudbeds triggers a confirmation on WhatsApp from your hotel's number, formatted in your brand voice. This works for direct bookings made through Visito (Flow A or Flow B), and equally for OTA bookings that sync into Cloudbeds from Booking.com, Expedia, Airbnb, Hostelworld, and others.

The OTA piece is worth calling out. Traditionally, a guest who books through Booking.com gets a confirmation from Booking.com, not from your hotel. The first time the guest hears from you directly is at check-in. The Guest Engagement Agent gives the hotel its own branded WhatsApp moment with every guest, regardless of where they booked. That's a relationship-building opportunity that most hotels didn't have before.

Post-checkout review requests. After the guest checks out, the agent thanks them and asks for a review on Google Maps or TripAdvisor with a direct link. Higher review volume lifts your visibility on Google, on TripAdvisor, and in AI search engines like ChatGPT and Perplexity, which increasingly recommend hotels to travelers based on review signals and authority.

The unified inbox

All four agents feed into one shared inbox for your team. WhatsApp, Instagram, Facebook Messenger, and your website chat (if you have one) all land in the same view.

• Unlimited users. Front desk, GM, reservations, marketing, ownership, all on the same workspace at no additional cost.
• Full conversation history visible to your team. When an agent handoff happens, the staff member sees everything the AI already said, quoted, or promised. No starting over.
• Manual takeover any time. Team members can jump into any conversation, override the agent, or take over the thread completely. The agent steps aside and the human is in control.
• Available on web, iOS, and Android. The night auditor can monitor from a phone. The GM can check the inbox from a tablet at the pool. The reservations lead works from a desktop. The same conversations are live across all three.

The reason the inbox matters is that no AI agent gets everything right on day one, and some conversations genuinely shouldn't be automated. The unified inbox is what makes the human-and-AI split actually work: the AI handles volume, the team handles exceptions, and nothing falls through the cracks because everything is in the same place.

Who this is for, and who it isn't

The Cloudbeds and Visito stack works best for hotels that have a real messaging problem and a real direct booking opportunity. If your hotel is fielding dozens or hundreds of WhatsApp, Instagram, and Messenger messages a week, your front desk is stretched, and you're losing direct bookings to OTAs because of slow response times, this is exactly the problem the integration solves.

It's not the right fit for everyone:

• Very low-volume properties. If your hotel gets a handful of messages a week, the setup work and ongoing tuning don't pay back fast. The economics work when messaging is a real channel for your business.
• Hotels whose model is OTA-first by design. If you're happy with your direct-to-OTA mix and not trying to shift it, the AI Booking Agent's biggest benefit doesn't apply. You might still get value from the Support Agent and the Guest Engagement Agent, but the booking flow is less compelling.
• Hotels that don't take direct bookings at all. If your direct channel is closed, Visito's role narrows to FAQ answering, which usually isn't enough on its own to justify the setup.

Most independent hotels on Cloudbeds (20 to 150 rooms, active on WhatsApp and Instagram) fit the profile cleanly. If you're not sure, the trial is free and you'll have a clear answer within two weeks.

How to get started with Visito for Cloudbeds

The Visito side of setup is fast. Most hotels are connected to Cloudbeds, on WhatsApp, and ready for first conversations in under 30 minutes. Real value (the agent answering accurately, handling bookings cleanly, escalating only the right conversations) lands within two weeks, after the agent has been trained on your specific FAQs, policies, and edge cases.

The flow:

• 1. Create a Visito account.
• 2. Connect Cloudbeds with a one-click OAuth authorization. Visito starts reading your live availability, rates, and reservations immediately.
• 3. Connect WhatsApp. Two options here. If you already use the WhatsApp Business app on a phone, you can connect it to Visito via QR code in under a minute. If you want a more robust setup (multi-device, higher message volumes, the official business badge on your number), you can connect via the WhatsApp Business API. The Visito WhatsApp guide walks through both options with screenshots.
• 4. Connect Instagram and Facebook Messenger through Meta's standard auth flow, and your website chat if you have one or want to add it.
• 5. Load your hotel's FAQs, policies, and supported languages. This is the work that pays back the most. Check-in times, pet policy, breakfast hours, parking, cancellation rules, anything guests ask weekly.
• 6. Configure human-handoff rules. Decide which conversations the agent owns end to end and which always route to staff.
• 7. Choose your booking flow (Flow A, Flow B, or both) and turn on the Upsells, Support, and Guest Engagement agents as needed.
• 8. Go live. Watch the conversations for the first two weeks and tighten anywhere the agent is missing context. By week four, most hotels are at 80%+ automation on routine messages.

The plan tiers and what's included on each are on the pricing page.