Cordiant for Hotels

The hyper-local AI website every Opera Cloud property should have.

Every guest request answered, fulfilled, and transacted — without a human in the middle.

Three sister products for hotel brands on the Oracle stack — Opera Cloud, NOR1, and Simphony. Cordiant is Generally Available today. Cordiant Email is generally available May 10, 2026. Cordiant Staff is in active engineering, targeting general availability July 2026. Priced independently.

Schedule a Briefing See the Reference Deployment
A family at the Zen Pacific Orlando pool above the Cordiant Discover sheet — a pre-arrival menu showing Express Check-in, Early Check-in, Getting Here, Airport Transfer, Enhance My Stay, and Make My Arrival Special.

From the moment a guest discovers your property to the moment they depart. One URL. One conversation.

Your property has never had a digital identity. Until now.

Every luxury hotel has a lobby, a concierge desk, a signature restaurant. Ask yourself: does your property have a digital presence that's truly its own? Not a page buried inside your brand's central website. Not an OTA listing where you're sorted by price between two competitors. Not a vanity site with a photo gallery and a booking redirect.

Hotel brands have built extraordinary digital ecosystems for discovery and loyalty. But the individual property — the place where the brand promise is actually delivered — has never had its own digital presence inside that ecosystem.

A single URL — yourflagship.com — gives your property its own digital identity inside the brand's ecosystem. For the first time.

Beneath that surface, the lifecycle is fragmented across booking engines, guest messaging tools, mobile apps, email programs, in-stay chat, loyalty portals, concierge tools, and feedback platforms. Each a different vendor. Each with its own chrome. Each with limits on what it can see about the guest. Your guest doesn't experience ten surfaces — they experience ten frictions. Every login re-introduces them to your brand. Every handoff loses context.

One AI website replaces the patchwork. Booking, concierge, knowledge, upsell, dining, wellness, and feedback converge into one continuous conversation — across Dreamer, Prestay, Instay, and Poststay.

And missing from every one of those digital surfaces is the thing hospitality is actually made of: nuance. The signature dish by name. The sommelier's seasonal pairing. The spa therapist's specialty. The staff member who remembers. The neighborhood walk. The festival next weekend. The property's specific rituals. The shape of a Tuesday in low season versus a Saturday in peak.

The phone carries nuance. The front desk carries nuance. The concierge carries nuance. The brand site does not. The OTA listing does not. The destination marketing site does not. For decades, the digital layer of hospitality has been the least hospitable surface in the entire industry — generic by structural necessity, commodity by design, brochure by default.

Cordiant for Hotels carries nuance. The AI has the full property context loaded — every menu item, every room type, every amenity, every neighborhood touchpoint, every brand-voice rule, every seasonal change. That's what hyper-local actually means. A digital surface that finally knows the property the way the staff knows it.

Not some things. Everything.

The reframe

For the first time, Opera Cloud isn't just your back-office engine. It's your guest-facing platform.

The shift

One AI website replaces the patchwork.

Cordiant for Hotels sits in front of Oracle Opera Cloud, NOR1, and Oracle Simphony — three Oracle systems, one guest surface. Booking, concierge, knowledge, upsell, dining, wellness, and feedback converge into one continuous conversation across Dreamer, Prestay, Instay, and Poststay.

One AI website, not ten apps.

Guests move through the entire lifecycle in one conversation. No re-contextualizing to a new vendor chrome between booking and concierge, between upsell and feedback.

Brand by architecture.

Every response — including every AI-generated synthesis from the property knowledge corpus — renders in your brand. Tone, voice, typography, layout. Inherited from a brand theme defined once and applied everywhere.

Vendor migrations become backend events.

Move from one CRS to another, one payments provider to another, one loyalty platform to another, and the guest sees nothing different. Your integration team re-points the adapter; the surface keeps working.

Commerce in the conversation.

Stay extensions, spa and dining reservations, transport requests, in-room ordering — all transact inside the same dialog the guest is already in. No new app, no re-auth, no context to re-explain.

