PROTÉGÉService before spectacle.
Every new capability must make a real guest-to-action journey clearer.
PROTÉGÉ product roadmap
Direction first. Availability confirmed separately.
The next request should be easier than the last.
The PROTÉGÉ roadmap follows a hospitality promise. However a guest expresses a need, the property should be able to understand it, own it, fulfil it and learn from the outcome.
Follow the pathRoadmap direction
No public release dates
The discipline
A roadmap should earn confidence.
Human authority stays visible.
Automation can prepare and route; people retain judgment where the moment requires it.
Readiness before breadth.
Permission, support, failure handling and commercial scope must mature with capability.
The path forward
The road ahead,
with purpose.
The sequence matters: make the request dependable, make access more natural, connect approved context, then help the property act earlier.
Earn the right to automate
Every request becomes one accountable service record.
Before voice, connections or prediction add value, the service journey must be dependable. The request needs context, reassurance, an owner, a visible promise and a verified outcome.
Property and stay context attached
Automatic or manual ownership
Handover history preserved
Closure and recovery confirmed
What this should change
A guest does not need to understand the hotel’s structure. The request reaches it without losing meaning.
Roadmap scenarioA spoken need.
An accountable outcome.
An accountable outcome.
Effective request handling
Every request should know what happens next.
In the intended voice-assisted experience, speed does not come from skipping steps. It comes from keeping the right steps connected.
0122:07
The guest speaks naturally.
“Could I have another blanket?” becomes a request without asking the guest to find the right department.
0222:07
Meaning and context travel together.
Intent, room, property, language and the live conversation form one service record.
0322:08
Reassurance comes first.
The guest hears what will happen next and when an update should arrive.
0422:08
Ownership is deliberate.
A property rule can prepare the right route, while a colleague can confirm or redirect it.
0522:19
Every handover keeps the promise.
The work, prior message, timing and exception history remain visible to the next responsible person.
0622:26
The outcome becomes useful.
Completion is confirmed with the guest, while the property retains a signal it can learn from.
Audio assistance
A natural voice for every responsibility.
Audio should adapt to the person and the moment. It should never create another disconnected inbox for the hotel to watch.
For the guest
Ask for help in the most natural way available, receive reassurance and continue the conversation without starting again.
For the team
Hear priorities, add a hands-busy update or request human help while the service record remains intact.
For the property
Receive concise briefings shaped to responsibility: what needs attention, why it matters and what changed.
Model Context Protocol
A standard doorway.
Carefully governed.
MCP is an open protocol for connecting AI applications with external context and tools. PROTÉGÉ is exploring that pattern selectively, giving approved capabilities a clearer path into the service experience.
The property chooses the connection.
A named system or capability is introduced for a defined hospitality purpose.
The boundary travels with it.
Only the context and tools appropriate to that connection should become available.
Risk still belongs to a person.
Sensitive, financial or ambiguous actions should surface human review rather than disappear into automation.
The outcome returns to the service story.
A connected action matters only when ownership, guest communication and result remain visible.
Intelligence in motion
Insight should travel with the person who needs it.
Audio briefings are intended to bring the right operational picture to the person who needs it in a concise, useful form.
Start of shift
What deserves attention now
Open risk, delayed promises and unresolved ownership.
During the day
What materially changed
Exceptions and decisions, not a stream of every update.
Across time
What the property is learning
Demand, recovery and operating patterns worth reviewing.
How capability earns priority
Dependability earns a place on the roadmap.
These are the questions that should shape sequence before a roadmap item becomes an offer.
01
Guest value
Does it make asking, understanding or reassurance meaningfully easier?
02
Operating fit
Can it respect the property’s responsibilities, language and service standards?
03
Human control
Can a person review, redirect or stop the action when judgment matters?
04
Trust boundary
Are permission, privacy and system responsibility explicit?
05
Supportability
Can it be implemented, monitored and recovered when something fails?
06
Measurable outcome
Can the property see whether the capability improved the service journey?
Roadmap language
Know what each word allows you to plan around.
Released
Usable and supported within written scope.
In development
Actively being built; not yet a general commitment.
Planned
Part of the intended path without a promised date.
Outside scope
Digital check-in, checkout and keys remain outside PROTÉGÉ.