PROTÉGÉNCIERGE | PROTÉGÉ
Ask what matters before you choose.
Straight answers for the people evaluating, approving, introducing and operating a guest experience platform.
From first fit to daily adoption, every answer leads to the part of NCIERGE that explains the point in full. Clear enough for the first conversation and detailed enough for a serious evaluation.
Property knowledge centre
Find the answer behind the decision.
Platform and fit
What PROTÉGÉ is, where it sits and when it belongs in a property.What is NCIERGE PROTÉGÉ?
PROTÉGÉ is NCIERGE’s accommodation focused guest experience platform. It connects guest intent, Front of House response, Back of House fulfilment and management visibility while keeping each audience in a view designed for its responsibility.
Is PROTÉGÉ a property management system or PMS?
No. PROTÉGÉ is not a PMS and does not try to become the property’s reservation, folio or room inventory backbone. It focuses on the service experience that begins when a guest needs something and continues until the property can see the outcome.
Which accommodation businesses is PROTÉGÉ designed for?
The platform is being shaped for accommodation led hospitality, including hotels, resorts, motels, extended stay properties, serviced residences, chalets, cabanas and comparable lodging operations. Fit depends more on service ambition and operating readiness than category labels alone.
What operational problem does PROTÉGÉ solve first?
It addresses the loss of context between a guest request, the person who receives it, the team that fulfils it and the leader who needs to understand the result. The aim is fewer blind spots, clearer ownership and a service history that survives handovers.
What are À Vous, Salle, Coulisses and EnVue?
They are role specific experiences within PROTÉGÉ. À Vous serves the guest, Salle serves Front of House, Coulisses serves Back of House, and EnVue gives leadership an operational and performance view. They are modules, not separate NCIERGE products.
Does PROTÉGÉ replace every hotel operating tool?
No. A credible deployment keeps useful systems in place and defines where PROTÉGÉ adds continuity. It may begin beside existing tools, connect with supported platforms, or cover a service gap where no suitable system exists today.
How is PROTÉGÉ different from a digital concierge or hotel app?
A guest interface is only one part of the proposition. PROTÉGÉ is designed to preserve the operating thread behind that interface, including responsibility, progress, escalation, completion and management learning. The value is not the menu; it is what happens after a request is made.
Where will PROTÉGÉ be offered first?
The initial commercial focus is the United States and Canada, with expansion into other international markets as operational support and product readiness grow. Market availability will be confirmed rather than implied.
Is PROTÉGÉ the NCIERGE restaurant product?
No. PROTÉGÉ is the accommodation led product family. Bon Appette is the planned NCIERGE direction for restaurant and table service guest experience, and it remains separate so each product can stay clear in purpose.
How should a property evaluate whether PROTÉGÉ belongs on its shortlist?
Bring one service journey that currently loses time, ownership or visibility. Test whether PROTÉGÉ makes the guest path simpler, team responsibility clearer and the outcome easier to measure without creating duplicate work.
À Vous
The property view of the guest experience and service access.What does À Vous give a property’s guests?
À Vous gives guests one property branded place to understand services, make requests, follow recent activity and access relevant stay information. The experience is intended to feel like the hotel within reach, not another directory to navigate.
Can a property offer À Vous without forcing an app download?
The product direction supports both app and app less guest access so a property can meet different guest preferences. The exact access method and available functions are confirmed during deployment planning.
Does À Vous include digital check in or digital checkout?
No. Digital check in and digital checkout are not part of the current PROTÉGÉ scope. À Vous concentrates on guest information, service access, requests, communication and experience continuity during the stay.
Does PROTÉGÉ provide a digital room key?
No. A digital room key is not part of the system. Properties should continue to use their approved access control and key systems while evaluating PROTÉGÉ for the guest service journey it is designed to support.
Can À Vous reflect the identity of an individual property?
The guest experience is intended to present the property, its services and local context clearly within the NCIERGE PROTÉGÉ environment. Branding depth, content ownership and configuration are defined with the property during evaluation.
Can À Vous make hotel Wi Fi details easier for guests to find?
Yes, where the property chooses to publish approved connection information. À Vous can present the network name, access guidance and relevant credentials in one clear guest facing path without changing the property’s network security model.
What housekeeping requests can a property expose through À Vous?
A property may configure relevant options such as room cleaning, towels, linen, amenities, turndown, preferred timing, Do Not Disturb exceptions and special requests. Enabled choices should match what the operation can actually fulfil.
Can guests see what happened after they made a request?
The experience is designed to keep relevant request progress visible so the guest is not left wondering whether the property received it. What is shown depends on the workflow and status language configured by the property.
How can À Vous support guest feedback and reputation?
The property can invite private feedback while there is still time to respond. Strong satisfaction may continue toward an approved public reputation destination, while lower scores can open a more useful recovery conversation within the property’s process.
How much control does the property retain over what guests can request?
The property defines the services, descriptions, availability, operating windows and fulfilment rules offered through its experience. The interface should promise only what the team has chosen and is prepared to deliver.
Salle
Front of House awareness, response, handovers and service recovery.What is Salle within PROTÉGÉ?
Salle is the Front of House operations experience. It is intended for the people responding around the guest environment, including reception, concierge, guest relations, lobby, bell, valet, runners and duty leadership according to property configuration.
Why is Salle designed for people who are moving through the property?
Front of House work happens beside arrivals, queues, luggage, rooms and conversations. Salle is designed to put current priorities and useful context in reach so colleagues can spend less time returning to a fixed screen and more time present with guests.
Can Salle help a reception team see what needs attention now?
That is a core design aim. A role appropriate view can bring forward arrivals, waiting guests, guest requests, room changes, unresolved issues and priority cases without making every colleague interpret the entire operation.
How does Salle support concierge work?
Salle can keep guest requests, reservations, transport, experiences, special arrangements and follow ups together in the concierge context. The goal is to preserve the conversation and next action as responsibility moves between people.
How can Salle improve service recovery before a poor review appears?
A concern can be made visible to the responsible Front of House colleague, followed through the response and escalated when time or severity requires it. Earlier awareness gives the property a better chance to recover the experience while the guest is still present.
What happens to open Front of House work at shift change?
The intended workflow keeps the request, owner, current status and relevant notes available for a deliberate handover. The next shift should inherit an operating memory, not a collection of disconnected messages.
Can Salle cover bell, valet and lobby workflows as well as reception?
Yes, these Front of House roles are part of the intended scope where enabled by the property. Each view can concentrate on its own flow while sharing relevant arrivals, guest priorities and handovers with the wider service operation.
Where does room dining delivery sit between Salle and Coulisses?
Preparation belongs behind the scenes in Coulisses; guest facing delivery and contact may belong in Salle. PROTÉGÉ is designed to keep the handoff intact so completed preparation does not wait unseen and the guest receives a coherent service.
Does every Front of House colleague see the same Salle screen?
The design direction is role aware. A lobby host, concierge, runner, guest relations colleague and duty manager need different priorities, permissions and depth. Shared context should not mean unnecessary visibility.
What should a property expect Salle to improve?
The practical test is whether Front of House can recognize priority sooner, respond with better context, hand work over cleanly and close the loop with less searching. Any claimed improvement should be measured against the property’s own starting point.
Coulisses
Back of House fulfilment across rooms, facilities, stores and production.What is Coulisses within PROTÉGÉ?
Coulisses is the Back of House operations experience. Its name refers to what happens behind the scenes, where teams prepare, deliver, maintain and complete the work that makes the visible guest experience possible.
Why is the Back of House module called Coulisses rather than Cuisine?
Cuisine suggests kitchen and culinary work only. Coulisses is broader. Kitchen remains inside the module, alongside housekeeping, laundry, engineering, maintenance, stewarding, stores, receiving and other configured Back of House functions.
Which hotel departments can operate through Coulisses?
Potential areas include housekeeping, laundry, engineering, maintenance, stewarding, stores, inventory, receiving, internal logistics, kitchen production, room service preparation and operational safety. Enabled departments depend on each property’s configuration.
How can Coulisses support room attendant routing?
A room attendant view can organize assigned rooms, checkout priorities, stayover work, requested amenities and reported issues. Intelligent assistance may help suggest the next practical move, while property rules and supervisors retain control.
Can Coulisses manage guest impacting maintenance work?
The intended experience can receive, prioritize, assign and track operational faults and work orders, including issues in occupied rooms. It is not a substitute for every specialist engineering system, but it can protect the guest service thread around the work.
How does Coulisses handle laundry and linen operations?
A configured view may cover guest laundry, pickups, pressing, delivery, linen replenishment and shortage signals. The purpose is to keep demand, ownership and readiness visible before a missing item becomes a guest facing delay.
Can stores and receiving teams use Coulisses?
They are within the intended Back of House scope. Stock requests, incoming items, transfers, low stock, approval holds and replenishment can be presented in a role appropriate operating view when the property enables those workflows.
Does the move from Cuisine to Coulisses reduce kitchen functionality?
No. Kitchen remains an important operating area inside Coulisses. The broader name simply places culinary production, pass coordination, special diets and pickup handovers within the complete Back of House environment they already depend on.
How are delayed or urgent Back of House tasks surfaced?
Configured priorities, operating targets and escalation rules can bring attention to work at risk. The goal is to direct the responsible person early and preserve the reason for urgency, especially when the issue can affect a guest or room readiness.
What should a property measure when evaluating Coulisses?
Useful measures may include response time, completion time, overdue work, room readiness, reassignments, repeated faults and the quality of handovers. The right measure is the one tied to the property problem selected for evaluation.
EnVue
Operational oversight, management briefings and measurable outcomes.What is EnVue within PROTÉGÉ?
EnVue is the management and intelligence experience. It turns live service signals into a clearer view of priorities, operating health, guest recovery, room readiness, team load and performance according to a leader’s responsibility.
Does EnVue show the same information to every manager?
No. A duty manager, Front Office leader, executive housekeeper, operations leader and general manager need different depth and focus. EnVue is designed around the decision a person must make, not a single dashboard copied across roles.
Can EnVue show what is happening across the property now?
The live operating view is intended to bring together active requests, rooms at risk, service recovery, workload, arrivals and escalations from enabled PROTÉGÉ workflows. It does not invent visibility into systems or departments that are not connected.
Can EnVue produce a useful management briefing?
That is part of the product direction. A briefing should summarize what changed, what needs intervention and why it matters, using the property’s operating context. It should lead to a decision, not simply repeat dashboard numbers.
Will EnVue support hotel groups or multiple properties?
Multi property oversight is a relevant direction for EnVue, but its availability and depth must be confirmed for the proposed deployment. Group reporting only has value when definitions and data quality remain comparable across properties.
Which guest experience measures can EnVue make visible?
Depending on enabled workflows, EnVue may show request demand, response and completion, service recovery, feedback, sentiment, room readiness and operating exceptions. Measures should be defined with the property so a number has an agreed meaning.
Is EnVue a revenue management or financial reporting system?
No. EnVue is centred on guest experience and operational intelligence. Relevant business context may be brought into a supported view, but PROTÉGÉ does not replace specialist revenue management, accounting or financial reporting platforms.
Can quality and assurance teams use EnVue?
The intended management scope includes service standards, training status, operational exceptions, inspection signals and recovery outcomes where configured. Formal audit requirements and evidence controls should be confirmed during evaluation.
Can leadership understand the property while away from a desk?
EnVue is designed to communicate through the moment of use, from immediate operating awareness to a deeper review. The experience is defined by purpose rather than by a specific device category.
What makes EnVue more useful than another dashboard?
Its value depends on whether it explains the operating story behind a signal and directs attention to a meaningful next step. More charts are not the objective. Faster understanding, better intervention and clearer accountability are.
AI assistance
How contextual assistance supports judgment without replacing it.What role does AI play inside PROTÉGÉ?
AI is being designed as a contextual assistance layer across the guest experience, operations and management. It can help interpret signals, summarize context, suggest priorities and support communication while accountable people remain responsible for decisions and service.
Is NCIERGE using AI to replace hotel teams?
No. The product direction is to give people better awareness and assistance, not remove hospitality judgment. A colleague who understands the guest, the property and the moment remains essential.
Can PROTÉGÉ assign a request to the right person automatically?
The workflow direction includes rule based and assisted routing according to service type, department, role, availability and property policy. Manual assignment and human override remain important where judgment or an exception is involved.
How can AI help a hotel decide what should happen first?
It may consider urgency, guest impact, waiting time, service targets, dependencies, room state and available team context. A recommendation should explain why something matters so the responsible person can accept, change or reject it.
How will NCIERGE reduce incorrect AI recommendations?
The intended approach is to ground assistance in authorized property context, limit actions by role and workflow, preserve source signals, and keep human review where consequences matter. Exact controls will be documented as capabilities reach deployment readiness.
Will a manager know why the AI made a recommendation?
That is the standard NCIERGE is working toward. A recommendation should point to the conditions that shaped it, such as a delayed room, rising queue or unresolved recovery case, rather than appear as an unexplained instruction.
Will PROTÉGÉ support voice or audio assistance?
Audio assistance for guests, teams and leadership is an intended roadmap direction, not a blanket promise of current availability. The experience must respect privacy, environment, language and the operating role before release.
Is Model Context Protocol or MCP part of the PROTÉGÉ roadmap?
MCP is part of the stated platform direction for governed connections between intelligence and approved tools or context. Its practical use, security model and availability will be validated before it is presented as a deployable capability.
Can PROTÉGÉ predict service problems before they happen?
Prediction is an intended intelligence direction where sufficient, trustworthy operating signals exist. The immediate value begins with earlier recognition of risk and clearer preparation. Forecasts should express confidence and limits rather than pretend certainty.
How much data does the AI need before it becomes useful?
Some assistance can begin with property rules, service definitions and current workflow context. Deeper patterns require reliable history and consistent status use. The evaluation should distinguish immediate assistance from intelligence that must be earned over time.
Integration and deployment
Standalone use, existing systems, configuration and rollout.Can PROTÉGÉ work if a property has no PMS?
A standalone starting point is part of the platform approach. The property can define selected guest service and operating workflows without pretending a missing PMS function exists. Scope must remain clear so PROTÉGÉ does not become an accidental replacement for a hotel core.
Can PROTÉGÉ work beside an existing PMS?
Yes, that is a central deployment question. PROTÉGÉ can begin beside the hotel core and connect through supported, secure methods where a useful integration is available. The property should not be asked to enter the same information twice without a reason.
Which property management systems does PROTÉGÉ integrate with today?
Supported connectors will be published only when they are validated and supportable. NCIERGE welcomes integration requests from properties and established hospitality platforms, but a requested connection should not be described as available before confirmation.
How does NCIERGE avoid creating another system the team must update?
The deployment should decide which system owns each piece of information, what PROTÉGÉ needs to receive, and where an outcome should return. If duplicate entry remains, its purpose and burden should be visible before rollout.
How will PROTÉGÉ connect with approved hotel systems?
The preferred method is an established, secure and documented interface appropriate to the partner system and use case. Integration scope, data direction, ownership, failure handling and support responsibility must be agreed rather than assumed.
What must be defined before a PROTÉGÉ implementation begins?
The property should agree the first journey, enabled roles, service catalogue, ownership rules, escalation logic, content, integrations, access boundaries, success measures, training plan and evaluation period. Clear scope protects both speed and trust.
How long does a PROTÉGÉ deployment take?
There is no responsible single answer before scope is known. A focused standalone journey and a multi property integrated rollout carry different work. Founding evaluations will define timing after reviewing content, systems, teams and operational complexity.
Can each property configure different services and workflows?
That is the intended model. Properties differ in outlets, departments, hours, service promises, roles and escalation standards. Configuration should preserve those realities while keeping the underlying service logic coherent.
Does PROTÉGÉ require proprietary hotel hardware?
PROTÉGÉ is presented as a software experience across guest, team and management contexts. Any device, infrastructure or external service requirement for a particular deployment must be identified and agreed during the evaluation rather than hidden inside a platform claim.
Can a hospitality technology company propose an integration with NCIERGE?
Yes. NCIERGE welcomes established systems, specialist platforms and teams solving a credible hospitality problem. A useful partnership begins with the guest or operating outcome and a secure, supportable way for both systems to contribute.
Trust and governance
Data boundaries, accountability, access and responsible operation.What information will PROTÉGÉ need from a property?
The answer depends on enabled workflows. NCIERGE’s principle is to use the property, service, role and guest context necessary for the agreed experience, not collect information merely because it may be available.
Who owns property and guest information in PROTÉGÉ?
Formal ownership, controller, processor and permitted use terms will be set in the applicable agreement and privacy documentation. A property should not rely on assumptions; these responsibilities must be clear before production use.
Can access be limited by hotel role and responsibility?
Role appropriate access is a core product principle. A person should see the information and actions required for their work, while sensitive or management context remains limited to authorized responsibilities.
Will a property be able to see who handled a request?
Traceable ownership and status history are central to the intended service record. The exact audit depth, retention and export available in a release must be confirmed during a formal product review.
What security documentation will NCIERGE provide?
Security, architecture, hosting, access, data handling, incident and supplier documentation will become more specific as PROTÉGÉ approaches production readiness. Procurement claims will be tied to evidence available at that stage.
Where will PROTÉGÉ property data be hosted?
Hosting region and data residency must be confirmed for the property, market and selected service before deployment. NCIERGE will not imply a location that has not been contractually and technically established.
How will data retention and deletion be handled?
Retention should follow the purpose of the workflow, property obligations and the agreed service terms. Production documentation will define periods, deletion paths, backups and legal exceptions before live data is entrusted to the platform.
Will property or guest data be used to train public AI models?
That question requires an explicit contractual and technical answer for the services used in deployment. NCIERGE’s stated direction is governed assistance with clear data boundaries, not undisclosed reuse. Final terms must identify any model provider and permitted processing.
How will NCIERGE handle a security or service incident?
A production relationship will require documented detection, response, communication, recovery and responsibility. The exact commitments belong in approved operational and contractual material, not an unsupported marketing promise.
Is accessibility part of the PROTÉGÉ product standard?
Yes, accessibility is treated as a product quality rather than an optional visual setting. Specific supported standards, assistive technology behaviour and testing evidence will be documented as each experience reaches release readiness.
Founding access
Selection, cost, evaluation and the path toward commercial release.What does founding access mean for a hotel property?
It is a limited, structured opportunity to evaluate PROTÉGÉ with NCIERGE before commercial release. The property contributes real operating context, team participation and useful feedback; NCIERGE evaluates fit and supports an agreed early scope.
Is the PROTÉGÉ licence free during founding access?
For selected founding properties, NCIERGE will not charge a commercial platform licence fee during the agreed evaluation. This position applies to the founding programme and does not define future commercial pricing.
What costs may still apply during founding access?
AI tokens, system resources, cloud storage or processing, human specialist time and necessary external services may carry an agreed cost. Any applicable amount should be fair, itemized and approved before it is incurred.
How will NCIERGE select founding properties?
Selection considers the operating problem, the person prepared to lead, team readiness, available attention and whether the proposed evaluation can produce meaningful learning. Property size alone does not decide fit.
Does joining the waiting list guarantee founding access?
No. A submission begins a review and conversation. Founding access is intentionally limited, and both the property and NCIERGE must agree that the problem, team, timing and evaluation scope are suitable.
What information should a property provide when joining the waitlist?
NCIERGE asks for the property type, location, approximate scale, current systems, the person driving change, team readiness and one guest or operating journey worth improving. A concrete problem makes the first conversation more useful.
When will commercial PROTÉGÉ pricing be announced?
NCIERGE has not published a commercial release date or price. Commercial terms will be announced separately when the product, support model and deployment scope are ready to be priced responsibly.
How long will a founding property evaluation last?
The period will be agreed after scope review. It should be long enough to observe real use and short enough to keep ownership, feedback and decisions active. No standard duration should be assumed before the property journey is defined.
What does NCIERGE expect from a founding property?
A named internal lead, honest operating context, access to the relevant team, timely feedback and willingness to test agreed changes. Founding access is collaborative product evaluation, not passive free software use.
What happens after a property submits the founding access form?
A hospitality specialist reviews fit, timing and operating readiness. If there is a credible starting point, NCIERGE invites a conversation about the team, current systems, first journey, resource needs and mutual evaluation decision.
People and adoption
Leadership, training, change readiness and daily team use.Who should lead a PROTÉGÉ evaluation inside the property?
The strongest lead has authority to connect guest experience, operations, technology and daily team reality. The title matters less than the ability to make decisions, resolve ownership and keep the evaluation moving.
How ready does the hotel team need to be before implementation?
The team does not need every answer, but it must be willing to describe current work honestly, test a clearer method and give useful feedback. A technology rollout cannot repair ownership that leadership is unwilling to address.
How should a property handle staff resistance to another system?
Begin with a problem the team already feels and remove visible friction from that journey. Explain what becomes easier, involve the people doing the work, keep roles clear and avoid launching more scope than the property can support.
What training will hotel teams need for PROTÉGÉ?
Training should follow the person’s role and actual decisions, not a tour of every screen. The founding scope will identify required workflows, operating rules, escalation responsibilities and the support needed to use them with confidence.
Must a property rewrite its standard operating procedures before using PROTÉGÉ?
Not necessarily. The evaluation should first identify which existing standards remain useful, where practice differs and which workflow needs clarification. Technology should make a sound operating method easier to follow, not disguise a missing one.
Should a property launch every PROTÉGÉ module at once?
Not by default. A focused journey can reveal whether the shared service logic works before wider expansion. The right sequence depends on the property’s problem, team capacity, integration needs and the evidence required for a confident decision.
How should a property define success before the evaluation starts?
Choose a small set of observable outcomes tied to the starting problem, such as faster ownership, fewer missed handovers, clearer status, improved recovery or reduced search time. Agree the baseline and evidence before judging the result.
Can hotel leaders override automation or AI suggestions?
Human control is an important operating principle. Property rules, permissions and escalation paths should define where automation may act, where approval is required and who can change an assignment or recommendation.
Can a hospitality consultant support a property’s PROTÉGÉ evaluation?
Yes, where the property authorizes the role and the consultant contributes genuine operating or implementation expertise. NCIERGE also welcomes partnership conversations with experienced hospitality professionals who can help make change practical.
What should a property bring to its first NCIERGE conversation?
Bring one difficult guest journey, how it works today, the people involved, the systems touched and what a better outcome would look like. That is enough to test fit without turning the first meeting into a generic software presentation.