How a guest ask moves through Obri.
A guest texts that hotel’s WhatsApp. Our team for that house takes the message in.
Obri routes the ask to the named seat that owns it. Staff mark Done or Not-done. Our team closes the guest. Staff never own the guest thread.
One shared Obri for every house. Each house’s guest book stays behind its own wall. Guest WhatsApp is live once the hotel provides the guest-facing number. Connect doors stay on the shelf until wired.
Guest to Done.
Guest
House WhatsApp.
House assistant
Our team for that house only.
Obri
One shared brain. Seats once.
Named seat
The person on shift who owns it.
Done / Not-done
Staff mark it. Our team closes the guest.
Guest flow · all houses at once
One Brain. Seats once. Motion on every House path.
Mint = ask out. Blue = Done / Not-done back. Flow lights House A · B · C into the same Obri at the same time. Guests see our team’s name only.
The product model is an ask pipe, Guest WhatsApp is working today once the hotel provides the guest-facing number. Connect doors stay on the shelf until wired.
Houses
A House is one boutique in the story — House A, House B, House C. One House gets our team for that house only. Each House keeps its own Guest Book behind its wall. House B cannot open House A’s book. All Houses share one Obri and one seat row.
Our teams
Our team is the live guest face for that House only. The House proposes the guest-facing name (for example, Luna). Guests text that House’s WhatsApp and speak with our team. Marketing and chat show our team’s name — never an internal trainer brand. Rule: 1 House = our team for that house only.
Shared Obri
Obri is one shared routing box under our teams. Asks from every house’s team enter that same Obri. Obri pings the shared named seat row drawn once under it. Do not picture three Brains or three copies of the seat row.
Isolation
Each House’s guest book, asks, room status, people, and culture stay behind that House’s wall. Tenant boundaries are a platform guarantee — one boutique’s day never leaks into another’s. Isolation is not a set of marketing module names.
Named seats — once under the Brain
Not a generic “team” blob. Ping the seat that owns the ask, then the person who’s on. Empty seat → Hold.
| Seat | Typical asks |
|---|---|
| GM | Complaints, refunds, safety, press |
| Housekeeping | Clean the room, towels, pillows, toiletries |
| Room service | In-room food / tray |
| Restaurant | Table, F&B that needs a human |
| Maintenance | Leak, AC, lock, Wi‑Fi still down |
| Front / Ops | Lost key, bags after checkout |
Home
Entry to the day — morning field, queue pulse, arrivals, rooms Clean / Not yet, what the house needs now.
House spaces
Rooms Clean / Not yet, People, Schedule, Culture, Board — spaces the floor uses while the house is open.
Roles
Permissions so GM, owner, and floor see the right slice. Same Brain; different depth.
Guest center
The ask pipe above: Guest → our team (that house only) → shared Obri → named seat → Done/Not-done → our team closes guest. Staff never own the guest thread.
System
Architecture, Data trust, Ask, Plugins shelf — chrome around the operating brain. Not vapor modules.
Connect doors
Own site / Booking.com / SevenRooms. Doors on the Connect shelf. Not drawn as live flowing pipes. Never “syncs today.”
Spine: Guest → our team (that house only) → shared Obri → named seat → Done / Not-done → our team closes guest. Seats once: GM · Housekeeping · Room service · Restaurant · Maintenance · Front / Ops. Empty seat → Hold. Connect remains shelf.