Sit down for a minute, because this is one of those topics that looks like a four-letter acronym and turns out to be a small lesson in human behaviour. You will meet two versions in most contact centres. LAST stands for Listen, Apologise, Solve, Thank. HEARD stands for Hear, Empathise, Apologise, Resolve, Diagnose (some organisations end it differently, and Disney’s version, from which many centres borrowed it, is usually described with these same words). Trainers argue about which is better. I think the argument misses the point, so let us look at what the steps are actually doing.
An upset person is not processing your solution yet
Imagine a customer whose broadband has been down for two days and who has already explained this to three people. By the time she reaches you, she is not really asking a question. She is checking whether anyone is going to take this seriously. If you jump straight to “Sir, please restart the router”, she hears the same dismissal she heard earlier, however correct your advice is.
That is why both frameworks begin with listening. Not a pause before you speak, but actual attention: letting her finish, noting the facts (two days, three calls, a work-from-home deadline), and not typing the account number while she is mid-sentence. Listening has a practical payoff too. Angry customers often state the real problem in the first thirty seconds, buried between complaints. If you interrupt, you pay for it later in a longer call.
Apology and empathy are different jobs
New agents tend to blur these, so take them slowly. An apology owns the experience: “I am sorry this has gone on for two days.” Empathy shows you understand what it cost her: “With a deadline tomorrow, that must be very stressful.” HEARD separates them, LAST folds them together. Either is fine, as long as you do both.
One firm opinion: apologise for the experience, not necessarily for the company’s fault, until you know the facts. “I am sorry you had to call again” is always true. “I am sorry we cut your line by mistake” may not be, and in a regulated process such as banking or insurance, admitting fault before checking can create a problem. Many companies give agents approved apology wording for exactly this reason. Follow yours.
The second common failure is the repeated apology. “Sorry, sorry, so sorry” three times in one minute starts to sound like a recording. One sincere apology early, and one more if the resolution slips, does more than ten.
Where Solve, Resolve and Diagnose differ
Here the two frameworks genuinely diverge. LAST says “Solve”, which can tempt an agent to offer the first fix that comes to mind. HEARD splits it into Resolve (fix this customer’s immediate problem) and Diagnose (work out why it happened, so it does not happen again). The Diagnose step is more valuable than it looks, but it mostly benefits the company, not the caller. Done on the call, it should be brief: a correct disposition code, a note on the account, or a flag to the team that studies repeat contacts. Do not make an angry customer sit through a root-cause interview.
A good Solve has three ingredients: what you will do, by when, and what the customer should expect to see. “I have raised a priority ticket, a technician will visit between 10 and 1 tomorrow, and you will get an SMS tonight with the visit code.” Compare that with “We will look into it.” The first gives her something to hold you to. Never promise a timeline you do not control; give the standard timeline and, if the process allows, the escalation route if it is missed.
The thank-you is not decoration
LAST ends with thanking the customer, usually for their patience or for bringing the issue to you. It does one useful thing: it signals the call is closing, so you can confirm that nothing else is pending. Ask whether the resolution works for her, restate the next step once, then close. A customer who is thanked sincerely is also more likely to answer a CSAT survey kindly, though you should never fish for it.
When the framework becomes a script
The risk with any acronym is that it turns into a checklist read out in order. Customers can tell. Two signs it has gone wrong: the empathy statement is identical on every call (“I understand your frustration”), and the agent delivers it in the same flat tone whether the problem is a ₹50 fee or a blocked salary account. A better habit is to use the customer’s own words. If she said “I have been going around in circles”, reflect “going around in circles” back to her. It takes no extra time and it proves you listened.
Another limit: frameworks assume the customer is angry about the product. Sometimes she is angry about the interaction itself, such as being transferred or kept on hold. Then the fix is less about what you say and more about what you stop doing: stop transferring, own the call, and call back if the line drops.
And a boundary, because it matters. Empathy does not mean absorbing abuse. If the language turns abusive, most processes allow a warning and then a polite call closure. The framework helps with anger; it does not oblige anyone to tolerate being insulted.
Choosing between them
If your team is new, LAST is easier to remember under pressure, and four steps fit in a head that is also navigating three systems. HEARD is better for teams that have the discipline to capture the cause properly and a back-end that actually uses it. If nobody reads the diagnosis, the D is wasted effort. Pick the one your quality form scores against, and make sure the form rewards sincerity and accuracy, not just the presence of the phrase.
The real skill underneath both is sequencing: calm the person, then fix the problem, then close properly. Acronyms are only a way to remember the order.
Figures and names in the examples are illustrative.
Leave a Reply