A customer's blender stops working after three months. They email your store: "My blender broke." You reply asking for the order number. They reply two days later. You ask for photos. Another day. You ask what exactly happened. By the time you have enough to decide, the customer has written a one-star review.
Warranty and faulty item questions are where customer loyalty is won or lost. Handling them well is mostly about capturing the right information in the first exchange.
Step 1: publish your warranty policy clearly
Customers want to know:
- How long the warranty lasts.
- What it covers and what it does not.
- How to make a claim.
- Whether they get a repair, replacement or refund.
- Who pays for returning the item.
Put this on your website in plain language. It answers many questions before a claim is made, and sets expectations.
Step 2: capture everything in the first exchange
A useful faulty item report includes:
- Order number.
- Which product.
- What is wrong, in the customer's words.
- When it started.
- Photos or a short video.
- Contact details.
Customer: My blender has stopped working. Assistant: Sorry to hear that. It's covered by our 12-month warranty. Could you share your order number, when it stopped working and what happens when you switch it on? A photo of the base would help too. I'll pass everything to the team so they can sort it quickly.
SpideyChat for ecommerce stores captures these details at any hour and passes them to your team. It explains the warranty policy but does not approve claims.
Want a 24/7 AI Employee for Your Website?
See how SpideyChat can answer customer questions, capture leads and handle enquiries while your team is offline.
Step 3: acknowledge fast
Even if the decision takes a day, the acknowledgement should be immediate. A customer who knows their claim is logged and when they will hear back is far calmer than one waiting in silence.
Step 4: decide and act quickly
With complete details, your team can decide in one step: repair, replace or refund. Delay here is what turns an annoyed customer into a lost one.
Step 5: separate faults from care problems
Some reported faults are really care or usage problems: a pan that was put in the dishwasher, a jumper that was tumble dried. Care information on product pages prevents many of these, as covered in care instructions questions are pre-sale questions too. Handle them politely, and consider whether the product page should be clearer.
Step 6: learn from faults
Track faults by product. If one item generates several claims, the supplier or the product itself may have a problem. Customers sending detailed information is the same kind of useful signal software teams get from developer questions, as described in API questions from developers evaluating your product.
Turning a fault into loyalty
Customers do not expect products never to fail. They expect you to put it right. A fast, fair resolution often leaves a customer more loyal than if nothing had gone wrong, because they have seen how you behave when it matters. A short follow-up after the replacement arrives, checking it works, costs nothing and is remembered.
Custom and personalised items
Warranty rules for custom items often differ. State them clearly, and explain them when customers order, as covered in handling custom order requests without losing them.
Answering questions before they become claims
Many "is this normal?" questions arrive before a customer decides something is faulty. Answering them from your product information prevents unnecessary claims, the approach described in how to answer product questions before they reach support. The installation guide and training guide cover setup.