Customer Complaint Tracker

What this tool does

CM8-245 is a working complaint register. You log each customer complaint as it arrives, track it through acknowledgement, investigation, resolution and the final response to the customer, record what it cost you, and print a report that shows the trend, the categories, the justified rate and the money — fit for a management meeting or a customer audit.

Everything runs inside this single file. There is no account, no upload and no network request of any kind, so customer names and commercial details never leave the computer you are using.

Why a complaint is a gift

Most dissatisfied customers do not complain. They pay the invoice, quietly mark you down, and give the next order to somebody else — and you learn nothing until the revenue line tells you, months too late. The customer who complains is doing something more valuable: handing you specific, dated, first-hand evidence of where your process failed, while there is still time to keep the relationship. That is worth treating seriously, which is what this register is for. It does not mean every complaint is right — some are not, and the tool has an honest place for those too — but every complaint is information, and information you did not have to pay a consultant to find.

Intake discipline

Two rules make the rest of the process work.

Acknowledge fast, even without answers. The acknowledgement is not the resolution — it is the message that says "we have it, someone owns it, here is who". Customers forgive defects far more readily than silence. Set an acknowledgement target on the Settings tab (two days is a common working standard) and record the date the customer got that first response. The tile shows what share of complaints met the target; a complaint acknowledged on day nine is remembered as nine days of being ignored, whatever happens afterwards.

Log every complaint, including the ones you think are wrong. A register that only holds the complaints you accepted is a marketing document, not a record. The "unjustified" outcome exists precisely so that logging a complaint costs you nothing in the statistics until the investigation decides it. Filtering at the door — "that's not really a complaint" — is how organisations blind themselves.

Write the summary in the customer's words, not your defence of them. "Burrs on every part, two assemblies scrapped" is a record; "customer unhappy with finish" is a shrug.

Investigating and deciding: justified, partial, or not

Every complaint should end with a decision:

• Justified — your process failed. The complaint was right.
• Partially justified — shared cause: you failed in part, but the customer's own actions, information or expectations contributed.
• Not justified — investigation showed the product or service was as agreed. The outcome is an explanation to the customer, with evidence, not a credit note.

Decide honestly, because the justified rate this produces is the only quality metric your customers ever experience directly. Internal reject rates, audit scores and process capability are invisible to them; the share of their complaints you had to accept is not. A team that marks everything "unjustified" to protect a bonus figure is building a register that will be contradicted by lost customers. A team that accepts everything to avoid difficult conversations is paying credits it does not owe. Both failures are visible in this tool: the category chart shows the split, and a category full of unjustified complaints is its own finding — usually a communication or expectation problem rather than a product one.

Root cause and CAPA

A justified complaint without a recorded root cause is a bill you paid without learning anything, which is why the tool refuses to accept one. The root cause field wants the answer after the whys, not the first symptom: "operator used the wrong file" is a symptom; "nothing links the cutting file revision to the works order" is a cause you can fix.

If you run a formal corrective-action system — 8D, 5-why, or a CAPA process under a quality standard — this register is the intake and the index, not a replacement. Put the one-paragraph cause here and reference the corrective-action record in it. The category and cost charts then tell your CAPA process where to spend its effort: the category that keeps recurring, and the category that costs the most, which are often not the same one.

Counting the cost

The cost field is for everything the complaint actually cost: credit notes, replacement product, rework hours, expedited freight, site visits, incoming-inspection charges passed back to you. Most firms undercount complaint costs by half or more, because the credit note is the only number that reaches an account code — the rework hours vanish into overhead and the freight into the carriage account. Estimate them anyway and record the total here; a defensible estimate beats an accurate zero.

The point of the number is the argument it wins. "Quality complaints cost us this much last year" funds a deburring machine faster than any percentage does.

Responding to the customer

Keep two things separate in your head and in the record. The correction is what the customer gets: the replacement, the credit, the rework, the collection of rejects. The corrective action is what stops it happening again: the process change, the check, the training. Customers are owed the first quickly; your future customers are owed the second. A firm that only ever corrects is running a returns desk; a firm that only ever writes corrective actions while the customer waits for a credit is about to lose the account. Record the correction in this register; keep the corrective action in your CAPA system and reference it from the root cause field.

For unjustified complaints, the response is an explanation with evidence — photographs, test results, the signed variation order — delivered with the same speed and courtesy as a credit note would have been. An unjustified complaint handled well often strengthens the relationship; handled smugly, it ends it.

Closing the loop

The tool distinguishes resolved internally from closed, and the difference is one checkbox: the customer was told the outcome. It is remarkably common for a complaint to be fixed — parts replaced, process corrected — while the customer is left wondering what happened. To them, an uncommunicated resolution is indistinguishable from being ignored. The tool will not let you set a complaint to closed until the "customer informed" box is ticked, and the open-complaints table keeps showing resolved complaints whose customers have not heard, with "inform the customer" as the next step. That is the loop: received, acknowledged, investigated, resolved, told.

Reading the charts

Complaints per month is the headline trend, and it needs careful reading: a falling line can mean happier customers or quieter ones. If complaints fall while repeat orders also fall, customers have stopped telling you and started leaving. A rising line after you make complaining easier is usually good news wearing a bad costume.

Complaints by category ranks where complaints come from and colours red the categories where most decided complaints were justified — your failure. That is the improvement shortlist. Severity of open complaints shows what is on the desk right now; anything critical outranks everything else regardless of age. Cost by category shows where complaints hurt financially — fix by cost as well as by count.

The formulas

Complaints still under investigation are excluded from the justified rate — the denominator is decided complaints only, so the rate does not swing while investigations are open. Complaints not yet acknowledged count against acknowledgement performance, including very recent ones, so the tile is slightly harsh in the days after a complaint arrives; that bias is deliberate and disappears as soon as you acknowledge.

FAQ

Should we log verbal grumbles? If a customer tells you something was wrong, log it — channel "phone" or "in person". The complaints that arrive informally are exactly the ones that vanish otherwise, and severity "low" exists so logging one costs nothing.

What counts as acknowledged? The customer received a response from a person who named themselves as the owner. An automated receipt does not count; a two-line email from the owner does.

What is a good justified rate? There is no universal benchmark and comparisons between firms mean little — the rate depends on what customers bother to complain about. Watch your own trend, and distrust sudden improvements that coincide with nobody wanting to admit fault.

Can a complaint be closed without a resolved date? No. Resolved and closed statuses both require the date, because the average-days-to-resolve figure depends on it.

One complaint covers many parts — one row or many? One row per complaint as the customer raised it. If the investigation splits it into separate causes, keep this row as the customer-facing record and let your corrective-action system carry the split.

Saving your work

Complaints, settings and the report header are written to this browser's local storage as you type, and the toolbar shows the time of the last save. That storage belongs to one browser on one computer: another browser, a private window, a second machine or a clean-up tool that clears site data will not have it.

Treat Export .json as the real save — one file containing everything, which Import .json restores anywhere. Export CSV gives you the register for spreadsheet work. Reset asks twice, then erases everything this tool has stored. There is no undo. A complaint register names customers and failures — treat exports as confidential.

Accuracy & disclaimer

This tool measures the complaints you record. Customers who left without complaining are invisible to it, and every figure it produces — the justified rate above all — is only as honest as the investigations behind the entries. Cost totals cover what you chose to count, and most organisations undercount.

Complaint-handling obligations, response deadlines and record-keeping requirements differ by country and by industry, particularly in regulated sectors. This is an internal record-keeping and analysis aid, not legal advice and not a compliance system.