Playbook, online store
The handover that exists because there is no record to read
On most sites a handover is what happens when the assistant fails. On a shop it is the designed route for an entire category of question, because order enquiries have no readable source and never will. That changes how the wording should feel. It is not an apology for falling short, it is the second half of a process, and the only thing left to influence is whether the person on the other end can act on the first message.
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.
- Here the handover is the intended path for a whole class of question rather than a failure, so it should read as the next step rather than as an apology.
- Almost every one of these needs the same two identifiers, the order number and the email used at checkout, and a form that collects neither costs the team a round trip per enquiry.
- Guest checkout means the name in the message may match no account at all, which is why the order number carries more weight in this trade than the person's name.
- The volume arrives in bursts behind a dispatch email or a carrier delay, so the same wording is read by many people within an hour and deserves the care of a product page.
How it arrives
- can i speak to someone
- i need to talk to a human
- is there a phone number
- nobody has replied to my email
- who do i contact about an order
- can you put me through to customer service
What has to be indexed for this to work
| Where enquiries land and who reads them | The nominated address, which team monitors it, and your published response time. The assistant should be able to say what happens next without inventing a service level nobody agreed to. |
|---|---|
| What a customer needs to have to hand | The order number, the checkout email, and for delivery problems the tracking reference. Naming these in the reply is what gets them supplied voluntarily instead of extracted over two days. |
| Your escalation routes for delivery exceptions | Marked delivered but missing, refused at the door, returned to sender, address wrong. Each of these goes somewhere slightly different and often has a carrier deadline, so the material should let the assistant flag urgency without adjudicating. |
| What must never enter a message field | Card numbers, passwords, account recovery codes. Customers volunteer all three when they are frustrated, and the material should tell the assistant to decline them explicitly rather than let them sit in a stored enquiry. |
The reply
I cannot open orders, so the quickest thing is to get this to somebody who can. If you leave your name, the email address you used at checkout and your order number, that reaches the team with your message attached. We reply within the times published on our contact page, and having the order number in the first message usually saves a day of back and forth.
It gives the reason for the handover in one clause and spends the rest of the reply making the handover work, because that is the only remaining variable. Naming the two identifiers and saying why they matter is what gets them entered. Quoting a published response time commits the shop to something it already agreed to rather than to something the assistant invented.
Where it stops
The trigger. The visitor asks for a person, or asks anything about a specific order, payment or parcel, which in this trade is the same moment.
I will pass this on. Leave your name, the email address on the order and your order number, and add anything you want the team to see. It arrives with them as an enquiry and the reply comes back to that address.
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 promise a phone call, a callback or a reply inside a time the shop has not published.
- Never say the message has gone to a named individual.
- Never accept card details, passwords or recovery codes into the message field.
- Never tell somebody a person will resolve it in their favour.
Questions
- What actually happens to the details it collects?
- The form takes a name, an email and a message, sends it to the address you nominate, and stores it so nothing is lost if the email fails to deliver. It does not create a ticket in a helpdesk or write into any other system.
- Should we offer the handover before it has tried to answer?
- For order questions, yes. There is nothing to attempt, and a paragraph of hedging before the form is read as stalling. For delivery, returns and stock the answer usually exists, so the form belongs at the end rather than at the start.
- How do we stop it inventing a response time?
- Index the one you publish and let it quote that. If you do not publish one, the honest wording is that the team will reply by email, with nothing after it. An invented number is a promise the shop then has to keep at its busiest moment.
Keep reading
- Everything for a online storeDelivery cut-offs, the returns window and restock questions get asked before purchase. The one thing an assistant cannot do is find an order.
- 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.
- Money going backwards, and the days nobody in the shop controlsA return, a refund and a chargeback are three different things. What the shop controls, and the issuer delay nobody there can shorten.
- It is already on a pick list, which is the whole answerStopping an order ends when the pick starts. The window to change your mind ends much later. Two rights wearing one word.
- The claim belongs to the shop, not to the person with the empty porchThe carrier contract is with the seller, so the buyer cannot claim at all. The window is short and it started at dispatch.
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.