The Brain — from Birth to closed ask.
HotelBrain is the operating brain beside the systems you already keep. A boutique wakes with its own face, trains our team for that house only, then runs guest asks through named seats — without staff owning the guest thread. Your boutique’s operating brain. Not another PMS.
The day path, in plain English
Three beats before the guest loop matters. Then the ask pipe runs the same way every time.
Birth & onboard
The house wakes through Birth — name, logo, colors — then onboard captures language, voice, rules, and what data our team may use. Empty wall to named Home. Awake in minutes, not a multi-week go-live project.
Our team trained (that house only)
Each boutique is a House. Each House gets our team for that house only — the guest-facing name the house proposes (for example, Luna). Our team speaks for that house only. Guests never meet an internal trainer brand. Unsigned / untrained means our team does not answer guests yet.
Guest flow — ask to close
Guest texts the house WhatsApp → our team receives it → shared HotelBrain routes to a named seat from who’s on → staff mark Done or Not-done → our team closes the guest in the same chat. Staff never own the guest thread. Empty seat → Hold (not a dump on the GM).
What staff do
Get the ping. Do the work. Mark Done / Not-done. They never reply inside the guest thread — our team owns that conversation end to end.
What the brain holds
Home, Action Queue, Needs-a-human, Rooms Clean / Not yet, Schedule, People, Culture, Board, Ask, Data trust — the day field, not another booking calendar.
The living guest pipe
One shared Brain. Asks seat once under that Brain. The guest stays with our team the whole time. Read it as blocks — not one endless sentence.
How an ask moves
- Guest texts that house’s WhatsApp — not a company-wide bot
- our team (that house only) receives the ask
- Shared HotelBrain pings the right named seat from who’s on
- Complaint → GM · clean → Housekeeping · room service → Room service
- Staff act and mark Done or Not-done — they never reply inside guest chat
- our team closes the guest in the same thread
Isolation (app truth)
On the living map, seats appear once under one Brain. In the product, pings and guest books stay per house — one boutique’s day never leaks into another’s.
- 1 House = our team for that house only
- Each House keeps its own Guest Book behind its wall
- House B cannot open House A’s book
- Connect doors stay shelf until wired — never “syncs today”
- A WhatsApp number can be stored; a live messaging pipe is not claimed as shipping product
Named seats — once under the Brain
Not a generic “team” blob. Ping the seat that owns the ask, then the person who’s on. This is not a crew org chart — seats are jobs the Brain routes to.
| Seat | Typical asks | When empty |
|---|---|---|
| GM | Complaints, refunds, safety, press | Hold — escalate only if SOP says |
| Housekeeping | Clean the room, towels, pillows, toiletries | Hold — do not invent a person |
| Room service | In-room food / tray | Hold |
| Restaurant | Table, F&B that needs a human | Hold |
| Maintenance | Leak, AC, lock, Wi‑Fi still down | Hold |
| Front / Ops | Lost key, bags after checkout | Hold |
What the floor feels day-to-day
Plain English — the same day without three parallel tools.
Morning
Open Home once. See arrivals, rooms Clean / Not yet, and queue density. Owner can glance the same field off-site.
When an ask lands
Named seat gets the ping from who’s on. Mark Done / Not-done. Our team closes the guest. Empty → Hold.
When it’s off-script
Needs-a-human keeps exceptions visible. Judgment stays with a person — not a silent auto-close.
When Ask doesn’t know
“Not in the brain yet.” Honest gaps beat invented certainty. Data trust shows what’s behind the house wall.
Live vs Shelf — honest labels
We mark what’s shipping and what isn’t. No vapor dressed as live modules.
Live · What runs the day
- Birth → named Home
- Guest messaging lane (ask → seat → Done / Not-done)
- Action Queue & Needs-a-human
- Rooms Clean / Not yet
- People, Schedule, Culture, Board, Ask, Data trust
Shelf · Ready when wired
- Connect doors: own site / Booking.com / SevenRooms
- A house WhatsApp number can be stored as the door
- No live WhatsApp pipe claim as shipping product
- No live OTA / PMS / POS / channel-manager / e-invoice sync
- Never “syncs today”
Story scenes (watch above)
- Open HotelBrain — the day brain
- Problem The house forgets
- What Brain on top of systems you keep
- Yours Your house, your data, your brain
- Guest Built around the guest
- Verbs Reads · remembers · makes sure
- Front Guest → our team (that house only) → Brain → named seat
- Staff Done / Not-done · empty → Hold
- Ask Ask & tell
- Not What it will not do
- Day One day with the brain
- Change What it changes (illustration, not a quote)
- Own Growth beyond the job
- Close Remember · make sure · deliver
What we don’t claim
- Not a PMS, channel manager, or POS
- No live OTA or WhatsApp pipe today
- Connect doors stay shelf until wired
- No House Pool · no 70+ tools pitch · no fake dollar claims
- When Ask doesn’t know: “Not in the brain yet”
- Not another booking calendar dressed as ops
- No crew org chart on the public site
Want the living diagram with seats once and isolation spelled out? Open Architecture. Want access talk? We work per key — contact us for the price on Pricing.
HotelBrain is not a PMS, channel manager, or POS. Connect doors sit on the shelf until wired — we don’t claim live sync today. Your boutique’s operating brain. The Brain for boutique hotels. Not another PMS.