From the operations desk
The situation
Thursday was the after-sales day. Sellers' support assistants posted tracking chasers, delivery failures and damage claims across Europe, Japan and the US, alongside a large prospect intake from Italy, the UK and the US. The two halves shared one weakness. A status answer, a resend decision or an onboarding template went out quickly but without the parts the other side needed to act on it.
Last scan, cause, action, date
A status reply has to carry four things: the last scan, what caused it, the next action and a date. A tracking link is not a status. "Signed for" is not a status. "Will be updated tomorrow" is not a status either; on Thursday it hid a stock-out that surfaced the following afternoon. Say the real blocker at the first reply.
An "exception" on a Belgium-bound parcel was answered first with a third-party link and "please check". The useful reply came hours later: incomplete address, returning to the overseas hub, reship for a fee once a corrected address arrives. That second message should have been the first. A Japan-bound parcel reported as not moving was answered "already signed for"; the next day the assistant asked what that meant, because the customer had nothing, and flagged that it was not the first delivered-but-denied case that month. A delivered-but-denied reply needs the carrier, the delivery date and place, what the recipient should check, and what we open and by when.
Check the destination carrier's own page before sending a failure alert: two French parcels were reported as failed while the local carrier showed both delivered two days earlier, because the first-attempt notice propagates with a lag. And copy the shape that worked: a Nordic parcel returned for non-collection was handled in one message with the redelivery fee, a deadline about ten days out, and a request for a new address and a reachable number.
The status vocabulary is published on the tracking status hub, and the guide on communicating tracking handoffs covers the wording sellers can pass straight to a customer.
Agree the default before the first case
The standing after-sales rule has to be agreed before the first case, not discovered inside it. Does a damage photo trigger a resend automatically, or does it wait for a yes? Does a charged resend go onto the next invoice on its own, or does it wait for explicit approval? What is refundable and what is not? What does neutral packaging mean in practice?
Four "we will charge and resend" messages had been read as offers on one side and as commitments on the other; one was three days old and only moved when the seller wrote "please send it". After a run of damaged kits had been resent on sight, the next report was answered with "should we resend?" and that order sat open into the evening. Either rule works; mixing them does not. A seller asked for no lettering or stickers on home textiles, which should have been the stated default rather than a request.
One after-sales lead set the rule in a single message: lost parcels, missing items and cancellations are refundable; parcels returned because the recipient was unreachable or refused are not. The seller had nothing further to ask. That sentence belongs in onboarding and in the group description, where the support assistants work.
The rule by cause, and who pays under each, is laid out in the after-sales window guide; for the decision on a single case, use refund, reship, replace or investigate.
Read the thread before you choose the template
The platform, the destination and what a teammate or the seller has already decided are usually in the group header or the thread before the question is. A marketplace seller who said twice that he sells on a handmade-goods marketplace received the Shopify collaborator template and had to correct us. A store owner answered a damage ticket within minutes, instructing a resend through a draft order; an hour later the assistant was asked whether the customer wanted a refund or a resend. A structured first enquiry covering transit to Italy, branding and custom packaging got "please send the product link" and none of its questions.
The fix is reading to the bottom before replying to a quoted message, and picking the onboarding path from the platform the seller named rather than the default. It is the same discipline as asking the exact question before the easy answer: the context is already there, and the template is the easy answer.
A useful status needs four parts
Sellers: before you forward a status to your customer, check it names the last scan, the cause, the next action and a date, and send it back if it does not. Ops teams: write the after-sales default into the group before the first claim, read the whole thread before choosing a template, and never let a link or a "tomorrow" stand in for the real blocker.