D3X VS RUNNR.AI
D3x vs Runnr.ai: orchestration depth vs a virtual concierge.
Runnr.ai is a hospitality guest-communication platform: WhatsApp-first virtual concierge, unified inbox, upsells, and PMS-connected request handling for hotels and holiday parks. D3x is an AI orchestration layer: the same agent runtime across messaging, email, and voice, with codified hotel logic, group governance, and production proof at European hotel-group scale.
WHERE WE SIT
AI that executes, not a wrapper that replies.
Left to right: does the AI only answer, or does it complete work in your PMS and ops stack? Bottom to top: bolt-on AI on a legacy product, or an AI-native runtime built for hotels.
Peers shown for context · positions are qualitative, not scored metrics
D3x in production
D3x production figures, not category averages.
- Years building hotel AI
- 4+
- People on the product
- 20
- Autonomous resolution
- 60–70%
- Messages / month
- 250K+
- AI CSAT (vs 4.62 human)
- 4.58
- Live integrations
- 25+
Founders spent 10 years as hotel operators, then built and scaled a PMS software company through exit, before founding D3x. Today D3x runs with large enterprise hotel groups across Europe.
What execution means
- Live PMS read & write-back
- Housekeeping / ops tickets created
- Human handoff with full context
THE VERDICT
The short version
If you want a strong WhatsApp / SMS virtual concierge with proactive messaging, upsells, and a unified guest inbox, especially for independents, holiday parks, and mid-size portfolios: Runnr.ai is a credible specialist. If you need AI that resolves the hard operational long tail across a hotel group, agentic email, voice on the same Skills Engine, full decision audit with rationale, human-in-the-loop policies, and 60–70% autonomous resolution already proven at 250K+ messages a month: D3x is built for that depth.
SKILLS VS FAQ AUTOMATION
Most “80% automation” is FAQ answers, not resolved work.
Vendors often count answered questions as automation. Guests still need towels, invoice fixes, reservation changes, and maintenance, and those threads land in the operator inbox unresolved. D3x Skills execute in your PMS and ops stack. That is the difference between deflection and resolution.
D3x
13/15 Resolves in stack
- 13 resolve in stack
- 1 FAQ-only
- 1 on roadmap
Runnr.ai
4/15 Resolves in stack
- 4 resolve in stack
- 6 route to inbox
- 2 FAQ-only
- 3 not offered
What automation claims usually count
| Skill | D3x | Runnr.ai |
|---|---|---|
| Answer FAQs & property knowledge | FAQ / answer only | FAQ / answer only |
| Make a new booking | Resolves in stack | Resolves in stack |
| Live rates & availability | Resolves in stack | Resolves in stack |
| Upsell written to the reservation | Resolves in stack | Resolves in stack |
| Online / digital check-in | Resolves in stack | Resolves in stack |
Operational work that empties (or overflows) the inbox
| Skill | D3x | Runnr.ai |
|---|---|---|
| Reservation changes in the PMS | Coming Q4 2026 | Routes to inbox |
| Housekeeping task in ops systems | Resolves in stack | Routes to inbox |
| Maintenance request in ops systems | Resolves in stack | Routes to inbox |
| Invoice request, correct & reissue | Resolves in stack | Routes to inbox |
| Lost & found (structured) | Resolves in stack | Not offered |
| Ticketing pushed to CRM and prioritised | Resolves in stack | Routes to inbox |
| Restaurant integration / table reservation | Resolves in stack | Routes to inbox |
| Spa reservation | Resolves in stack | Not offered |
| Agentic email that resolves threads | Resolves in stack | Not offered |
| Voice agent on the same skills | Resolves in stack | FAQ / answer only |
Coverage reflects publicly documented capabilities and typical production behaviour. Always verify write-backs on your own PMS and housekeeping stack in a paid pilot.
SIDE BY SIDE
Feature by feature
Based on public positioning and D3x production capability. We keep this honest, if something changes, we update it.
| Capability | D3x | Runnr.ai |
|---|---|---|
| Core architecture | AI orchestration layer above your hotel stack | AI virtual concierge + unified guest inbox |
| Primary focus | End-to-end resolution across the whole stay and ops stack | Guest messaging, proactive journey, upsells |
| Executes actions in PMS | Yes, live reads and writes, 25+ integrations | Yes: PMS-connected requests, check-in, upsells (public positioning) |
| Autonomous resolution | 60–70% in production (measured) | High automation claimed; not published as measured group CSAT |
| Channels | WhatsApp (official partner), OTA inbox, web chat, SMS, email, social, voice | WhatsApp, SMS, OTA inboxes, webchat, email, phone |
| Agentic email workflows | Yes: FAQs, groups, invoices, booking modifications | Inbox coverage; not positioned as agentic email ops |
| Housekeeping & ops ticketing | Yes: Optii, Flexkeeping, Alkimii, SnapShot, and more | Housekeeping request creation (selected tools) |
| Voice AI | Yes, natural-voice phone agent on the same Skills Engine | Phone channel supported; not the same orchestration depth |
| Skills Engine (codified hotel logic) | Yes, hundreds of PMS/OTA quirks codified | Property knowledge + automation flows |
| MCP server (control from any LLM) | Included for every customer | Not offered |
| Human-in-the-loop & audit logs | Full decision logs with agent rationale | Inbox / conversation history |
| Advanced enterprise reporting | Portfolio AI CSAT, resolution rates, channel and property views | Inbox and journey analytics |
| Role-based access control & enterprise security | RBAC, enterprise SSO, scoped agent permissions; SOC 2 Type II in progress | Team inbox roles |
| Pricing transparency | From €5 per room / month, public | Quote-based (unit tiers); WhatsApp usage separate |
| Proof at group scale | 250K+ messages/month, 4.58 AI CSAT, 100% logo retention | 1,000+ properties; strong NL / holiday-park footprint |
Choose D3x if you need
- One orchestration layer across messaging, OTA inbox, agentic email, and voice, not a concierge bolted on
- 60–70% autonomous resolution with published production CSAT, not only automation anecdotes
- Group governance: escalation policies, VIP rules, audit logs with agent rationale your DPO can review
- Hundreds of codified hotel edge cases (Skills Engine) your ops team should not rediscover
- Public per-room pricing and an MCP server so engineering can extend without rebuilding the platform
Runnr.ai may fit if
- Your priority is WhatsApp-first guest messaging, proactive journey messages, and upsells
- You operate hotels, aparthotels, or holiday parks and want a virtual concierge with a unified inbox
- You are optimising front-desk deflection and ancillary revenue more than deep multi-channel ops automation
IN PRODUCTION
Production proof, not promises
D3x handles 250K+ guest messages a month with a 4.58/5 AI CSAT and 100% logo retention. At Staycity Group, 75% of web chat and WhatsApp conversations are handled by AI, connected to live reservation data, not a script.
FAQ
D3x vs Runnr.ai: common questions
Runnr.ai is a hospitality virtual-concierge platform focused on guest messaging, proactive journey outreach, upsells, and PMS-connected request handling. D3x is an AI orchestration layer: agents that resolve requests end to end across messaging, email, and voice, with a Skills Engine of codified hotel logic, human-in-the-loop policies, and full decision audit. Both can message guests; D3x is built for group-scale operational resolution and governance.
SEE IT LIVE
Compare D3x and Runnr.ai on your own stack.
30 minutes with the founder, your properties, your channels, and what phase-1 looks like.