Service recovery guide
How to handle negative feedback before review outreach
Negative feedback becomes useful when one person owns the response and the customer knows what will happen next. The aim is to fix or explain the service problem, not to soften, hide or argue with the feedback.
Quick answer
Quick answer
Acknowledge the concern, name the person handling it, check the job facts, agree the next action and date, then verify that the action was completed. Keep review outreach out of the conversation while the issue is still open.
Use this when
- A customer reports missed work, poor communication, delay, damage or missing paperwork.
- The team needs a clear owner rather than several people replying separately.
- A recurring problem may require a process change as well as a customer response.
What you should have at the end
A customer-facing outcome that can be verified and, where needed, a separate improvement task for the business.
Start with a useful first reply
The first response does not need to solve everything. It should show that the concern was understood and that somebody is responsible for the next step.
Copyable starting point
Thank you for telling us. I am sorry that [brief accurate description of the issue]. [Name or role] is looking into this and will update you by [day or time]. We will confirm the next step once we have checked the job details.
Do not promise a remedy before checking the facts, but do give the customer a real update time.
Check the job without looking for an excuse
Review what was agreed, what happened on the day and what remained outstanding. The purpose is to understand the gap between the promise and the customer's experience.
- Original scope, quote or booking notes.
- Arrival times, access instructions and messages.
- Work completed, work deferred and reasons recorded.
- Invoices, reports, photographs or other relevant evidence.
Agree one next action and one date
Vague promises create a second complaint. Record the action, the owner and when the customer will hear from you again.
Example: missed area after a clean
The service owner confirms the missed room from the agreed checklist, offers a return visit on Thursday, records who will attend and asks the customer to confirm once the follow-up is complete.
Close the issue with evidence, not a status label
Changing a record to “resolved” is not enough. Write down what was actually done and how the outcome was checked.
- The remedy, explanation or correction provided.
- The date the customer was contacted.
- Evidence that the promised action was completed.
- The customer's response, where they supplied one.
- A new follow-up date if anything remains outstanding.
Keep review outreach separate
An open service issue is a reason to finish the follow-up first. It is not a way to filter out customers with low scores. The same open-issue rule should pause outreach for a customer who gave five stars but is still waiting for a report or repair.
- Do not ask the customer to change or remove criticism before receiving help.
- Do not delete or rewrite the private response.
- Recheck review eligibility only after the issue is genuinely closed.
Fix the process when the same problem can happen again
Customer follow-up fixes the immediate case. A separate improvement task should address the cause when the same failure could affect another job.
Example: invoices repeatedly sent late
Close the customer's invoice issue, then create an internal task to define who prepares invoices, when they are checked and how the office confirms they were sent.
This guide covers a practical follow-up process, not legal, insurance, safety or refund advice.