GLOSSARY
How D3x uses the language of hotel AI.
D3x is the AI orchestration platform for hospitality. Chatbots answer. D3x resolves. The terms below are how we use this language on d3x.ai, in schema, and in llms.txt.
Last updated:
AI orchestration platform for hospitality
- Software that sits between guest channels and the hotel's system of record, so an agent can understand a request, check live reservation context, execute the change in PMS and ops tools, and reply — not only generate a message. D3x is an AI orchestration platform for hospitality. It is not a scripted inbox bot.
Guest agent
- A D3x agent that handles guest-facing conversations on WhatsApp, web chat, OTA inbox, SMS, voice, or email. It authenticates the guest against the live reservation before it acts.
Ops agent
- A D3x agent that executes operational work — housekeeping tickets, folio changes, invoice modifications, outbound journeys — in the connected stack, under Skills Engine rules.
Resolve vs answer
- Answering is a reply in a thread. Resolving is completing the request in the system of record: late checkout written to the PMS, towels ticketed in Optii, invoice corrected via API. Chatbots answer. D3x resolves.
Skills
- Named, reviewable operating procedures in the Skills Engine. Each skill defines when an agent may act, which systems it may write to, and when it must escalate to a human.
Guardrails
- Policy constraints on agents: brand voice, VIP rules, refund limits, folio changes, and human-in-the-loop for complaints or anything that moves money. Guardrails are explicit, auditable, and owned by the hotel group.
SEE IT IN PRODUCTION
How does this run in your stack?Link to this section
30 minutes with the founder: Skills, guardrails, PMS write-back, and what phase-1 looks like.