Playbook, electronics retailer
Passing on a diagnosis that has run out of road
This handover happens in the middle of something rather than at the start of it. A few things have been checked, a few have been ruled out, and the next honest move is to stop. What makes it distinctive is that there is already work in the conversation worth carrying across, and the commonest failure is not the stopping, it is letting the next person begin again from nothing.
Why this is not the general answer
The handling pattern for asking for a person holds across every trade. What follows is the part that does not.
- This one happens mid diagnosis rather than at first contact, so there is real work in the conversation already and losing it is the main risk.
- Four things travel with it that the customer will otherwise be asked for twice: the model, the serial number, the symptom and what has already been tried.
- Continuing to guess past the stable checks is worse than stopping, because a wrong instruction given in the shop's name becomes the shop's advice.
- The serial number decides which of the three covers applies, so collecting it at handover is what lets the next reply be a decision rather than another question.
How it arrives
- can someone actually help me with this
- i have tried everything you said
- i need to talk to someone technical
- can i bring it into the shop
- is there someone who knows this product
- i want to send it back as faulty
What has to be indexed for this to work
| What the technical team needs in a first message | Model, serial, symptom, when it started, what has been tried and what changed just before. Six fields, and a message carrying all six is answered once instead of three times. |
|---|---|
| Where the serial number is printed | Per product family, in plain terms: under the base, inside the battery compartment, on the box end label. This is the field customers cannot find and the one that unlocks the cover question. |
| The in store and send back routes | Which products can be brought to a counter, which have to be sent, whether anything goes direct to the maker, and what the customer needs to bring or include. Choosing the wrong route costs a fortnight. |
| Published response times for a technical enquiry | What the team has committed to, so the handover can end with something concrete. Somebody who has just spent ten minutes failing to fix a device needs to know when a human will look. |
The reply
I have taken this as far as I usefully can, and guessing further would waste your time. Leave your name, email, the model and the serial number, which on this range is on the label underneath, and describe what it is doing and what you have already tried. That reaches somebody technical with the whole picture, so their first reply can be a decision about repair or replacement rather than another round of questions.
Saying it has run out of road is more honest than a soft deflection, and it stops the customer waiting for one more suggestion. Naming exactly where the serial number is printed removes the single commonest cause of a second exchange. Telling the customer what the handover buys them, a decision rather than more questions, is what gets the form filled in properly.
Where it stops
The trigger. The stable checks are exhausted, the next step would be a settings menu, or the customer uses the word faulty.
This needs somebody technical. Leave your name, email, the model, the serial number and what you have already tried, and they will come back with what happens next.
It stops answering before it guesses, says who will pick it up, and asks for the one thing that makes a reply possible. Nothing about it reads as a dead end.
Never say this here
Out of bounds
- Never say the unit is faulty, or that it is not.
- Never promise a repair, a replacement or a refund at the point of handover.
- Never offer one more thing to try after saying the diagnosis has stopped.
- Never ask for a card number, an account password or a proof of purchase image in the message field.
Questions
- Why collect the serial number at handover rather than later?
- Because it decides which of the three covers applies, and asking for it later costs a full exchange. It is also the field the customer is least likely to find on their own, which is why the wording should say where it is printed rather than just ask for it.
- Does the team see what was already tried?
- Only what goes into the message, so the wording has to ask for it explicitly. That is why the reply names the four things rather than saying add any details. A vague prompt produces a vague message and the diagnosis restarts.
- Should it ever suggest bringing the item in?
- Where your material says that product can be handled at a counter, yes, and it is often the fastest route. Where the maker insists on handling it directly, sending somebody to a counter that will turn them away costs them a journey and costs you the goodwill.
Keep reading
- Everything for a electronics retailerCompatibility, warranty and returns on opened items answer well from your own terms. Firmware level setup advice does not.
- Handling asking for a person in generalThe design question at the centre of a support assistant. Offer early, offer once, collect what a reply needs, promise a time you can keep.
- The launch date was never the shop's to promiseA release date belongs to the maker. What a status line means when an order is waiting on stock the retailer has not received yet.
- No safe place, no neighbour, and somebody has to be inValue forces a signature, cells restrict the route, and a large screen is a booked appointment with two people and an old unit to remove.
- It comes back with everything in it or it does not come back wholeSeals, cables and an account registration decide this rather than the calendar. What has to be undone before the box travels back.
Try it on your own material
Upload a document or point it at your site, paste one line of HTML, then ask it something only your business could answer.