A customer is standing at your counter, or on the phone, or typing an angry message into your booking platform, and the person handling it has been on your payroll for eleven days. There is no script taped under the register. No laminated card by the phone. So they improvise. Maybe they apologize too much and give away a full refund for a problem that needed a five dollar fix. Maybe they get defensive because they do not know what they are allowed to offer, so they offer nothing. Either way, you hear about it later, usually from a one star review, and you find yourself asking the same question you asked last time: who told them to say that?

Nobody told them to say that. That is the actual problem. You have a menu, or a listing description, or a service agreement, all written down in careful language. But the moment a customer is upset, you have nothing written down at all. You are trusting a script that does not exist, delivered by whichever employee happens to be standing there, and hoping their instincts match yours. Some days they do. On your busiest Saturday, three tables deep or juggling four check ins at once, they usually do not.

Why untrained improvisation is the default, not the exception

Owners tend to assume good service recovery is a personality trait. Some people are naturally calm and generous under pressure, others panic or freeze, and you just have to hire well and hope. That is partly true, but it puts all the weight on hiring and none on the business. Even your best employee, the one who has been with you three years and handles complaints beautifully, is running on pattern recognition built from watching you handle a hundred situations. Your new hire has watched zero. With no pattern to draw from, they either overcorrect toward appeasement or undercorrect toward defensiveness, and both cost you money and reputation in different ways.

There is also an authority gap hiding underneath all of this. Most frontline employees do not actually know what they are allowed to do. Can they comp a meal without asking a manager. Moving a check in time, discounting a service call, deciding how far an apology can go without sounding like an admission of fault your insurance would not like, all of it defaults to guesswork when nobody has ever spelled it out. When that authority is undefined, employees default to one of two extremes: give away the business, or give the customer nothing. Neither is a decision you actually made.

A service recovery playbook fixes this before the next complaint happens, not after. It does not need to be long. It needs to be specific enough that a new hire can follow it without guessing. A working version usually includes:

  • A short list of the five or six complaints that happen most often in your business, named specifically, not generically
  • Exact opening language for each one, the first sentence an employee says out loud
  • A clear dollar or action threshold for what any employee can approve on their own, and what requires a manager
  • A one line rule for when to bring a manager over immediately versus handle it solo
  • A simple way to log what happened so patterns show up over time instead of disappearing into memory

That last point matters more than owners expect. Without a log, you keep solving the same complaint from scratch every few weeks because nobody remembers it already happened twice this month. A playbook without a feedback loop just becomes another document nobody opens after week one. It is the same reasoning behind fixing the after hours call that goes straight to voicemail instead of hoping the next caller gets lucky: build the customer experience system once, so nobody has to improvise it live again.

Building this takes an afternoon, not a consultant retainer. What it does take is pulling yourself out of the day to day long enough to write down what is already in your head. That is usually the real barrier. You know exactly what you would say to that customer. Your new hire does not, and until you write it down, they never will.

If the response to your worst complaint only exists in your head, you do not have a service standard. You have a bottleneck.