Opera

• Oracle Opera via OHIP
• Room types, rates, rate plans, availability
• P3 Hotels, SynXis, or custom booking deep links
• Reservation lookup (OTA ID or confirmation number)
• Invoice redelivery (Opera sends the email)
• P3 Hotels or custom guest portal and online check-in
• Outbound guest journeys, including room is ready

Oracle Opera (including Opera Cloud) is the PMS standard at enterprise hotel chains. D3x connects through OHIP, the Oracle Hospitality Integration Platform, and treats Opera as the system of record for the stay: agents read inventory and reservations, answer with live context, act on the booking, and run outbound guest journeys, on WhatsApp, SMS, email, website chat, voice, and social, with the same Skills Engine and audit trail as every other channel.

Opera does not include a booking engine or a guest portal. Many D3x Opera properties pair it with P3 Hotels or SynXis for booking and check-in. Others use a custom booking engine or a custom guest portal. This page is the operator view of the Opera connector. For the marketing overview, see the Opera integration page and AI for Opera.

Rates, availability, and booking

When a guest asks about booking a stay, D3x connects to Opera over OHIP and syncs the catalogue the agent needs to answer with live inventory, not a static brochure.

• Room types and group types: the sellable units configured in Opera
• Rates and rate plans: live prices for the dates and occupancy the guest specified
• Availability: remaining inventory for those dates

That data is used to serve rates and availability in the conversation. Matching room types appear in a carousel: each card shows the room, estimated prices, and a Book now action. Opera has no booking engine, so Book now is never an Opera checkout URL.

P3 Hotels, SynXis, or custom booking engine

Many Opera hotels on D3x use a P3 Hotels booking engine or a SynXis booking engine. The carousel deep-links into that engine so the guest can complete the booking there. See the P3 Hotels docs and the P3 Hotels integration.

If the property uses another booking engine, D3x still supports custom booking engine linkage, provided that engine accepts deep links. The agent already has the guest's search in context and constructs the URL from those parameters:

• Start date
• End date
• Number of adults
• Number of guests
• Room type

The guest taps Book now and lands on the booking engine with the search already filled in. If the engine cannot accept those parameters, D3x cannot construct a useful deep link.

Booking engine rates and availability API

Some booking engines override the rates and rate plans that sit in Opera: special offers, membership rates, and similar. In those cases D3x can connect to the booking engine's own rates and availability API, so the carousel shows the price the guest will actually pay at checkout, not only the Opera rack.

1. 1

   Guest asks about dates or a stay

   Occupancy and date range are confirmed in the thread (for example 2 adults, 10 to 14 October).

2. 2

   D3x queries Opera (and the booking engine when it overrides rates)

   Room types, group types, rates, rate plans, and availability are pulled over OHIP. If the booking engine applies its own offers, D3x reads those prices from the booking engine API instead.

3. 3

   Carousel and deep link

   Available options render as cards with estimated prices. Book now opens P3 Hotels, SynXis, or a custom booking-engine URL built from start date, end date, occupancy, and room type.

Find a reservation

Once the guest is talking about an existing stay, D3x needs the right Opera reservation in context (past, upcoming, or in progress) so it knows whether they are in-house, not yet arrived, or recently checked out.

Answer questions about the reservation

With the reservation loaded, the agent can answer questions about that stay using live Opera data: dates, room type, rate, status, arrival expectations, and other fields on the booking. Replies stay grounded in the reservation in context, not generic FAQ copy.

Act on the reservation: invoice redelivery

Beyond answers, D3x can execute post-booking work in Opera while the guest stays on the same channel. On Opera, invoice handling is a redelivery: D3x does not fetch a PDF and attach it in-thread, and it does not modify VAT or company fields the way it does on Apaleo.

When a guest asks for their invoice, D3x connects to Opera and asks Opera to trigger the invoice email to that guest. Opera sends the document from its own billing flow. The guest receives the invoice they already expect from the hotel.

Dynamic guest portal and online check-in

Opera does not provide a guest portal or online check-in product. D3x still delivers those guest-facing features by authenticating the guest, then connecting to the portal or check-in system you already run.

• P3 Hotels: many Opera groups use P3 Hotels for the guest portal and online check-in. D3x authenticates the guest and opens that flow.
• Custom guest portal or online check-in: if the property built its own, D3x supports connecting to it the same way, after the guest is authenticated.

Outbound guest journeys

Inbound chat is only half of the Opera connection. D3x also runs outbound guest journeys: timed, segmented messages across WhatsApp, SMS, and email, triggered as the Opera reservation moves through its lifecycle. Opera is where D3x can do quite a lot on the outbound side.

Stay events

Journeys can fire on Opera stay events. The ones groups use most often:

• Booking confirmation: when the reservation first lands in Opera
• Pre-arrival: before the guest arrives
• Check-in: when they check in, or around that moment
• Room is ready: when the room is assigned and ready for the guest
• Pre-departure: before checkout
• Check-out / post-stay: when they leave, or after they have left

Messages can be scheduled before or after each event (for example a welcome WhatsApp the evening before arrival, a room-is-ready SMS when the room is released, or a thank-you email an hour after checkout).

Audience filters

Not every reservation should get every message. D3x filters the audience against live Opera fields so you segment who receives each send.

• Package: for example send a breakfast email only to guests who booked a breakfast package
• Guest language
• Room type (include or exclude)
• Rate plan (include or exclude)
• Booking source
• Stay dates / arrival date
• Stay length / number of nights

This is the same outbound guest journey capability described on the WhatsApp docs and the Outbound page, with Opera as the event source that starts each send.

Notable customers

These groups run D3x on Opera.

• Staycity Group: Staycity and Wilde aparthotels across Europe
• L&R Group (Iconic Hotels & Resorts): luxury hotels and resorts, including Strand Palace
• Dalata Hotel Group: Ireland's largest hotel operator, Clayton and Maldron

Go-live

Opera connects through OHIP rather than a marketplace token. D3x sends a request to connect. The property administrator approves that request. Then the property is live. It is one extra approval step compared with Mews or Apaleo, and it is the standard Opera Cloud path, not a custom API project.

1. D3x sends an OHIP connection request for the property.
2. The property administrator approves the request in Opera.
3. Once approved, D3x is connected to Opera for that property.

Keep Opera as the system of record. D3x sits above it as AI Agents for Hotel groups across channels. Pair P3 Hotels, SynXis, or a custom booking engine and guest portal. Opera does not provide either.