Guest message
Received · Jun 14, 2026, 4:30 p.m.
I would like to be in Habitat tower
Expedia · Message
Received · Jun 14, 2026, 4:30 p.m.
I would like to be in Habitat tower
Sent · Jun 14, 2026, 4:31 p.m.
Thank you for your preference to stay in the Habitat tower. We'll do our best to accommodate your request, but please note that room assignments are subject to availability.
Source: 1
Score · 55.18%RAG Context: Escalation guideline for Flamingo Las Vegas guest reports involving pest sightings (bed bugs, cockroaches, rodents), unsanitary room conditions (bodily fluids, waste), visible mold or mildew, strong chemical smells from cleaning products, broken glass or sharp objects in rooms or pool areas, dirty linens or towels suggesting prior use, food left by a prior guest, or sewage/plumbing hazards. Maps to risk category HYGIENE & ENVIRONMENTAL (tag HYGIENE-HAZARD) in the master Flamingo Risk Management Framework (
flamingo-escalations.md). All matches must be escalated; the LLM must acknowledge seriously and must not minimize or attribute cause.
Trigger keywords (non-exhaustive): bed bugs, cockroach, rodents, mice, rats, infestation, mold, mildew, biohazard, dirty, unsanitary, disgusting, filthy, stained linens, broken glass, sharp object, chemical smell, sewage, plumbing hazard, prior guest food.
Overlap note: Pest, mold, and contamination signals also fall under HEALTH-MEDICAL when the guest reports illness or exposure symptoms. If both are present (e.g., "I saw bed bugs and got bites" or "mold and I couldn't breathe"), tag as HEALTH-MEDICAL instead of HYGIENE-HAZARD and escalate at the higher tier.
Use one of the approved Risk Management response templates from flamingo-escalations.md §5. Acknowledge seriously. Do not minimize, attribute cause to the guest, blame housekeeping or third parties, describe cleaning protocols or pest-control procedures, or hint at compensation.
Do not investigate or attempt to resolve. The LLM is authorized to acknowledge and empathize only. Capture the guest's exact wording — including the room number if mentioned — in the escalation record so the concierge can route to property leadership and housekeeping/operations as appropriate.
[HYGIENE-HAZARD] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue.Source: 2
Score · 53.81%RAG Context: Escalation guideline for Flamingo Las Vegas guest reports involving sexual harassment by staff or another guest, discriminatory treatment (race, gender, disability, religion, etc.), verbal abuse or threatening behavior from staff, profiling/surveillance/targeting, hostile guest-to-guest interactions, complaints about use of force by security personnel, or ADA accommodations denied or mishandled. Maps to risk category HARASSMENT & CONDUCT (tag CONDUCT-HR) in the master Flamingo Risk Management Framework (
flamingo-escalations.md). All matches require immediate escalation. The LLM must not investigate, validate, or dismiss the claim.
Trigger keywords (non-exhaustive): harassed, sexual harassment, touched me, inappropriate, discriminated, racist, sexist, bias, profiled, staff was aggressive, threatening, yelled at me, abusive, felt unsafe, threatened, intimidated, followed, ADA, disability, accessibility, wheelchair, accommodation denied.
Use one of the approved Risk Management response templates from flamingo-escalations.md §5. Acknowledge with grounded seriousness. Do not investigate, validate, dismiss, name staff or other guests, describe internal HR or security protocols, or hint at compensation. Avoid any language that could read as taking sides.
Do not investigate or attempt to resolve. The LLM is authorized to acknowledge and empathize only. Capture the guest's exact wording in the escalation record — wording matters in HR and conduct matters. The concierge will route to property leadership and HR as appropriate.
[CONDUCT-HR] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue with priority flag.Source: 3
Score · 52.49%RAG Context: Escalation guideline for Flamingo Las Vegas guest reports involving unsafe conditions or security failures — broken or non-functional room door locks, guests feeling stalked or followed, harassment by another guest or staff, unauthorized individuals entering or approaching guest rooms, suspicious behavior, weapons sightings or threats on property, security escort/removal complaints, key-card failures with security implications, or poorly lit areas cited as a safety risk. Maps to risk category SECURITY & UNSAFE CONDITIONS (tag SECURITY-SAFETY) in the master Flamingo Risk Management Framework (
flamingo-escalations.md). All matches require immediate escalation; the LLM must confirm the guest is currently safe if it is an in-stay message.
Trigger keywords (non-exhaustive): unsafe, threatened, stalked, followed, intimidated, harassed, broke into / forced lock, lock broken, key card not working / security concern, weapon, gun, knife, threat, unauthorized person, suspicious, escort, removed by security.
Use one of the approved Risk Management response templates from flamingo-escalations.md §5. Acknowledge gravity. If the guest is in-stay, lead with confirming they are safe and direct them to the on-site Security Team at 702-733-3523 while the escalation is being processed. Do not speculate on cause, name staff or other guests, describe internal security protocols, or hint at compensation.
For in-stay guests, the LLM may state that Security is available 24/7 at 702-733-3523 and that the front desk is reachable 24 hours. Do not investigate, validate, or attempt to resolve. Capture the guest's exact wording — including any names, locations, or descriptions — in the escalation record so the concierge can route appropriately.
[SECURITY-SAFETY] + [TIER LEVEL] + [CHANNEL: Expedia] and route to the Flamingo Concierge queue with priority flag.This response was not escalated. Was that decision correct?
Not yet assessed
Set by the preferred response below — saving a correction marks it incorrect, clearing the correction marks it correct.
Not yet assessed
Optionally provide a better response. Saving non-empty text marks the LLM response incorrect; clearing it marks the LLM response correct.