The 3 WhatsApp alerts that prevent the 'where is my order?'

"Where is my order?", Sunday 11:10 p.m. The package is perfectly fine, traveling between two distribution centers, and the tracking has not logged a new event since Friday. That is the whole logic: the buyer does not write because the shipment is slow, they write when the tracking goes silent and they fill that gap with the worst hypothesis. The three moments when that happens are not confirmation, dispatch and delivery —those are your store's events and your platform's automatic email covers them reasonably well—. They are dispatch, where you promise an exact date you do not control; the 24 to 72 hour window with no new event, which on the other side reads exactly like "it got lost"; and the carrier exception —failed visit, wrong address, package at a branch—, which you find out about a week later, when the package comes back. One message at each of those three moments, with the right text, takes most tracking queries out of your inbox. None of the three is triggered by your store: they are triggered by the carrier, or by the carrier's silence.

Moment 1: when you dispatch, promise a range, not a date, and say explicitly when not to worry

The classic mistake is the email that says "your order has been dispatched" and attaches a tracking number. That does not inform: it delegates. The buyer now has homework, which is to go to the carrier's site, paste the code and decipher what "accepted at distribution center" means.

The message that works does three things that email does not: it gives a date range instead of a date, it warns in advance that the tracking may not move, and it sets a day from which you file the claim yourself (Andreani, in the sample text, is an Argentine carrier).

Hi Martín, your order #1042 left our warehouse today.
Andreani is carrying it, tracking 360000123456.
It arrives between Tuesday the 5th and Thursday the 7th.
One thing so you do not worry: for the first two days the tracking
may show no movement. That is normal, the package is in transit.
If it has not arrived by Thursday night, write to us here and we file the claim.

The last line is the one that does the most work. It turns a diffuse worry —one that can go off at any moment and reach your inbox on a Sunday at 11 p.m.— into an action with a date that the buyer respects. And you take the paperwork off their hands: you open the claim with the carrier, and you open it better because you hold the proof of posting.

Moment 2: the alert that fires because nothing happened is the one almost nobody sends

This is the invisible moment. In a typical domestic shipment there is a 24 to 72 hour window in which the tracking logs no new event: the package is traveling between distribution centers and does not pass any scanner. On the buyer's side that reads exactly like "it got lost".

The trigger for this message is not an event, it is the absence of one: 48 hours have passed with no status change. That is why no e-commerce platform sends it. Tienda Nube (a Latin American e-commerce platform), Shopify or WooCommerce react to what happens in your store, and here nothing happened anywhere.

Hi Martín, we are following your order #1042.
The tracking has not moved since Monday, so we already asked
Andreani what is going on.
We will confirm today before 6 p.m. You do not need to do anything.

Two warnings about that text. "We already asked" has to be true: if you are not going to check, do not write it, because the buyer will be waiting for the 6 p.m. answer. And "you do not need to do anything" is the phrase that prevents the long reply with screenshots of the carrier's site, which is what arrives when the message leaves the ball on the other side.

Moment 3: the exception has a clock, and the carrier sets that clock

This is the only one of the three moments that also saves you a package. Between 3% and 8% of shipments generate an exception —failed visit, incomplete address, recipient absent, package redirected to a branch— and the carrier logs it the same day. These are the usual ranges in the sector, not audited figures from one company: you will only see your real percentage once you have counted it for three months.

The problem is that almost nobody checks the carrier's panel daily, so most stores find out about the exception when the package comes back to the warehouse. And it comes back because there is a holding period at the branch —five to ten business days depending on the carrier, the first fact worth confirming with yours— that expired while the buyer was waiting at home.

Hi Martín, the carrier tried to deliver your order #1042 today
and there was nobody at the address.
It is at the Av. Rivadavia 4550 branch and they hold it until Friday the 14th.
Bring your ID.
After that date it comes back to our warehouse and reshipping has a cost.
If you prefer them to try again at a different address,
reply ADDRESS and we will arrange it.

