Turn honest customer feedback into service improvements

Ask a few neutral questions at a useful moment

Choose a normal point after the customer has experienced the service. Keep the invitation optional and consistent across customers. A practical introduction is: “We are reviewing how this service works. If you have a moment, what went smoothly, and what could we make clearer or easier?” Avoid wording that assumes the experience was excellent.

Our starting questions are: “What was clear or unclear before the appointment?”, “Was anything different from what you expected?”, and “What should we change for next time?” Include an optional way to request a response about a specific issue. Ask only what someone will review and act on; an elaborate survey with no owner creates an unattended queue.

Separate the original response from your interpretation

Google Forms can display individual responses and link responses to Sheets. If you use that setup, check who can access both the form and the linked spreadsheet. Keep the working feedback log limited to the people who need it.

Create fields for received date, service, original comment, theme, issue owner, next action, due date, and outcome. Keep contact details in the appropriate customer record where possible. Preserve the actual comment separately from your summary: “I did not know when the team would arrive” supports an arrival-window theme, but does not prove that the team was late.

Code themes and route individual issues

GOV.UK’s research-analysis guidance separates observations, grouped themes, findings, and actions. Adapt that distinction to a small feedback log so a comment does not turn directly into an unsupported conclusion.

Start with a few practical codes: appointment timing, preparation, scope explanation, communication, work quality, and aftercare. Allow more than one code when needed. Write a short definition for each so colleagues classify similar comments consistently. Keep “needs review” for an unclear comment instead of guessing.

An individual service concern needs an owner immediately; it should not wait for the monthly theme review. Record what the owner will investigate, when the customer will hear back, and any agreed remedy. Acknowledging the message is a first step, not proof that the issue is resolved.

Use a small worked example to choose an action

Imagine a fictional cleaning business receives eight responses. Three mention uncertainty about arrival time; one reports a missed area; four raise no concern. The office manager contacts the customer about the missed area and owns that service task. Separately, the manager reviews the appointment email and finds that it omits the arrival window.

The corrective action is specific: add the agreed arrival-window explanation, have the operations lead verify it, and test the next booking confirmation. Review later responses for the same confusion. These invented counts illustrate the process; they are not a representative survey or evidence of a business-wide satisfaction rate.

Close the loop and review the change

Where the customer requested contact, explain what you checked, what you can do, and the next date if investigation remains open. Do not promise a change before the responsible person confirms it. Mark a task complete only when its agreed action is done, then record whether the customer needs anything further.

At the monthly review, examine repeated themes, overdue actions, and whether previous changes helped. Keep public review invitations on their own consistent process rather than using feedback scores to decide who receives one. For that workflow, use Ask for Google Reviews Ethically in the related guides below.