METODOLOGÍA · SKILLS VS AUTOMATIZACIÓN FAQ
D3x publica un rango de 60–70% de resolución autónoma en mensajería de huéspedes. Esta página define exactamente qué significa, para que operadores, CIOs y compras comparen vendors con el mismo scorecard.
Definición pública · Mensajería en producción · Actualizado 2026
01 · EL SCORECARD
Los vendors suelen contar una respuesta de base de conocimiento como “automatizada”. El huésped sigue necesitando toallas, una corrección de factura, un cambio de reserva o mantenimiento, y ese trabajo sin terminar llega a la bandeja del operador. Los Skills de D3x ejecutan en tu PMS y stack ops. Esa es la diferencia entre desviar y resolver.
Responde
El huésped recibió texto. El hotel sigue teniendo trabajo.
Resuelve
El huésped obtuvo el resultado. Stack del hotel actualizado.
02 · DEFINICIÓN
En claro: el huésped pidió algo, el agente lo terminó (o lo rechazó correctamente), y ningún compañero tuvo que tomar el hilo. Una respuesta FAQ educada que deja la petición operativa sin terminar no es resolución autónoma.
Fórmula
Resolución autónoma = numerador ÷ denominador
Numerador
Hilos de mensajería de huéspedes cerrados sin toma humana, donde el agente completó el resultado pedido (o un rechazo seguro por política) bajo reglas del Skills Engine.
Denominador
Todos los hilos de mensajería de huéspedes en alcance de automatización en el periodo medido (por propiedad y canal), excluyendo spam, tráfico de prueba e hilos deliberadamente fuera de automatización.
Aprobación human-in-the-loop
Si la política exige aprobación humana antes de commit, el hilo no es autónomo hasta que la acción se complete sin que el staff sea dueño de la conversación del huésped.
Co-piloto / borrador para el staff
Los borradores que un humano debe enviar no cuentan. El humano sigue siendo dueño del resultado.
Hilos multi-intent
Si un hilo pide toallas y una corrección de folio, ambos resultados deben completarse (o rechazarse correctamente) sin toma humana.
Transferencia con contexto
Un handoff limpio con contexto es buen producto. No es resolución autónoma para ese hilo.
03 · EJEMPLO
Huésped in-stay en WhatsApp: “¿Puedo tener late checkout hasta las 14:00? Mi tren es a las 15:00.” La política permite late checkout por 35 € entre semana si la ocupación lo permite.
Ruta A
Contado como “automatizado” por muchos vendors. Trabajo aún abierto.
Ruta B
Cuenta como resolución autónoma. Bandeja vacía para esta petición.
04 · EL RANGO 60–70%
Los típicos de portfolio en mensajería de huéspedes rondan 60–70% de resolución autónoma cuando los Skills están activos y la automatización after-hours está en vivo. El rango no es una garantía para cada propiedad el día uno.
60–70%
#Típico de portfolio · mensajería
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+
#Volumen en producción
D3x processes 250,000+ guest messages per month in production across live hotel groups.
Definition →4,58
#vs 4,62 humano · muestra 90 días
AI-handled conversations score 4.58 CSAT versus 4.62 for human agents on a 90-day sample.
Definition →71,3%
#Ago 2026 · 9 hoteles · 57,6% totalmente contenidas
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 · AUDITORÍA DEL COMPRADOR
Lleva este scorecard a cada demo. Si un vendor no puede responder con evidencia de producción, trata su “80% de automatización” como deflexión FAQ hasta que se demuestre lo contrario.
01
Los write-backs son la línea entre resolución y chat.
02
Si sí, están comparando unidades distintas. Pide por separado una tasa de resolución por Skills / stack.
03
Los promedios de portfolio ocultan canales FAQ-heavy y skills ops débiles.
04
Alta automatización con CSAT en caída no es una victoria.
05
Los grupos enterprise necesitan decision trails, no stats de deflexión en caja negra.
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 · GLOSARIO
07 · LÍMITES Y HONESTIDAD
La confianza gana a un porcentaje vanidoso. Preferimos publicar una tasa autónoma menor en un portfolio luxury bien gobernado que inflarla con deflexión FAQ.
VÉALO EN SU VOLUMEN
Mapearemos qué peticiones se convierten en resoluciones por Skills en su PMS y stack ops, y cuáles deben seguir humanas por política.