Skip to content

Service recovery

Putting a service failure right for the customer: hear them out, learn what happened, say what you can do, do it, and name the next step. The shape for a question or role play that opens with something gone wrong.

On this page

What it is

Service recovery is what a business, and the person at the counter or on the line, does after a service failure to bring an unhappy customer back to satisfied. The idea was set out by Hart, Heskett and Sasser in a 1990 Harvard Business Review article: because services are often delivered in front of the customer, a late flight or a burned steak will happen now and then, but a customer who leaves dissatisfied doesn't have to. Recovery differs from complaint handling because it works at the moment of service: many unhappy customers are reluctant to complain, so recovery tries to solve the problem during the encounter, before the customer walks away dissatisfied.

StepWhat you doWhat it gives the customer

Hear and acknowledge

Let them finish. Say back the problem in your own words and that you can see why it matters to them.

Being treated as a person, which is one of the three things customers weigh when judging a recovery.

Ask

Get the facts you need: the order, the account, what they were told, what they expected.

A fix aimed at the actual problem, and fewer repeat visits.

Say what you can do

Name the options you really have. If the decision sits above you, say so and go ask.

A fair process: a quick, clear path rather than transfers and waiting.

Act

Do the fix, or hand it to the person who can, and keep talking while you do.

The outcome itself: the refund, the replacement, the corrected booking.

Close and follow up

Say what happens next and when. If you promised a call back, make it.

Confidence that it's really done.

Why the order matters. Research on recovery describes customers judging it on three kinds of fairness: the outcome they got, the process it took to get there, and how they were treated along the way. A full refund still scores poorly when it took three transfers and nobody acknowledged the problem. That's why hearing and acknowledging come before the fix, and why a quick route to a decision counts as part of the fix.

Authority is part of the design. The original article argued that companies should give frontline staff the authority and the responsibility to correct a mistake, even when that means departing from the rules. In an interview you're describing the authority you actually had. A strong answer names the policy that covered the case, or names the point where it stopped being your call and who you asked. Claiming discretion you didn't have reads as a story that wouldn't survive a follow-up question.

The recovery paradox, and why not to count on it. The term, coined in 1992, describes a customer ending up more satisfied after a well-handled failure than if nothing had gone wrong. Studies since have reported mixed results: the effect appears rare, and more likely when the customer saw the failure as minor and outside the company's control. Our advice: treat it as a reason to recover well, not as a reason to over-compensate, and don't present it in an answer as something a good agent can reliably produce.

When to use it

Use the shape whenever a question or a role play puts someone in front of you with something already gone wrong: "tell me about a time a customer was upset", "a caller says the order hasn't arrived", a coworker whose shift you covered wrong. A strong answer shows two things in one story: the fix you found for the person, and the policy or authority you worked within while finding it. One without the other is half an answer: a fix that ignored the rules, or a rule recited while the customer left unhelped.

In a past-tense story, use the STAR method shape and spend most of the time on your steps, in the order you took them. End with two facts: what the customer needed, and what they left with. A story that ends "and they calmed down" has left out the result.

In a live role play, the same beats happen in real time. Two habits carry it: speak while you check ("I'm looking at the account now, give me a moment") so the line doesn't go quiet, and keep sentences short enough that you're not talking over the person when they push back. When they push back, answer the objection; don't restart the script.

When you were the one who got it wrong, say so and move to the fix. For the story shape, see Failure and conflict without blame.

When not to

The full shape is for a failure. Some situations look similar and want something simpler.

  • Nothing has gone wrong. A customer asking where the fitting rooms are, or how to reset a password, wants the answer. Wrapping a plain request in apology and empathy sounds rehearsed and slows them down.
  • The request is outside policy and outside your authority. The recovery here is small and honest: say what you can do, say who decides the rest, and go ask. An apology followed by a promise you're not able to keep turns one failure into two.
  • The customer is abusive or you feel unsafe. The goal shifts from recovery to safety: follow the store or call-center procedure and bring in a lead. Staying to finish the five steps is not the standard.
  • The question is a hypothetical about policy, such as "how would you change our returns process". Answer it as a design question; see Answering a hypothetical.
  • Over-compensation. Because the paradox is rare, a bigger gesture doesn't reliably buy a happier customer. Fix the problem, offer what policy allows, and stop.

Compared

MomentWeakerStrongerWhen the weaker one is right

Opening

"Let me look that up."

"I'm sorry, that shouldn't have happened. Tell me what you ordered and when it was due."

The customer is calm and in a hurry, and the problem is small and obvious: a receipt that didn't print. Go straight to the fix.

Finding out

Offering a refund before asking anything.

Asking for the order number and what they were told, then proposing a fix that matches.

The setup already gave you all the details and the customer has said them twice. Asking again reads as not listening.

The offer

"Don't worry, I'll get this sorted."

"Here's what I can do: replace it with next-day delivery, or refund it today. Which do you want?"

As a bridge while you check, as long as a specific offer follows in the same call.

Authority

Deciding something above your level to end the conversation faster.

Naming the policy that applies, and asking a lead for the part it doesn't cover.

The employer has explicitly given you that discretion, and waiting for a lead would cost the customer more than the decision is worth.

Closing

"Anything else I can help with?"

"The replacement ships today. You'll get tracking by email, and if it hasn't arrived by Friday, call this line and ask for me."

The fix finished in front of the customer and nothing is pending, so there's no next step to name.

Follow-up

None.

The call back you promised, at the time you promised it.

The issue closed on the spot and the customer asked not to be contacted.

In a picture

Listen firstAsk the details

Step 1 of 3

Hear and ask

The customer is talking. You let them finish, say back what went wrong, and ask for the details you'll need.

How to say it in an interview

The common mistake

Quiz

A caller is angry that a delivery didn't arrive. What's the best first move?
The customer wants something policy rules out, and the decision isn't yours. What do you say?
What does the research say about the service recovery paradox?
Which closing is stronger at the end of a support call?

Related

Sources

  1. The Profitable Art of Service Recovery (Harvard Business Review, July–August 1990)
  2. Profitable Art of Service Recovery, article summary (HBR Store)
  3. Service recovery (Wikipedia)
  4. Service recovery paradox (Wikipedia)
Sign in to report a mistake