A procedure is most useful when work crosses teams. Staff need to know who will act, who may approve the outcome, and who will keep the customer informed. This guide sets out those decisions alongside the records and timeframes that support them.
Explore ResolveCX's approach to governed customer resolution for context on connecting complaint, case and escalation work. The model below is educational guidance, not a statement of product behavior or legal advice.
What is a complaint handling procedure?
A complaint handling procedure is a documented sequence for recognizing dissatisfaction, recording it, assessing risk, assigning responsibility, investigating, deciding, responding and learning. It applies to calls, emails, forms, chat and other monitored channels.
The customer does not need to use the word “complaint.” Ask whether they have expressed dissatisfaction with a product, service, decision or treatment and expect a response.
Policy explains access. Procedure explains action.
A public complaint policy tells customers how to raise concerns. The internal procedure specifies records, remedy authority, clocks, specialist routes and decision review. Align the two so the public promise matches the team's working instructions.
ISO 10002 provides guidance on organizational complaint handling. It does not provide one global response deadline.
Complaint handling lifecycle
Receive
Record dissatisfaction
Assess
Triage risk and owner
Decide
Investigate and approve
Verify
Respond, deliver, learn
The four summary stages above group the work. The eight steps below explain the actions, owners and outputs within that lifecycle.
What are the eight steps in handling a complaint?
Some steps happen in one conversation; others require investigation. Each needs an owner, an output and a route for exceptions.
| Step | Accountable owner | Required output | Clock or trigger |
|---|---|---|---|
| 1. Receive | First handler | Customer concern captured | Receipt timestamp |
| 2. Acknowledge | Complaint owner | Issue and next contact confirmed | Acknowledgment target |
| 3. Assess | Complaint owner | Severity and route recorded | Urgent-risk trigger |
| 4. Assign | Complaint owner | Named next owner and action | Handoff acceptance |
| 5. Investigate | Investigator | Findings and evidence linked | Update milestone |
| 6. Decide | Authorized approver | Rationale and remedy approved | Decision deadline |
| 7. Respond | Complaint owner | Reasoned customer response | Final-response clock |
| 8. Verify and learn | Complaint owner | Remedy checked; cause referred | Closure and review |
1. Receive and recognize dissatisfaction
Make monitored channels accessible. Capture the customer's account, channel, received time, affected service and requested outcome. Preserve wording that matters to the allegation. Record even a simple correction under your organization's rules so repeat causes do not disappear from reporting.
2. Record and acknowledge
Create an identifier and confirm the issues, contact person, next step and expected update. An acknowledgment confirms receipt, not the merits of the complaint. Clarify multiple concerns and communication preferences. An automatic receipt can help, but someone still needs to check that the right person owns the work.
3. Assess risk and scope
Triage for harm, urgency, repetition, disputed facts, privacy or safety implications, and applicable requirements. Record why the route is routine, complex or urgent. A serious allegation may need a specialist even when the customer sounds calm. Sentiment cannot replace factual assessment.
4. Assign a named owner
One person or team must own the customer commitment. Record the next action, due date and contributors. A queue referral is incomplete until the recipient accepts the work and its context. The complaint owner keeps visibility of the response commitment throughout the transfer.
5. Investigate proportionately
Gather relevant interactions, service records, policies, staff accounts and customer evidence. Separate established facts from disputed accounts. Avoid asking customers to repeat information already held. Log significant actions, findings and open questions. A straightforward correction needs less analysis than a material disagreement.
6. Decide and approve
Compare the evidence with policy and available remedies. Record the reasoning, offer limits and approval authority. A frontline agent may correct a simple error; a sensitive finding may need management or compliance review. AI may organize context, but people make and approve consequential decisions.
7. Respond and explain
Address each material point in plain language. State the decision, reasons, promised action, delivery date and applicable review route. Explain rejections. Check that another team has accepted any action you promise, and retain the approved response with the record.
8. Verify the action and learn
Sending a response and completing a remedy are separate events. Verify the commitment, record closure and any reopening, and assign recurring causes for corrective review. Keep individual customer outcomes distinct from longer-term problem management.
Who owns each step of the complaint process?
Ownership is a continuing responsibility for the customer outcome, not a label on the current queue. The complaint owner coordinates updates and deadlines while investigators and specialists contribute findings. The authorized approver remains accountable for the decision.
Document authority by complaint type and risk. Review unusual cases rather than assuming every agent can make every offer.
Roles at decision points
Handler
Capture and resolve within authority
Owner
Keep action and update visible
Specialist
Investigate and document
Approver
Review outcome and rationale
| Role | Primary responsibility | Decision boundary |
|---|---|---|
| Frontline handler | Recognize, listen, record and resolve within authority | May not decide outside delegated limits |
| Complaint owner | Coordinate work and customer updates | Keeps the commitment visible through handoffs |
| Investigator or specialist | Establish facts and recommend action | Does not silently replace the complaint owner |
| Manager or approver | Review and authorize defined outcomes | Records the decision and rationale |
| Compliance or risk reviewer | Advise on applicable obligations and sensitive issues | Reviews within its assigned mandate |
A handoff is complete only when:
- The recipient has accepted ownership.
- The record contains the context they need.
- A dated next action exists.
If any part is missing, the original owner should follow up. In outsourced or cross-functional work, the customer-facing owner also needs to know who can make the substantive decision.
See ResolveCX's complaint management workflow for a relevant view of complaint ownership, investigation, response and learning.
How should complaint timeframes be set?
Start each clock from a defined event and identify its source: an internal service commitment, a contract or an applicable rule. Specify business versus calendar days, working hours, reminder points and the person responsible for an exception.
Reassignment should not silently erase the original customer commitment. A complex investigation may need interim updates before the final-response date.
Complaint clocks
Receipt
Record original time
Acknowledge
Confirm next contact
Update
Raise delay before breach
Respond
Issue approved outcome
| Commitment | Start event | Responsible person | If at risk |
|---|---|---|---|
| Acknowledge | Complaint received | Intake or complaint owner | Alert coverage owner |
| Customer update | Last promised contact | Complaint owner | Contact customer before target |
| Investigation | Accepted assignment | Investigator | Raise blocker with owner |
| Approval | Complete proposed finding | Approver | Escalate decision capacity |
| Final response | Applicable rule-defined event | Complaint owner | Apply permitted exception route |
| Remedy completion | Approved action | Delivering team | Tell owner and customer of delay |
Choose realistic internal targets
An internal procedure might promise an acknowledgment by the next business day and an update every five business days. These are illustrative operating choices, not universal requirements or confirmed ResolveCX clock behavior. Choose targets based on severity, capacity, customer needs and any stricter obligation.
When a delay is foreseeable, record the cause, decision authority, revised date and customer communication before the target passes. A new internal due date does not automatically extend a regulatory deadline.
Keep regulatory examples within their scope
- UK regulated firms: the FCA's DISP rules address complaint time limits, including particular provisions for payment-services and electronic-money complaints. Check the applicable complaint category and any relevant exceptions in DISP 1.6.
- US CFPB complaint process: the CFPB says companies generally respond in 15 days. In some cases, a company reports that its response is in progress and provides a final response in 60 days. This describes complaints submitted through that process, not all US customer complaints.
- UAE licensed financial institutions: clause 8.1.3.7 of the CBUAE Consumer Protection Standards specifies a final written response with detailed reasons within 30 complete business days of receiving a complaint, or another time limit prescribed by the Central Bank.
These examples apply to their stated processes and institutions. Legal and compliance teams should verify the rules, counting method, exceptions and current requirements that govern a particular complaint before the organization publishes targets.
When should a complaint become a case or an escalation?
A complaint expresses dissatisfaction. A case coordinates extended work across people or teams. An escalation brings an issue to the authority needed for a decision, risk response or threatened deadline.
One customer issue may involve all three records, but each should have a clear purpose. The complaint owner must know who is acting and when the customer will hear back. These are conditional work paths, not three mandatory stages.
Choose the next work path
Check the issue, risk, authority and deadline.
Frontline
Clear issue within authority
Case
Coordinate several contributors
Escalation
Risk, authority or deadline trigger
Select the route that fits the assessment. These are conditional alternatives, not sequential stages.
After assessment, choose one conditional route: Frontline, to clear an issue within authority; Case, to coordinate several contributors; or Escalation, when risk, authority or a deadline triggers it. The three routes are alternatives, not a sequence.
| Path | Use when | Lead | Key control |
|---|---|---|---|
| Frontline resolution | Issue is clear and within authority | Handler | Record remedy and confirmation |
| Coordinated case | Several teams or actions are required | Case owner | Link work and preserve context |
| Escalation | Risk, authority, dispute or deadline requires intervention | Receiving decision owner | Accept trigger and next decision |
Define escalation triggers before they occur
Triggers may include suspected harm, a sensitive allegation, an external referral, a remedy beyond delegated authority, repeated failure or a deadline likely to be missed. For each trigger, specify the receiving role, notification urgency, evidence to transfer and who updates the customer.
An escalation should create a decision path, not just copy an executive into an email. Review ResolveCX's escalation management approach for relevant context on triggers, tiers, ownership and human-reviewed decisions. For extended coordination, see customer service case management.
What should the complaint record show?
Another authorized person should be able to understand the issue and decision without reconstructing separate inboxes. Capture enough to support fair handling, while limiting access and retention under applicable privacy, security and organizational requirements.
- The customer's concern, requested outcome, channel and receipt timestamp.
- The complaint identifier, category, severity assessment and named owner.
- Applicable targets, updates, handoffs, accepted actions and changes to dates.
- Relevant evidence, investigation chronology, disputed facts and findings.
- Options considered, rationale, remedy, human approval and final response.
- Delivery of promised action, closure check, review request and recurring-cause referral.
Ask a reviewer to explain what was known, who decided, why, when the customer was told and whether the promised action happened. If the record cannot answer those questions, the procedure needs a clearer evidence rule.
Agree access and retention periods with legal, compliance, privacy and security stakeholders.
What does the procedure look like in practice?
Both examples below are hypothetical workflows, not customer deployment stories or evidence of product capabilities.
Example 01 / Retail
A damaged delivery
A customer reports a damaged item and asks for a replacement. The handler records the complaint and evidence, checks the order and confirms whether the remedy is within delegated authority. If it is, the handler arranges the replacement, gives a delivery expectation and checks completion.
If the product suggests a wider safety issue, the route changes immediately. A simple replacement does not remove the need to assess that risk.
Example 02 / Financial services
A disputed fee and conflicting explanations
A customer disputes a fee and says earlier explanations conflict. The owner acknowledges both issues, confirms the account and relevant interactions, and asks a specialist to check the transaction and policy. An authorized reviewer examines the finding and proposed response.
The owner sends any required interim update, issues a reasoned outcome within the applicable jurisdictional clock, and records any correction and review route. The organization must check its regulatory scope before setting that clock.
How can teams implement and improve the procedure?
Start with a small sample of recent complaints: one simple resolution, one cross-team investigation and one deadline exception. Walk each through the proposed rules. If staff cannot identify the next owner, approval boundary or customer-update date, revise the procedure before configuring software or training everyone.
- List monitored channels and define what counts as a complaint.
- Assign decision authority and an accountable owner for each path.
- Define clock starts, reminders, update rules and exception approvals.
- Specify required evidence and the minimum final-response review.
- Rehearse handoffs, disputed findings, absence coverage and missed-target scenarios.
- Sample closed records and refer repeated causes to an improvement owner.
Measure the quality of handling, not just speed
Track acknowledgment timeliness, overdue open complaints, unaccepted handoffs, missed updates, reopened cases, delivered remedies and recurring causes. Segment results by complaint type and risk.
A low complaint count can mean customers cannot reach the process. Fast closure can hide weak investigation. Pair timing measures with record sampling and customer outcomes.
At each monthly review, sample complaints that closed quickly as well as those that missed a target. Check whether the promised action happened, whether the decision addressed every material issue and whether any escalation was accepted. Assign each improvement an owner and a review date.
Keep people responsible for decisions
Software can connect owners, deadlines, evidence, decisions and related cases. AI may assist classification or summarization, subject to review rules and data controls. People should retain responsibility for remedies, approvals and consequential communications.
ResolveCX's complaint, case and escalation modules are relevant where teams need those distinct activities connected. Configuration and operating practices still determine whether a procedure works.
Test the procedure before you rely on it
Try a real transfer, a disputed finding and an approaching deadline. Each scenario should still have a named owner, a valid clock, sufficient evidence and a clear customer update. Adapt the model to your sector and check applicable obligations before publishing targets.
To examine the workflow with your team, discuss your complaint process with ResolveCX.
Frequently asked questions
Receive, acknowledge, assess, assign, investigate, decide, respond, then verify the remedy and review causes. Simple matters may complete several steps together; complex matters need separate investigation and approval. Keep the customer informed throughout.
The organization should name one accountable complaint owner for the customer outcome and next update. Frontline staff, specialists, managers and compliance teams may perform different tasks. A transfer needs acceptance and a dated next action so responsibility does not disappear between teams.
Use the applicable sector rule or a published internal commitment. There is no single global acknowledgment deadline. Tell the customer what was received, who to contact and when to expect the next update. Confirm the local business-day counting rule.
It begins at the event specified by the applicable rule, contract or published policy, often receipt of the complaint. Do not assume an internal reassignment restarts it. Record the original timestamp and any distinct stage or update clocks.
Yes, when the issue is understood and the handler has authority to deliver a proportionate remedy. Record the concern, action and outcome even if the conversation ends quickly. Route material risk or disputed facts for further review.
Escalate when the issue needs higher authority, specialist risk review or intervention to protect a deadline. Define the receiving owner and information required. Anger alone does not explain the underlying risk, so assess the facts as well as tone.
The person with delegated authority under the organization's procedure. Routine actions may sit with frontline staff; sensitive findings or substantial remedies may need management or specialist review. Record who approved the decision and the rationale.
Address the material issues, explain the finding and reasons, state any remedy and delivery date, and provide the applicable review or external referral route. Match the response to the approved decision and retain it with the record.
The owner should raise the risk before the deadline, obtain any required approval, explain the delay and give the customer a realistic update. An internal extension cannot override a binding external limit. Retain the reason and revised action plan.
Group complaints by underlying cause, check whether different channels report the same failure, and assign corrective work to a responsible team. Review whether the change reduced recurrence. Closing individual customer records does not itself remove the cause.
Sources
Use the original sources to check scope and current requirements. Source inspection is not legal or compliance approval of your procedure.