Service Evidence: Your Quality Crisis Is Hiding
Most manufacturers do not have a quality-information problem. They have an evidence problem. Service evidence reaches support every day, then gets compressed into labels such as “noise,” “intermittent,” or “customer error.” By the time the quality team sees a pattern, customers have already lived through it.
Nidec offered a brutal reminder this week. An independent investigation identified 844 cases of quality-related misconduct across the group. The cases included unauthorized changes to materials and processes, falsified test results, and shipments of substandard items. The company’s response calls for stronger quality governance and better information management. You can read the investigation summary from Nidec.
That report does not say customer support could have uncovered the misconduct. However, it exposes a broader operating risk. Centralized quality data has little value when the evidence entering the system is vague, delayed, or stripped of context.
Service Evidence Needs More Than a Ticket Field
Most support systems are built to move cases, not preserve reality. An agent selects a reason code. A technician adds a short note. Then someone closes the case after a refund, replacement, or repair.
That workflow may satisfy the customer. However, it often destroys the signal that product and quality teams need. As a result, support reports activity while quality teams miss repetition.
Suppose twenty customers report that a motor “sounds wrong.” One agent writes “unusual noise.” Another chooses “performance issue.” A third marks the case “resolved” after arranging a replacement. Consequently, one physical pattern becomes three unrelated records.
The problem gets worse when the failure appears only under load, at a certain angle, or after several minutes. Text cannot preserve timing, motion, sound, location, and operating context with equal precision. Service evidence can.
Yet many companies treat photos and video as attachments. They are stored at the edge of the case, if they are captured at all. Quality teams receive the summary, not the source material.
Customer Descriptions Destroy Detail
Customers are not unreliable. They are simply not trained to describe a physical failure in the vocabulary your engineers use.
Ask a customer where a leak begins, and you may get “under the unit.” Ask whether a panel is misaligned, and you may hear “it does not close right.” Those answers are reasonable. Still, each answer forces the next person to interpret it.
Every interpretation removes detail. Therefore, a support case can become cleaner as a record while becoming less useful as evidence.
I have seen this repeatedly while building Viewabo. The hard part is rarely getting a customer to cooperate. The hard part is helping a support agent see the same thing the customer sees before the case turns into a dispatch or replacement.
That distinction matters because diagnosis begins with observation. If the observation is weak, every downstream decision rests on a guess.
Visual Proof Changes the Escalation
Remote visual support gives the agent a chance to capture service evidence during the first interaction. The agent can ask the customer to show the label, connection, movement, damage, or operating condition. Next, the agent can guide the view toward details that matter.
This changes more than resolution speed. It creates a record that another expert can review without reconstructing the whole event from notes.
For example, a quality engineer can compare several videos and notice that a vibration begins at the same component. A product manager can see that customers repeatedly install one part backward. A service leader can separate product defects from training gaps.
Those are different problems. They should not share one reason code.
In addition, visual proof protects the customer. A clear record reduces arguments about misuse, warranty eligibility, and whether damage existed before service. We made a similar point in our article on why warranty support needs remote visual inspection.
Quality Teams Must Join the Support Loop
Capturing better service evidence is only the first step. Someone must review it, classify it, and connect repeated observations.
First, define which cases deserve visual capture. Safety concerns, repeat failures, disputed warranty claims, and no-fault-found visits are obvious candidates. Then give agents a short capture checklist for each product family.
Next, make the evidence searchable by product, component, symptom, and operating condition. Do not bury it in a generic attachment folder.
Finally, create a regular review between support, field service, product, and quality. The goal is not another dashboard. The goal is to identify weak signals before they become expensive patterns.
Support leaders also need to resist a familiar mistake. A closed ticket does not mean the underlying issue disappeared. It only means the customer interaction ended. Therefore, resolution status should never decide whether quality teams see the evidence.
Service request resolution should require evidence of the restored outcome, not just proof that an assigned task was finished.
Build the Evidence Path Before the Crisis
After a quality failure becomes public, companies centralize reporting, rewrite controls, and appoint review committees. Those steps may be necessary. Still, they begin after the cost is visible.
The cheaper move is to build an evidence path from the customer to the people who can change the product.
Start with one high-cost case type. Capture video during support. Preserve the original recording. Tag the physical symptom. Route recurring patterns to quality. Then measure whether diagnosis improves and repeat visits decline.
This is not a grand transformation. It is disciplined observation.
Most quality crises do not arrive as one dramatic alert. They arrive as scattered calls, repeated replacements, unexplained noises, and technicians saying, “I have seen this before.”
Your customers may already be showing you the pattern. The question is whether your support operation preserves enough service evidence for anyone else to see it.