The Message Before the Query: Designing Parcel Updates That Reduce WISMO Without Losing the Personal Touch

WISMO — the customer asking 'where is my order?' — is often treated as an unavoidable cost of selling online. For UK SMEs, it is more useful to treat it as a communication gap with a measurable price. Each ticket takes staff time, but the bigger loss is confidence. A customer who has to chase is being reminded that the delivery experience is not under control.

The objective is not to remove human contact. It is to make routine queries unnecessary, so that the contact that remains is more valuable.

Map the uncertainty before choosing the message

Start by tagging WISMO tickets by reason and by consignment stage: pre-dispatch, awaiting first carrier scan, in transit, out for delivery, failed attempt, exception, delivered but not found. A four-week review will usually show two or three recurring gaps. One business may find that most queries arrive between despatch and the first scan; another may find the problem is failed attempts where the customer did not receive a card. The message plan should follow the evidence, not a generic template.

Proactive updates should answer the next question

A dispatch email that says only that the parcel is on its way adds little. A better update confirms the service, the carrier, the expected delivery window and what the customer should do if no scan appears after a stated number of working days. At the point of first carrier scan, the next message can confirm that the parcel is in the network. On the morning of delivery, a short window message is more useful than a second generic reassurance. For UK customers, be precise about working days and bank holidays; 'next day' without a cut-off time is an invitation to query.

Frequency matters. Every message should have a job. A customer who receives five updates that say the same thing may trust the process less, not more. Set a frequency cap and suppress messages when a delivery has already been confirmed.

Branded tracking owns the context, not the carrier data

A branded tracking page keeps the customer inside your identity while still using the carrier's scan data. The page should show the current status in plain English, the expected date, any delivery attempt history and the next available action. It should not invent milestones or hide an exception. If the carrier supports rescheduling or a safe-place change, link to it directly. If not, provide a clear route to your team. The aim is continuity: the customer should not have to decode a carrier page to understand what happens next.

Self-serve pages need to answer the next question

A tracking link that displays only raw scan events is a data feed, not a service. A useful self-serve page answers the questions that generate tickets: Has it been dispatched? When was it last scanned? Was a delivery attempted? Can I change the address? What do I do if it has not arrived? Each answer should end with a next step, not a dead end. Include an escalation route for exceptions, but keep it visible rather than forcing every customer through a contact form.

Metrics that separate trust from noise

Measure WISMO contacts per 100 parcels, the share of contacts by stage, repeat contacts from the same customer and first-contact resolution. Add delivery success, failed-attempt rate, opt-out rates for notifications and post-delivery satisfaction. A fall in routine contacts alongside stable delivery performance is a good signal. A rise in opt-outs or a fall in satisfaction suggests the updates have become noise. Do not rely on open rates alone; an opened message is not proof of reassurance.

Run changes as a controlled pilot by carrier, route or postcode area. Set a baseline before you change templates. Review the pilot weekly, and keep the messages that reduce contacts without increasing escalations.

Keep the personal route for the exceptions

Reducing WISMO is not the same as withdrawing service. Complex exceptions, high-value consignments and key accounts still need a named contact and a human reply. The point of better automation is to free staff for those cases. A customer who has a genuine delivery problem should reach a person quickly; a customer whose parcel is simply two scans away from delivery should not need to.

Used well, delivery communication becomes a retention tool. It shows that the business knows where the parcel is, what happens next and who to ask. That is a more durable advantage than a cheaper carrier — and it is within reach of most UK SMEs without a large systems project.