The demo resort

A real property, run by Studio. Outside and in.

Meet Sapphire Bay: a fictional resort running the real conversational system. Watch it help a guest. Then see where every conversation, request, and answer lands for the owner.

Fictional property. Real system.

Watch it work ↓

The Sapphire Bay Resort cove at golden hour

Outside · the guest experience Inside · the Studio Console

Watch it work

Three moments. No email required.

Three short replays from the real system at Sapphire Bay. Each proving a different quality. Pick one.

This replay is produced from the real system. It arrives with the capture.

No staged UI, no retyped answers: the moment is recorded from the live Sapphire Bay widget and dropped into this frame, with its transcript below.

STU-D01 · awaiting capture

Ask to see every room type. The reply arrives as the real gallery — photographs, names, and the prices printed by the property.

Transcript · arrives with the capture (the visitor’s question, the settled gallery, and the plain-language caption).

Ask about the spa. Durations and prices are quoted exactly from approved knowledge; when a figure is absent, the assistant says so.

Transcript · arrives with the capture.

Change language without starting over. The warmth changes register; names and prices do not.

Transcript · arrives with the capture.

Not a recording of what Studio might do. A replay of what the system did.

Then ask it to do something

It knows when the conversation belongs to a customer.

A guest verifies her stay, sees the real folio attached to it, and asks for something she needs. The assistant doesn’t invent the account or promise around it; it reads and acts through the connected demo system.

The connected My Stay journey · replay arrives with the capture.

Verification → the real folio → a service request, recorded on the live demo path. Reusable verification credentials never appear in the public replay.

STU-D02 · awaiting capture

Recognized

The stay is verified, so the conversation becomes a customer’s.

Account found

The real folio, with its line items, read and never invented.

Request made

Extra pillows, through the connected system. Acted on, and logged.

Demo data, real lookup and request path.

The other side of the conversation

The demo has an inside.

Every conversation and request arrives in the Studio Console. Follow the answer back to approved knowledge. See what needs attention. Ask for a report in plain words. This is the same property, viewed from the owner’s side of the counter.

Outside, it receives the guest. Inside, it works for the owner.

The owner’s side · real Console capture, post-rebrand.

The same guest session, visible inside: the conversation, the request, the approved knowledge, the report. Shown only with controls the scoped demo account actually has.

STU-D03 · awaiting capture

The conversation · what the guest asked, and how it answered

The request · with its context attached, routed

The approved knowledge · follow any answer back to its source

The report · ask what happened, in plain words

When you have the keys, try this.

Guest side

Ask to see every room type.

Ask for the exact price of a treatment.

Continue the same exchange in French.

Use the private guest scenario in your access note to inspect a stay and make a request.

Owner side

Find the conversation you just had.

See the request with its context attached.

Trace an answer to the knowledge behind it.

Ask the Console what happened.

Your access note tells you what is safe to view and change in this isolated demo property.

Full access, inside and out

Want the keys?

Tell us who you are. We review every request personally, then open the Sapphire Bay guest experience and its scoped Studio Console for approved visitors.

Access is not instant. The Console is included; that is why we check.

This is a fictional property. Want yours built from your own website? → How the pilot works