rio-las-vegas-hotel-casino-name-addition-escalations.md
Edit- File length
- 723 B
- Created
- Apr 24, 2026, 6:15 p.m.
- Updated
- Apr 24, 2026, 6:15 p.m.
- Source
- View on GitHub ↗
RAG Context: Escalation guideline for Rio Las Vegas name additions / guest authorization. Includes guest asks, TAG classification, AI-handleable response, and escalation triggers.
A. Name additions / guest authorization
Guest asks:
- "Can you add a name to the reservation?"
- "Can someone else check-in before me"
- "Can I change the name on my stay"
TAG as name-addition
Respond with
Collect name, explain check-in/card requirements, note request
Escalate when:
- The guest wants to change the primary guest
- The guest wants a guarantee that another person can check in without the booker present
- There is any billing authorization / third-party payment / identity mismatch