A flight diverted an hour ago, a passenger is working down a list of properties, and your lobby phone rings at an empty chair. Cloudbeds stays the system of record for rooms, rates and folios. Siya is the layer in front of it that picks up, quotes a rate, and takes the booking.
Cloudbeds runs the reservation grid, the rates and the channel manager. It does not pick up the phone.
Most independent properties on Cloudbeds do not carry a night auditor. The desk closes around 10 p.m., the duty manager takes the cell home for genuine emergencies, and the rest rolls to voicemail until seven. The same gap opens in daylight: one person already on a call while the second line rings.
Put a number on it. Four after-hours calls a week, half of them from people ready to sleep somewhere tonight, at a $140 average room night, is roughly $560 a month walking to the property that answered on the second ring. Nobody in that group left a message.
Then there is the cost that never registers as a missed call. The guest who cannot reach you at 11 p.m. opens an app and books you anyway, through a channel that keeps 15 to 25 percent of the stay. Same head, same bed, thinner margin. The OTA commission calculator turns that habit into a year-size figure; after-hours answering covers the night shift itself.
Same property, same Cloudbeds setup, same rates. The only variable is who answers.
| Desk closed, voicemail on | Desk closed, Siya on | |
|---|---|---|
| Who answers at 2 a.m. | Nobody. Voicemail, or the line rings out. | Siya, in about one ring, 365 nights a year. |
| Caller rings while the desk is on another line | Busy tone or a long ring-out, then they dial the next property. | Answered on the spot. Overflow stops queueing behind one person. |
| Where a 2 a.m. booking ends up | Nowhere. At best a voicemail returned after the guest has booked elsewhere. | On your AskSiya bookings page: dates, room type, rate, guest name, callback number, confirmation code. |
| Cancellation called in overnight | Not taken. The room stays blocked until someone plays the message. | Taken by confirmation code, so the room is back for sale by the morning rate check. |
| OTA commission on that stay | 15 to 25 percent, if the caller books through an app instead. | None. A call you answer is a direct booking. |
| Languages on the line | Whatever the night person speaks, if there is a night person. | 100+, with automatic mid-call switching. |
Cloudbeds is the system of record in both columns. What changes is whether the call becomes a booking or a lost lead.
AskSiya has no native Cloudbeds connection. Siya does not read your Cloudbeds availability, and she does not write a reservation into it.
Here is the actual sequence. Siya answers, quotes from the room types, rates and allotment you set up in the AskSiya dashboard, takes the guest's details, and reads the confirmation code back slowly enough to write down. The booking lands on your bookings page with the transcript attached and an email hits the desk inbox. Whoever opens the terminal next enters it in Cloudbeds: under a minute of typing from an already-confirmed record, which is a different job from decoding a voicemail.
GET /bookings or subscribe to the booking.created webhook and route bookings wherever your team already works. See the API reference.It is not built, and we would rather say so than let you find out after signup. Reading availability out of Cloudbeds and writing the reservation back is on the roadmap, with no date attached. Properties that describe how their phone channel really works get to shape it, so tell us you want Cloudbeds sync and we will come back before it ships.
Taking bookings by phone needs the hotel room booking add-on, +$49/mo, free on Pro and free on every plan during early access. Starter is $29/mo for 150 minutes, Growth $99/mo for 500, Pro $199/mo for 1,000, and annual billing gives you two months free. See pricing, browse the integrations hub, or read the Mews edition of this page. Smaller house? Inns and B&Bs and the lodging overview cover the same ground.
Not today, and we are not going to imply otherwise. There is no native Cloudbeds connection: Siya does not read your Cloudbeds availability and does not write a reservation into it. She quotes from the room types, rates and allotment you configure in the AskSiya dashboard, takes the booking with a spoken confirmation code, and your desk enters it in Cloudbeds at the next natural break. Native sync is on our roadmap, and you can register interest so we build it around how your property actually runs.
Hold a small phone block. Give AskSiya an allotment of four or five rooms in the types you are happy to sell by voice, and keep the rest of the house in Cloudbeds. Two pools, no overlap, no oversell. When Cloudbeds shows a night sold out, close that date in AskSiya and Siya offers the next available night instead. Properties that only want night coverage often skip the block entirely and use Siya for questions, messages and cancellations after the desk closes.
Yes, and it is the most common way to start. Conditional call forwarding sends busy and unanswered calls to Siya while the desk is open, then every call once the desk closes. Your line, your number, no hardware. The after-hours answering page walks through both modes, and the carrier guides under call forwarding cover the dial codes.
Yes. The REST API and outbound webhooks are live on every plan. Poll GET /bookings with a ?since= timestamp, or subscribe to the booking.created webhook and receive each booking the moment the call ends. Full details, auth and retry behaviour are on the API reference.
Most independent properties sit on Growth at $99/mo for 500 minutes; Starter is $29/mo for 150 minutes and Pro is $199/mo for 1,000. Phone bookings need the hotel room booking add-on at +$49/mo, which is free on Pro and free on every plan during early access. Annual billing gives you two months free, and the 7-day trial includes 30 minutes with no card. One recovered $140 room night usually covers the month. See pricing for the full ladder.