In tenant. In your cloud.

Deploys inside your Oracle Cloud Infrastructure tenant, under your existing security posture, alongside Opera Cloud. No guest data leaves your tenant. No new SaaS vendor in your data path.

Guest trust, engineered.

Passkey-first guest authentication with magic-link fallback. Phone detection auto-assigns personal trust. Shared and public devices get contextual inactivity timeouts and a visible sign-out chip. Full capability at every trust level — session behavior is the protection, not capability restriction. Arguably the most considered trust model in guest-facing hospitality.

The intelligence loops back.

Guest feedback is captured conversationally, mostly in-stay — sensitivities, praised areas, celebrations, and service issues surface in natural dialog, not a star rating. NPS and CSAT compute directly from the conversation. Service issues route instantly into recovery; praise is nudged into a public review on TripAdvisor, Google, or Booking.com. The next conversation opens already knowing what happened last time. Staff intelligence and guest personalization are the same system, not two integrations.

Three sister products

Cordiant. Cordiant Email. Cordiant Staff.

Three products built on the same three-layer architecture. Cordiant is the hyper-local AI website every Opera Cloud property should have — the mature application with three years of platform refinement and a live reference deployment, Generally Available today. Cordiant Email is the AI-powered email automation every Opera Cloud property should have — generally available May 10, 2026. Cordiant Staff is the AI-powered staff application every Opera Cloud property should have — in active engineering, targeting general availability July 2026. Cordiant and Cordiant Staff can each be licensed standalone. Cordiant Email is an extension to a Cordiant deployment.

Cordiant
Generally Available today

The hyper-local AI website every Opera Cloud property should have.

One branded URL per property. Connected to Oracle Opera Cloud, NOR1, and Oracle Simphony — every transaction writes back to the PMS. Conversations persist on the Cordiant platform. Zero hallucination risk for even a single transaction — guaranteed, architecturally. No conversation writes to Opera Cloud; every transaction is routed through a deterministic GUI and a deterministic backend. Three years of platform refinement; a working reference deployment runs today at zenpacorlando.com on the Oracle Hospitality Integration Platform sandbox.

What a guest can do in seconds

  • Confirm a reservation, extend a stay, modify a booking
  • Book spa, dining, transport, and in-room service
  • Charge anything to the folio instantly
  • Ask grounded questions about the property and its experiences
  • Move across Dreamer, Prestay, Instay, and Poststay without leaving the conversation
Integrates with: Oracle Opera Cloud · NOR1 · Oracle Simphony · your property knowledge corpus · your payment rails · your loyalty platform. Guest authentication is passkey-first with magic-link fallback, on a three-tier session model engineered for hospitality. Runs inside the brand's own Oracle Cloud Infrastructure tenant.
Cordiant Email
In final pre-launch — generally available May 10, 2026

The AI-powered email automation every Opera Cloud property should have.

The same conversational paradigm, now for inbound guest email. Pre-arrival inquiries, post-booking confirmations, in-stay requests, post-stay follow-ups — all answered automatically, in your brand voice, against the same Opera Cloud, NOR1, and Simphony systems of record that power Cordiant. Every reply is auditable. Email reads from the systems of record, never writes to them; when a guest action is required, a magic link routes the guest to the Cordiant surface where execution happens by the guest's hand, through the same deterministic backend the brand already trusts.

Email is the single largest inbound communication channel for most luxury and upper-upscale hospitality brands — and the channel where labor cost in guest services compounds invisibly. Cordiant Email replaces the highest-volume, lowest-complexity portion of that traffic entirely — at a quality and consistency that generic auto-responders cannot match. Labor freed for the calls and walk-ups that need a human.

