To reduce avoidable appliance returns, offer safe, model-specific troubleshooting when an operating or setup issue could explain the symptom. Use remote video only when seeing an accessible display, control state or changing sequence could help the advisor choose the next action. Keep service, replacement and return routes open when further checks will not help.
A newly installed dishwasher that will not start illustrates the decision. The advisor may have the order record and a troubleshooting script yet still be unable to tell what the control panel is showing. Another round of questions can add frustration without resolving that uncertainty.
A live view may reveal a state that the manufacturer’s instructions explain how to correct. It may instead show that customer troubleshooting should stop and service should take over. Build the workflow around that distinction, rather than getting more customers onto video.
Offer troubleshooting where it can change the outcome
An avoidable return is one arising from a safely correctable problem that leaves the customer with a functioning, suitable appliance. Damage, an unsuitable purchase or a fault requiring service should not be relabeled as an operating misunderstanding to improve a retention figure.
At intake, capture the customer’s requested remedy separately from the appliance symptom. “Wants a return” describes the request. “New dishwasher will not begin a cycle” describes the problem to investigate.
The advisor also needs:
- The model, preferably from the product record or an identifier the customer can access safely
- Installation status, including whether the appliance has ever operated successfully
- The visible message or behavior and when it occurs
- Checks already attempted and their results
- Any safety concerns
- Whether the customer wants to try further troubleshooting
Offer troubleshooting when a plausible operating or setup issue can be checked safely using current model-specific guidance. Proceed to the applicable service or return route when the reported facts already justify it, the approved checks have been exhausted or the customer does not want to continue. Video participation must not become a condition for accessing an applicable remedy.
This distinction also protects advisor time. A clearly damaged appliance does not need a live demonstration merely to complete a troubleshooting script.
Ask what you need to see before offering video
Before opening a camera session, the advisor should be able to finish this sentence: “Seeing this detail will help me choose between these next actions.”
For the dishwasher, the unresolved question might be whether the visible display and control state match a model-specific operating setting or a condition requiring service. That is more useful than a broad instruction to “show me the appliance.”
Choose the least demanding channel that can answer the question:
| Missing information | Proportionate approach |
| A setting or message the customer can describe clearly | Continue by phone using the exact model’s instructions |
| A static display that is difficult to describe | Request a photograph through an approved channel |
| A changing display or control sequence whose timing matters | Offer live remote video |
| A condition already requiring qualified inspection | Arrange the appropriate escalation rather than seeking more footage |
Use remote visual assistance to follow a relevant change, such as what the display shows before and after a manufacturer-approved check. If the view remains unclear, record the observation as inconclusive rather than guessing at the setting or code.
External installation details belong in the session only if they are relevant and already safely accessible. The customer should never need to pull out the dishwasher to obtain a better camera angle.
Give advisors a short, bounded video workflow
Before launch, provide current model-specific instructions, advisor training, a suitable customer device and connection, a non-video fallback and a clear service or return handoff. Advisors also need to know who owns the case when remote checks cannot resolve it.
Keep each session focused:
- Confirm the gap. Summarize the symptom, previous checks and the observation still needed.
- Ask permission. Explain what the advisor wants to see and how it could affect the next action. Explain whether recording will occur and obtain any required consent before it starts.
- Frame the relevant area. Ask for the accessible display or controls, avoiding people, private documents and unrelated areas of the home. Do not ask the customer to use the device in an unsafe position.
- Guide one approved check. Use the instructions for that exact model. Avoid generic button sequences and improvised error-code interpretations.
- Observe the result. Compare what happens with the expected behavior in the instructions. If the view or result is inconclusive, record that uncertainty.
- Choose the next action. Continue to an appropriate operating test, arrange service or proceed with the applicable replacement or return route.
Routine troubleshooting stops if the customer reports smoke, a burning smell, a suspected gas leak, exposed electrical parts or water near electrical components. Follow the organization’s approved safety procedures and escalation route rather than continuing the camera session to investigate.
Customer actions should stay within accessible, manufacturer-authorized checks. Do not ask customers to move appliances, remove panels, handle electrical or plumbing connections or perform hazardous live testing. A camera does not turn an advisor into an on-site technician.
If the customer cannot or does not want to use video, continue through phone guidance, an approved image channel or the appropriate service or return process. If connection problems prevent a useful observation, switch routes rather than repeatedly restarting the session.
Follow the dishwasher from symptom to next action
Consider an illustrative customer whose newly installed dishwasher will not begin a cycle. They request a return. The advisor confirms the model, installation status and checks already attempted, screens for safety concerns and asks whether the customer would like help checking the accessible controls.
The customer cannot confidently describe how the display changes when they try to start the appliance. Because that sequence could distinguish an operating setting from a service condition, the advisor offers a human-assisted video session, with the customer’s permission, to view the control panel.
Suppose the visible state matches an operating setting described in the exact model’s approved instructions. The advisor guides the documented correction, one step at a time, then asks the customer to confirm the expected start sequence. The next step is the manufacturer’s appropriate operating test.
Now consider the alternative result in the same scenario: the display points to a condition that the manufacturer’s instructions route to installation or service support. The advisor stops customer troubleshooting. The remaining question is which team should take responsibility for the next step.
If ownership is unclear, the advisor and customer can review a relevant installation or warranty requirement through an available, approved channel. It may clarify whether the condition belongs with the installer or the appliance service team. The advisor then explains the handoff and passes the model, symptom, observation and completed checks to the responsible team so the customer does not have to rebuild the explanation.
Record evidence, not a premature resolution
Record what changed and what still needs to be tested. For the dishwasher, “setting corrected, expected start sequence observed” is a useful finding. Beginning a cycle does not establish that the appliance will complete it or resolve every reported symptom. “Resolved” needs support from the manufacturer’s appropriate operating test and any necessary follow-up.
If that test cannot be completed during the contact, record verification as pending and assign an owner to the follow-up. Tell the customer what remains to be checked and how to report a recurring symptom.
A concise case record should include the original symptom, relevant observation, approved check, result, remaining uncertainty and disposition. Distinguish customer-confirmed operation from service arranged, replacement authorized, return initiated and awaiting verification.
For unresolved cases, name the next action, its owner and what the customer should expect. Pass the findings to the receiving team so it can act on completed checks rather than automatically repeat them.
Do not describe an installation issue as a confirmed product defect, or a possible control-setting issue as a confirmed fix. Accurate uncertainty is more useful to the next team than an optimistic closure code.
Measure what happens after the call
Start with a pilot covering a defined appliance category and symptom, such as newly installed dishwashers reported as unable to start. Set eligibility before the video offer. Otherwise, advisors may select the easiest cases and make the workflow look more effective than it is.
Use unique appliance return-request cases as the unit of analysis. Multiple contacts about the same appliance and issue belong to one case, not several opportunities to claim a save.
Define a follow-up window from the initial eligible request before launch. It should be long enough to observe the intended outcome, and both groups need complete, equivalent follow-up.
Completed-return rate = eligible unique cases with a completed return during the stated follow-up window ÷ all eligible unique cases with complete follow-up × 100.
A withdrawn request is not a completed return or evidence of sustained operation. Exclude cases whose follow-up window has not yet elapsed and report their number separately. All eligible cases whose window has elapsed stay in the denominator, including those with a pending return. Report pending returns separately so delays remain visible.
A practical evaluation should specify:
- The baseline period and comparable model, symptom, installation-stage and purchase-timing groups
- How cases enter the pilot and comparison group, ideally through random allocation of the offer where feasible or a documented matching method
- How duplicate contacts are linked to the original case
- How replacements are classified, reported separately and treated consistently in both groups
- How later returns and faults are linked back to the original case
Assess the effect of offering the workflow across eligible cases. Comparing only customers who accept video with those who decline can mislead because their circumstances and willingness to troubleshoot may differ.
Track completed-return rates alongside sustained operation, subsequent faults, repeat contacts, service escalations, customer effort, time to an appropriate remedy and total support cost. Include video handling time, follow-up and downstream service work in that cost view.
A lower return rate with more repeat faults or a longer wait for a remedy is not a successful result. Neither is shifting the same unresolved problem into the service queue.
Use recurring findings to improve the source of the problem. Repeated confusion about a model-specific setting may justify clearer setup instructions and advisor guidance. Repeated uncertainty about installation responsibility may call for a better handoff. Those improvements may eventually remove the need for some video sessions.
