Guest messaging for OPERA Cloud hotels

OPERA Cloud knows everything about the reservation and nothing about the conversation. It holds the guest’s name, dates, rate and preferences, and it has no channel to the guest’s phone. That gap is where guest messaging lives, and for OPERA Cloud hotels it closes cleanly, because Oracle built OHIP precisely so external systems can react to what happens in the PMS. This guide explains how the messaging layer works at an OPERA Cloud property: what OHIP contributes, which channels land in one inbox, how reservation context reaches the team, what setup involves, and how the platforms on the usual shortlist compare.

Why OPERA Cloud hotels add a messaging layer

Three pressures push OPERA Cloud properties toward a messaging layer. Guests expect answers on WhatsApp at any hour, in their own language, and a front office cannot staff for that alone. Revenue teams want the pre-arrival window worked systematically, because the days before check-in are when upgrades and treatments sell. And operations want one place to see every guest conversation instead of five browser tabs.

The PMS is deliberately not that place. OPERA Cloud is the system of record; a communication platform is the system of conversation. Kept separate and connected, each does its job: nothing about how the property uses OPERA changes, and the guest experience changes visibly.

WhatsApp through OHIP, in real time

The heart of the setup is event timing. When a reservation is created in OPERA Cloud, OHIP pushes the event to chatlyn within moments, and the journey starts: a WhatsApp confirmation with the guest’s name and stay dates, a pre-arrival message that opens the upsell window days before check-in, arrival information on the day, and a review request after check-out. A cancellation stops every pending message for that stay instantly.

Timing is what makes the channel perform. A pre-arrival offer sent minutes after the booking, while the trip is being planned, behaves differently from the same offer sent from a nightly export. Spa Resort Geinberg runs this journey and reaches a 95% open rate on WhatsApp, with 86% of enquiries resolved by the AI before staff are needed. The mechanics, supported events and specs are on the Oracle OPERA Cloud integration page, and if the acronym itself is new, start with what is OHIP?

Email, webchat and OTA messages in one inbox

WhatsApp carries the journey, but guests do not confine themselves to one channel. Email arrives with documents and questions, webchat catches the website visitor who has not booked yet, Meta Messenger collects the social audience, and Booking.com guests write inside the platform. In chatlyn, every one of those conversations lands in the same inbox, assigned and answered by the same team, with the same AI handling first response on WhatsApp and webchat around the clock in more than 100 languages.

For the front office this is the difference between monitoring channels and answering guests. One conversation history per guest, whatever the channel, is what guest messaging software for hotels exists to provide.

Guest profiles and reservation context

Guest relationship management begins with the conversation and the reservation on the same screen. Because OPERA Cloud data flows into chatlyn, the agent answering a WhatsApp message sees the stay dates, the room category and the booking history next to the chat, and replies with the details in view rather than asking the guest to repeat them.

The data direction is worth stating precisely: it flows one way, from the PMS to chatlyn. chatlyn reads reservation context to personalise and time communication; it does not write to OPERA, create bookings or change rates. Your team stays in charge of the PMS, and the messaging layer carries zero risk to it.

Upselling by message, alongside Nor1

Many OPERA Cloud properties already run Nor1, Oracle’s machine-learning upsell engine, which scores and presents upgrade offers around booking and check-in. Messaging-led upselling is complementary rather than competing: the offer travels on WhatsApp, where guests actually answer, timed by the reservation events and phrased as a conversation with quick replies. The AI answers questions about the offer at any hour, and your staff confirm and fulfil each accepted request. Properties running both let Nor1 optimise what to offer while the messaging layer wins on where and when the guest sees it.

Setup, property by property

OHIP supports multi-chain organisations, and each property runs its own integration: its own Oracle-side authorisation, its own chatlyn connection, its own guest journeys. A ten-property collection is ten setups, which keeps every property’s data and journeys separate by design.

The practical work is coordination rather than development. chatlyn’s integration team runs the Oracle-side authorisation together with your IT contact, property by property, and the timeline usually depends on how quickly that authorisation completes. To assess where your property stands before starting, the free whitepaper Is your OPERA Cloud hotel ready for AI? includes a six-domain readiness scorecard built for exactly this decision.

The platforms compared

Hotels on Oracle OPERA Cloud choosing a guest messaging layer keep meeting the same shortlist, and the vendor pages all sound alike. This comparison looks at what each platform actually documents about its OPERA connection, its channels and its AI, so you can shortlist on facts. A note on fairness: chatlyn builds one of these platforms. Every claim about the others below comes from their own public pages, checked in July 2026, and we tell you where our own limits sit too.

What actually separates these platforms