What inbound email handles automatically

  • Pre-arrival inquiries from booked guests — brand-tone replies in seconds
  • Post-booking confirmations and clarifications, against live Opera Cloud reservations
  • In-stay requests, transacted against the same systems Cordiant writes to
  • Post-stay follow-ups that drive the next booking, the public review, or loyalty enrollment
  • Prospect emails (no Opera profile yet) — welcoming response with property signup-claim link
  • OTA-booker emails — routed correctly by booking provider and workflow
Integrates with: Oracle Opera Cloud · NOR1 · Oracle Simphony · the property's email infrastructure · Auth0 magic links for prospect-to-bound conversion. Shares the brand voice, knowledge corpus, and governance layer with Cordiant and Cordiant Staff — one architecture, three surfaces. Runs inside the brand's own Oracle Cloud Infrastructure tenant.
Cordiant Staff
In active engineering — targeting general availability July 2026

The AI-powered staff application every Opera Cloud property should have.

The same conversational paradigm, now for the people running the property. Staff say what they need — make a booking for a walk-in, extend a stay, add breakfast to a folio, apply an appeasement, check a guest in — and the platform surfaces the right Opera Cloud workflow, pre-populated. No Opera Cloud screens to navigate. No systems to learn. The same Discover surface that guides guests now guides staff through the property's full operational repertoire. Every signal the guest surface captures enriches the next staff response; every staff action enriches the next guest conversation. The two halves of the platform make each other smarter.

A 400-room hotel typically spends between $150,000 and $300,000 a year on onboarding and training once turnover, HR time, and systems-training programs are counted. Cordiant Staff eliminates the systems-training portion of that spend entirely — because there is no system for staff to learn. Day one, staff serve guests. Not screens.

What staff can do by saying so

  • Make a booking for a walk-in, or on the phone on behalf of a guest
  • Extend a stay, modify a reservation, or move a guest to another room
  • Add breakfast, dining, spa, transport, or any ancillary to the folio
  • Check a guest in, process a departure, apply an upgrade or appeasement
  • Add a preference, dietary note, or sensitivity to the profile
  • Pull up a guest's full 360 — history, feedback, preferences, past issues — by name
  • Ask for today's detractors, promoter recognition, or issue spikes in plain language
Deployed with: the same three-layer platform, security posture, and tenant architecture as Cordiant. Staff identity federates through OCI IAM — zero hotel IT configuration; role mapping auto-syncs from Opera Cloud job titles. Shares brand theme, sprite, and governance with the guest-facing surface.
Cordiant · In practice

Every moment a guest wants something — heard, confirmed, and taken care of in seconds.

A guest converses directly with Oracle Opera Cloud and gets everything done. Three Oracle systems behind one surface. One branded URL per property. Zero hallucination risk for even a single transaction — guaranteed, architecturally.

$25+
per room night in attributable new revenue. For luxury and upper-upscale hotels with strong ancillaries.
70%
gain in operational efficiency on guest-facing workflows. Across every class of hotel. From economy to luxury.
Worked example · Revenue at scale

For a 50-property brand · 7,500 keys · 70% occupancy:

≈ $48 million in attributable new revenue. Every year.

yourflagship.com
A flagship hotel in the Gulf

102 hyper-local property websites powered by AI. The arrival ritual, choreographed.

11:15 PM
Mid-flight, ninety minutes from landing. The guest texts to confirm the suite is still held after a delayed connection from Frankfurt. Confirmed in seconds. Kitchen alerted that arrival will be late.
12:45 AM
Guest just past immigration. Asks if a light meal can be arranged in-room since the restaurants have closed. Chef on duty confirms a curated late-arrival plate. Charge committed to the folio.
8:30 AM
Guest extends checkout to 4 PM and asks for a private breakfast in the suite. Late checkout written to Opera Cloud. Suite breakfast booked with dietary preferences pulled from the profile.
yourflagship.com
A historic palace hotel in Southern Europe

43 hyper-local property websites powered by AI. Ancillary commerce, in conversation.

