Complaint Resolution Workflow for SMBs: A 5-Stage Kanban That Actually Closes Issues

Most SMB Complaint Processes Stall at Stage One . Intake

A 50-person manufacturing facility receives 80 supplier complaints per month. 15 arrive via WhatsApp to the operations manager's personal phone. 30 come as email to the factory@gmail.com address, which three people monitor sporadically. 20 are phone calls to whoever answers. 15 are written notes left at the goods-receiving bay. Each channel is checked on a different schedule. Nobody owns the end-to-end process. A complaint about defective materials sits in the WhatsApp thread for three days. An invoice discrepancy email gets a 'Thanks for flagging' reply but no actual investigation. A phone complaint is promised a callback that never comes.

The problem isn't that complaints are arriving it's that arrival doesn't trigger a defined workflow. Without structure, complaints are acknowledged informally and disappear. The submitter never knows if anyone is actually investigating. The business never knows if the issue is resolved. The pattern repeats until trust erodes and the supplier switches vendors.

The 5-Stage Complaint Resolution Kanban Explained

**Stage 1 – Received:** A supplier submits a complaint via QR code on Tuesday at 2:15 PM. The system auto-logs it with a timestamp, assigns it a unique tracking code (#FSV-4521), and categorizes it based on the dropdown the submitter selected. The complaint is now visible in the 'Received' column on the Kanban board. It has not yet been looked at, but it has been logged. The submitter receives their tracking code immediately.

**Stage 2 – In Review:** The quality manager opens the dashboard Wednesday morning, sees the new submission, and reads it. They may need clarification ('What batch number?') and request more information from the submitter via the tracking code. Once they understand the issue, they assign it to the appropriate team member (the quality officer, the logistics manager, the procurement team) and move it to 'In Progress.' The submitter can check their tracking code and see 'In Review being investigated by Quality Team.'

**Stage 3 – In Progress:** The assigned team member starts investigating. They contact the supplier for more details, check records, conduct tests if needed, and document findings in internal notes (invisible to the submitter). The status stays in 'In Progress' until resolution is ready. The submitter can check their code anytime and see 'In Progress Assigned to Quality Officer' with the assignment date.

**Stage 4 – Resolved:** The investigation is complete. The issue has been fixed (a new batch shipped, a process corrected, an invoice re-issued). A public reply is drafted and sent: 'We've investigated the defect. The supplier has been corrected and a replacement batch is shipping tomorrow.' The status changes to 'Resolved.' Resolution time is automatically calculated (days from Received to Resolved).

**Stage 5 – Closed:** The submitter confirms they received the resolution and are satisfied, or the manager marks it 'Closed no further action needed' if the complaint was out of scope or duplicate. The complaint is archived for reporting. Closed items feed into the resolution rate calculation (Resolved + Closed ÷ Total × 100).

Roles and Responsibilities at Each Stage

Clarity about who owns which stage is essential. **Receive stage:** Any team member with dashboard access can receive a new complaint. Ideally, the system sends an automatic email notification to the operations manager so nobody misses incoming items. **Review stage:** The team lead or operations manager reviews the complaint and decides who should handle it based on category and complexity. **Resolution stage:** The assigned team member (quality officer, maintenance contractor, procurement manager, etc.) investigates and fixes the issue. **Reply stage:** Often the same person who resolved it sends the public reply this creates accountability and ensures the submitter hears from someone with full knowledge of the fix.

Internal notes are critical for accountability but invisible to submitters. When the quality officer investigates a defect claim, they document their findings, root cause analysis, and corrective action plan in internal notes. When a contractor fixes a maintenance issue, they document what they found and what they did. When procurement investigates a billing discrepancy, they note exactly what was corrected. These notes are for internal accountability and audit trails, never shown to the submitter. The public reply summarizes the outcome in customer-friendly language.

How to Measure Whether Your Complaint Resolution Workflow Is Working

Your primary metric is resolution rate. In November, your manufacturing facility received 85 complaints. By December 5th, 70 have been moved to 'Resolved' or 'Closed.' Your resolution rate is 82% above the healthy benchmark of 80%. This single number tells you whether your workflow is functioning. If it's 45%, your team is receiving complaints but not closing them. If it's trending upward month-to-month (45% → 55% → 68% → 75%), your operational maturity is improving.

Secondary metrics reveal system health. Average resolution time (days from Received to Resolved) shows whether your team is fast or slow. If it's 35 days, you're taking too long submitters lose faith. If it's 2 days, you're moving quickly. Submissions by category ('Defect' is 35% of all complaints, 'Billing' is 20%) show where problems concentrate. Monthly trends show whether specific categories are getting worse or better. Red flags: anything sitting in 'In Review' for more than 72 hours is stalled and needs escalation. If >20% of closed items lack a public reply, your communication process is breaking down.

FAQs