Generic AI
Stops at the answer.
Output
Replies to guest
- Cannot match reservation
- Cannot create ticket
- Cannot escalate VIP
PLATFORM
D3x sits above your fragmented hotel stack. Agents resolve guest requests, execute against PMS and operations systems, and run on every channel — with codified hospitality logic underneath.
100K+
messages/month across the platform
4.58
AI CSAT vs 4.62 human, 20K guest surveys
3 weeks
typical implementation from API access
D3x
Channels
Guest reaches your property on any channel
Inbound
Guest message received
WhatsApp · room 512
“Hi, I need extra towels in room 512 please.”
D3X Agent Runtime
Agent Core
Reasoning → Routing → Execution → Guardrails
Context & Memory
Policies & Guardrails
Observability
Tracing · Metrics · Logs · Alerts
Fetch
Retrieve context from systems
PMS · Mews
reservation.find({ room: 512 })→ guest: John Smith→ arrival: 2025-05-20
Context retrieved
Integration Fabric
API / Webhook — PMS, ops, messaging, and helpdesk
PMS
Housekeeping & Operations
Messaging & Channels
CRM & Guest Experience
Helpdesk
Table Management & Other
Action
Execute actions across systems
Housekeeping · Optii
housekeeping.ticket.create({room: 512, type: 'extra_towels'}) → HSK-88421
Action executed
Reply
Respond on guest channel
“Hi John, we've sent extra towels to room 512. Anything else? — Your stay team”
Reply sent
Full Context & Decision Logs
Every step logged with reasoning, inputs, outputs and outcomes.
Self-Learning Knowledge Base
Property knowledge self-learns and self-heals from conversations, corrections, and live stack data.
Feature Learning Loop
Resolved interactions feed back into skills, policies, and routing — the platform improves with every cycle.
Human-in-the-Loop
Auto or review depending on confidence, channel and policy.
Audit & Compliance
Immutable logs, data retention policies and access controls.
Confidence Scoring
Every action carries a confidence score; sub-threshold paths escalate or queue for human review.
LAYER 01
Skills Engine
Booking.com _1 suffix matched · housekeeping ticket created · audit logged
LAYER 02
Agent Runtime
Intent classified · rules applied · integration called · outcome logged
LAYER 03
Channel Agents
WhatsApp intent parsed · PMS fetch · action executed · guest reply sent
LAYER 04
Integration Fabric
reservation.find() · ticket.create() · CRM update · channel reply
THE PROBLEM
PMS holds inventory. Housekeeping holds tasks. CRM holds guest data. Channels hold conversations. Each system works in isolation — guest intent gets lost between them.
01
PMS · inventory
02
Housekeeping · tasks
03
CRM · guest data
04
Channels · conversations
Generic AI can reply. It cannot route work across this patchwork. D3x sits as the orchestration layer above it — one runtime, one audit trail, live integrations.
D3x sits as the orchestration layer above this patchwork.
HOW IT WORKS
LAYER 01
Codified hospitality domain logic — reservation matching, VIP escalation, brand voice, and hundreds of operational edge cases.
Booking.com _1 suffix matched · housekeeping ticket created · audit logged
LAYER 02
The orchestration core — reasoning, routing, policy enforcement, and execution with full audit trails on every guest action.
Intent classified · rules applied · integration called · outcome logged
LAYER 03
Messaging, voice, and email — each configured with guardrails, escalation policy, and human-in-the-loop where it matters.
WhatsApp intent parsed · PMS fetch · action executed · guest reply sent
LAYER 04
25+ live integrations across PMS, housekeeping, CRM, OTA, and messaging. REST and webhook-driven with per-integration observability.
reservation.find() · ticket.create() · CRM update · channel reply
SKILLS ENGINE
When a Booking.com reservation enters your PMS through the channel manager, the reservation ID gets an _1 appended. A generic AI workflow fails to match the booking. D3x knows — and hundreds of quirks like this, codified across every PMS and channel manager.
Skill definition
> reservation_id: BK-48291_1> pms_match: SUCCESS> action: housekeeping.ticket.create
Generic AI
Stops at the answer.
Output
Replies to guest
D3x agents
Answers, then executes.
Output
Replies to guest
Hundreds of rules. Years to replicate. Compounds.
AGENT RUNTIME
A configured workflow tied to a channel, knowledge sources, integrations, guardrails, and an escalation policy — not a chatbot wrapper.
input
Input
Channel message or call
rules
Rules
Skills Engine + guardrails
integrations
Integrations
PMS · housekeeping · CRM
output
Output
Guest response + system action
audit
Audit
Decision rationale logged
INTEGRATION FABRIC
25+ integrations across PMS, housekeeping, channel managers, OTA, table management, CRM, and messaging. Average build from API access: 3 weeks.
PMS
HOUSEKEEPING
MESSAGING & CHANNELS
CRM & GUEST EXPERIENCE
HELPDESK
OPERATIONS
CONTROLS
Late checkout until 2pm for €35?
Awaiting staff review
CONTROL 01
High-stakes channels operate as co-pilot. Staff review before send. Per-channel toggle.
Riverside Hotel
Response warmth
CONTROL 02
Per-property tone, vocabulary, and response style.
CONTROL 03
Channel-by-channel rollout. Property-type guardrails.
CONTROL 04
Full conversation history with decision rationale, queryable for review.
Agent controls dashboard
Brand voice configuration
Audit log view
GDPR Compliant (today)·SOC 2 Type II (in progress, Q3 2026)·EU-hosted infrastructure·Data not used to train third-party models
IN PRODUCTION
100K+
messages/month across the platform
4.58
AI CSAT vs 4.62 human, 20K guest surveys
3 weeks
typical implementation from API access
100%
logo retention since founding
Same metrics, every quarter. Not a roadmap.
TALK TO US
A working conversation about what AI orchestration looks like at your group's scale — not a generic product tour.