- Make complaints easy to record.
- Give each case one owner and a clear authority limit.
- Close the customer issue, then fix any repeated cause.
A customer says an order arrived late. The sales lead promises a credit, the owner hears about it two days later, and nobody records why the delay happened. The customer issue may close, but the same failure can return next week.
A complaint process gives the team a shared route. It says what to capture, who owns the reply, what that person may offer, and when a case must move up. For a small firm, one page and one log are often enough.
Define what counts as a complaint
Use a plain rule. A complaint is an expression of dissatisfaction that needs a response. The customer does not have to use the word “complaint.” A refund request, poor review or repeated service question may all reveal an unresolved issue.
Keep general ideas in your customer feedback loop. Put a case in the complaint process when someone expects an answer, a remedy or a decision. This keeps urgent cases from getting lost among survey comments.
State the scope. List every covered channel and customer type. Regulated firms may need special routes or deadlines, so check the rules for your industry and location.
Choose one intake route
Customers may speak in person, call, email or post online. Staff can accept the issue in any channel, but every case should enter the same internal log. Do not make the customer repeat the full story to three people.
Give the case a simple ID. Record the date, channel, order or job reference, issue, customer’s requested outcome, evidence, owner and promised next step. Save only the personal data you need and follow your privacy duties.
The US Federal Trade Commission tells consumers to gather purchase records, explain the problem, state the result they want and keep notes about promises made. That view helps a business design an intake form that captures useful facts without turning it into an interrogation.
Acknowledge before you investigate
A first reply does not need to solve the case. It should confirm what you heard, name the owner and say when the customer will hear next. Use a time the team can meet instead of copying a bold promise from another company.
HMRC’s current complaint guidance tells staff to understand the concern before replying, use plain English and avoid jargon. That advice transfers well to a small-business process. A short summary also gives the customer a chance to correct the record.
Write one acknowledgement pattern for staff, then allow natural language. A stiff script can sound dismissive. The goal is a clear handoff, not a perfect phrase.
Set an authority ladder
Frontline staff need to know what they may decide. Without a limit, they may promise too much, lose time and send every small issue straight to the owner. Use a ladder based on cost, safety, legal risk, customer impact and whether the case has happened before.
| Case level | Example owner | Possible action | Escalate when |
|---|---|---|---|
| Routine | Frontline lead | Explain, correct or replace within policy | Facts are disputed |
| Material | Operations manager | Approve a larger remedy or rework plan | Cost or customer impact exceeds authority |
| Critical | Owner or specialist | Protect people, evidence and legal position | Safety, privacy, fraud or legal risk appears |
Labelled example: This ladder is an invented operating model, not a legal classification. Change the roles, limits and actions to fit your contracts, policies, insurance and local duties.
Connect the ladder to your small-business SOP. The complaint page can stay short while the linked procedure explains how to handle a return, service redo or damaged item.
Investigate the case, not the customer
Separate facts from assumptions. Check the order, quote, messages, delivery record and the version of the policy the customer saw. Ask one clear question at a time when evidence is missing.
Do not make a minor customer error cancel a business mistake. HMRC’s guidance makes the same point: material errors can be explained, but they should not be used to score points. Keep the reply focused on what happened and what can be done now.
For a new client, check whether the failure began in your customer onboarding checklist. An unclear contact, deadline or approval step can create several complaints that look unrelated.
Offer a clear outcome
Match the outcome to the facts. Depending on the case, options may include an explanation, correction, repair, replacement, refund, credit or agreed rework. Do not promise a result before the owner has the needed authority.
Give the decision in writing when the issue is important or complex. State what the business will do, who will do it and the next date. If the request is declined, explain the reason in plain words and name the next internal or external route when one applies.
ISO 10002 treats complaint handling as a process that covers design, operation, maintenance and improvement. Its current edition also calls for an open, effective and easy-to-use route. You do not need ISO certification to use those ideas as a practical check.
Close the case twice
First, close the customer issue. Confirm that the promised action happened and record the outcome. The customer may still disagree, so mark the status honestly instead of calling every sent reply “resolved.”
Second, close the operating issue. Add a cause, action, owner and due date when the case points to a process fault. Several late orders may lead to a capacity fix, not another apology template.
Review patterns on a fixed rhythm. Sort cases by cause, product, channel and outcome. If a skill gap keeps appearing, update the small-team skills matrix and schedule a short practice session.
Use this one-page complaint process
- Accept the concern in any listed customer channel.
- Create a case ID and capture the key facts.
- Acknowledge the issue and name one owner.
- Set the next update time.
- Check records, policy and missing evidence.
- Choose an outcome that sits within the owner’s written authority.
- Escalate safety, privacy, fraud, legal or high-impact cases.
- Confirm the decision and action in clear language.
- Record clearly whether the customer issue has now closed.
- Assign any process fix and review repeated causes.
Test the page with three past cases. Staff should be able to show where each one enters, who owns it, what that person may decide and what proof closes it. If a step depends on the owner’s memory, write it down.
Frequently asked questions
What should a customer complaint process include?
Include one intake route, a case record, an owner, a first-response target, authority limits, escalation rules, a written outcome and a review step.
Who should own a complaint in a small business?
Name one person for each case. A frontline team member may own routine cases, while safety, legal, privacy or high-cost issues go to a named senior person.
Should every complaint receive a refund?
No. The response should match the facts, the business policy and the law that applies. Possible outcomes may include an explanation, repair, replacement, refund, credit or another agreed action.
What should go in a complaint log?
Record the case ID, date, customer channel, order or job reference, issue, evidence, owner, promised next step, deadline, outcome and any follow-up action.
Sources and scope
ISO 10002:2018 complaint-handling guidance · US FTC: resolving problems with a business · HMRC: dealing with complaints · Business.govt.nz complaint process checklist. This article gives general operating guidance, not legal advice. Policies, remedies and required response times depend on the contract, industry and location.