RAG Context: Section 2 general escalation rules for Flamingo Las Vegas routine guest-service requests — Name Additions & Guest Authorization, Stay Modifications & Cancellations, Invoice/Folio/Receipt Requests, Room Issues & Housekeeping, Maintenance Requests, Noise/Neighbor/Safety Complaints, Billing Issues & Charge Disputes, and General Complaints & Compensation Requests. For each: trigger phrases and a clear split between what the LLM responds to directly versus what it escalates to a human Concierge. Safety, medical, injury, theft, and billing-dispute messages always escalate. The on-site Security Team is available 24/7 at 702-733-3523. Part of the master framework in flamingo-las-vegas-hotel-casino-escalations.md.

Section 2 — General Escalation Rules

These rules apply to routine guest-service requests that arrive via message. The LLM should acknowledge professionally, provide any information it can, and escalate when the situation requires human action or decision-making.

E — Name Additions & Guest Authorization

Trigger Phrases

• "Can you add a name to my reservation?"
• "Can someone else check in before I arrive?"
• "Can I change the name on my booking?"

flamingo customer-phone-number

RAG Context: Escalation guideline for Flamingo Las Vegas guest messages where the guest's message contains a phone number — i.e. the guest supplies a phone number (their own cell / mobile, a callback number, an alternate contact, or someone else's) or asks to be called or texted at a number (e.g. "Please call me at (702) 555-0199."). The Flamingo automated assistant operates on text-messaging and post-stay review channels and cannot place or receive phone calls or SMS; a guest sharing a personal phone number is requesting — explicitly or implicitly — direct human or voice contact, and is supplying personal contact information (PII) that a person must handle. Every guest message that contains a phone number is therefore an immediate, always-on escalation to a human Concierge. Maps to risk category CUSTOMER PHONE NUMBER (tag CUSTOMER-PHONE-NUMBER) in the master Flamingo Risk Management Framework (flamingo-las-vegas-hotel-casino-escalations.md). All matches require immediate escalation. Do not call or text the number, and do not repeat the full number back in a public reply — acknowledge and route to a human.

Customer-Supplied Phone Number

Guest asks / says:

• "Please call me at (702) 555-0199."
• "My cell is 702-555-0142 — call anytime."
• "Can someone reach me at +1 555 867 5309?"
• "Text me at 5550100123."
• "Here's my number: 555-0188, please follow up by phone."
• "Call my husband at 702.555.0177 to sort this out."
• "I'd rather talk — my number's 555 0150."

Trigger keywords (non-exhaustive): call me at, reach me at, text me at, my number is, my cell is, my mobile is, here's my number, you can reach me on, call my [husband / wife / assistant] at, call me back, give me a call — plus any digit sequence formatted as a phone number in the guest's message: (NPA) NXX-XXXX, NPA-NXX-XXXX, NPA.NXX.XXXX, 7-digit NXX-XXXX, international +CC … / +1 NPA NXX XXXX, or a bare 10-/11-digit run.

Disambiguation: This category fires when the guest supplies or shares a phone number (or asks to be contacted at one). A guest asking for the property's phone number ("what's the front-desk / pool / spa number?") is a routine information request — answer from flamingo-las-vegas-hotel-casino-property-details.md, do not tag here. Do not over-trigger on non-phone digit strings: reservation / confirmation numbers, Caesars Rewards numbers, room numbers, dates, and dollar amounts are not phone numbers. Tag only when the digits are presented as a phone / contact number or paired with a call/text request. When a message both shares a number and raises another issue (billing, safety, complaint), apply both tags.

TAG as customer-phone-number

Respond with

Thank the guest and let them know a team member will follow up. Send a holding reply only (e.g. "Thank you — I've passed your details to our team and someone will be in touch."). Never state that a call or text has been placed, returned, or scheduled for a specific time; do not call or text the number yourself; and do not echo or repeat the full phone number back in the reply — especially on a public review channel — treat it as private contact information.

Before escalating

Do not call or text the guest and do not promise a specific callback time. The LLM is authorized to acknowledge only. Capture in the escalation record: the guest's exact wording, the phone number provided and whose number it is (guest / spouse / assistant), any preferred call or text window, the reason they want to be contacted, the inbound channel, and full reservation details — so the Concierge can make voice/SMS contact.

Escalate when:

• Always. Any guest message that contains a phone number, or any request to be called or texted, is an immediate escalation so a human can make voice/SMS contact and handle the personal contact details — regardless of the reason, tone, or topic. The LLM has no ability to place or receive calls or texts.
• If the phone number accompanies a sensitive issue (safety, injury, theft, health, harassment, legal, billing dispute), escalate under both this tag and the relevant risk-category guide, and flag the higher-severity tier.
• Tag the conversation: [CUSTOMER-PHONE-NUMBER] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue with priority flag.

RAG Context: Master escalation framework for Flamingo Las Vegas automated guest messaging and post-stay reviews. Defines the core operating principle (the LLM handles routine information and upsell conversations up to — but not including — the moment a guest commits or a sensitive situation arises, then sends a holding reply and generates a human-Concierge escalation email), the required fields for every escalation email, and a quick-reference decision table. Detailed decision rules live in the companion documents: flamingo-las-vegas-hotel-casino-upsell-escalations.md (Section 1), flamingo-las-vegas-hotel-casino-general-escalations.md (Section 2), and flamingo-las-vegas-hotel-casino-review-response-escalations.md (Section 3). Serious guest-reported incidents (injury, theft, health, security, harassment, hygiene, legal) route through the detailed risk-category guides listed below; any guest confirmation or acceptance of a fee or charge routes through the always-escalate fee-confirmation guide (CONFIRM-FEE).

