AI Technical Support: Troubleshooting Hardware Products
Technical support for a physical product is different from answering order questions. The customer has a device that does not work, the answer depends on the exact model, and a bad answer sends them to a repair shop for something they could have fixed in two minutes. In the support system from our case study, troubleshooting is done by AI in chat and email for an e-bike brand. These are the rules that came out of that work.
Rule 1: the fix comes first
When a customer asks how to solve a problem, the reply starts with the solution: the steps to try, the way to remove or reset the part, the likely cause, what to do if the steps fail. A customer wrote that the battery lock was jammed and the battery would not come out. An early draft told them to contact their dealer. The removal method was in the knowledge base the whole time.
Dealer visits, warranty verification and requests for photos are steps in a process. They come after the fix, or beside it, never in place of it.
Rule 2: the steps must survive the pipeline
Between the knowledge base and the customer, text passes through filters: one removes internal fields, one shortens, one strips links. Each can delete the answer. We had a filter that removed video links by cutting whole sentences. In the knowledge base, the component, the operation, the cause and the fix were written as one long sentence ending in a link. The filter removed all of it, and for a day one draft in four lost its troubleshooting steps.
The check we now run on any change to that pipeline: take one real knowledge base entry, pass it through, and compare before and after. The business content has to arrive complete.
Rule 3: the right model, the right video
Troubleshooting steps and video guides differ by model and version. Identify the customer's model from the order, not from their description, and pick the guide for it. A video is matched by its own title. A spreadsheet tab once listed videos for several models together, and the agent sent a tail-light video for the wrong bike. Another time a charging-port fault was answered with a video about a battery light cover. When the customer says the video does not match, the agent must not send the same link again.
Rule 4: ask for what a customer can do
A customer with a new bike that would not switch on was told, in the second email, to test the battery with a multimeter. Most customers do not own one. Steps escalate in order: what can be checked by looking, then by pressing and holding, then by reseating a connector, then by a photo or a short video for the team. A tool the customer has to buy is not a troubleshooting step.
Rule 5: do not ask twice
The thread is distilled before the model sees it, into facts that include what the customer has already sent. If a video of the fault is in the thread, the reply works from it. Asking again for material the customer supplied weeks ago is the fastest way to turn a fault report into a complaint.
Rule 6: give a judgement
Often the facts point to a likely cause without proving it. The reply says so: based on these symptoms, our judgement is that the controller is at fault, and this is what we suggest. It does not say "we cannot determine the cause" and stop. It also does not present a guess as a diagnosis: it names the facts the judgement rests on.
Rule 7: answer from the knowledge base, every time
Even when the case cannot be decided yet, the reply gives what the knowledge base has: the standard answer, the process, the video, the part information. In a review of 400 drafts that agents edited, 10 percent of the edits replaced "we have no information on this" with an answer the knowledge base already contained. The fix was in the search, described in why RAG does not find answers.
When troubleshooting is not enough
If the steps fail, the case becomes a warranty or repair matter. The agent proposes a solution, such as a replacement part or a local repair with a reimbursement limit stated in the same email, and a person approves it. When the fault makes the product unsafe, the reply tells the customer to stop using it. The path from there is in AI warranty claim handling.
Chat and email
Chat is good at troubleshooting: the customer is in front of the product, and steps can go one at a time. The chat AI does this directly, including inside the mobile app, where 4,715 of the 15,725 conversations in the 30 days to 19 November 2026 took place. When a part or a repair is needed, the chat creates a ticket listing what has already been tried, so the email team does not start from zero.
By email the AI drafts the full troubleshooting reply. Product questions after delivery are one of the six types in the "AI review" queue for replies the AI sent on its own.
Keeping the knowledge base correct
Support agents find errors in the knowledge base while reviewing drafts. A correction made by the team is kept in a corrections layer that is applied when the entry is read, so the next sync from the source document does not overwrite it. When the source is fixed, the correction is removed.
What to measure
- Faults solved by the first reply, with no part shipped.
- Replies where the customer answered "that is not my model" or "I already sent that".
- Drafts in which an agent added a troubleshooting step. Each one is a gap in the knowledge base or the pipeline.
Who this fits
Brands whose products have firmware, batteries, moving parts or assembly steps, and whose support team answers the same faults in several languages.
Related: what goes into the knowledge base and hallucination examples and fixes. Send us your top ten faults and the free plan maps them within two working days.