Decision owner
Duty manager
The named role remains accountable for the consequential decision.
Travel & Hospitality
Designed for Frontline employee
Equip frontline hospitality staff to resolve guest requests on the spot using property knowledge, standard operating procedures, reservation context, and guest preferences, with manager approval for compensation beyond service authority.
Contract TRV-03 · primary aggregate GuestServiceRequest · mode loading
Decision brief
This brief starts with the decision, evidence, and accountable owner. The guided workflow then shows how the recommendation was produced.
The evidence and control points that shape this recommendation.
Decision owner
Duty manager
The named role remains accountable for the consequential decision.
Governed evidence
6 record types
Structured records and cited text ground the recommendation.
Workflow
5 controlled stages
Each transition records its input, output, status, and audit context.
Human controls
1 approval gate
Approval gates prevent the copilot from making consequential decisions.
A guest messages at 22:40 that their room air conditioning is failing; the copilot shows the suite is on a package rate with late checkout included, cites the SOP requiring an engineering visit within 20 minutes and a room move if unresolved, surfaces the guest's prior noise complaint, and routes the proposed one-night rate adjustment to the duty manager because it exceeds the agent's authority limit..
Equip frontline hospitality staff to resolve guest requests on the spot using property knowledge, standard operating procedures, reservation context, and guest preferences, with manager approval for compensation beyond service authority.
Approved gesture posted to the folio with justification gives Duty manager the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Step 1 of 5
| Field | Value |
|---|
| Field | Value |
|---|
The output appears here immediately. More technical evidence remains available below.
The demonstration keeps deterministic controls, AI assistance, and approval separate.
Source systems enforce identity, workflow order, policy filters, and record updates.
Retrieval and generation assemble relevant evidence into a cited recommendation or draft.
Duty manager verifies material claims and approves the consequential action.
Run the stages in order before using the Copilot. Every stage explains what happens, why it matters, the evidence it uses, and the complete API request and response.
Automated stage
What happens: Frontline employee performs capture the guest request using Guest message, call, or in-person request and produces GuestServiceRequest with room and urgency. The transition is deterministic and does not require autonomous model approval.
Why it matters: GuestServiceRequest with room and urgency gives Stay context service the evidence needed to begin Load reservation and guest preferences, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/capture-the-guest-request
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Stay context service performs load reservation and guest preferences using Reservation identifier and guest profile and produces Stay context with inclusions and preferences. The transition is deterministic and does not require autonomous model approval.
Why it matters: Stay context with inclusions and preferences gives Retrieval agent the evidence needed to begin Retrieve property knowledge and SOP, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/load-reservation-and-guest-preferences
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Retrieval agent performs retrieve property knowledge and sop using Request kind and property scope and produces Verified property facts and applicable SOP steps. The transition is deterministic and does not require autonomous model approval.
Why it matters: Verified property facts and applicable SOP steps gives Hospitality copilot the evidence needed to begin Guide the resolution at the point of service, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/retrieve-property-knowledge-and-sop
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Automated stage
What happens: Hospitality copilot performs guide the resolution at the point of service using SOP steps, inclusions, and preferences and produces Cited response with the staff member's authority limit shown. The transition is deterministic and does not require autonomous model approval.
Why it matters: Cited response with the staff member's authority limit shown gives Duty manager the evidence needed to begin Approve compensation beyond authority, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/guide-the-resolution-at-the-point-of-service
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Human approval required
What happens: Duty manager performs approve compensation beyond authority using Proposed ServiceRecoveryAction and value and produces Approved gesture posted to the folio with justification. A named human approver must review the evidence before the transition completes.
Why it matters: Approved gesture posted to the folio with justification gives Duty manager the evidence needed to begin the final governed business outcome, with the decision trail retained for review.
Loading relevant sample records.
Ready to run.
POST /api/domain/workflow/approve-compensation-beyond-authority
Run this API to see its formatted outcome.
| Field | Value |
|---|
| Field | Value |
|---|
Run a stage to see its explanation, evidence, full request, and full response.
Ask a question and receive an answer grounded in retrieved GuestServiceRequest evidence.
Select a starter question or enter your own.
Loaded live from /api/config, /api/domain/model, and
/api/domain/sample.
guestServiceRequests/tenantId + /propertyIdA guest messages at 22:40 that their room air conditioning is failing; the copilot shows the suite is on a package rate with late checkout included, cites the SOP requiring an engineering visit within 20 minutes and a room move if unresolved, surfaces the guest's prior noise complaint, and routes the proposed one-night rate adjustment to the duty manager because it exceeds the agent's authority limit.
| Container | Role | Hierarchical partition key | Document types |
|---|---|---|---|
guestServiceRequests |
Primary | /tenantId + /propertyId |
GuestServiceRequest, ReservationContext, PropertyKnowledgeItem, ServiceRecoveryAction |
hospitalitySopLibrary |
Reference | /tenantId + /requestKind |
StandardOperatingProcedure |
guestProfileStore |
Reference | /tenantId + /guestProfileId |
GuestPreferenceRecord |
| Type | Container | Partition key | Identifier pattern | Embedding fields |
|---|---|---|---|---|
GuestServiceRequest |
guestServiceRequests |
/tenantId + /propertyId |
request::{propertyId}::{requestId} |
requestTextVector |
ReservationContext |
guestServiceRequests |
/tenantId + /propertyId |
reservation::{propertyId}::{reservationId} |
None |
PropertyKnowledgeItem |
guestServiceRequests |
/tenantId + /propertyId |
knowledge::{propertyId}::{itemId} |
bodyVector |
StandardOperatingProcedure |
hospitalitySopLibrary |
/tenantId + /requestKind |
sop::{requestKind}::{sopId}::{stepIndex} |
stepVector |
GuestPreferenceRecord |
guestProfileStore |
/tenantId + /guestProfileId |
guestpreference::{guestProfileId} |
None |
ServiceRecoveryAction |
guestServiceRequests |
/tenantId + /propertyId |
recovery::{propertyId}::{actionId} |
None |
Read the open requests and the reservation context for the stay in one partition-aligned query. Guest preferences follow the guest across properties, so they are read from the guestProfileStore container by guestProfileId instead of being duplicated into every property partition.
guestServiceRequests
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.propertyId = @propertyId AND c.type IN ('GuestServiceRequest','ReservationContext','GuestPreferenceRecord') ORDER BY c.urgencyLevel DESC
Return only property knowledge that is in its validity window and recently verified.
guestServiceRequests
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.propertyId = @propertyId AND c.type = 'PropertyKnowledgeItem' AND c.validFromUtc <= @nowUtc AND c.validToUtc > @nowUtc ORDER BY c.lastVerifiedUtc DESC
Knowledge-container query against hospitalitySopLibrary (partition-aligned to /tenantId + /requestKind): pull the SOP steps and authority limits for the specific request type; the library stores one SOP document per request kind so the lookup is a single partition read.
hospitalitySopLibrary
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.requestKind = @requestKind AND c.type = 'StandardOperatingProcedure' AND c.revisionStatus = 'current' ORDER BY c.stepIndex ASC
Show service recovery gestures waiting on duty-manager sign-off.
guestServiceRequests
single-partition
SELECT * FROM c WHERE c.tenantId = @tenantId AND c.propertyId = @propertyId AND c.type = 'ServiceRecoveryAction' AND c.approvalState = 'pendingApproval' ORDER BY c.monetaryValue DESC