METHODIK · SKILLS VS FAQ-AUTOMATISIERUNG
D3x veröffentlicht 60–70 % autonome Resolution im Gästemessaging. Diese Seite definiert genau, was das bedeutet, damit Betreiber, CIOs und Einkauf Anbieter auf demselben Scorecard vergleichen können.
Öffentliche Definition · Messaging in Produktion · Stand 2026
01 · DER SCORECARD
Anbieter zählen oft eine Wissensdatenbank-Antwort als „automatisiert“. Der Gast braucht trotzdem Handtücher, eine Rechnungskorrektur, eine Reservierungsänderung oder eine Wartung, und diese unerledigte Arbeit landet in der Operator-Inbox. D3x Skills führen in Ihrem PMS und Ops-Stack aus. Das ist der Unterschied zwischen Ableiten und Lösen.
Antwortet
Gast bekam Text. Hotel hat noch Arbeit.
Löst
Gast bekam das Ergebnis. Hotel-Stack aktualisiert.
02 · DEFINITION
Klartext: Der Gast hat etwas angefragt, der Agent hat es erledigt (oder korrekt abgelehnt), und kein Teammitglied musste den Thread übernehmen. Eine höfliche FAQ-Antwort, die die operative Anfrage offen lässt, ist keine autonome Resolution.
Formel
Autonome Resolution = Zähler ÷ Nenner
Zähler
Gäste-Messaging-Threads, die ohne Human-Takeover geschlossen wurden, weil der Agent das gewünschte Ergebnis (oder eine policy-sichere Ablehnung) unter Skills-Engine-Regeln abgeschlossen hat.
Nenner
Alle Gäste-Messaging-Threads im Automations-Scope im Messzeitraum (nach Property und Kanal), ohne Spam, Testverkehr und bewusst ausgenommene Threads.
Human-in-the-Loop-Freigabe
Wenn Policy eine Freigabe verlangt, bevor eine Aktion committed, ist der Thread nicht autonom, bis die Aktion ohne weitere Staff-Ownership der Gästekonversation abgeschlossen ist.
Co-Pilot / Entwurf fürs Personal
Entwürfe, die ein Mensch senden muss, zählen nicht. Der Mensch besitzt das Ergebnis.
Multi-Intent-Threads
Wenn ein Thread Handtücher und eine Rechnungskorrektur verlangt, müssen beide Outcomes ohne Takeover erledigt (oder korrekt abgelehnt) sein.
Warme Übergabe
Eine saubere Übergabe mit Kontext ist gutes Produktverhalten. Sie ist keine autonome Resolution für diesen Thread.
03 · BEISPIEL
In-Stay-Gast auf WhatsApp: „Kann ich Late Checkout bis 14 Uhr haben? Mein Zug fährt um 15.“ Property-Policy erlaubt Late Checkout für 35 € an Wochentagen, wenn die Belegung es zulässt.
Pfad A
Bei vielen Vendors als „automatisiert“ gezählt. Arbeit noch offen.
Pfad B
Zählt als autonome Resolution. Inbox für diese Anfrage leer.
04 · DIE 60–70 %-SPANNE
Portfolio-Typicals im Gästemessaging liegen bei 60–70 % autonomer Resolution, sobald Skills aktiv sind und After-Hours-Automation läuft. Die Spanne ist keine Garantie für jedes Haus am Tag eins. Sie spiegelt Produktionsportfolios nach dem Rollout wider.
60–70 %
#Portfolio-Typical · Messaging
Across production guest-messaging portfolios on D3x, autonomous resolution typically runs in a 60–70% range once Skills and after-hours automation are live — a portfolio typical, not a day-one SLA.
Definition →250K+
#Produktionsvolumen
D3x processes 250,000+ guest messages per month in production across live hotel groups.
Definition →4,58
#vs 4,62 Human · 90-Tage-Sample
AI-handled conversations score 4.58 CSAT versus 4.62 for human agents on a 90-day sample.
Definition →71,3 %
#Aug 2026 · 9 Hotels · 57,6 % voll enthalten
McDreams’ August 2026 case study across nine German properties cites 71.3% of all guest replies written by D3x (20,440 of 28,686), with 57.6% of conversations fully contained and a 4.8s average first reply versus 12 min 02 s for humans.
Definition →05 · BUYER-AUDIT
Nehmen Sie diesen Scorecard in jedes Demo. Wenn ein Vendor keine Produktionsbelege liefern kann, behandeln Sie „80 % Automatisierung“ als FAQ-Deflection, bis das Gegenteil bewiesen ist.
01
Writebacks sind die Grenze zwischen Resolution und Chat.
02
Wenn ja, vergleichen Sie unterschiedliche Einheiten. Fordern Sie separat eine Skills- / Stack-Resolutionsrate.
03
Portfolio-Durchschnitte verstecken FAQ-lastige Kanäle und schwache Ops-Skills.
04
Hohe Automation bei einbrechendem CSAT ist kein Gewinn.
05
Enterprise-Gruppen brauchen Decision Trails, keine Black-Box-Deflection-Stats.
06 · METRIC DEFINITIONS
Precise definitions for every figure D3x publishes. Numbers change quarterly; these definitions are meant to stay stable. Each term has a deep-linkable anchor.
Combined production scale of D3x AI agents across hostels worldwide. Named references include Nomads, Clink, Wombats, LaTroupe, Samesun, Che Hostels, Other Wonder, Smart Hostels UK, Capsule, Copenhagen Downtown, Via Amsterdam, InOut Hostel Barcelona, and Destination Hostel Portugal. Used for procurement comparisons among dedicated hostel AI agent platforms.
Cited on: Home · resources/answers/best-ai-agents-for-hostels · customers/hostels
Combined production scale of D3x AI agents across large European hospitality chains — named references include L&R Group (125 properties), Arp-Hansen (Denmark's largest chain), Dalata (58 hotels), Strand Palace (800 rooms on messaging), and Clayton Hotel Dublin Airport (650 rooms on Voice AI). Used for procurement comparisons among dedicated hotel AI agent platforms, not horizontal chatbots.
Cited on: Home · resources/answers/best-ai-agents-large-hotel-chains · resources/answers/best-ai-for-hotels · resources/docs/what-is-d3x
Share of guest messaging threads closed without human takeover because the requested outcome was completed (or correctly refused) under property policy, with PMS/ops stack updates where required. Published portfolio typical on guest messaging is a 60–70% range after Skills and after-hours automation are live — not a day-one SLA for every property.
Measurement: Autonomous resolution = (threads resolved by AI with required stack actions, no human takeover) ÷ (eligible guest messaging threads in the measurement cohort).
Excludes: FAQ-only replies that leave requested work unfinished; routing/ticket creation without completing the ask; human-in-the-loop takeovers; channels not yet running the same Skills depth.
Vs common use: Unlike many “automation rate” or “containment” claims, this does not count a knowledge-base reply as resolved unless no operational action was requested.
Cited on: Home · resources/methodology · resources/labour-efficiency · resources/direct-bookings
Share of guest contacts that did not reach a human agent (also called deflection). Useful for queue load, but not the same as autonomous resolution: a contained FAQ answer can leave a late checkout, invoice, or housekeeping ask unfinished in hotel systems.
Measurement: Containment = (contacts with no human reply) ÷ (contacts in cohort).
Excludes: Does not require PMS/ops write-backs. Does not prove work was completed.
Vs common use: Vendors often treat containment and “automation” as synonyms. D3x separates containment (no human touch) from autonomous resolution (outcome completed under policy).
Cited on: Home · resources/methodology
Median time from guest message to first AI or agent response on messaging channels. Production proof on D3x cites a 120× faster median response when comparing a ~15 minute baseline to ~7 seconds after automation.
Measurement: Median of first-response latency across messages in the cohort.
Excludes: Does not measure time-to-resolution of the full guest ask.
Vs common use: Speed alone is not resolution; pair with autonomous resolution and AI CSAT on the same cohort.
Cited on: Home · resources/direct-bookings
Estimated frontline hours returned to hotel ops from AI-only handling of routine guest contacts, typically expressed per team member per month. D3x publishes +20 hours saved per team member per month as a production-oriented figure.
Measurement: Hours ≈ (AI-resolved contacts × average handle time) aggregated and normalized per team member per month.
Excludes: Not a headcount-reduction guarantee. Does not count hours spent supervising escalations as “saved.”
Vs common use: Framed as capacity returned under load, not as FTE cuts.
Cited on: Home · resources/labour-efficiency
D3x’s founding thesis is 3× more direct bookings via messaging, email, and phone that catch intent, extend stays, and keep the next stay off the OTA. The 3× figure is a company mission / build bar, not a contractual ROI guarantee for every property.
Measurement: Direct-booking attribution covers owned-channel conversions assisted by messaging, email, and phone — including stay extensions and rebookings kept off OTAs — under property-specific rules; 3× remains a mission bar, not a portfolio-audited ROI formula.
Excludes: Not a guaranteed ROI. Illustrative € channel models on the direct-bookings page are scenarios, not audited portfolio results.
Vs common use: Many “booking chatbot” claims measure widget sessions; D3x frames direct bookings across owned channels plus ops execution in the PMS.
Cited on: Home · resources/direct-bookings · about
Vendor-dependent percentage that often mixes FAQ deflection with true stack resolution. Always ask what sits in the numerator before comparing to D3x autonomous resolution.
Measurement: Vendor-defined — request the numerator and denominator in writing.
Excludes: Not a D3x primary KPI. Prefer autonomous resolution for apples-to-apples audits.
Vs common use: Commonly inflated by counting FAQ answers as “automated.”
Cited on: resources/methodology
Guest satisfaction score on conversations handled by AI. D3x publishes 4.58 AI CSAT against 4.62 for human agents on a 90-day sample.
Measurement: Mean CSAT on AI-handled conversations in the sample window.
Excludes: Not blended with human-only conversations unless stated.
Vs common use: Should be reported on the same cohort as autonomous resolution, not a cherry-picked channel.
Cited on: Home · resources/methodology · resources/labour-efficiency · resources/direct-bookings
Production guest-message volume handled by D3x across live hotel groups. Published figure: 250,000+ messages per month.
Measurement: Count of guest messages processed in production during the reporting window.
Excludes: Not a forecast. Not limited to a single customer.
Vs common use: Volume without resolution rate is vanity; pair with autonomous resolution and CSAT.
Cited on: Home · resources/methodology · resources/direct-bookings
Production voice hours handled per month by D3x Phone AI. Published figure: 18,000+ hours per month.
Measurement: Sum of handled call duration in production.
Excludes: Not concurrent ports or peak concurrency.
Vs common use: Voice depth can lag messaging until the same Skills run on phone.
Cited on: Home · resources/direct-bookings
Observed message-volume growth absorbed without proportional frontline headcount increase. Published figure: +95% volume growth with no headcount increase.
Measurement: Δ message volume vs baseline, with headcount held flat for the measured roles.
Excludes: Not universal across every customer.
Vs common use: Efficiency under load, not a layoff metric.
Cited on: Home · resources/labour-efficiency
Definitional stability matters more than any single quarter’s figure. When a formula or exclusion rule changes, it is recorded here.
Public methodology page launched with Skills vs FAQ framing and autonomous resolution formula.
Added citable metric DefinedTerm anchors, Dataset schema, and self-contained claim sentences beside published figures. No formula change.
06 · GLOSSAR
07 · GRENZEN & EHRLICHKEIT
Trust schlägt eine Vanity-Prozentzahl. Lieber eine niedrigere autonome Rate auf einem streng gesteuerten Luxury-Portfolio als Inflation durch FAQ-Deflection.
AUF IHREM VOLUMEN SEHEN
Wir mappen, welche Anfragen auf Ihrem PMS- und Ops-Stack zu Skills-Resolutions werden, und welche aus Policy human bleiben sollten.