Four things, in order of consequence. First, integration depth: a realtime OHIP event subscription reacts to a booking in seconds, while an unspecified “Opera API integration” can mean anything from realtime to a nightly sync, so ask which. Second, channel coverage: where do your guests write, and do OTA messages from Booking.com land in the same inbox. Third, AI behaviour: languages, response time, and what happens at handover. Fourth, proof: named properties in your segment with published numbers.

The comparison

Different category note: HeyKoala answers the phone; the rest answer messages. Many properties end up wanting one of each.

The platforms, briefly

chatlyn is an AI guest communication platform built only for hotels, used by more than 1,000 properties with a luxury focus. Reservation events from OPERA start the guest journey: pre-arrival WhatsApp with upsell offers, AI first response in the guest’s language, and every channel, including Booking.com messages, in one omnichannel inbox next to the reservation data.

Viqal is an AI concierge for hotels, led by WhatsApp, documenting an OHIP integration, a 200+ language claim and named references with numbers (Axiom Hospitality’s Radisson Blu portfolio, Hazlewood Castle). A fit for properties that want a concierge-style assistant on one channel.

SleekFlow is an omnichannel messaging and AI platform serving several industries, with roots in commerce. It publishes guidance on Opera API integration and one resort case study reporting faster responses and higher conversions. A fit if you run messaging across more businesses than a hotel.

Myma.ai offers AI chat and voice for hospitality with an APAC footprint; its help centre documents OHIP onboarding for OPERA Cloud. Ask which events it covers and about on-premise properties.

HeyKoala is voice AI for the hotel phone line, connecting OPERA Cloud and OPERA 5 through the legacy OPI/OWS interfaces. It complements a messaging platform rather than replacing one.

Where chatlyn stands apart, stated carefully

Three places the documentation still favours chatlyn, re-checked on 27 July 2026. Integration pairing: chatlyn is the only messaging platform here that pairs OHIP realtime events on OPERA Cloud with a documented on-premise integration; the other OHIP vendors are Cloud only, and the one platform covering both generations does so for voice, through the legacy OPI/OWS interfaces that Oracle’s own documentation treats as the migration path to OHIP. OTA messages in the inbox: Booking.com conversations sit next to WhatsApp and email today, with the OPERA reservation context attached; none of the four offers that live. And reference tier: chatlyn’s published numbers come from properties up to ultra-luxury flags (Hotel Sacher, St. Regis Le Morne); the published references elsewhere in this list sit in upscale and boutique segments.

And one thing we deliberately do not do: chatlyn’s AI informs guests and hands the conversation to your team. It does not create bookings, quote live availability or write to OPERA. If a vendor claims its guest-facing AI operates your PMS, ask exactly which OPERA operations it performs, under whose credentials, and what happens when it gets one wrong.

How to choose

Shortlist by channel reality first (pull last month’s enquiry log), then ask every vendor the same four questions in writing: which OPERA integration method, which events in real time, which languages the AI has actually answered in production, and which reference property matches your segment. The chatlyn OPERA Cloud integration page answers all four for us, and what is OHIP? explains the integration layer itself; the journey sections earlier in this article show what the messaging looks like in practice.

Frequently asked questions

Is there hotel guest messaging software compatible with an OPERA Cloud integration? Yes. chatlyn connects to Oracle OPERA Cloud through OHIP with realtime event subscriptions, so reservations, arrivals, check-ins, check-outs and cancellations trigger guest messaging automatically, and every conversation shows the OPERA reservation context.

Which channels can OPERA Cloud hotels message guests on? WhatsApp, email, webchat, Meta Messenger and Booking.com, all in one inbox. The AI answers routine questions on WhatsApp and webchat; staff handle every channel from the same screen.

Does the messaging layer write anything into OPERA Cloud? No. Data flows one way, from OPERA Cloud to chatlyn. The messaging layer reads reservation context to personalise and time messages; every change to a booking happens in the PMS, by your team.

How long does the OPERA Cloud connection take to set up? It depends mainly on the Oracle-side authorisation for your property. chatlyn’s team manages the process with you, property by property, and the Oracle OPERA Cloud integration page covers what is involved.

Which guest messaging platforms integrate with OPERA Cloud through OHIP? Of the platforms compared here, chatlyn and Viqal document an OHIP integration, and Myma.ai documents OHIP onboarding in its help centre. Others reference an Opera API connection without naming the method, which is worth clarifying before you sign.

Does any platform also support OPERA 5? For guest messaging, chatlyn documents an OPERA on-premise integration via SFTP alongside OHIP. HeyKoala documents OPERA 5 support for its voice product.

Can these platforms make bookings inside OPERA? chatlyn does not: the AI informs and escalates, and staff execute changes in the PMS. Treat any booking-execution claim as a question to verify in a demo, not a checkbox.

What should a luxury property check first? Named references in the luxury segment with published numbers, language coverage in production, and how handover to human staff works when the AI reaches its limit.