It is 23:40 and they want to know what time breakfast stops.
OpusDone answers the eleven questions every guest asks — breakfast, wifi, checkout, somewhere to eat — from knowledge you wrote and approved, in whatever language they typed in. Your guest is already inside the building. They are not booking anything; they want an answer at 23:40 without ringing a desk nobody is sitting at.
Reviewed


A guest will not open your website from inside your building. They will scan the card next to the kettle, because it is there and it is one movement. That card answers in Polish, Dutch or Portuguese without you doing anything, and it works at three in the morning.
An A6 card by the kettle, or a sticker inside the wardrobe door where the hangers are.
Self check-in, a late arrival, which bell to press, where the lockbox is.
One line at the bottom of the letter you already print for every guest.
The same link in the message you already send, for the guests who never look at the card.
That code opens our own OpusDone assistant — the same assistant your property would get. One property or forty — each gets its own code and its own knowledge, and nothing from one property is ever visible to a guest in another.
None of it is difficult. All of it arrives when there is nobody at the desk.
Check-in runs late, the flight lands at one, and the person who knows where the spare towels are went home at ten. A short-term rental has no desk at all — every question becomes a message to a phone somebody is trying not to look at.
Wifi. Breakfast. Checkout. Parking. Towels. Air conditioning. The bins. The beach. Late arrival. Luggage after checkout. Somewhere to eat. Every one of them has been answered before, out loud, by somebody carrying something.
You know the bakery that opens at seven and the place two streets back that is better than anything on the front. Nobody is there to say it, so the guest eats at the chain on the corner and writes that you had no local knowledge.
Breakfast, wifi, checkout, parking, air conditioning, the bins, the nearest pharmacy. Answered from the knowledge you wrote and approved — and if you have not told it something, it says so rather than guessing. A guest who writes in Dutch gets Dutch back.
Knowledge you have not marked live is never used.

The bakery that opens at seven. The restaurant that will take a table of six without notice. The beach that is not the one on the postcard. You write the list once; it gives the right part of it to the right guest, at the hour they ask.
It will not recommend a place you never mentioned, and it does not search the web.

A late checkout, an upgrade, an extra night, a complaint. The assistant takes the request, writes down what was asked and who asked it, and puts it in front of a human — with the whole conversation attached, so nobody has to ask the guest twice.
Escalation is enforced in the runtime, not left to the model to remember.

“Is breakfast still on tomorrow? We land late.” It answers with the real hours and offers to ask the team about a late one. Nobody’s phone rings.
A late breakfast is not the assistant’s to grant, so it becomes a flagged item with the conversation attached. It promises nothing on your behalf.
Not forty transcripts — the two things that needed you, and a note of what was handled on its own while the building was asleep.

Somebody comparing your own site against a booking platform has one question — is there parking, is it walkable from the station, can we bring the dog. Unanswered, they go back to the platform, and the platform takes its cut of a guest you had already won.
This is the block we wrote before the rest of the page. A hotel assistant that is vague about its limits is one that will eventually confirm a room it cannot see.
No PMS, no channel manager, no availability, no rates, no cancellations, no modifications. It does not work “alongside” one either — there is no integration, and we will not imply there is.
It will not hold a card, take a deposit, charge for a late checkout or process a refund.
It takes the request and puts it in front of a person with the conversation attached. It never says yes on your behalf.
No door codes, no smart locks, no safe combinations. If your check-in instructions include a code, you decide whether it is in the knowledge base at all.
If you have not told it about a restaurant, it says it does not know and offers to ask somebody. It does not search the web on your behalf.
It says it is an AI assistant in its first sentence, every time, and a member of your team is one message away. That is enforced in code and a client cannot edit it away.
Breakfast, wifi, checkout, parking, somewhere good to eat — answered at 23:40 in the language the guest typed, from knowledge you wrote. Late checkouts, upgrades and complaints go to a person with the conversation attached, so nothing is ever promised on your behalf.