Customers call to ask "where's my order?" when they have no other way to find out. The fix is not a bigger support team. It is a small set of well-timed messages, each with a live tracking link, sent automatically at the moments customers start to wonder. Good delivery tracking software lets you build those messages once, as rules, and then forget about them.
This post covers which notifications to send, when to send them, what to put in them, and how to set them up so they actually reduce calls rather than adding noise.
Why "where's my order" calls happen
Status calls, often called WISMO (where is my order) contacts, are a symptom of a gap in information. They spike in a few predictable moments:
- After the order is placed, when the customer has no confirmation that anyone is working on it.
- Around the promised time, when the window is close and nothing has happened yet.
- When something is late, and the customer finds out by waiting rather than by being told.
- For high-stakes orders, like catering for a meeting, where the contact is nervous even when everything is on schedule.
Each call costs time: finding the order, checking where the driver is, calling the driver if you cannot see them, then calling the customer back. Homemade in DC used to coordinate deliveries through a mix of email, texts and calendar invites. After moving to FULFLLD's automated tracking and proactive customer alerts, the team saved about an hour per delivery on manual tracking.
The notifications that matter most
You do not need ten messages per order. You need the right four or five. Here is a sequence that works for most point-to-point and routed deliveries:
- Order confirmed or assigned. Tells the customer the order is in the system and a driver is on it. Include the delivery window.
- Driver on the way. Sent when the driver starts the drop-off leg. Include the tracking link and ETA.
- Driver nearby. Sent when the driver is close, either by distance or, on routes, a set number of stops away. This is the message that gets someone to the door.
- Delivered. Sent when the drop-off is completed, so the customer knows to look for it.
- Running late. Sent only when an order is delayed past a set number of minutes. This one message prevents more angry calls than any other.
SMS, email or tracking link: which to use
SMS
SMS is the best channel for time-sensitive updates. It is read quickly and works on any phone. Keep messages short, include the business name so the customer recognizes it, and always include the tracking link.
Live tracking link
The tracking link is what actually ends the call. Instead of a static ETA, the customer sees the driver's progress and updated ETA. FULFLLD's branded tracking page carries your brand, so the experience feels like yours, not a third party's.
Email works best for summaries and records, not for "driver is two minutes away." In FULFLLD, email rules send a route summary when a route is completed, with a link to a detailed view that includes proof of delivery for each stop and a downloadable report. That is ideal for B2B clients and account managers who want a record without logging in.
Slack for your own team
Internal alerts matter too. The same rule builder can post to a Slack channel, so dispatch hears about a delayed order before the customer does.
How to set up notification rules in FULFLLD
FULFLLD's SMS and Slack rule builder works on triggers. For each rule you choose:
- Order type: point-to-point or routed.
- When: action-based (order created, assigned, unassigned, started pickup, started drop-off, drop-off completed), geo-based (driver near the pickup or drop-off), time-based (a set time of day, or order delayed by a set number of minutes), or route progress (driver X stops away).
- Market: which markets the rule applies to.
- To: the pickup contact or the drop-off contact.
- Conditions: optional custom fields, so a rule can apply only to certain order types, such as catering or high-value orders.
Messages use placeholders that fill in automatically: customer name, business name, driver name, delivery window, order ETA, order number, drop-off address and tracking URL. For example: "Hi Sam, your driver Alex is 2 stops away. Track your delivery here: [link]." A live preview shows the message as you type, and every rule can be duplicated, edited, or switched on and off.
Common mistakes to avoid
- Too many messages. If customers get a text at every status change, they stop reading them. Pick the moments that matter.
- No tracking link. A message that says "on the way" without a link just moves the call five minutes later.
- Silence on delays. If you only automate good news, the late orders still turn into calls.
- Generic sender. Always include your business name. Unknown numbers get ignored.
- Same rules everywhere. A catering client and a residential customer need different messages. Use custom fields and markets to split them.
One more: do not forget the pickup side. The same rule builder can text the pickup contact, such as a kitchen or store, when a driver is close. That cuts the calls in the other direction, from staff asking dispatch when the driver will arrive.
Notification setup checklist
- List the moments customers call you today, by order type
- Create an "assigned" SMS with the delivery window
- Create a "driver on the way" SMS with the tracking link
- Create a "nearby" or "X stops away" SMS
- Create a "delivered" SMS
- Create a delay rule that texts the customer and posts to Slack
- Set up route completion emails for B2B clients
- Split rules by market and custom field where needed
- Track inbound status calls for four weeks and adjust
Pressed uses automated SMS status updates so catering customers can follow their orders at every step, and reached 97% on-time catering deliveries. To see the tracking page and notification options, visit our delivery tracking page. For background on driver visibility, read driver tracking: why it matters.
Want to see how this would run on your own orders? Book a demo and we will walk through it with your real delivery volume.