What to Do When a Customer Files a Quality Complaint

A customer just sent an email. One of your parts failed. They want to know what happened and what you are going to do about it.

How you respond in the next 24 hours matters more than almost anything else about that relationship. A complaint handled well can strengthen a customer relationship. A complaint handled badly — or ignored — costs you the account.

Here is what to do.

In the First 24 Hours: Contain, Acknowledge, Commit

Before you investigate, before you write a root cause, before you do anything else — respond to the customer.

Not with an investigation. Not with a defense. With a simple acknowledgment:

You have received their complaint
You are taking it seriously
You will have an initial response by a specific date

This matters because customers who do not hear anything assume you are not doing anything. The complaint goes to their purchasing manager. Then their quality director. Then you get a formal corrective action request with a three-day deadline instead of a conversation.

While you are acknowledging, contain the problem:

Quarantine any suspect inventory at your facility — anything from the same lot, same run, same time period as the complaint
If the customer still has affected parts, advise them to hold until you can verify
If you have shipped to other customers from the same lot, identify them now — you may need to notify them too

Containment is about stopping the bleeding. You are not waiting for the root cause investigation to finish. You are acting now on what you know.

Gather the Facts Before You Form an Opinion

Once you have contained the problem and acknowledged the customer, start collecting information — not opinions. Not explanations. Facts.

From the customer:

The exact part number, revision, and lot number (if available)
What failed, where it failed, and when it failed
How many parts are affected
Whether they have photos, measurements, or a failed sample they can send back

From your own records:

The production record for that lot — who ran it, what machine, what material, what date
The inspection record — what was checked, what the results were, who signed off
Any deviations or unusual events noted during production

Do not rely on memory. Pull the actual records. The production record will show you facts that people on the floor may not remember or may misremember under pressure.

If the customer can return failed parts, request them. Physical evidence is almost always more useful than a photograph. The failure mode on the part itself often tells you where in your process the problem originated.

Find the Real Root Cause

Here is the thing about customer complaints: the cause is rarely what it looks like on the surface.

A weld that cracked. A dimension that was out of tolerance. A part that did not fit. These are symptoms. The question is why they happened — and why your inspection process did not catch them.

Use the 5 Whys to trace each symptom back to its system-level cause.

Take a dimensional failure as an example:

The diameter was out of tolerance. Why?
The operator did not check it during production. Why?
The in-process inspection step was missing from the job traveler for this part number. Why?
The traveler was written before the customer tightened the tolerance. Why?
There is no process to update travelers when customer specifications change.

The root cause is not the out-of-tolerance part. It is the gap in your change control process. Fix that, and this class of problem stops happening — not just for this part number, but for all of them.

A good root cause analysis answers both of these questions:

Why did the defect happen?
Why did our inspection process fail to catch it?

Both matter. Your customer wants to know that the part will not fail again. They also want to know that if something does go wrong in the future, you will catch it before it reaches them.

Write the Response

Most customer complaints, once escalated formally, require a written corrective action report. But even if the customer just wants an email response, the content is the same.

A complete response includes:

Problem description. What happened, with specifics. Part number, lot, quantity affected, failure mode.

Immediate containment. What you did in the first 24–72 hours. Quarantine, inspection, notification. What you found.

Root cause. Your 5 Whys chain. Not just the conclusion — the reasoning. This is what auditors and sophisticated customers look for. A root cause with no supporting logic does not hold up to scrutiny.

Corrective action. What you changed, specifically. Not "will improve training" — "updated work instruction WI-031 to include in-process dimensional check at the 40mm station. Effective March 22. All operators briefed and signed."

Effectiveness verification. How you will confirm the fix worked. "Will inspect 100% of the first three production runs following the change and report results." Then actually do it and report back.

Preventive action. Did you find anything similar elsewhere? Did you check? Write what you checked and what you found.

Keep it factual. Avoid passive language. "The operator grabbed the wrong part" is better than "the incorrect part was inadvertently selected." Own what happened and show what you did about it.

Things That Make a Customer Escalate

Understanding what makes a customer escalate — or stop ordering — helps you avoid the outcomes you do not want.

Late response. No response in 48 hours is often treated as no response at all. Set a calendar reminder when you receive a complaint.

Blaming the operator. "The operator made a mistake" is not a root cause. Customers know that people make mistakes. What they want to know is whether your system prevents those mistakes or catches them before they ship. If your answer is "we will retrain the operator," expect a follow-up.

Vague corrective actions. "We will be more careful" or "we will increase attention to this area" are not corrective actions. They tell the customer nothing has actually changed.

No effectiveness verification. Saying the fix worked is not the same as showing the fix worked. Whenever possible, include data. First article results. Pass rates over the first three runs. A supervisor sign-off date.

Missing the second question. Customers care about the failure. They care just as much about why inspection did not catch it. A response that explains the defect but ignores the inspection escape is incomplete.

After the Response: Keep the Thread Open

Do not close the loop in your response and then go quiet.

If you committed to monitoring the first three production runs and reporting back, do it. Set the reminder now. Put it on someone's task list with a due date.

Follow-through after the initial response is what builds trust. A customer who filed a complaint and got a careful, complete response — and then heard back with effectiveness data — will tell you something important: "we are satisfied and consider this closed." That is a relationship strengthened, not damaged.

The ones who escalate, or reduce orders, or quietly switch suppliers — they are almost always the ones who filed a complaint, got a response, and then heard nothing.

What CLEO Does With Customer Complaints

When a customer complaint comes in, CLEO logs it as a problem, walks your team through the 5 Whys investigation, tracks the corrective action to completion, and reminds you to verify the fix held.

The paper trail that customers and auditors want — problem statement, root cause chain, corrective action with owner and date, effectiveness check — is created automatically as your team works through the process.

You focus on actually solving the problem. CLEO keeps the record straight.

The Short Version

When a customer files a complaint:

Acknowledge within 24 hours with a specific response date
Contain suspect inventory immediately
Collect facts from production and inspection records, and from the customer
Run a 5 Whys analysis — find the system cause, not just the symptom
Write a response with problem description, containment, root cause, corrective action, and effectiveness plan
Follow through on the effectiveness check and report back

The customers who stay are the ones who believe you take problems seriously and fix them for real. A complaint, handled right, is how you prove that.