A useful recovery process gives each concern an owner, a next action and a review time. Start by understanding the feedback, contact the customer only through a permitted channel, record what you agreed and close the case when the work is actually complete.
Read the concern before choosing a response
A low rating is a signal to investigate. Read the accompanying feedback and check the location and time. A complaint about waiting needs a different action from a billing mistake or a concern about the service itself.
Separate an urgent operational issue from a preference or a question. If a message suggests an immediate safety problem, follow your business’s incident process rather than leaving it in an ordinary follow-up queue.
Give the case a clear next action
In Kintouch, private feedback rated 1–3 stars creates a recovery case. Use its responsibility label, due time and notes to make the next step explicit. A label such as “Owner” or “Reception lead” is an assignment aid; it does not invite a separate staff account.
- Review the original feedback and any customer context.
- Assign a person or team label and a realistic time to check the case.
- Write the next action in plain language, such as “Check appointment delay with reception”.
- Move the case to in progress when work begins.
- Record the outcome and resolve the case when no further action is outstanding.
Make a proportionate follow-up
A customer may have submitted feedback anonymously or without permission to receive messages. You can still improve the service internally. Do not treat every complaint as permission to look up a phone number and start messaging.
When a permitted channel is available, acknowledge the specific concern, explain the next action and give the customer a way to respond. Avoid asking them to change a public rating in exchange for help.
- Acknowledge: “Thank you for telling us about the wait.”
- Act: “I am checking what happened with our reception team.”
- Set an expectation: “Would you prefer a reply here once I have an update?”
A small example: a delayed salon appointment
Imagine a customer leaves a two-star private note because an appointment started late. This is an illustrative workflow, not a Kintouch customer result. The owner checks the booking record, assigns the reception lead and notes a time to follow up.
If the customer allowed contact, the business can acknowledge the delay and explain a concrete change, such as confirming revised timing before the next visit. If the customer did not allow contact, the team can still adjust its scheduling process and record the internal action.
Close the loop with the team
A completed task means an action was marked complete; it does not prove the customer is satisfied. Add a short outcome note distinguishing “customer replied”, “no response” and “internal process changed”. Do not invent a resolution to make the queue look tidy.
At the end of the week, review repeated themes manually: waiting, communication, product availability or another issue relevant to your business. Pick one operational change and check whether the same concern returns. Archive resolved cases when appropriate, while keeping the records needed for your business’s retention policy.