BusinessPublished

Why “where is my order?” costs you an hour a day

Status questions are a symptom, not a nuisance. Four changes that remove most of them without adding a portal nobody logs into.

  • 8 min read
  • 1,274 words
Why “where is my order?” costs you an hour a day — shipping at a print shop
Business8 min readA1printsoft EditorialPhoto: Claudio Schwarz / Unsplash
On this page5 sections

The short answer

  • Status questions are a symptom of missing updates, not of impatient customers
  • Four proactive messages remove most of them: confirmed, proof, in production, shipped
  • Push updates by email or text. Do not rely on a portal customers must remember to visit
  • Give a date at every stage, even when the date has not changed
  • Count the calls for one week — the number is usually higher than anyone guesses

Count how many times someone in your shop answers "where is my order?" in a single week. Include the emails, the texts, the phone calls, and the ones that arrive through a social media message at nine in the evening. In most shops the honest total is between fifteen and thirty, and each one costs three to five minutes once you include finding the job, checking its actual status, and replying. That is comfortably an hour a day of skilled time spent restating information that already exists.

The instinct is to treat this as a customer problem — people are impatient, people do not read their confirmation email, people ask too soon. That framing is comfortable and it is wrong. Every one of those messages is a customer telling you they do not know something they reasonably expected to know, and that is a communication design problem you own.

What is the customer actually asking?

Almost never "what is the current state of my job?" They are asking one of three much more specific things, and knowing which one changes what a good answer looks like.

Sometimes they are asking "will it arrive in time?" There is an event, a game, a conference, a first day of term. The deadline is real and it is the only thing they care about. A status update that does not reference the delivery date does not answer their question, no matter how detailed it is.

Sometimes they are asking "did you forget about me?" They placed an order, received one confirmation, and then heard nothing for eight days. Silence is ambiguous, and people fill ambiguity with the worst plausible explanation. This is the most common version and the easiest to eliminate.

Sometimes they are asking "do I need to do something?" They half-remember approving a proof and are not certain it went through, or they were asked for a size list and cannot recall whether they sent it. They are checking whether the ball is in their court. All three are answered by the same thing: telling them before they ask.

Every status call is a message you did not send, arriving in the most expensive form available.

Which four moments matter?

You do not need continuous tracking, and attempting it usually produces so much noise that customers stop reading. Four messages, at four moments where the customer's mental model of the job would otherwise go stale, will remove the large majority of inbound status questions.

MomentWhat it prevents
Order confirmed, with the delivery date"Did it go through?"
Proof ready, with a clear approve link"Do I need to do something?"
In production, date restated"Did you forget me?"
Shipped or ready, with tracking"Where is it now?"

The third message is the one shops most often skip, because from the inside nothing interesting has happened — the job moved from one column to another on a board. From the customer's side, that message is the difference between a week of silence and a week of knowing they are being looked after. It is the cheapest of the four to send and it prevents the most calls.

The second message is where the proof lives, and it is worth attaching to the job rather than sending as a loose email. An approval you can point to later settles arguments about what the customer actually signed off, which is a different problem that shows up in the same inbox.

Why do customer portals not fix this?

Because they require the customer to remember a portal exists, find the link, recall a password, log in, and navigate to the right screen — all to get information you could have sent them in a sentence. That is a lot of friction in front of a question that takes ten words to answer.

Portals work well for the small proportion of customers who order frequently and have a genuine reason to look things up: reorder history, past artwork, invoices. For the occasional customer placing a single order for an event, a portal is a place they will never visit. They will message you instead, which is faster for them and slower for you.

Build the portal if you have repeat accounts who will use it. But do not treat it as the answer to status questions. Push beats pull for anything time-sensitive, every time.

What should each message actually say?

Short, specific, and always carrying a date. The most common mistake is sending an update that describes activity without committing to a timeline, which leaves the customer no better informed than before.

The four messages

  • Confirmed — "Order #1042 is in. 48 navy tees, front print. You will have a proof by Wednesday and delivery is Friday the 14th."
  • Proof — "Your proof is ready. Approve it here [link] and we stay on track for the 14th. If we do not hear back by Thursday the date may move."
  • In production — "Approved and on the press today. Still on for the 14th."
  • Shipped — "Shipped this afternoon, tracking [number], arriving Thursday — a day ahead."

Notice that the delivery date appears in all four. That repetition feels excessive when you are writing them and it is the single most valuable element, because the date is what the customer actually cares about and the thing they are least likely to have retained from the previous message.

Notice too that the proof message states a consequence: approve by Thursday or the date moves. That converts a request into a deadline, and proof approval times drop noticeably once you start saying it. The same shape works when the news is bad — a substitution notice that arrives with an option already attached gets a one-word reply instead of a three-day silence.

How do you know it worked?

Count. For one week, put a sheet by the phone and mark every status question, noting which of the four moments the job was between when it came in. The pattern is usually stark: most questions cluster in the gap between proof approval and shipping, which is exactly the stretch where shops send nothing.

The week-one exercise

  • Tally every status question, by channel and by job stage
  • Multiply by four minutes to get the real weekly cost
  • Find the stage where most of them cluster
  • Add one proactive message at the start of that gap
  • Count again the following week
  • Our back-office management sends those four updates from the job itself, so nobody has to remember

Most shops find one message removes half the calls, because most of those calls were about the same silent stretch. The remainder are usually customers with a genuine change of plan, which is a conversation worth having rather than a cost to eliminate.

That is the point. You are not trying to stop customers from contacting you — you are making sure that when they do, it is about something that matters. The same four moments work for a whole team store as they do for a single order, and the rest of the business archive assumes nobody is spending their morning restating a delivery date.

Filed underBusiness
Share
Written byA1printsoft Editorial
175 articles

The print production desk at A1Printsoft. Writes the practical side of running a decorating shop: what things cost, how long they take and what to charge, checked against published trade figures.

Keep reading

More on business

All Business articles

Set up in an afternoon. From what you already do.

Free for 14 days · no card · pick what you make and we preload the methods, products and price tables.