A page explaining dispatch times, how tracking works, when to worry and what to do next answers the majority of order enquiries before they are sent, and costs an hour to write.

The email you receive most

For any shop past its first few months, one message dominates: some version of asking where an order is.

It is rarely a complaint. It is somebody with no information looking for some, and the only route you have offered them is writing to you.

Which means each one costs you a reply and costs them a wait, for an exchange that contains no decision and no judgement.

That is the definition of something a page should handle.

What the page needs to answer

The fifth is the one that removes most emails. Somebody who knows an order is not considered late until day seven does not write on day four.

A worked example

A shop selling art supplies, receiving perhaps fifteen order-status emails a week against a modest order volume.

Answering them took an hour or two a week and produced nothing except reassurance.

They wrote a single page: dispatch within two working days, transit two to five, tracking sent by email when it leaves, what to check if the tracking has not updated for a day, and a request not to contact them before day eight because parcels frequently arrive on days six and seven.

They linked it from the order confirmation email, the dispatch email, and the footer.

Emails fell to about four a week, and those four were genuine problems rather than uncertainty.

The page took an hour to write and returned an hour a week indefinitely.

Where to link it

Placement is most of the value, and a page nobody finds does nothing.

The order confirmation email, which is the message customers actually keep.

The dispatch email, where the question is most likely to arise next.

The footer, alongside shipping and returns.

And the contact page, ideally above the form, so somebody about to write about an order sees the answer first.

That last placement feels like discouraging contact and reads as helpfulness when the page genuinely answers the question.

The counter-case

Where this page is unnecessary.

A shop with a proper account system, where customers log in and see order status directly. There the page is redundant and the emails should already be rare.

Very low volume, where two emails a month does not justify a page and the personal reply is part of the service.

And made-to-order businesses where every order is a conversation anyway, so a generic page cannot say anything useful.

For a shop dispatching standard products at moderate volume, which is most small shops, the page pays for itself within a fortnight.

Explaining carrier statuses

An underrated part, because carrier language causes real confusion.

Statuses like awaiting collection, in transit, and processed at facility mean things to the carrier and very little to a customer.

A short translation is genuinely useful: what each one means, and specifically which ones are normal to sit at for a day or two without anything being wrong.

Most anxious emails come from a tracking status that has not changed since yesterday, which is usually entirely ordinary.

The tone of the page

Worth attention, because this page can easily read as defensive.

A page that opens by explaining you are not responsible for carrier delays, in a paragraph about terms, tells a worried customer that their concern is unwelcome.

The same information, framed as helping them work out where their parcel is, does the same job and reads as service.

Open with what they want: how to check, what the statuses mean, when to be concerned. Put anything about liability at the bottom, briefly, if it needs to be there at all.

The difference is entirely in the ordering, and it decides whether somebody who reads the page feels helped or fobbed off.

Saying when to worry

The single most effective sentence on the page.

Give a specific day. "If it has not arrived by working day eight, contact us and we will chase it."

That does three things. It stops early enquiries. It tells somebody their concern is legitimate when the day arrives. And it commits you to doing something, which is reassuring.

Vague reassurance does none of that. A date does all three.

Order numbers people can find

A practical detail that decides whether the page is usable.

Asking somebody to quote an order number only works if they can locate one. Many customers cannot, because the confirmation email was deleted or went to junk.

Make the number prominent in the confirmation, say on the page where to find it, and be prepared to look an order up by email address or postcode instead.

A support process that stalls because the customer cannot produce a reference is worse than no process, and it turns a two-minute enquiry into three exchanges.

The same applies to the tracking number, which should be in the dispatch email rather than only in an account area somebody would have to log into.

What to do about the ones that still arrive

They will, and they should be easy to handle.

Have a short template covering the common case: checking the order, giving the tracking, and stating what happens next.

Answer them quickly even though they are routine, because somebody worried about an order is not in a patient frame of mind.

And note which questions the page failed to answer, because those are the paragraphs it is missing.

Building it

  1. Read your last twenty order emails and list the questions.
  2. Answer each one in a sentence or two.
  3. Add the specific day at which something counts as late.
  4. Link it from both automated emails and the footer.
  5. Revisit after a month and add anything still arriving.

The first step writes the page for you, which is why this is an hour rather than an afternoon. The questions are already there; you have been answering them individually for months.

What the estimate on that page should say is covered in what your delivery estimate is promising.


Frequently asked questions

What is the most common shop email?

Some version of where is my order. It is rarely a complaint, just somebody with no information whose only route is writing to you.

What should the page answer?

Dispatch time, transit time, where the tracking is, what carrier statuses mean, when an order counts as late, and what to do then.

Which element removes most emails?

Stating the specific day at which something is genuinely late. Somebody who knows that does not write on day four.

Where should it be linked?

The order confirmation email, the dispatch email, the footer, and above the form on the contact page.

When is the page unnecessary?

When customers log in and see status directly, at very low volume where a personal reply is the service, or for made-to-order work.

Why explain carrier statuses?

Because most anxious emails come from a tracking status that has not changed since yesterday, which is usually entirely ordinary.

West Coast Media Solutions Inc. provides web design, web development, hosting, digital marketing, and business consulting to organisations across Canada, drawing on more than twenty-five years in the field.

Answering the same order question every week?

An hour writing one page usually returns an hour a week indefinitely.

Start a Conversation