Two weeks before the ISO 9001 audit, the same exercise starts at many forwarders. The quality manager asks dispatch for last year's complaints. Dispatch searches the inbox. Customer service searches the key account's portal. Billing searches for credit notes. The result is a spreadsheet. The auditor leafs through it and asks whether the corrective actions worked. Then it gets quiet.
My position: the audit is the wrong opponent. Whoever collects ISO 9001 complaints two weeks before the audit has the problem in the wrong place. The record has to be created where the complaint arrives. In the inbox, in the customer portal, in the TMS status. Everything else is reconstruction, and reconstruction is exactly what an auditor does not want to see.
The standard is specific here. ISO 9001:2015 clause 8.7 covers the control of nonconforming outputs. A damaged pallet, a late delivery, a short quantity: all nonconforming outputs. Under 8.7.2 the organisation has to retain documented information with four items. What the nonconformity was. What action was taken. What concession the customer granted. And who decided.
Clause 10.2 goes one step further. The organisation has to react to every nonconformity. It has to evaluate the cause. And it has to check whether similar cases exist. Under 10.2.2 the evidence has to show the nature of the nonconformity, the actions taken, and the result of the corrective action. Management review under 9.3 then needs customer feedback and nonconformities as input. In plain words: one line per case, with date, type, action, concession, result. And a summary on top.
This is not an exotic requirement. ISO 9001 is the most common management standard in the world. The ISO Survey 2024 counts 1,474,118 valid certificates. At the forwarders we talk to, it is basic equipment. And the list is built by hand before the audit. The audit consultancy secjur keeps a list of typical findings (May 2026). Near the top: nonconformities are discussed verbally but not documented. No cause analysis, no corrective action. (That is not a reproach to the quality manager. He never saw the complaint. It sat in a dispatcher's inbox.)
A complaint at a forwarder has three entry points. The customer's mail to the dispatcher, usually with the subject "Tuesday's delivery". The key account's portal, where a ticket opens with a category and a deadline. And the TMS, where the driver noted damage on the proof of delivery. None of these three entry points writes into the QM system. So a human writes. Or nobody does.
Then there is transport law. Under Article 30 CMR, apparent damage has to be reported at delivery. Non-apparent damage within seven days. Delay within 21 days. For German domestic transport, section 438 of the Commercial Code sets the same deadlines, in text form. So the time a complaint arrives is more than a line in the audit evidence. It decides whether a claim exists at all. Reconstruct it two weeks before the audit and you can no longer prove it.
That is the core of the argument. The quality manager cannot make the list better, because it is created in the wrong place. The entry channel has to write it.
We build this in logistics projects as a mail agent with a protocol. The pattern is the same as order capture from mail and PDF. Only the classes differ.
First, the agent reads the complaints mailbox and the dispatch mailboxes. For every mail it decides: complaint, no complaint, or unclear. "Quick question about Tuesday's delivery, the goods arrived wet" is a complaint. The customer just did not call it one.
Second, it classifies into three types: damage, delay, shortage. Plus a fourth class, "unclear". The fourth is the important one. Anything the agent cannot assign with confidence goes into a review list with a reason. A human decides in seconds. The agent learns nothing from that, and that is deliberate. The rules stay readable.
Third, it links the case to the shipment. The shipment number sits in the subject line. Or plate, date and consignee sit in the text. Both are matched against the TMS. No shipment, no line. With the shipment, everything the auditor wants to see hangs on the case. Customer, tour, driver, delivery time, proof of delivery.
Fourth, it writes the protocol. Entry with timestamp, type, shipment, deadline under CMR or the Commercial Code, status. Every further step is added as a line. Reply to the customer. Credit note. Corrective action. Effectiveness checked after 30 days. The ISO 9001 evidence for clauses 8.7 and 10.2 is an export of this table in the end. Filtered by period.
Fifth, it delivers the metric per customer. Complaints per 1,000 shipments, by type, by month. Nobody had that number before. It belongs in the management review, and it belongs in the next customer meeting. (A customer with three shortages a month usually has a problem in his own goods receipt. Sales would rather have that conversation with numbers.)
Three honest limits.
The complaint by phone. The agent reads mails and portals. What the dispatcher hears on the phone, he has to enter himself. A form with three fields is enough, but it has to exist. Otherwise the one case the auditor samples is the one that is missing.
The portal without an interface. Many key accounts run complaints in their own portal. Without an API, the option is a browser agent that reads the portal like a dispatcher. That works. But it needs its own protocol, and a fallback for the day the interface changes.
The ticket system that already exists. Whoever already runs every complaint through a ticket system with mandatory fields does not need an agent. He needs an export. The agent is the answer to scattered inboxes, not to a working system.
A caveat on the data: I have not found a solid industry figure for how often forwarders receive complaints. What I see are individual operations. Their numbers do not transfer, so none are in this post.
Mailbox access via IMAP or Graph. A classifier with four classes and readable rules. A match against the TMS shipment table. A protocol table with a deadline field. A review list with reasons. A monitor that counts the runs and reports when they stop. None of this has to be invented. What is new is the timing. The complaint becomes a line at the point of entry, not two weeks before the ISO 9001 audit.
Which entry channel swallows your complaints, inbox, portal or phone? Tell me. If it is the inbox, I will show you the agent's protocol on one anonymised mail.
