Can AI draft the reply to a customer's technical complaint?
Summary
Only if a person checks it: AI can draft the complaint reply, but someone must confirm lot, CoA and cause facts before sending. That holds for chemical and lubricant complaints answered in writing. Generated text can state errors with confidence, and a reply that has reached another company's inbox cannot be pulled back.
ISO 10002:2018 gives guidelines for complaints handling in organizations, and ISO reviewed and confirmed it in 2023, so the 2018 edition remains current (ISO, 2023).
ISO 9001:2026, the sixth edition of the quality management standard, was published on 16 September 2026 and retains the Harmonized Structure used across ISO management system standards (ISO, 2026).
Outlook can recall a sent email only if sender and recipient have Microsoft 365 work or school accounts in the same organization and the message is unopened (Microsoft Support, 2026).
NIST AI 600-1 names automation bias, "excessive deference to automated systems", as a risk that can make confabulated output worse (NIST, 2024).
When is an AI-drafted reply to a technical complaint safe to send?
An AI-drafted reply to a technical complaint is safe to send only after a person has checked each fact in it against the lot record and the Certificate of Analysis (CoA) and approved every commitment it makes. The table below gives the verdict for each part of a typical draft answering a chemical or lubricant complaint.
Situation | Verdict | Why |
|---|---|---|
Acknowledgment: received, case number, next step and date | Yes, after a quick read | States no cause and no fault |
Cause named before the lot record and retained sample are checked | No | Commits the supplier to an unproven cause |
Lot number, CoA values or SDS revision quoted | Only if each is checked against its source document | Generated text can be confidently wrong (NIST AI 600-1, 2024) |
Apology for the disruption | Yes, if it names no cause or fault | Regret is not a finding |
Credit, replacement, return or visit offered | No, without the approver's sign-off | A promise the company must keep |
Customer's storage, dilution or mixing blamed | No, until the evidence shows it | May be wrong and reads as deflection |
Another customer's case or data mentioned | No | Confidential information leaves the company |
The row that decides most drafts is the first: an acknowledgment that names no cause can go after a quick read, while any sentence that states a cause or offers a remedy waits for the facts and the approver. Splitting the reply this way also keeps the customer informed early: the acknowledgment goes the same day, and the technical answer follows once the retained sample has been tested and the investigation owner has signed off.
What should a complaint reply not say before the cause is confirmed?
A technical complaint reply written before the cause is confirmed should not name a cause, accept or deny fault, or promise an outcome. It should say what was received, what will be checked and when the customer will hear next. AI drafts tend to fill that gap with a plausible explanation, and NIST defines confabulation as "The production of confidently stated but erroneous or false content" (NIST AI 600-1, 2024). In a chemical complaint, a plausible cause such as a contaminated batch or wrong dilution on site can be wrong in either direction.
Quality management systems treat the cause as a finding of the investigation, not as its starting point. ISO 9001:2026 retains the Harmonized Structure (ISO, 2026), whose clause 10.2 requires the organization to "evaluate the need for action to eliminate the cause(s) of the nonconformity", including "determining the causes of the nonconformity" (ISO/IEC Harmonized Structure, 2025). A reply that states a cause before that evaluation commits the supplier, in writing, to an answer its own investigation has not reached. Cut phrases such as "caused by", "due to", "a one-off" and "your process" from the draft until the evidence supports them.
Where is the line between an apology and admitting liability in a complaint reply?
In a technical complaint reply, an apology expresses regret for the customer's trouble, while an admission states that the product or the supplier caused it. Keep the first and hold the second until the investigation is complete. "We are sorry for the disruption to your line" accepts no cause; "We are sorry our product failed" does. AI drafts often blend the two because both read as polite.
The line matters most where a complaint may turn into a claim. Rules on apologies, warranty and liability differ by country and by contract, and this article gives no legal advice. If the complaint mentions damage, injury, a recall or a claim for costs, send the draft to whoever handles legal or insurance matters before it goes out.
ISO 10002:2018, the guideline for complaints handling, includes "recognizing and addressing the needs and expectations of complainants" among the aspects it covers (ISO 10002:2018). A customer whose line stopped needs to know who owns the case, what is being checked and when they will hear back. Those three facts carry more weight than any wording about fault, and an AI can draft them well because they need no cause.
Which facts must be checked before replying to a technical complaint?
Before replying to a technical complaint, check five things against their source: the lot number, the CoA values, the SDS revision, every commitment in the draft and the recipient list. An AI draft can copy these correctly from the records it was given, but it can also mix up two lots or quote a superseded CoA, and the customer will read every number as checked.
Check | Confirm against | If skipped |
|---|---|---|
Lot number and ship date | Delivery note and lot record | The reply answers about the wrong batch |
CoA values quoted | The CoA for that lot | A typo becomes the supplier's statement |
SDS revision referenced | Current SDS on file | The customer acts on outdated hazard data |
Dates, credits, replacement, visits | The named approver | A commitment nobody agreed to |
To, Cc and attachments | The case file | Internal notes or other customers' data leave the company |
The recipient line deserves the last look because a sent email is hard to take back. Outlook recall works only if both sender and recipient have Microsoft 365 work or school accounts in the same organization and the recipient has not opened the message (Microsoft Support, 2026), which rules out a customer at another company. For the approval rules that apply when an agent can send mail itself, see Is it safe to let an AI agent send emails to customers?. In Lubinpla, the main agent drafts the reply and suggests edits from the customer's records and CoA, and by default shows an approval card before the email is sent; sending needs the Gmail connection.
Frequently asked questions
Can AI acknowledge a technical complaint without a full review?
An acknowledgment that only confirms receipt, gives a case number and says when the customer will hear next carries little risk, so many teams let it go after a quick read. It should name no cause, no fault and no offer. Once a draft contains any of those, it needs the full fact check.
Should a complaint reply quote CoA values taken from an AI draft?
Quote CoA values only after comparing each one with the CoA for the same lot. The CoA is the supplier's own record, so a value copied wrongly into a reply puts two different numbers for the same lot in writing, and the customer will ask which one is true.
Is ISO 10002 a requirement for answering complaints?
No. ISO 10002:2018 gives guidelines, and ISO describes its process as "suitable for use as one of the processes of an overall quality management system" (ISO 10002:2018). A customer's contract or quality agreement may set reply times, so check it before promising a date in the reply.