Can D3x really match Booking.com messages to the right PMS reservation?

Yes, including the edge cases. Booking.com appends a "_1" suffix to reservation numbers on modified bookings, which breaks naive matching; D3x codifies this and similar quirks in the Skills Engine so conversations attach to the correct booking automatically.

Why do Booking.com response times matter?

Booking.com tracks how quickly properties respond to guest messages, and slow responses hurt guest experience scores and pre-arrival confidence. With D3x answering around the clock, midnight questions are resolved in minutes instead of waiting for the morning shift.

Does this replace our extranet access?

No, your extranet stays as is. D3x handles the message traffic, unifying it with your other channels, while your team keeps the extranet for rates, availability, and account management.

OTA INBOX

Booking.com messages answered in minutes, not at the end of the shift.

The extranet inbox is nobody's favorite job: it lives in a separate tab, the guest's question needs a PMS lookup anyway, and response-time metrics quietly affect your visibility. Messages sent at midnight get answered at 9am, if the morning shift remembers.

OTA guests expect answers before arrival, and Booking.com measures how fast you give them. D3x pulls the OTA inbox into the same AI agent that runs your other channels, with Booking.com's quirks already codified.

Last updated: 11 August 2026

Book demo See pricing

D3x connects the Booking.com inbox to the same AI Agents for Hotel groups that handles your WhatsApp, chat, and email. The agent matches the OTA message to the real PMS reservation, answers from your policies, and keeps response times inside SLA around the clock.

60–70%

of routine messages resolved autonomously

250K+

guest messages handled per month

24/7

OTA inbox coverage

3 weeks

typical new integration build

01

The Booking.com quirks, already handledLink to this section

OTA plumbing has sharp edges, like Booking.com appending a "_1" suffix to reservation numbers on modified bookings, which breaks naive PMS matching. D3x codifies these edge cases in the Skills Engine, so messages attach to the right reservation without manual fixing.

Reservation matching that handles the Booking.com "_1" suffix and similar quirks
Guest identity resolved across OTA alias emails and PMS records
Policy-correct answers on prepayment, cancellation, and OTA-specific rate rules

02

One inbox, one agent, every channelLink to this section

OTA messages land in the same queue as WhatsApp, web chat, and email, handled by the same agent, with the same reservation context and property policies. Your team stops tab-switching between the extranet and everything else.

Booking.com inbox unified with WhatsApp, chat, SMS, and email
Consistent answers across channels, no extranet-only improvisation
Escalations land with your team carrying full OTA and PMS context

03

Response-time SLAs, kept automaticallyLink to this section

Because the agent answers 24/7, pre-arrival questions from OTA guests get resolved in minutes regardless of shift patterns, protecting the response metrics that influence your ranking and reducing pre-arrival cancellations driven by silence.

ON THE PLATFORM

Same Skills Engine and audit trail; pick the channel or capability underneath.

Messaging Unified inbox for hotel chains Multi-channel AI for hotels

FAQ

Common questions.Link to this section

OTA inbox automation is software that answers guest messages arriving through channels like the Booking.com extranet automatically. D3x connects the OTA inbox to an AI agent that matches each message to the live PMS reservation, applies your property's policies, and replies within response-time SLAs, 24/7.