THE GUEST EXPERIENCE
Your hotel,
wherever guests ask.
Telephone, web and mobile first. In-room tablets when you want them.
CHOOSE THE CHANNEL
One companion. Different ways in.
Answer the call. Keep the context.
Natural voice conversations for questions, recommendations and supported requests. Routing and transfers are scoped for your hotel.
“We’d love a special dinner.”
Hotel CompanionIllustrative voice interactionGUEST EXPERIENCE. TEAM OWNERSHIP.
Your team gets the next step.
The request, the context and the confirmation. Follow one dinner from conversation to recorded outcome.
YOUR HOTEL · GUEST COMPANIONDinner for two
Restaurant · Room 204
Anniversary · Quiet table · Vegetarian option
- Requested time
- 8:00 pm
- Next step
- Restaurant review
The guest’s words. The useful details.
An interest becomes a request. It is not a confirmed booking.
Illustrative workflow and sample amounts. Supported actions and team routing are agreed for each hotel.
See the actual staff request screen
Product interface with test data; identifiers and timestamps are masked. This example shows a housekeeping request and its staff-controlled status changes.
What if the guest needs a person?
A human handoff, with context.
Complaints, sensitive requests and a request for a person go to the agreed team. The handoff includes the guest’s request, relevant context and what remains unresolved. Offers pause during sensitive interactions.
Before launch, agree who receives each handoff, the channel, coverage hours and the backup when nobody is available. Telephone transfers are tested for your routing setup.
What if a connection cannot confirm the action?
Pending stays pending.
“I can’t confirm that time yet. Your hotel team needs to check it.”
The rollout plan defines checks, support contacts, notification destinations and recovery steps. An unconfirmed action is not presented as booked, paid or completed. Automatic retries for payments or bookings require safeguards against duplicates.
BEFORE YOU LAUNCH
A few practical details.
Do guests need an app or a tablet?
No app download is required for mobile or desktop web. Guests use a link or QR code. Tablets are optional; the hotel covers hardware, setup and agreed device support. Voice availability depends on device, browser and configuration.
What about telephone and WhatsApp?
Telephone routing, transfers and supported actions are validated for each property. WhatsApp is an additional connection to assess, not an automatically enabled channel.
How are languages and voice checked?
We agree the first guest languages, voice channel and hotel vocabulary, then test real questions, accents, names and handoffs with your team. A voice misunderstanding should lead to clarification or the agreed human route. Website voice also depends on browser and microphone support; guests can type instead. Channel and language coverage are signed off before launch.
THE OUTCOME-BASED PILOT
Start with one hotel.
Pay for proven value.
No upfront software or standard setup fee for a qualified pilot. Agree how value is measured before launch. No verified lift means no success fee.
Success fee: an agreed share of additional contribution after costs. Custom connections and optional hardware priced separately.