How to Manage Angry Customers: The HEAT Model
Knowing how to manage angry customers is a core skill for any frontline team — contact centres, retail, service desks, healthcare reception, hospitality. Done well, you turn a volatile moment into trust and resolution. Done badly, you get escalations, complaints, bad reviews, and repeat contacts.
This guide walks through the HEAT acronym for customer service — Hear, Empathise, Apologise, Take Action — with practical scripts, frontline tips from named practitioners, and the guardrails your team needs to use it well. Written for busy team leaders and agents who want a framework that works, not theory.
Outcome: shorter calls, calmer customers, fewer escalations, and a team that feels in control under pressure. Plus a free single-page Cheat Sheet for the desk.
Why it matters
The first 2–5 minutes of an angry-customer conversation determine whether the rest of the process succeeds. HEAT gives frontline staff a reliable structure to navigate that window without panicking or escalating prematurely.
Why it's tricky
HEAT is a conversation framework, not a script. Read it word-for-word and customers can tell. The skill is in the sequence and intent — knowing which move you're making and why.
What this guide covers
The four HEAT steps with verbatim "say this" phrases, frontline tips from practitioners, common pitfalls, where HEAT fits in a complaints framework, and the free Cheat Sheet to keep at the desk.
What is the HEAT Model?
The HEAT Model is a four-step conversation framework used to manage angry customers across customer service, contact centres, retail, healthcare reception, and any frontline role. The h.e.a.t. acronym for customer service stands for:
- H — Hear them out: Let the customer talk without interrupting. Take notes. Reflect back the core problem to confirm you've understood.
- E — Empathise: Acknowledge how the situation has affected them. Name the feeling and validate it without agreeing to fault.
- A — Apologise: Offer a sincere apology for the experience the customer has had — without hedging, blaming, or making it conditional.
- T — Take Action: State the next action, the owner, and the timeline. Confirm what the customer can expect and follow through.
It's used most often when a customer is unhappy, frustrated, or emotionally charged — billing surprises, delayed deliveries, missed callbacks, service outages, policy friction, or anywhere a customer asks to "speak to a manager." HEAT works the same way across phone, chat, email and in-person service, though the execution adapts to the channel.
Plain English
HEAT is the structured way to handle the first few minutes of an angry conversation so the customer feels heard and acknowledged before you try to fix anything. Skip those steps and even a good solution lands badly. Get them right and even a partial fix can land well.
✓ What HEAT IS
- A conversation framework — a sequence of intentional moves, not a word-for-word script
- A frontline tool for the first 2–5 minutes of an emotionally charged interaction
- Adaptable across phone, chat, email and in-person service
- The conversation layer that sits inside a broader complaints handling framework
- A capability — built through coaching and practice, not memorisation
✗ What HEAT IS NOT
- A rigid script to be read aloud — customers hear that immediately
- A replacement for your organisation's complaints process or escalation rules
- A reason to tolerate abuse or threats — safety always overrides framework
- A fix for poor systems, broken policies or genuine service failures
- A guarantee of resolution — it's the door to resolution, not the resolution itself
Why it matters when managing angry customers
Most frontline complaints don't escalate because of what went wrong — they escalate because of how the first conversation about it went. A customer who feels dismissed, talked over, or fobbed off escalates regardless of whether the underlying issue gets fixed. A customer who feels heard often accepts a partial outcome they would have rejected if it were offered cold. That's the entire reason a structured way to manage angry customers matters in the first place.
For frontline staff
HEAT gives you a structure to follow when emotions are high and your instinct is to defend, fix or rush. Knowing which move you're making and why steadies the conversation — and your own state.
For team leaders
HEAT is teachable, observable, and coachable. You can name the step a frontline person skipped (usually Hear or Empathise), demonstrate the alternative, and reinforce it on the next call.
For organisations
HEAT reduces escalation rates, complaint formalisations and repeat contacts — all expensive outcomes — by stabilising the first interaction. The economics of getting the first conversation right are significantly better than the economics of recovering after it goes wrong.
The four HEAT steps
Each step in HEAT is a deliberate move with a specific intent. Understanding what you're trying to achieve matters far more than the exact words you use — but the verbatim phrases below are field-tested and a fine starting point if you're new to the model.
Hear them out
Intent: let the customer feel fully heard before you try to do anything else.
Do: Listen without interrupting. Take notes on facts, dates, names, and impacts. Reflect back the core problem to confirm understanding before moving on. Use minimal encouragers ("I see," "go on") that signal you're engaged without taking over.
Don't: Jump in to defend, multitask, or correct facts before the customer feels heard. Especially: don't start solving while they're still venting — it lands as dismissal.
Say this: "I'm listening. Let me make sure I've got this right: [brief, accurate summary]."
Empathise
Intent: acknowledge the impact the situation has had on them — without agreeing to fault.
Do: Name the feeling and its legitimacy in plain language. Keep it specific to their situation so it doesn't sound canned. Empathy ≠ sympathy ≠ admission of fault.
Don't: Generic phrases like "I understand" without saying what you understand. Customers hear that as a brush-off.
Say this: "I can see why you're frustrated — you were promised delivery yesterday and it didn't arrive. That's not what you should have experienced."
Apologise
Intent: offer a sincere, professional apology for the experience the customer has had.
Do: Apologise for the experience, not necessarily the cause. Saying "I'm sorry this has happened to you" is a courtesy, not an admission of liability. Most organisations explicitly allow this; check yours if unsure.
Don't: Hedge ("I'm sorry if you feel that way"), defer ("It wasn't our fault"), or imply blame on the customer ("That shouldn't have happened" without owning it). All three escalate.
Say this: "I'm really sorry this has happened. You shouldn't have had to chase us, and I appreciate you taking the time to bring it to me."
Take Action
Intent: move the conversation from emotion to action with concrete next steps the customer can rely on.
Do: State the action, the owner, and the timeline. Underpromise and overdeliver. Confirm how and when you'll update them. Close the loop in your system afterwards.
Don't: Vague commitments like "we'll look into it" or "someone will be in touch." Repeat-contact rates are driven by Take Action failures more than any other step.
Say this: "Here's what I'll do now: I'll contact the depot, confirm stock, and call you back by 3pm today with the outcome. If anything changes I'll let you know sooner."
The sequence matters
HEAT is a sequence, not a menu. Solving before you've heard, empathised and acknowledged is the single most common reason a frontline conversation escalates. The customer doesn't hear your solution — they hear that you didn't listen. Run the sequence in order, even when the answer feels obvious to you.
How to take ownership of a complaint
Take Action — the T in HEAT — is where empathy and apology turn into something tangible. Done well, the customer leaves the conversation knowing exactly what happens next, who's doing it, and when. Done badly, they leave wondering — which is how recoverable complaints turn into formal ones.
Source a solution
Search internal knowledge management tools, intranet, CRM records and previous tickets. Ask colleagues or managers who may have seen the same issue before. Be creative — sometimes an alternate solution keeps the customer happy even when the original issue can't be resolved as requested. Use your judgement, within your authority.
Present the solution clearly
Outline your recommendation or next steps in plain language. Ask whether it's suitable for them — don't assume. If there's a choice between options, present both with your recommendation and the reason for it. Customers respond better to "here are two options, I recommend X because Y" than to a single take-it-or-leave-it answer.
Follow through — every time
Keep the customer informed. Always meet your commitments — if you promise an update by end of day, deliver it, even if it's "I don't have an answer yet, here's what I'm doing next." Silence after a promised callback is the single most damaging failure in complaints handling. Even a "no progress yet" call beats no call.
Confirm closure with the customer
After resolution, confirm the customer is satisfied with the outcome. This is rare in practice — most organisations close internally and never check externally — and it's where customer perception of the whole experience is set. A two-minute closing call often turns a complaint into loyalty.
"Ownership means the customer never has to wonder what's happening next — they know, because you told them."
Four ways to go the extra mile
Following the HEAT sequence will stabilise most conversations. If you want to lift satisfaction further and reduce repeat contacts, add these four moves. They're small, practical, and they work.
Use their name (sparingly)
Drop the customer's name at key moments — after you've listened, when you empathise, and when you confirm the plan. Two or three well-timed mentions show personal attention; more sounds robotic.
Say this: "Lucas, you've got every right to be upset. Here's what I'm going to do now."
Smile (yes, they can hear it)
Smiling shifts your tone and pace. People hear warmth in your voice. Take a slow breath before speaking — it steadies your tone and projects confidence. Posture matters too: open posture changes how you sound.
Say this: "Thanks for hanging in there while I checked that. I've got a clear next step for you."
Match their style
Some customers want reassurance; others want facts and timeframes. Mirror their pace and formality without mimicking. Direct customers want clear steps. Relational customers want a human tone. Policy-focused customers want references and accuracy.
Say this: "Here are the two options. Based on what you've said, I recommend X. I can action that now."
Use a brief hold (with consent)
When emotions peak, ask to place the customer on a brief hold to check details or compose yourself. It's a reset, not avoidance. Always ask first, keep it short, and return with a summary and a concrete next step.
Say this: "Can I place you on a quick one-minute hold while I confirm the account notes? I'll come straight back with an update."
Tips from the frontline
If there's one superpower in this industry, it's how practitioners help each other. Below is a curated set of practical moves contributed by ACXPA community members for managing angry customers — kept verbatim because the voice matters.
Susan Jones: "Take notes while they vent. It gives you a buffer from feeling attacked and lets you recap back to the caller — it proves you listened and gets them on the road to resolving the issue."
Sezzy Trevs: "Listen, empathise, try to understand how they're feeling. Say what you can do. Reassure. Get TL help if needed."
Kerry Petersen: "Don't raise your voice in return — it only makes things worse. Talk with a smile; it's hard to sound rude when you do."
Rachel Christian: "If they keep talking over you, stop talking. Wait for acknowledgment or ask if they're still there — then continue. If it keeps happening, say: 'To help you, I need you to let me speak. Is it OK if I do that?'"
Kris Loxley: "Just breathe. 99.9% of people are decent. Acknowledge what you hear, apologise, and tell them you're here to help — respectfully."
Kerrie Meyer: "Don't take it personally. People are frustrated with the situation. Direct that frustration appropriately: let them talk, note exactly what's raised, repeat it back, set expectations, and follow through. Don't break trust."
Roz Donaldson: "They want you to listen and understand their values behind the concern. Ask questions. When people are heard, they'll tell you what matters."
Heather Potts: "Avoid 'I didn't say that' / 'that's not what I said'. Re-explain instead. Accusatory phrasing sounds like you're calling them a liar — the last thing an angry person wants."
Mick Kane: "Talk about the options we do have. Avoid hard stops like 'I can't do that.'"
Sandra Bailey: "Step away from the screen; let them vent. Acknowledge you're listening without jumping to solutions mid-rant. Once they've let it out, then act — helping too early can add fuel."
Ryan Pelėks: "Give them a moment — it's not about you. Acknowledge the frustration, apologise for what happened, offer a resolution (or escalate), and reassure that it will be resolved."
Chris Ferreira: "ACT is a solid variant: Acknowledge the concern, Confirm the concern, Take action."
David Mitchell: "Acknowledgement, Empathy, Action. Whether the customer is 'right' is less important than addressing the issue and their perception quickly. Failing to acknowledge/empathise looks like you don't care."
Geoff Crane: "Most angry callers are frustrated by lack of progress. Show empathy from their perspective and outline tangible steps — it turns detractors into grateful repeat customers."
Joanie Badenhorst-Awasthi: "Stay calm and don't take it personally. It may not be your fault, but it is your problem to solve."
Keszia Tyler: "Let them talk. Then ask, 'What would you like me to do to help?' It often resets the conversation."
HEAT across channels
The HEAT sequence stays the same across every channel. The execution varies. Here's how the four steps land in the three most common frontline contexts.
Phone
Tone is the tool. Customers hear your warmth, pace, and breathing. Use minimal verbal acknowledgments ("mm-hmm," "I see") to signal you're listening without interrupting. Slow your delivery — fast talking sounds dismissive when emotions are high.
In person
Body language carries the message. Open posture, eye contact, and leaning slightly forward all signal you're engaged. Resist the screen — turning toward the customer matters. Be aware of physical safety: if a situation is escalating beyond what HEAT alone can manage, follow your safety protocol.
Email and chat
Structure mirrors the sequence. Open with a short acknowledgment of what's happened (Hear), follow with empathy that names the impact (Empathise), apologise for the experience (Apologise), then state the next step with a timeline (Take Action). Avoid corporate boilerplate — written HEAT lands worst when it sounds templated.
Common pitfalls
Most failed HEAT conversations fail in predictable ways. The pitfalls below are the patterns that turn recoverable interactions into escalations, formal complaints, or repeat contacts.
Solving before hearing
The instinct to fix is strong, especially when the answer is obvious. But solving before the customer feels heard lands as dismissal — even when the solution is correct. Run the H, E, A in order before you reach for T.
Conditional or hedged apologies
"I'm sorry if you feel that way" is not an apology — it's a deflection wrapped in apology language, and customers hear it instantly. Apologise for the experience, sincerely, without conditions.
Vague commitments
"We'll look into it," "someone will be in touch," "I'll see what I can do" — none of these are Take Action. They're language designed to end the conversation without committing. Specificity (action, owner, time) is the entire point of the T step.
Sounding scripted
HEAT is a framework, not a script. Reading verbatim phrases word-for-word, especially with no warmth, sounds robotic and amplifies frustration. Use the framework as scaffolding, not as a teleprompter.
Missing the safety boundary
HEAT does not require staff to tolerate abuse, threats, or behaviour that crosses a safety line. The framework is for emotionally charged conversations within reasonable limits — not for managing aggression. Every organisation needs a clear escalation/safety protocol that sits alongside HEAT.
No follow-through
The single most damaging failure in complaints handling is a Take Action commitment that doesn't get delivered. Even an "I don't have an update yet, here's what I'm doing next" call beats silence. Most repeat contacts trace back to a previous Take Action that never happened.
Where HEAT fits in a complaints framework
HEAT is the conversation layer of complaints handling — the first 2–5 minutes of an interaction. It is not a complete complaints process. A complete complaints framework also covers: how complaints are logged, when and how to escalate, what happens behind the scenes to investigate, how customers are kept informed, and how the complaint is formally closed and used to drive improvement.
Both layers matter, and they fail in different ways. Strong HEAT skills with no operational framework leads to inconsistent outcomes — what each agent commits to varies by who picked up the phone. Strong operational frameworks with weak HEAT skills leads to angry customers who escalate before the framework gets to do its job. The discipline is doing both.
The full picture
For frontline staff: HEAT is the conversation framework you use in the moment. For team leaders, managers and CX leaders: HEAT is one component inside the broader complaints framework — alongside complaint logging, escalation rules, root-cause analysis and improvement loops. The ACXPA Complaints Handling Hub covers the whole picture, with HEAT as its frontline entry point.
How to know it actually worked
The honest measure of frontline HEAT capability is whether the conversations are landing — measurable in three ways:
Customer-side measures
CSAT on complaint interactions, repeat-contact rate, escalation-to-formal-complaint rate, complaint resolution timeframes. Strong HEAT execution shows up here as fewer escalations and lower repeat contact rates.
Agent-side measures
Frontline confidence in handling complaints (survey-able), escalation-to-supervisor rate per agent, after-call recovery time. Strong HEAT capability shows up as agents staying in conversations longer before reaching for an escalation.
Quality and coaching measures
QA scoring of complaint interactions against HEAT steps, coaching actions raised per agent, time-to-improvement on identified gaps. The strongest contact centres run regular HEAT-specific QA reviews on a sample of complaint interactions.
The honest test
If complaint interactions are landing well, your customer-side measures will move. If they're not, the framework isn't being executed — it's being recited. The fix is coaching, not more training.
Free HEAT Model Cheat Sheet
HEAT Model Cheat Sheet (PDF)
A single-page printable reference card teaching the HEAT Method in the moment — designed to be printed, stuck to monitors, or laminated for desk reference. Includes verbatim "what good sounds like" phrases for each step plus the common failure mode to avoid.
Free to download — no membership required.
Want to train your team on HEAT?
HEAT Training Facilitator Guide (PowerPoint)
Hi — available as part of 's ACXPA Business Membership. A complete 23-slide PowerPoint deck with detailed speaker notes for running a 60–90 minute HEAT training session for your frontline team, including scenario practice exercises, channel-specific adaptation, and pre-prepared answers to the most common participant questions.
The HEAT Training Facilitator Guide is exclusive to Business Memberships
Hi — the HEAT Training Facilitator Guide is included with ACXPA Business Memberships only. 's ACXPA Vendor Membership doesn't include access — speak to your account holder, or contact ACXPA if you'd like to discuss your training needs.
Frequently Asked Questions
Are we allowed to apologise? Doesn't that admit liability?
This is the most common question asked in HEAT training, and the answer for almost every Australian organisation is: yes, you can apologise for the customer's experience without admitting liability for the cause. "I'm sorry this has happened to you" is a professional courtesy. "I'm sorry we caused this" is potentially different. Most organisations explicitly allow the experience-focused apology — check your own complaints policy if unsure, but don't use uncertainty as a reason to skip the A step.
What's the difference between HEAT and a complaints handling framework?
HEAT is the conversation framework — what to say in the first 2–5 minutes of an interaction. A complaints handling framework is the broader operational framework — how complaints are logged, escalated, investigated, resolved and closed. HEAT sits inside the framework as the frontline entry point. You need both: HEAT without the framework leads to inconsistent outcomes; the framework without HEAT skills leads to escalations before the framework gets to act.
Does HEAT work for written channels (email and chat)?
Yes — the sequence stays the same. Open with a short acknowledgment of what's happened (Hear), follow with a sentence that names the impact (Empathise), apologise sincerely for the experience (Apologise), then state the next step with action, owner and timeline (Take Action). The biggest difference: written HEAT lands worst when it sounds like a corporate template. Personalise it.
What if HEAT isn't working — the customer is still escalating?
HEAT is the door to resolution, not the resolution itself. If a customer is escalating despite HEAT being executed well, the underlying issue may need a more senior decision-maker, more authority, or a different solution. Escalate professionally — warm handover, not cold transfer; document before handing over; brief the receiving person on what's been done. Reaching escalation is not a HEAT failure; refusing to escalate when it's needed is.
Does using HEAT to manage angry customers mean we have to put up with abuse?
No. HEAT is for emotionally charged conversations within reasonable limits — frustration, upset, anger about a legitimate issue. It is not a framework for tolerating abuse, threats, or behaviour that crosses a safety line. Every organisation needs a separate, clear escalation and safety protocol for abusive behaviour. HEAT applies up to that line, not past it.
Should we use the customer's name throughout the conversation?
Use it deliberately at key moments — after you've listened, when empathising, and when confirming the action. Two or three well-timed mentions feel personal. Beyond that, it starts to sound robotic or salesy and has the opposite effect.
How do we coach HEAT effectively?
Listen to a recording with the agent, identify which step they skipped (it's almost always Hear or Empathise), demonstrate the alternative phrasing, and watch for it on the next call. Avoid critiquing the whole interaction at once — pick one step, coach to it, reinforce it, then move on. HEAT is teachable specifically because each step is observable and named.
Are there other models like HEAT?
Yes — ACT (Acknowledge, Confirm, Take action), AEA (Acknowledgement, Empathy, Action), and various organisation-specific variants all cover similar ground. HEAT is the most widely used h.e.a.t. acronym for customer service in Australian customer service and contact centre training because the four steps map cleanly onto observable agent behaviour and coachable skills. The exact acronym matters less than running the sequence — listen, acknowledge, apologise, act.
Where to next
Summary
Knowing how to manage angry customers is a core capability in customer service and contact centres — and the HEAT Model gives your team a reliable structure to do it well. The h.e.a.t. acronym for customer service — Hear, Empathise, Apologise, Take Action — works because it follows the human sequence of de-escalation: feel heard, feel understood, receive acknowledgement, gain a clear path forward. Skip any of those and even a perfect solution lands badly.
The skill is in the sequence and the intent, not the words. Read the framework verbatim and customers will hear it as a script. Run it as a series of deliberate moves — knowing what each step is for and why you're making it — and even tense conversations stabilise. The four steps are observable, coachable, and improve with practice.
HEAT is the conversation layer. It sits inside a broader complaints handling framework that covers logging, escalation, investigation and continuous improvement. Both layers matter, and the strongest organisations build both — frontline conversation skill and the operational framework that backs it up. Start with HEAT, build the rest, and the way your business handles angry customers becomes a measurable capability rather than a hope.
Does anyone else find it ironic that the heat method helps people chill?