Cloudbeds

Cloudbeds tends to be chosen by properties that sell everywhere — Booking.com, Expedia, Airbnb, their own site, sometimes a wholesaler — because the channel manager is the hard part and Cloudbeds does it well.

The consequence is a guest base arriving through many doors, each with its own messaging surface and its own expectations about response time. Keeping up means either watching several inboxes or accepting that some messages wait.

Connecting Cloudbeds collapses that into one conversation stream in ProhostAI, where the AI answers from the actual reservation and escalates what needs a person. Hostels and guesthouses running lean get the most from it, because the alternative is somebody at a desk relaying the same answers all day — and at a property selling dorm beds and private rooms through a dozen sources, that is a full-time job nobody budgeted for.

Once Cloudbeds is connected, ProhostAI works from its reservations and guest data.

Read

• Sync reservations Bookings from every channel Cloudbeds manages arrive with guest details and dates.
• Read guest conversations Threads come into one place instead of being spread across channel extranets. "Can we store bags after checkout?"

Create & update

• Answer routine questions The AI replies from the reservation and hands over anything it should not close alone.
• Create work from requests Turn a guest request into a task for the person who can actually do it.

Cloudbeds connects through its API using credentials from your Cloudbeds account.

1. In Cloudbeds, generate an API key from the API credentials section of your account.
2. Open ProhostAI and go to Settings → Connections.
3. Search for Cloudbeds, select Connect, and paste the key.
4. Wait for the first sync to finish, then check that your listings and upcoming reservations look right.

• This connection is in Early Access, covering reservations and guest messaging rather than the whole Cloudbeds feature set.
• Cloudbeds stays the system of record for rates, inventory and channel distribution.
• Properties with many room types should check that the first sync mapped them as expected before turning Autopilot on.
• Disconnecting stops the sync and leaves Cloudbeds untouched.