Public order-tracking links: fewer where-is-my-order calls

The WISMO call: a silent cost that compounds with growth

In the delivery business this class of contact has a global name — WISMO, short for Where Is My Order — and it is usually the first item consuming a support team's capacity. The irony is that most of these calls address no real problem: the order is moving along its normal path, but the customer has no way to know it, so they call.

Try a quick calculation on your own operation: how many status enquiries does your team receive daily across phone, WhatsApp, and social accounts? How many minutes does each one consume between opening screens, finding the order, and composing a reply? Multiply the two numbers, then multiply by the days in a month — and you will find the "innocent question" swallowing whole working hours every week without adding value for anyone involved.

The cost is layered. An agent is tied up on a repetitive question instead of the cases that genuinely need intervention; a dispatcher is interrupted to check the status of a single order; and a customer waits on hold to hear an answer they could have read themselves in seconds. As orders grow, this burden grows at least linearly — every new order is a potential call — while support teams rarely grow at the same pace.

The problem peaks in the seasons — major sale events, Ramadan, the Eids — when orders multiply and delivery times stretch slightly, so customer anxiety multiplies and with it the calls, precisely when your team is at its most stretched. The stores that come through their peak seasons intact are rarely the ones that hired temporary support; they are the ones that made information precede the question all year round.

The fix is not answering calls faster. It is removing the reason for the call: making the answer available before the customer needs to ask for it.

What a good tracking page actually shows

A public tracking link is a page the customer opens directly in the browser — no account, no app, no password. In Pixa's dispatch module, every order gets a public link that can be sent to the customer the moment the order is confirmed. A good page answers exactly three questions:

• Where is my order right now? A clear status within understandable stages: received, being prepared, out for delivery, delivered.
• What happens next? The upcoming stage and what the customer should expect — clarity about the next step defuses anxiety more than any other detail.
• What if something changes? Status that updates as it changes, because a page lagging behind reality is worse than none: it pushes the customer to call just to check whether the page itself is telling the truth.

The governing design rule: every piece of information shown must reduce the probability of a call. Whatever does not serve that goal — internal operational detail, logistics jargon, device identifiers — has no place on a customer-facing page.

The page should also carry your store's voice, not the technology vendor's — the customer ordered from you, and every touchpoint during the wait is part of your brand. Language deserves particular care in this market: an Arabic-speaking customer should read a genuinely Arabic page built right-to-left, not a machine translation layered over a foreign template that breaks at the first long sentence. That is one of the practical differences between a platform designed Arabic-first and one localised as an afterthought.

Notifications and the link work together, not instead of each other

The link is a "pull" channel: the customer opens it when they wonder. A complete experience adds a "push" channel: a proactive notification at each meaningful stage — order confirmed, out for delivery, courier approaching, delivered. When the notification arrives on time, the customer has no reason left to ask at all.

In Pixa these notifications ride on 5 channels — WhatsApp, SMS, email, app push, and browser push — plus an in-platform notification centre. And because WhatsApp is the first channel in the Saudi market, the platform supports 3 interchangeable WhatsApp Business providers, along with a conversational AI agent that can answer recurring questions from a knowledge base — absorbing part of the inbound before any of it reaches a human agent. See the alerts page for channels and delivery rules.

The combination that works in practice: a short notification at each stage, and inside every notification the same tracking link for whoever wants detail. That way each message serves two goals at once — immediate reassurance, and less need for any follow-up contact.

Beware the opposite extreme, too: flooding. A notification for every minor internal movement teaches the customer to mute the whole channel, and your store loses the most valuable asset in this relationship — the customer's attention at the moment a message truly matters. Keep the rule strict: only meaningful stages earn a notification; everything else belongs on the tracking page for whoever wants the detail.

Before and after: what actually changes

When the link and stage notifications work together, the shape of a customer-service day changes before any report shows it:

The decisive difference is the last row: presence. A store that stays present in the gap between payment and delivery builds trust that outlasts any single order — and in e-commerce, trust is the cheapest marketing channel with the longest reach. A reassured customer comes back, and recommends you unprompted.

Privacy and security of a public link

"Public" means the page opens without login — not that it reveals more than it should. A correct design shows only what concerns that single order: its status, its stages, and what the customer needs in order to receive it — no sensitive data and nothing about anyone else's orders. In Pixa this is not a page-level convention but a deeper architecture: strict tenant isolation enforced by a database-level guard, rate limiting that blunts automated probing, a unified API gateway every request passes through, and a tamper-evident hash-chained audit log. The security page covers these layers in full — with hosting inside Saudi Arabia.

And remember that the security of the public surface is inseparable from the security of the system behind it: your internal team's accounts are protected by server-enforced multi-factor authentication rather than an option left to each user, and every administrative change lands in an audit log built on a hash chain that blocks after-the-fact editing. The trust your tracking page builds with a customer is worth nothing if what stands behind it is exposed.

How to roll it out in your store

Activation is simpler than it looks; the usual path is three steps:

• Connect your store: through the Partner API and Webhooks, orders flow from your platform into the dispatch system automatically, and the tracking link comes back to be embedded in the order-confirmation message — see the integrations page.
• Enable stage notifications: pick the channels that fit your audience and the stages worth a message, and avoid flooding — one notification too many teaches the customer to ignore them all.
• Measure before and after: log the volume of where-is-my-order enquiries for a week before activation and compare a few weeks later. That difference is the success metric, alongside customer ratings and repeat purchases.

After launch, treat the experience as a product that keeps improving: revisit message wording, experiment with send timing, and ask your support team which questions still reach them despite the link — whatever remains points to information missing from the page, not to a failure of the idea. Once you are confident in the result on your main channel, extend it to the remaining channels and branches under the same rules.

The tracking link is one of those rare features that serves both sides with no trade-off: the customer gains transparency and peace of mind, and the store gains a support team free to handle what matters. The earlier you switch it on, the earlier the effect shows.

Ready to try tracking links and notifications on your store's orders? Talk to the Pixa team for a hands-on walkthrough that starts from your real scenario.