Academy › Build › Bookings and orders
The reminder that answers 'where's my order?' before they even ask
By the end, you'll know what an order notification needs to say so the customer never has to ask, and when it's worth adding a direct WhatsApp button too.
By Yodai · Published September 6, 2026 · Updated October 12, 2026
You let the customer know when their order was ready, with the right message depending on whether they were picking it up or you were shipping it. And still, at eight that night, they text you: where's my order?
It's not that they didn't read the notice. It's that the notice arrived when you decided to send it, not when the doubt hit them. A notice pushes information at a fixed moment. The question can hit them at any other moment: on the subway, before bed, while they're deciding whether to wait on you or go do something else.
The question here isn't whether to send a notification. It's whether the notification itself should already carry the answer, written out, so when the doubt creeps in, the customer can find it right there in the conversation, without you having to be glued to your phone to answer.
A notice pushes; a lookup pulls
The real test isn't whether you have WhatsApp, you probably already use it to confirm reservations or take payments. The test is whether it's worth writing the status into the notification itself, right where the customer will look for it, instead of answering by hand every single time.
Count how many times a week people ask about an order that already got a notice sent. If it's one or two, answer by hand and don't set anything up: the channel takes work to keep current, and for two messages it doesn't pay off. If it's ten or fifteen, and every day you're repeating the same line with different names, the channel already saves you more time than it costs.
Think of a bakery that delivers custom cakes every afternoon. With fifteen orders a day, five customers text before seven asking if their cake is ready yet, even though the ready notice already went out at four. They're not asking because they don't trust you. They're asking because they don't remember if the notice arrived, or they skimmed it and want to confirm before they leave the house.
And you don't need a new app or a tracking page. The channel is the same WhatsApp you already use: the notification carries the status already written out, with the time and the location, and if it ships, the tracking link your carrier gives you, so most customers never have to type a thing.
Setting up this channel has a cost worth counting before you decide. The status text has to stay current, and if you ever change locations or pickup hours, you have to update that change in the notification text you've saved, or the notification will be wrong. It's not a lot of work, but it's work you didn't have before. That's why ten or fifteen inquiries a week is a rough guideline, not an exact number: below that, keeping the template updated usually costs more than it saves.
- The customer texts every time the doubt hits, whether or not it makes sense to ask
- You decide on the spot what to answer, even if it's just repeating what you already sent
- Every new order triggers the same question all over again
- The notification carries the status already written out, with the time and location, without anyone having to ask
- The WhatsApp number stays reserved for what actually needs a conversation
- You only answer the exceptions, not the "what about my order?" for every single order
Which one to pick: Always start with the written status inside the notification itself. Open up the direct number only once volume keeps you from answering by hand, and when you do, add a WhatsApp button that opens the message with the order number already filled in, so you don't waste time asking which one it is.
What you show them before they text
What you write in the notification has to settle the question without the customer typing a word. Three things, no more.
First, the status in the customer's language, not yours: not "in queue," but "in progress, ready around 6:30 PM." The customer doesn't know what your internal workflow means, only how much longer they have to wait.
Second, what to do if something's missing, so they're not texting blind: who to reach out to and what that button is for, not just a bare number with no context.
Third, if it applies, the option to change something without having to ask first whether it's allowed: moving pickup earlier or later, for example. That heads off a lot of messages before they're ever sent.
The third lesson, letting customers change something without asking first whether it's allowed, applies to both pickup and delivery. For pickup, that means moving the time earlier or later. For delivery, it means changing the address before the order leaves your store, something that, if you allow it right from the notification, saves you a lot of the last-minute messages that now catch you by surprise.
Whatever falls outside those three things is an exception, and that's when you do want them to reach out. A wrong order, an address that changed, an allergy you forgot to write down. The number reserved for talking to you fills up with that, not with questions the notice already answers. And when a message comes in through that channel, you know right away it's worth reading carefully, because it's not repeat noise.
Notice that none of the three things you're showing is new information. You already had the status in the notice, the contact for issues already existed somewhere, and you were already handling time or address changes through one-off messages. All you're doing is putting it all together, in one place, before anyone has to ask for it. That's the real work in this last stretch: not inventing information, but organizing it where the customer will go looking for it.
This wraps up the arc of this course: the four statuses, the notice for each one, the different notice depending on pickup or delivery, partial delivery, and running out of stock on something already paid for. What's left is this last stretch: making sure the repeat question doesn't depend on you staring at your phone.
- The notification isn't just an alert anymore: it carries the status written in the customer's language, with the time and what to do if something's missing
- The WhatsApp button shows up after the status, not instead of it
- You know when it's worth setting up: when repeat questions are eating minutes out of your day, every day
- The message that opens the conversation already has the order number in it, so nobody has to ask
Test yourself
Answer before opening each one. If one gives you trouble, go back to the section that explains it.
1. You have a WhatsApp number you only use to confirm reservations, and every afternoon you get six messages asking about orders you already marked as ready. What do you change first?
You write the full status right into the ready notification, with the time and where to pick it up, because those are questions the notification should already answer without anyone typing. The direct number stays for whatever falls outside that.
2. A customer texts your WhatsApp number asking if they can pick up their order an hour later. Is that an exception, or is that exactly what the notification should have covered?
It's a real exception, because it changes something about the order instead of just asking about its status, so you answer it yourself; if it keeps coming up, it's worth adding as an option inside the notification itself.
3. With two inquiries a week about orders that already got a notification sent, is it worth building the full notification, with its WhatsApp button, for every single order?
No: at that volume, answering by hand costs less than keeping the channel up to date. As a rule of thumb, it starts paying off around ten or fifteen repeat inquiries a week.
In Yodai the store comes with the Free plan, with a catalog, a cart and orders. See how to create your online store for free.
NextSubscription, membership, or fee: pick the one that charges for what you actually give