Service Recovery
Part of Service recovery
Explaining what changed after a repeated service problem
Tell affected customers what was found, what has changed, what remains uncertain and what they can do if the problem recurs.
When a customer encounters the same problem repeatedly, explain what has been established, which change is planned or in use, and what still needs checking. A general claim that the team has learned from feedback gives customers little help in judging what to expect next.
Establish the finding
Compare affected cases before writing the update. Record the customer task, the point of failure, what each person was told and the outcome. Check the relevant operational step with its owner. Similar complaints may point to a shared cause, but similar wording alone does not prove one.
For example, repeated contacts about corrected invoices could reflect approved corrections that were never sent, or documents sent without an understandable explanation. Those are hypothetical alternatives. An actual update should name only a finding supported by the organisation’s evidence.
State the change at its real stage
| Stage | What can be explained |
|---|---|
| Cause still being checked | Describe the reported problem, what is being examined and when the next update is due. |
| Change approved | Explain the intended change without saying it is already operating. |
| Change implemented | Name the altered step after confirming it is in use. |
| Effect checked | Explain what was checked, including limits and remaining exceptions. |
The customer message need not use these labels, but its claim must match the stage. If a routing change is approved but has not been put into use, say that work is planned. Once it is in use, describe the change and the next check without promising that no failure can recur.
Answer the affected customer’s questions
A useful update says what went wrong to the extent known, what changed or will change, whether the customer needs to act, and how to get help if the problem happens again. If the cause cannot be shared in full, explain the practical effect without disclosing another person’s information or implying certainty that the evidence does not support.
Keep an individual remedy separate. A customer still waiting for a corrected invoice needs its delivery or an accurate case update even if the wider process has changed. A corrected invoice for one customer, in turn, does not establish that the recurring cause is fixed. Give a contact route for anyone whose own case remains unresolved.
If a proposed change was declined, explain the decision where appropriate and say what evidence would prompt another review.
Check the message against the service
Before sending an update, confirm the changed step and its effective point with the operational owner. Review relevant cases after implementation to see whether the intended outcome occurs, and record what remains untested. Fewer complaints alone do not prove that the change worked; the complaint route or the number of affected customers may also have changed.
If the same failure appears again, correct the customer message and reopen the investigation. The update should describe the service as it operates at the time it is sent.
