Complaint handling: exception and recovery register
This register records the complaints that did not follow the normal path and what was done to put them right. It is for the service lead and owner of a small business who want a clear record of misses, so the same mistake is not repeated. A missed callback, a refund paid twice or a complaint that reopened after closure all belong here.
When to use it
Add a row whenever a complaint breaks your normal process: a promised date is missed, evidence is lost, a remedy is wrong or paid twice, a customer reopens a closed case, or the same fault is complained about again. Review the register every month to look for patterns.
The template
| Date noticed | Complaint no. | Type of exception | What went wrong | Impact (₹ or days) | Recovery step | Owner | Done on | Root cause | Prevention step |
|---|---|---|---|---|---|---|---|---|---|
| Missed date | |||||||||
| Wrong remedy | |||||||||
| Evidence missing | |||||||||
| Reopened case | |||||||||
| Repeat complaint | |||||||||
| Duplicate payment |
The types in the third column are suggestions. Replace them with the types you actually see.
How to fill it
- Type of exception: choose from a short fixed list so that rows can be counted later.
- What went wrong: say what happened, not who is to blame.
- Impact: write money in rupees where there is a cost, and days of delay where there is not.
- Recovery step: the specific action taken to repair the case for this customer.
- Root cause: the reason behind the miss, found by asking why until you reach something you can change.
- Prevention step: a change to the process, checklist or training, with an owner. It is different from the recovery step.
Example row
| Date noticed | Complaint no. | Type of exception | What went wrong | Impact (₹ or days) | Recovery step | Owner | Done on | Root cause | Prevention step |
|---|---|---|---|---|---|---|---|---|---|
| 12 July | C-0203 | Duplicate payment | Refund of ₹3,200 paid twice by two staff | ₹3,200 | Asked customer to return the extra amount, adjusted on next bill | Accounts executive | 14 July | No check for an earlier refund | Look up the complaint register before any refund |
Review and sign-off
- The service lead reviews every new row within a week, and the owner reviews the full register.
- Review monthly, and count exceptions by type.
- Escalate to the owner any money loss above the limit you set, any type that repeats in the same month, and any message sent to a customer in error.
Keeping it up to date
- Close a row only when the prevention step is done, not when the recovery step is done.
- Merge or rename types when several rows describe the same thing in different words.
- Keep the register for the period your CA or the law requires.
Did not find your answer?Message the lamp team on WhatsApp. Ask about setup, your records, or anything we have not covered here.Ask us on WhatsApp →