Flamingo Las Vegas — Escalation Decision Rules

Escalation decision rules for automated guest messaging and post-stay reviews.

How to Use This Guide

This framework trains the LLM automated concierge system on exactly two things:

• When to respond directly to a guest message without human involvement.
• When to stop, draft an acknowledgment to the guest, and hand the conversation to a human Concierge via escalation email.

Core operating principle: The LLM handles routine information requests and upsell conversations up to — but not including — the moment a guest commits or a sensitive situation arises. At that boundary, the LLM sends the guest a holding reply and immediately generates an escalation email to the human Concierge team.

Companion Documents

• Section 1 — Upsell Escalation Rules: flamingo-las-vegas-hotel-casino-upsell-escalations.md (Early Check-In, Late Check-Out, Connecting Rooms, Room Upgrade / Stay Extension). Escalate only after confirmed guest intent to purchase/proceed.
• Section 2 — General Escalation Rules: flamingo-las-vegas-hotel-casino-general-escalations.md (Name Additions, Stay Modifications, Invoice/Folio, Room Issues, Maintenance, Noise/Safety, Billing, General Complaints).
• Section 3 — Post-Stay Review Response Rules: flamingo-las-vegas-hotel-casino-review-response-escalations.md (positive and negative/mixed review handling and escalation triggers).

Detailed Incident-Category Guides

For serious guest-reported incidents, route using the risk-category guides (all are always-escalate):

• flamingo-las-vegas-hotel-casino-safety-injury-escalations.md — Safety & physical harm (SAFETY-INJURY)
• flamingo-las-vegas-hotel-casino-security-theft-escalations.md — Theft & property crime (SECURITY-THEFT)
• flamingo-las-vegas-hotel-casino-health-medical-escalations.md — Health & medical (HEALTH-MEDICAL)
• flamingo-las-vegas-hotel-casino-security-safety-escalations.md — Security & unsafe conditions (SECURITY-SAFETY)
• flamingo-las-vegas-hotel-casino-conduct-harassment-escalations.md — Harassment & conduct (CONDUCT-HR)
• flamingo-las-vegas-hotel-casino-hygiene-hazard-escalations.md — Hygiene & environmental (HYGIENE-HAZARD)
• flamingo-las-vegas-hotel-casino-legal-threat-escalations.md — Legal threats (LEGAL-FLAG)

One additional always-escalate guide covers a guest commitment rather than a harm incident:

• flamingo-las-vegas-hotel-casino-confirm-fee-escalations.md — Fee & charge confirmation (CONFIRM-FEE) — guest accepts/authorizes any fee or surcharge; catch-all backing the Section 1 upsell rows below

Required Fields in Every Escalation Email

• Guest First & Last Name
• Reservation ID / Confirmation Number
• Booking Channel (Expedia / Booking.com / direct)
• Arrival Date & Departure Date
• Nature of Request / Issue (detailed)
• Guest Contact Phone or Email (where applicable)

Section 4 — Quick Reference: LLM Decision Rules

Use this table as a fast lookup for any incoming guest message. Find the request type, confirm whether the LLM handles it or escalates, and identify the specific trigger that activates the escalation.

Request / Scenario	LLM Response	Escalation Trigger
Early Check-In	Share $60 + tax fee, explain availability	Guest confirms they want to pay — then escalate
Late Check-Out	Share fee schedule, explain availability option	Guest confirms fee + desired time — then escalate
Connecting Rooms	Explain $25/room/night fee, request names & conf #s	Guest confirms fee + provides all names & conf #s — then escalate
Upgrade / Extend Stay	Ask for best contact phone number	Guest provides phone number — then escalate
Fee / Charge Confirmation (any)	Thank guest, acknowledge the accepted fee; do not apply the charge or guarantee the add-on	Guest accepts/authorizes any fee or surcharge — always escalate (CONFIRM-FEE)
Name Addition / Alt Check-In	Collect name, explain ID/card requirements	Primary name change, billing auth, identity mismatch
Stay Modification / Cancel	Explain 3rd-party policy, direct to booking channel	3rd party cannot process; complex booking changes
Invoice / Folio / Receipt	Explain who issues folio, set timeline expectations	Itemization, billing correction, refund request
Room Issue / Housekeeping	Apologize, gather details, direct to front desk first	Front desk unresponsive; safety impact; comp requested
Maintenance Request	Acknowledge, direct to front desk / Laurel text	Front desk unresponsive; repair still needed
Noise / Safety Complaint	Acknowledge, direct to Security (702-733-3523)	Security/front desk intervention needed; unresolved
Billing Dispute / Refund	Acknowledge, collect details	Any correction, dispute, or refund — always escalate
General Complaint / Comp	Empathize, document thoroughly	Compensation requested; multiple failures; emotional guest
Post-Stay Review — Negative	Acknowledge publicly with empathy template	Safety, discrimination, viral-risk — escalate within 12h
Post-Stay Review — Positive	Respond with standard thank-you template	No escalation required