10:30 AM
Guest asks about a private guided tour of the Old Town for the afternoon. Property's curated partner contacted. Booking confirmed. Transport arranged from the lobby. Folio updated.
3:15 PM
After the tour, guest asks for a wine pairing for the partner's birthday dinner. Sommelier's notes synthesized in the property voice. Rooftop table reserved. Signature pairing waitlisted with the kitchen.
7:30 PM
Guest extends two more nights and adds the spa hammam for the morning. Both written back to Opera Cloud in eight seconds. Spa schedule updated in real time.
yourflagship.com
A harborside resort in the Asia-Pacific

220 hyper-local property websites powered by AI. The next stay, already booked.

Departure
Guest leaves a brief in-conversation note praising the spa therapist by name. Praise routed to the therapist's profile. Public review nudge sent. NPS computed from the conversation — no star rating asked.
+ 4 hours
In transit. Guest receives a personalized goodbye with the favorite cocktail recipe from the rooftop bar and a curated invite for the harbor festival next quarter. Composed in the property voice. Sent without staff review.
+ 14 days
Guest receives a tied invitation to two festival nights with the same suite category held. Books in three taps. Loyalty tier upgraded. Suite of preferences carried over.

And the moments most platforms miss.

A contextual assist

"It's warmer than I packed for."

The platform interprets the intent, offers the property's loaner closet, suggests the nearest retail, and at the guest's request arranges a car. No menu navigation. No opening a second app. The conversation carries across amenity, retail, and transport without a handoff.

A detractor alert reaches the GM

"Really disappointing end to the stay — room service took forty-five minutes on my last morning."

Thirty seconds after the guest closed the feedback conversation, a Slack alert reached the GM. Guest name, loyalty tier, room, NPS score, the verbatim quote, and a one-tap Mark Contacted action. The appeasement was authorized. The service-recovery note was written to Opera Cloud as a reservation comment. The sensitivity was flagged so the guest's next stay opens with it already in memory. The raw transcript stayed inside the role-based dashboard. Only the action reached Opera.

Three systems. One guest surface. One intelligent URL per property. Ten seconds each time.

Every dollar of new revenue generated by Cordiant is tracked end-to-end in Oracle Opera Cloud. Running dashboard, in play.

Runs inside the brand's own Oracle Cloud Infrastructure tenant.

Cordiant · Generally Available

See it running end to end.

A working reference deployment runs on the Oracle Hospitality Integration Platform sandbox. Three years of platform refinement behind it. The full guest lifecycle handled end to end — Opera Cloud integration, identity flow, payment rails, and the conversational commerce surface composed into one complete experience.

The Cordiant guest surface running live at Zen Pacific Orlando — Sara confirms breakfast at The Terrace with an embedded chef-prep video, a Perfect! Your breakfast at The Terrace awaits confirmation card, and a personalized response noting three stays coming up.

In-stay dining, arranged in the same conversation. Sara writes the booking back to Opera Cloud — no second app, no phone call.

Open zenpacorlando.com
Two golden dice resting on a polished marble lobby counter, with a property management system screen blurred in the background — a visual metaphor for the unacceptable risk of AI that guesses at availability, rates, and inventory.
The reliability test

AI that never touches Opera Cloud.

Most hotel AI guesses. It guesses the room is available. It guesses the rate is $429. It guesses the spa has a 2 PM slot. It pulls from cached data, stale snapshots, training sets — and delivers the answer with absolute confidence.

Until the guest shows up and the room is sold. The rate was wrong. The spa slot was booked an hour ago. In any other industry, that's a bug. In hospitality, that's a 1-star review that mentions your property by name.

Conversation and transaction are two different problems. Asking "what's available this weekend?" is a conversation. Saying "book it" is a transaction. One should feel personal. The other must be deterministic. Most hotel AI treats them as the same problem. They're not.

Cordiant splits them in two. A cognitive layer that knows your guests — remembers preferences, understands context, makes every interaction feel personal. An execution layer that guarantees accuracy — proven workflows, deterministic transactions, audit-ready writes through Opera Cloud, NOR1, and Simphony's existing role-based access controls.

