HotelChatBook unifies a fragmented hospitality stack into a single brain. HBSP is the protocol layer that lets any LLM talk to it — without touching the systems underneath.
Three design principles that make the hotel brain reliable, auditable, and safe to expose to any model.
One Brain, Any LLM
One HBSP server exposes the ChatBook brain to any MCP-compatible model — Claude, GPT, Gemini, or whatever your team prefers. Connect once, run everywhere.
One Canonical Model
Rooms, rates, channels, guests and revenue share one vocabulary. The fragmentation stops at the brain — the model never sees it.
Human Approval Required
AI agents propose changes. Humans approve or reject them. No rate change, restriction, or allocation executes without an explicit sign-off.
Your existing systems stay exactly where they are. ChatBook unifies them into one model; HBSP exposes that model to the AI layer. Nothing in production is modified.
Your systems, databases, and internal workflows remain untouched. No model writes to production directly.
Start with the Distribution module. Add Reservations, Guest, Operations, and F&B incrementally. No all-or-nothing migration required.
Every tool call, proposal, and approval decision is logged. Minimum 90-day retention. Built to satisfy enterprise procurement requirements.
A hotel runs on a dozen disconnected systems. HotelChatBook turns them into one operating model — and HBSP is how any LLM reaches it. Running in production on real hotels today.
The adapter is a service that calls Chatbook's existing REST API as a client. The core system is untouched. This is the compliance model for any hospitality system vendor.
The compliance model for any hospitality system vendor.
B2B path
Any llm agent calls HBSP server and returns property information to the hotelier.
B2C path
a user writes to the official communication channel (WhatsApp). The message is forwarded to the chatbook conversational assistant, which processes it and provides a response.
No installs, no passwords to share. Add the ChatBook connector in Claude and sign in with the Google account you already use.
How's occupancy looking next weekend at Hotel Amazonas?
Saturday's at 92%, with 3 Deluxe rooms still open. Want me to check competitor rates before you touch anything?
Yes — and don't change anything until I confirm it.
Understood. I'll show you exactly what would change before anything goes live.
Claude Desktop, or the Claude app — wherever you already work.
Settings → Connectors → Add custom connector.
The same account you already use for ChatBook. Your password is never shared with Claude.
Rates, availability, leads, performance — in plain language.
Each admin connects with their own account and only ever sees the hotels they manage.
HotelChatBook reads your live data instantly. Any change it proposes — a rate, a restriction, an availability block — is shown to you in plain language before it ever reaches your channels.