Every other step has a system. The callback gets whoever answers the phone.

The call comes in at ten past four. It is not right, or it is leaking again, or nobody showed up on Tuesday and she took the morning off work for it.

What happens in the next hour is almost certainly unscripted, and it is the only part of your customer relationship that is.

Look at what does have a process

Booking has one. Reminders have one. The quote has a template, the invoice has a template, and the review request fires on a trigger without anybody thinking about it.

Then the highest-stakes conversation in the whole relationship gets handled by whoever happens to pick up, in whatever mood the day has left them in, with no agreed wording and no idea what was promised the last time this happened to somebody else.

That is not a discipline problem. Nobody ever sat down and decided it should work that way, which is exactly why it does.

What she is actually deciding

Not whether you are any good. That question closed when the thing failed.

What is open is whether this is going to be difficult. Whether she will have to chase you, whether somebody will imply she caused it, whether there will be an argument about money. The dread is not about the fault. It is about the next three weeks.

Which means a fault handled visibly and quickly leaves you in a better position than a job that simply went fine, because she now has evidence about how you behave when something goes wrong. Nobody can get that evidence from a job that worked.

The thing that turns her into a reviewer

It is rarely the original fault. It is being made to explain it again.

She called on Tuesday and told somebody the whole story. On Thursday she calls back and a different person asks her to start from the beginning, because the first conversation lives in one person's memory rather than anywhere a colleague can see it. That is the moment a manageable problem becomes a thing she wants other people to know about, and it costs nothing to prevent.

One record, visible to everybody who might answer, containing what she said and what was promised. That is the whole fix.

A process short enough to actually follow

Four things, and none of them requires software you do not have.

Acknowledge the same day with a real time attached, because "we will look into it" is the sentence that starts the chasing. Give it one named owner, so she is not passed between people who each know a third of it. Log it where the next person can read it. And when it is fixed, say so to her directly rather than letting the absence of further complaint stand in for a resolution.

Switch the asking off

One automated message can undo all of that.

If your review request fires on job completion and her job is technically complete, she is about to be asked to rate her experience in the middle of an open complaint. That is the most expensive collision in a small business stack, and it hands somebody an invitation to write down exactly what she is currently feeling. An open complaint has to suppress the ask, and that is a rule somebody has to write on purpose.

Callbacks are data

Write down what each one was, in two words, somewhere you can count them later.

Three callbacks in a quarter about the same fitting is not a customer service problem and no amount of good handling will fix it. It is a purchasing decision, or a training gap, or a step somebody has quietly stopped doing. Most businesses never find that out, because each callback is resolved individually and then forgotten individually.

And if it does reach the profile anyway, answering it well in public is a separate skill with its own shape. Worth knowing, and worth needing less often.

If your business has a system for everything except the day something goes wrong, book a strategy call. It is usually the cheapest process to build and the one nobody has written down.