The AI cannot hallucinate a reservation. It cannot apply a rate outside policy. It cannot commit a change your compliance team wouldn't approve. Not because we trust it not to — because, structurally, it is not the thing executing the action.

Opera Cloud stays canonical. Every write is direct. Every transaction is logged. Every change is guaranteed accurate. One source of truth.

The reliability test

Two questions for any AI vendor:

  1. When a guest says "book it," is that transaction deterministic or probabilistic?
  2. If Opera Cloud goes down for thirty seconds, what does your AI tell the guest?

If the transaction is probabilistic — your PMS is at the mercy of a language model. If the AI keeps going when Opera Cloud is down — it's making things up, with no source of truth.

100% reliable doesn't mean 100% available.
It means 100% honest.

Every answer sourced. Every transaction deterministic. Every write auditable. Every time.

Hotel software should not act like the roll of a dice.

Deployment

Cordiant ships today. Brand first, properties next.

Cordiant runs today and was built for Oracle Opera Cloud properties. Adoption is configuration, not bespoke engineering. The first Cordiant property in a brand reaches production in six to eight weeks — brand theme, Oracle Opera Cloud, NOR1, and Oracle Simphony integration, identity federation, commerce engine, knowledge corpus ingestion, and payment rails, all configured against a platform that already works. Subsequent Cordiant properties compress to two to four weeks because the brand-level foundation is already live. By the third or fourth property, each deployment is primarily configuration against patterns Cordiant has already built for the brand.

Cordiant for Hotels deploys inside your Oracle Cloud Infrastructure tenant, under your existing security and compliance posture, alongside Opera Cloud. No new SaaS vendor in the data path. No guest data leaves your tenant. Staff and platform identity federate through OCI IAM. Guest-facing identity is a separate surface — passkey-first, with a three-tier session model engineered for hospitality and full capability at every trust level. LLM inference runs against your chosen model posture under your data-residency and model-governance rules.

Two operating modes. One architecture. Self-operated: your platform team runs the system, with Cordiant Brand Support covering architecture, upgrades, and issue triage. Cordiant-operated: Cordiant runs the platform inside your tenant under an ops contract, with audited access and no data leaving your cloud. Tenant ownership, identity federation, audit trail, and the trust posture are identical in both modes. Only the operator changes. Brands choose based on internal platform engineering capacity and where they want their team's attention to land.

Cordiant Email and Cordiant Staff follow the same deployment pattern. Same three-layer platform, same tenant architecture, same per-property compression once the brand foundation is in place. Email reaches general availability May 10, 2026 and is available for first-deployment scoping conversations now. Staff reaches general availability July 2026 and is available for briefing and early-commitment conversations.

6–8 weeks
First Cordiant property from kickoff to production
2–4 weeks
Each subsequent Cordiant property in the brand
In tenant
Your cloud. Your audit trail. Your control.
Commercial model

Perpetual license. Per-property implementation. No take-rate.

Each product is priced per regional deployment, with each deployment covering up to 100 properties. Cordiant and Cordiant Staff can each be licensed standalone. Cordiant Email is an extension to a Cordiant deployment. Predictable line items. Commercial patterns your technology leadership already understands from PMS, RMS, and CRS contracts.

Cordiant brand license
$320,000 / regional deployment
Per-property implementation
$20,000 – $30,000
Property-level annual support
$4,800 / property / year
Cordiant Email
priced at half the standard structure
Cordiant Staff
matches the Cordiant structure

No take-rate. No revenue share. No per-transaction metering.

See full pricing · worked examples for ten-, twenty-, and forty-property brands
Next step

From conversation to first property in production.

Thirty to forty-five minutes with Cordiant leadership. We walk the architecture, show the live reference deployment at Zen Pacific Orlando, and propose a first-property scope. Every guest request answered, fulfilled, and transacted — without a human in the middle. Every transaction sourced. Every write auditable. Every time.

Stop managing software. Start managing guests.

Schedule a Briefing