How to Handle Guest Complaints in a Hotel (Scripts, Framework, and 12 Practice Scenarios)
A service recovery framework, exact scripts for the 12 complaints your front desk hears most, and a way to practise them before a real guest is standing there.
A guest is standing at your desk at 2pm. Their room is not ready, they have driven six hours, and the lobby is full. What your agent says in the next thirty seconds decides whether this becomes a one-star review or a recovered stay.
Handling a guest complaint follows a five-step sequence: listen without interrupting, acknowledge the impact on the guest, resolve with a concrete fix, verify the guest actually accepts that fix, and log it so the property can address the cause. The steps matter less than doing them in order, every time, under pressure. That ordering is what separates a trained response from an improvised one.
The rest of this guide gives you exact scripts for the twelve complaints front desks hear most, the lines to never say, and a way to rehearse all of it before a real guest is the one teaching your team.
Complaint handling is a trained skill, not a personality trait
Most complaint "training" is one sentence: be empathetic. That is not training. It is a hope dressed up as instruction.
Empathy is a behaviour, and behaviours are built by repetition. Telling a new front-desk agent to be empathetic is like telling a new line cook to make good food. True, useless, and impossible to coach against.
The agents who recover badly are rarely cold people. They are people who have never run the sequence enough times for it to hold when a guest is shouting and three others are watching. Under stress, untrained staff default to defending the property — explaining the policy, blaming the OTA, listing what they cannot do. Every one of those instincts makes the guest angrier.
What works is the opposite, and it is learnable. A clear framework, exact words for the common cases, and enough practice that the words arrive automatically when the adrenaline does. The rest of this guide is built around that idea.
The known frameworks, honestly
You do not need a proprietary acronym to recover a guest. Several well-known frameworks already describe the core sequence, and they are good.
LEARN. Listen, Empathise, Apologise, React, Notify. The guest is heard fully, their feelings are acknowledged, responsibility is taken, action follows, and the guest is told what was done. Widely taught in hospitality for good reason.
HEART. Hear, Empathise, Apologise, Resolve, Thank. Popular in Disney-influenced service training. Nearly identical to LEARN, with a closing thank-you that is a genuinely nice touch — it returns a little dignity to a guest who started the conversation upset.
Both are sound. If your team already uses one, keep it. The point of a framework is shared language, not novelty.
There is, however, one step that almost every published framework treats as implicit rather than required. And implicit steps are the ones that get skipped under pressure.
The Switchboard Recovery Loop
We teach a five-step loop that makes the missing step explicit: Listen, Acknowledge, Resolve, Verify, Log.
Listen. Let the guest finish. No interrupting, no problem-solving over the top of them. Most complaints are 80 percent the need to be heard.
Acknowledge. Name the impact, not just the fact. Not "I see the room is not ready" but "I'm sorry — you have driven a long way and now you are waiting, that is genuinely frustrating."
Resolve. Offer a concrete fix with a timeline. Vague reassurance is worse than no reassurance; it reads as a stall.
Verify. This is the step the others skip. Confirm the guest actually accepts the resolution before you move on. "Does that work for you?" "Is there anything else you need sorted before you head up?" Without this, you have a guest who nodded but did not agree, and you will see them again at checkout — or in your reviews.
Log. Record what happened and why, so the property can fix the root cause. A complaint handled but never logged is a complaint you will handle again next week.
The Verify step is the differentiator. A guest who feels heard but is quietly still unhappy is the source of most "but I thought we recovered that one" surprises. Asking, plainly, whether the fix is acceptable closes that gap. It is one sentence, and it is the one most agents forget.
The 12 most common complaints, with scripts
Each of these follows the same shape: the situation, an exact script you can lift, the lines to avoid, and the point where a manager takes over. Read the scripts as starting points — the words your team actually uses should sound like them, not like a recital.
1. The room is not ready
Situation. Guest arrives, room is not cleaned or the previous guest has not checked out. Common at peak occupancy.
Say this. "I'm sorry — your room isn't quite ready yet, and I know that's not the welcome you were hoping for after the trip. Here's what I can do: I'll fast-track your room to the top of housekeeping's list, and it'll be ready by [time]. In the meantime, let me take your bags so you're not carrying them, and the [cafe / lounge] has a coffee on us while you wait. Does that work for you?"
Not this. "Check-in isn't until 3." (Technically true; emotionally a slammed door.)
Escalate when. The delay will exceed an hour with no clear room available, or the guest needs the room for a specific time-sensitive reason (a wedding, a medical need).
2. Noise
Situation. Neighbouring room, corridor, street, or event noise keeping the guest awake.
Say this. "That sounds exhausting, especially when you came here to rest. Let me move you to a quieter room on a higher floor right now — I'll have a key ready in five minutes and someone can help with your things. If you'd rather stay put, I'll speak to the room next door directly. Which would you prefer?"
Not this. "We can't control other guests." (You can act on it, so say what you'll do.)
Escalate when. The noise is a recurring property issue (a faulty lift, ongoing construction) that warrants a comp or rate adjustment beyond the agent's authority.
3. Cleanliness
Situation. Room not cleaned to standard — hair in the bath, stained linens, a missed bin.
Say this. "I'm really sorry — that should never be how your room looks, and I understand why that's off-putting. I'm sending housekeeping up right now to put it right, or I can move you to a fresh room immediately if you'd prefer not to wait. What feels better to you?"
Not this. "I'll let housekeeping know." (Passive. The guest does not want a memo filed; they want it fixed now.)
Escalate when. The cleanliness issue is a health concern (pests, mould, biohazard). That is a manager matter and often a room change plus a goodwill gesture.
4. A billing surprise
Situation. A charge the guest did not expect — a resort fee, a minibar item, an early-departure fee, a hold they read as a charge.
Say this. "Let me pull up your folio and walk through it with you line by line, so there are no surprises. [Explain the charge.] If anything here wasn't made clear to you when you booked, I want to make it right — let me look at what I can adjust. Thanks for catching it."
Not this. "That's a standard fee, it's in the terms." (Correct, and exactly the wrong tone for a guest who feels misled.)
Escalate when. The guest disputes a charge you cannot waive at your authority level, or alleges fraud on the card.
5. A broken amenity
Situation. Air conditioning, Wi-Fi, TV, hot water, or the pool is out.
Say this. "I'm sorry the [amenity] isn't working — that's a real part of what you're paying for. I've logged it with maintenance and they'll be up within [time]. If it can't be fixed quickly, I'll move you to a room where it's working. While you wait, [interim fix — a fan, a hotspot code, a pass to the spa]. I'll check back with you personally."
Not this. "The whole building's Wi-Fi is down." (A property-wide failure the guest is hearing about for the first time, with no fix offered, just makes it worse.)
Escalate when. The outage is property-wide and ongoing, which usually calls for a coordinated comp policy a manager sets.
6. A rate dispute against the OTA price
Situation. The guest found the same room cheaper on an OTA — Booking.com, Expedia — and feels overcharged at the desk.
Say this. "I understand — seeing a lower price anywhere feels frustrating. Let me look at exactly what you're comparing. Often the rates include different things — breakfast, cancellation terms, the loyalty rate. If it's a like-for-like room, I'll match it, and booking with us directly means [direct benefit]. Give me a moment to check."
Not this. "The OTAs sell at a loss, that's their problem." (Never make the guest feel foolish for shopping around, and never throw your distribution partners under the bus.)
Escalate when. A genuine rate-parity breach exists that the agent cannot price-match within policy.
7. Overbooking and the walk
Situation. The property is oversold and the guest must be walked to another hotel. One of the hardest conversations in the building.
Say this. "I owe you a straight answer and an apology. We're fully committed tonight and I'm not able to give you the room you booked, which I know is the last thing you want to hear. Here's exactly what I'll do: I've secured you a room at [comparable property] at our cost, I'll cover your transport there, and your stay with us tomorrow is on the house. Let me handle every part of this so it's as easy as possible for you."
Not this. "We're overbooked, there's nothing available." (A walk handled without a concrete, fully-covered plan becomes a review, a chargeback, and a lost guest for life.)
Escalate when. Always loop a manager in on a walk. The cost commitments usually exceed agent authority, and the guest deserves to see the property take it seriously.
8. Slow service
Situation. Long check-in queue, slow room service, a delayed request the guest chased twice.
Say this. "You shouldn't have had to wait this long or ask twice — that's on us. I'm sorting it right now and I'll personally make sure it's done. Thank you for your patience; I know it's worn thin, and fairly so."
Not this. "We're short-staffed today." (Your staffing is not the guest's problem to absorb.)
Escalate when. Slow service has compounded into multiple failures in one stay; a manager should reach out to recover the whole stay, not just the latest incident.
9. A lost reservation
Situation. The guest has a booking; you cannot find it. Often a name mismatch, an OTA sync gap, or a wrong date.
Say this. "Let me find this for you — bear with me one moment. I'll search by your email, card, and confirmation number. [If found:] Here it is, thank you for your patience. [If not found:] I can't locate it under those details, but I'm not going to leave you without a room. Let me get you checked in now and we'll reconcile the booking afterwards so you're not standing here while I sort paperwork."
Not this. "There's nothing in the system, are you sure you booked with us?" (Doubting the guest in front of a queue is the fastest way to escalate.)
Escalate when. No room is available and the booking cannot be confirmed, which becomes a walk (see #7).
10. A pet or smoking policy conflict
Situation. The guest brought a pet to a no-pet room, or smoked in a non-smoking room, and there is a fee or a relocation in play.
Say this. "I want to sort this so it works for both of us. Our [pet / smoking] policy is [policy], and I should have flagged it more clearly. Here's what I can offer: [pet-friendly room / a designated area / waiving the fee this once with a heads-up for next time]. I'd rather find a way forward than make this a standoff."
Not this. "That's a [fee] charge, no exceptions." (Lead with the solution, not the penalty — the fee is the fallback, not the opening line.)
Escalate when. The guest refuses to comply and there is a genuine policy, safety, or other-guest impact (an allergy complaint, a damaged room).
11. A weather-ruined experience
Situation. The reason for the trip — the beach, the ski, the rooftop, the tour — is washed out by weather you do not control.
Say this. "I'm sorry the weather's not cooperating — I know that's exactly what you came for, and it's genuinely disappointing. I can't change the forecast, but I can make the rest of your stay better. Let me point you to [indoor alternatives], and [a small gesture — a late checkout, a drink, a spa pass]. We'll make the most of it together."
Not this. "Well, there's nothing we can do about the rain." (Literally true and emotionally abandoning. Acknowledge, then pivot to what you can control.)
Escalate when. The guest wants a refund or a comp for the weather; that is a goodwill decision for a manager, not a frontline one.
12. A social-review threat
Situation. "I'm going to post this everywhere." The guest is escalating to the threat of a public review.
Say this. "I hear you, and I'd honestly rather fix this for you than have you leave unhappy. Tell me exactly what would make this right, and let me see what I can do — I'm on your side here. Your experience matters more to me than the review."
Not this. "Go ahead, that's your right." (Defensive and cold.) Also not: caving instantly to any demand, which trains guests that threats work. Stay calm, stay solution-focused, and bring a manager in.
Escalate when. The threat is paired with an unreasonable demand, or the guest is abusive. A manager takes over — both to recover the guest and to protect the staff member.
De-escalation mechanics
The scripts above only work if the delivery matches. A perfect line in the wrong tone makes things worse.
Tone. Lower and slower than the guest, not matching their volume. When someone is loud, the instinct is to get loud back; resist it. A calm, even voice gives the guest something to come down to.
Pacing. Leave gaps. Let the guest finish their sentence and then a beat more — the pause that feels too long to you feels like being heard to them. Rushing to the fix before they have finished venting reads as dismissal.
The hand-off rule. If you are going to bring in a manager, hand off cleanly. Brief the manager in front of the guest in one calm sentence — "This is [guest], their room wasn't ready and they've been waiting, I've offered X" — so the guest does not have to repeat the whole story. Making an upset guest start over is its own small insult.
When a manager takes over. Early, not late. A manager who arrives after four failed attempts inherits a worse situation than one who arrives at the first sign the issue exceeds frontline authority. Escalation is not a failure; escalating too late is.
Practising complaints safely
Here is the uncomfortable part. For most properties, the place a new agent first runs the overbooking script is in front of a real, exhausted, furious guest. That is the training environment: live fire, no rehearsal, a review on the line.
You would not let a new agent run a fire drill for the first time during an actual fire. Complaint handling is the same. The skill needs reps, and the reps need to happen somewhere the stakes are zero.
This is the case for practising complaints against a realistic AI guest before facing a real one. In a Switchboard simulation, an agent speaks out loud to an AI guest that talks back live — and that guest can be set to a frustrated, skeptical, or time-pressured mood, so the agent runs the room-not-ready scenario at the intensity it actually arrives in. Run it once and it falls apart; run it eight times and the Acknowledge step stops being something the agent has to remember.
The point is not to script robots. It is to build the muscle memory so that when the real guest is shouting, the framework holds instead of the agent reverting to defending the property.
Measuring whether it is working
"Get better at complaints" is not measurable, which means it is not manageable. To improve it, you have to score it.
Two of the eight dimensions Switchboard scores map directly onto recovery. Empathy measures whether the agent acknowledged the guest's actual experience rather than just the facts of the problem. Call Control measures whether the agent kept the conversation moving toward a resolution rather than getting pulled into a loop of defending and explaining.
Below those, coaching cues track specific checkable behaviours — did the agent acknowledge the impact before offering a fix, did they verify the guest accepted the resolution, did they avoid the banned lines. Each cue is scored met, partial, or missed, and cue adherence is tracked over time so you can see an agent's recovery steadying across weeks rather than guessing from the occasional review.
That turns a soft skill into a visible trend line. A manager can see that empathy scores on the frustrated-guest scenarios climbed from the low sixties to the eighties over a month, and that the "verify the resolution" cue went from routinely missed to routinely met. That is the difference between hoping the team got better and knowing it.
Turning the 12 complaints into a practice curriculum
The cleanest way to use everything above is to stop treating it as a document and start treating it as a curriculum.
Each of the twelve complaints becomes a practice scenario: the situation as the setup, the guest mood dialled to match (a billing surprise plays skeptical, a walk plays frustrated and time-pressured), and the script as the model answer the coaching report measures against. You can load your own property's policies and prices into the Knowledge Base so the AI guest argues with real numbers, and so an agent who quotes the wrong fee gets flagged for a knowledge error rather than coached on a fictional one.
From there it becomes a rotation. New starters run all twelve before their first solo shift. Existing staff get the two or three scenarios their scores say they are weakest on. And when a real complaint reveals a gap — a new resort fee guests keep disputing, a recurring noise issue — you add it as a thirteenth scenario rather than waiting for the next training day.
The complaints your front desk hears are predictable. That predictability is the opportunity: anything predictable can be scripted, and anything scriptable can be practised until it is reliable. Recovery stops being a matter of who happens to be on shift, and becomes a standard the whole team holds.
Frequently asked questions
What are the most common guest complaints in hotels?
The most frequent are: the room is not ready at check-in, noise from neighbours or the street, cleanliness issues, a surprise charge on the bill, a broken amenity such as air conditioning or Wi-Fi, a rate that is cheaper on an OTA, an overbooking that forces a walk, slow service, a reservation that cannot be found, a pet or smoking policy conflict, a weather-ruined experience, and a guest threatening a bad public review. Each has a predictable shape, which means each can be scripted and practised in advance.
What is the LEARN method for handling complaints?
LEARN is a service recovery framework that stands for Listen, Empathise, Apologise, React, and Notify. The guest is heard fully, the staff member acknowledges how the issue affected them, takes responsibility, acts on a fix, and then notifies the guest of what was done. It is a sound sequence and close to HEART (Hear, Empathise, Apologise, Resolve, Thank). The gap most versions share is that none of them explicitly confirm the guest accepts the resolution before the interaction ends.
What should you never say to an angry guest?
Never say "calm down," "there's nothing I can do," "that's our policy," or "you should have..." Each of these tells the guest the problem is theirs to manage. Avoid blaming a colleague, another department, or the OTA they booked through. Also avoid over-apologising without a fix, which reads as a stall. The aim is to acknowledge the impact, then move quickly to a concrete next step the guest can see is happening.
How do you train staff to handle complaints?
Give staff a framework and exact scripts, then let them rehearse against a realistic frustrated guest before a real one is standing at the desk. Reading a script once is not training; recovery is a pressure skill that needs repetition. AI voice simulation lets an agent run the same complaint at different intensities, get a coaching report on empathy and call control, and repeat until the response is steady. That is far safer than learning on a live guest.
When should a complaint be escalated to a manager?
Escalate when the guest asks for a manager, when the resolution exceeds the staff member's authority (a refund, a rate change, a comp beyond their limit), when there is a safety, health, or discrimination concern, or when the guest's behaviour has turned abusive. Escalate early rather than after several failed attempts. A clean hand-off — where the manager already knows the situation — protects both the guest relationship and the staff member.
Request a demo · For hotels & resorts · Seasonal readiness