P3 Hotels

• P3 guest journey, kiosks, online check-in
• D3x answers guest replies
• D3x unified inbox
• P3 booking engine deep links
• Rates and availability from the P3 API
• Website chat, WhatsApp, SMS, Phone AI
• Typical pair: Opera PMS
• Four-field booking engine connect

P3 Hotels is the guest-facing layer: guest journey, kiosks, online check-in, and the online booking engine. D3x does not replace those products. D3x sits behind them as AI Agents for Hotel groups: when a guest replies to a journey message, D3x answers; when the team needs the thread, they open the D3x inbox; when a guest asks to book on chat, WhatsApp, SMS, or the phone, D3x reads P3 rates and deep-links into the P3 booking engine.

Many D3x Opera properties pair Opera with P3 Hotels because Opera has no booking engine or guest portal. See the Opera docs for the PMS connector. This page is what D3x does with P3 Hotels itself.

Who does what

Guest journey replies

P3 Hotels owns the outbound guest journey. D3x owns the reply. The PMS notifies P3 of reservation and journey updates. P3 sends the journey message via Twilio, on WhatsApp or SMS. SMS uses the same path as WhatsApp: Twilio delivers, D3x receives the reply. That send is synced into D3x so the inbox already has the outbound. If the guest replies or asks a question, the inbound webhook lands in D3x, not in a P3 inbox.

P3 Hotels does not provide a unified inbox for the hotel. D3x does. The property visualises every guest reply, the original journey message, and any human take-over in one D3x inbox.

Kiosks and online check-in

P3 Hotels provides kiosks and online check-in. D3x does not replace those flows. Guests still check in in P3. D3x is there if they write back on a journey thread, or if they ask a question on WhatsApp, SMS, website chat, or the phone.

Rates, availability, and the P3 booking engine

P3 Hotels also provides the online booking engine. When a guest asks about a stay on a D3x channel, D3x connects to the P3 API, fetches live rates and availability, and sends a deep link into the P3 booking engine so the guest can complete a direct booking. WhatsApp and SMS work the same way; SMS rides on Twilio.

• Website chat: the guest asks on the hotel site; D3x reads P3 rates and deep-links Book now into the P3 booking engine.
• WhatsApp: the same lookup and deep link in the thread. Properties can put the WhatsApp number on the Google Business Profile, so the path is Google to WhatsApp to the P3 booking engine.
• SMS: the same lookup and deep link as WhatsApp, delivered via Twilio. See the SMS docs.
• Phone AI: the guest calls; D3x reads P3 rates during the call, then sends a WhatsApp or SMS message with the P3 booking deep link.

WhatsApp on the Google Business Profile is covered on the WhatsApp docs. SMS via Twilio is covered on the SMS docs. Phone AI continuation onto WhatsApp or SMS is covered on the Phone docs.

Notable customers

Dalata Hotel Group runs P3 Hotels and D3x together in production.

• Dalata Hotel Group: Ireland's largest hotel operator, Clayton and Maldron

Go-live

Connecting the P3 Hotels booking engine is a very simple go-live. D3x does not pull sensitive booking-engine credentials. It reads publicly visible rates, availability, and deep links. Once the property is linked to D3x, enter four fields and D3x connects to the P3 API for the rest.

1. Link the property to D3x.
2. Open Connect your Booking Engine [P3].
3. Enter API Base URL, Company ID, City ID, and Hotel ID.
4. D3x calls the P3 API and can serve rates, availability, and booking deep links.

Opera, if that is the PMS, still connects through OHIP (Opera go-live). Journey-reply sync and the unified inbox are configured in the same onboarding. The booking engine step is the four fields above.