The explicit expiry date is what gets the person moving. "Pick it up at the branch" with no date gets postponed; "until Friday the 14th" gets put in the calendar. And a single keyword as a reply is enough: the alternative —a form, a link, an email to another mailbox— is what makes the package come back.

What your platform's email covers and what it does not

Two lines about last month's orders: your time and the packages that come back

Take your orders from the last month and do two lines.

Line 1, your time. Count how many "where is my order?" conversations came in. With no proactive alerts, between 20% and 35% of buyers usually ask. With 200 orders that is 40 to 70 queries. Each one is a real 4 to 6 minutes: read it, find the order, open the carrier's site, paste the code, translate the status and reply. Between 3 and 7 hours a month.

Line 2, the packages that come back. Multiply your shipments by 5% to estimate the exceptions: 10 cases. If a quarter of those come back because of a late notice, that is 2 or 3 packages a month. Each one costs you the return freight plus the reshipping, the product immobilized for two weeks and, in a share of the cases, a refund request you no longer argue about.

In a store with 200 monthly orders that comes to an order of USD 80 to 140 a month between time and useless logistics. It is money, but it is less than an automation subscription costs, and that is precisely the point: at that volume, the three messages sent by hand capture almost the entire benefit at zero cost.

Moment 2 is the only one that forces you to look at what did not happen

The other two alerts fire because of something that happened. The silence one fires because of an absence, and that asymmetry decides everything that follows.

The dispatch and exception messages have a trigger that is already on your screen —you dispatch, the carrier notifies you— and you send them while doing something else. The silence one does not: it requires reviewing every package in transit, every day, to find the ones that have not moved. With 12 daily dispatches and an average delivery of five days, at any given moment you have around 60 open trackings. Going through them one by one is 25 to 30 minutes a day, every day, including Hot Sale week, the regional sales event.

That is the real ceiling: up to 10 or 12 daily dispatches, around 250 monthly orders, the three messages hold up by hand if somebody keeps the habit. Above that, moment 2 is the first one to fall, and it falls silently: nobody notices it stopped going out until the queries start climbing again.

That ceiling arrives by four different routes and only the first one is about volume. The other three catch up with you at 80 orders a month if your operation has the wrong shape.

When you pass 250 monthly orders. It is not that the messages stop working: it is that you stop sending them. And the order in which it pays to automate is not the order in which we presented them. First moment 3, the exception, because it has the cheapest trigger to detect —the carrier notifies you— and the highest cost per case avoided. Then moment 1. Moment 2 goes last, because it is the only one that requires checking the status of every shipment on a sustained basis.

When you work with two carriers or more. Each one names the statuses differently: what one calls "in distribution" another calls "in dispatch" and another "out for delivery". By hand that is two panels and two vocabularies; moment 2 becomes unfeasible because of this before it does because of volume.

When the buyer replies with something that is not a keyword. You send the three-message flow, but the replies come in anyway and they are free text: "no, better send it to my sister's place", "can you bring it on Saturday?", "I want to return it". At that point no template is enough, and that part —reading the intent, updating the address in the system, triggering the reshipment— is the one that does not get done by hand once volume goes up.

When the problem is not one of information. If your shipments take twelve days because you dispatch every 72 hours, communicating better fixes nothing. You will have perfectly informed buyers about a delay that is still your delay.

The week that tells you whether you have a moment 2 problem

All of this is decided with a two-column spreadsheet and five days. Every morning this week, open your carrier's panel and write down two things: how many trackings you have in transit and how many of those have been on the same status for more than 48 hours. Nothing else. You do not need to do anything with the ones that show up: counting them is enough.

On Friday, look at the second column. If the number stayed at two or three every day, your moment 2 is a five-minute check and will go on being one for a good while: implement the three messages by hand on Monday and do not hire anything. If it started at three on Monday and ended at eleven on Friday, you already know that what piled up on you was not the stalled packages, it was the reviewing, and that on the first difficult Monday that column stops being written.

That pair of numbers —the peak of the second column and the number of carriers you work with— is all it takes to know in what order to automate. Send them to info@striqtech.com and we will tell you whether to start with the exception or with the silence.