Practical working guide
A customer complaint log focused on resolution
Triage a customer complaint by recording what happened, the customer’s requested outcome, any immediate operational risk and the person responsible for the next response. Acknowledging the complaint is different from confirming its cause or promising a remedy. Keep both the customer’s account and verified findings.
Record facts without jumping to conclusions
| Field | Useful entry |
|---|---|
| Customer account | Their description, date and affected service reference |
| Desired outcome | What the customer is asking to happen |
| Immediate concern | Access, damage or service interruption needing escalation |
| Next response | Named owner, agreed time and information to check |
Worked example: investigate before promising
Fictional example: a customer says a repaired item stopped working and requests another visit. Record the service reference and symptom without labelling the customer “difficult”. Acknowledge: “We have recorded the issue with [item]. [Owner] will review [records] and contact you by [agreed time] about the next step.” If there is a potential safety concern, use the business’s established escalation process rather than offering speculative technical instructions.
Close with evidence and remaining disagreement
Record investigation, proposed action, authorised decision, customer response and whether the action was completed. Do not mark “resolved” solely because a reply was sent. Keep unresolved disagreement visible and follow the applicable complaint process. This operational template does not set refund rights, warranty terms or statutory deadlines; those depend on the actual service and applicable rules.
If the response deadline cannot be met, update the customer before it passes and record the newly agreed next step.