Handle an overbooking and relocate a guest to another hotel
A walk procedure, front desk script, and follow-up for when the hotel is oversold and a guest must be relocated.
The prompt
Help me handle an oversold night where guests must be walked.
Tonight's position: [ROOMS OVERSOLD, EXPECTED NO-SHOWS AND LATE CANCELLATIONS, ROOMS OUT OF ORDER]
Arrivals still to come: [COUNT AND TYPES - loyalty members, multi-night stays, groups, OTA bookings]
Walk partner hotels and agreed rates: [NAMES, DISTANCE, AVAILABILITY]
Our walk policy and what we pay for: [first night room, transport, phone call, return transfer, loyalty benefits]
Loyalty or brand standards: [ANY WALK COMPENSATION RULES]
Steps:
1. Decide who should be walked: suggest selection criteria (e.g. one-night stays, non-loyalty, earlier contact possible) and who to avoid walking (loyalty elite members, guests with disabilities or children arriving late, repeat guests, VIPs), and why.
2. Options to avoid a walk: upgrade chains, contacting likely no-shows, checking out-of-order rooms that can be returned, day-use releases.
3. Pre-arrival contact: a phone script and an email for guests we can reach before they travel.
4. At-desk script: acknowledge, apologize without blaming, explain what we have arranged and paid for, and get them moving quickly; how to respond if the guest is angry.
5. Follow-up: welcome back the next day with a room ready, a note, and how to record the walk.
6. Root cause: what to check in our overbooking levels and forecast so it happens less.
Return a checklist for the night manager, both scripts, and a short welcome-back note. Use only the compensation I list; do not promise anything else.
Highlighted [brackets] are blanks to replace with your own details.
Fill in the blanks and use this promptMore Customer Support prompts
What to fill in
- NAMES, DISTANCE, AVAILABILITY
- ANY WALK COMPENSATION RULES
How this prompt is built
This prompt follows the RTF structure (Role, Task, Format). RTF tells the model who to be, what to do and what shape the answer should take. It is the quickest structure that still gives noticeably better results than a bare request.
Related prompts
- Write a compliant collections call script for overdue accountsA debt collection call script with required disclosures, hardship options, and phrases to avoid under collection rules.
- Consolidate overlapping help docs and FAQs into one knowledge baseAn inventory, conflict list, taxonomy, article template, and merge plan to turn scattered help content into one reliable source.
- Write a weekly live chat support reportTurns chat data into a weekly report on volume, response times, satisfaction, top questions, and actions for the next week.
- Follow up with a detractor after a low NPS or CSAT scoreA personal follow-up to a customer who gave a low score, to understand what went wrong and close the loop.