Your Customer Shouldn’t Have to Call You to Find Out What’s Happening

The question behind the phone call

The useful website feature here is a place to see the latest reliable update, with a clear route to a person. It could be a page in your existing order system. It could start as a well-timed email. The goal is to help someone make their next decision.

For the sign customer, that decision changes as the job moves. First: do I need to approve the artwork? Later: is the sign being made? Finally: can I collect it today? A single “in progress” label covers all three and answers none of them.

That distinction matters before anyone designs a dashboard. A shipping-tracking page can be useful once a parcel exists, but a custom order may spend days waiting for a proof, a material choice or a customer response. Those are different kinds of waiting.

Shopify, for example, already offers an order-status page where customers can follow shipments after tracking details are added; live shipment information depends on supported carriers. That is a useful starting point for a shop shipping products. It is not evidence that every custom production or approval step is already covered. [1] (opens in a new tab)

Follow one order through the awkward middle

In our imagined sign shop, the customer has selected a finish, but the layout still needs approval. The owner could show a polished progress bar at 40 percent. Or the page could say what is actually holding the job up.

The second version gives the customer a job to do. After approval, the message should change: “Layout approved. Your sign is queued for fabrication. We expect to confirm pickup on Wednesday.” That is a commitment to an update, not a claim that fabrication is finished.

Then imagine the chosen material arrives damaged. Keeping the old estimate on screen would make the page less useful than a phone call. The next update should explain the delay, name the decision the shop is making and give a time for the next message—even if the final pickup date is unknown.

This is where the design earns its space. Put the current message first, the next action immediately below it, and a short history farther down. Include a real contact route for a deadline the page cannot resolve. A customer checking on a phone should not have to decipher an internal job board.

Who keeps the answer true?

Before building the customer page, choose the record the team will maintain. In the sign-shop example, the person handling artwork records approval, the production lead records fabrication, and the person checking the finished sign marks it ready. Give each step an owner and a clear meaning.

“Ready” should mean the sign has passed the shop’s check and can actually be collected. It should not mean the printer finished or a target date arrived. A timer cannot know whether a missing fitting has been installed.

For a first version, one staff member can update a short customer-facing message from the existing job record. Avoid asking everyone to maintain the same date in a spreadsheet, a portal and a separate messaging tool. Each extra copy creates another place for the answers to disagree.

If updates are connected automatically, plan for the connection to fail. Keep the last confirmed update and its timestamp visible, alert the responsible staff member, and provide a way to correct it. When information is stale, say so. Do not replace missing information with an AI-written guess.

Also separate publishing an update from delivering a notification. A changed page does not prove the customer received an email or text. Keep failed deliveries visible to staff, avoid repeatedly sending the same message, and make sure the customer can still ask for help.

Use what you have before buying a portal

For straightforward online orders, inspect the tools already included in your selling platform. Square documents emails triggered when an online order is marked ready or shipped, and text updates for pickup and delivery. These features require a Square site, and some text options require a paid subscription. Check your account’s options before planning a separate system. [2] (opens in a new tab)

If you handle a few long-running jobs, a consistent email at agreed milestones may be enough. A short message from the person responsible can be more useful than a dashboard the team forgets to update. Trial the wording and ownership first.

A customer portal—a private area of your website—becomes more interesting when people need to approve artwork, find the latest document or check several active orders. In the sign example, opening the current proof and recording approval could justify a shared page. A parcel-tracking screen alone would not solve that problem.

Ask a builder to price the whole working arrangement: connection to job records, customer access, staff editing, notification delivery, correction history and ongoing support. Those choices drive effort. Adding a polished page is only part of the work, and an off-the-shelf tool may already cover enough of it.

Easy to open should not mean open to everyone

An order page can reveal names, artwork, addresses or commercial details. Decide what the customer actually needs to see and leave internal notes out. Ask the builder how access to each order is checked, including its downloadable files. OWASP recommends validating permissions on every request; signing in alone does not grant access to every customer’s records. [3] (opens in a new tab)

Test that boundary with two test customers. Customer A should not be able to retrieve Customer B’s order by changing a number or opening a document link. Include lost-access recovery in the design so a legitimate customer is not forced into a dead end. [3] (opens in a new tab)

Keeping a page out of Google is a separate issue. Google explains that a noindex instruction can keep content out of search results while people with a link can still visit it. It is not a substitute for protecting private content with appropriate access controls. [4] (opens in a new tab)

Keep the experience simple: readable text for each status, clearly named actions, visible keyboard focus and a layout that works on a narrow phone screen. Show “waiting for your approval” in words, not only as an amber dot. Test the page with people who did not help build it.

A small pilot that can tell you something

Try the new approach with one type of job before expanding it. For the sign shop, that might be standard shopfront signs with one artwork approval. Record how many orders go through, how many prompt status questions, and how much staff time goes into keeping customers informed.

Compare similar groups of completed orders, rather than one busy week with one quiet week. Count status contacts per order and time spent both answering and updating. Separate ordinary updates from complaints, changes and urgent deadline questions; those may still deserve a conversation.

Ask customers one direct question: “Could you tell what happens next?” Then watch whether they can find their proof, understand the estimate and reach a person. If calls decrease because help has become harder to find, the design has failed.

No percentage improvement is promised here. The useful result may be fewer repeated questions, faster approvals or simply fewer mismatched expectations. If the pilot shows that staff cannot maintain the updates, fix that workflow before adding more screens.

The best version is the one your team can keep honest. A customer who knows what is happening can get on with their own work—and call when there is something worth discussing.