TEAM TRAINING REAL CONVERSATIONS. WITHOUT THE REAL CONSEQUENCES.
Happy Customer Complaint toolkit

FREE MANAGER WORKSHEET / 01

A complaint procedure your team can use.

Turn “we handle complaints” into a clear, practical route: how someone raises a concern, who takes responsibility and how the customer hears what happens next.

Start the worksheet

Free to use · No account needed · Practical starting points

BEFORE YOU START

Make the route clear.

A procedure explains how your team receives, considers, responds to and learns from complaints. This is a draft starting point for your business to review and approve; check the legal, accessibility and sector requirements that apply to you. A policy cannot remove customer rights.

Safety comes first. If someone is at risk, follow your workplace’s safety and emergency arrangements. A complaint is not automatically abusive, and a script is not a substitute for a safe exit.

YOUR EDITABLE WORKSHEET

Build your procedure.

Answer in your own words. Use job roles instead of names and leave actual customer details out.

Your entries stay only in this open page and are not sent to Happy Customer or saved automatically. Download an editable copy, copy or print before leaving. Anyone with access to the downloaded file can read it: keep it secure. Do not enter customer names, account numbers, case notes or other personal information.

Define what your business treats as a complaint, who it covers and where staff can find the approved procedure.

List available channels and how your team can arrange an accessible or alternative way to communicate.

Say who records and acknowledges the concern, using your organisation’s agreed process and timeframes.

Set the approved authority for this role and when facts, rights or a decision need checking.

Name the receiving role and a backup. Include what must be handed over and who owns the next customer update.

Describe the contact method and how update times are agreed and met. Do not promise an outcome before it is known.

Set out who checks the decision, explains reasons and appropriate next steps, and records it in the approved system.

Set a role to review recurring issues, track improvements and check the procedure remains accurate.

A FICTIONAL WORKED EXAMPLE

A small hotel team.

A guest says their room was not ready and they missed part of an event. The receptionist checks what happened, listens to the guest’s desired outcome and records the concern through the hotel’s approved system. They explain that the duty manager will review the options rather than promising a discount.

Owner and backup

The fictional procedure names a duty manager role and a backup role for the handover. It says who takes ownership of the next update when shifts change.

Decision and update

The manager checks the facts, relevant rights and the venue’s approved options, then explains the decision and any agreed next step. The team gives an update when it has agreed to do so.

What the team learns

If room-readiness complaints repeat, the manager reviews the process with housekeeping and reception. The aim is a change in the operation, not just a polished reply.

REVIEW BEFORE USE

Would your team know what to do?

  • Can a customer find an accessible way to complain and understand what happens next?
  • Does someone own the complaint, and is there a backup at handover?
  • Do staff know their authority and how to get help without overriding a customer’s rights?
  • Are update expectations realistic and set by your organisation or applicable sector requirements?
  • Are staff safety, privacy, decisions and recurring issues covered?

Check this draft with the people responsible for your policies. It does not certify legal or regulatory compliance.