Academy › Build › Bookings and orders

What the customer gets when they order and pay, and what you write yourself

By the end, you'll know which order notifications you can send over WhatsApp with a single template for everyone, and which ones need a message you write yourself for that customer.

By Yodai · Published on September 6, 2026 · Updated on October 12, 2026

Every order moves through several stages, and at each change the customer expects to hear something from you. You need to decide which notices can go out with fixed, one-size-fits-all wording, and which ones need your own touch. You set up a template message for each order status change, and for two weeks it worked fine: the customer pays, you tap to send the usual WhatsApp message that says "order confirmed," and you haven't had to write a thing. Then an order gets complicated. An ingredient runs out, the delivery driver is running late, the customer asks to change the size after paying. The template goes out the same as always, with the same old wording, and suddenly it sounds like nobody's actually there.

The customer replies to that message, and nobody reads it until that night. You'll be tempted to swing to one extreme or the other. Sending everything with a template saves you time, but makes you sound like a machine right when the customer most needs to hear from a person. Writing everything by hand makes you sound approachable, but it means watching your phone every time someone pays for a $15 service, and that stops being sustainable the moment sales pick up.

Neither extreme works. The problem isn't using templates. It's not having decided, status by status, which one goes out with a set text and which one you write yourself, by hand, thinking about that specific order instead of the generic one.

The question that separates one from the other

You don't decide this by how important the status sounds. You decide it with one question: would the message be exactly the same for any order that reaches that status, without looking at what happened to this particular one? If the answer is yes, the template works. If it depends on this order, this customer, or something that didn't go as planned, you write it yourself.

A payment received is the same for order number 12 as for order number 480: the money came in, and that doesn't change from one customer to the next. A forty-minute delay during the dinner rush isn't the same for someone in a hurry to serve a meal as it is for someone who never gave a specific time. A template doesn't have that nuance. You do, or nobody does.

Paying isn't the same as accepting: before you promise anything, it's worth taking a minute to look over the order. The "order confirmed" notice is the one you send once that minute is up and you've already said yes. That's why this notice can be a template: by the time it goes out, you've already looked at the order and decided to take it. And before you build your templates, check what your store already sends on its own: if the customer gets a receipt by email when they order, and a sales note with fixed wording when they pay, that payment notice is already covered, and sending another one on top of it just repeats what's already been said.

Four statuses that don't need you, three that do

With that rule in place, a typical order for a small business moves through just a few statuses, and half of them don't require you to think at all when they go out.

The "order in progress" notice is optional, and that's fine

Of the four template notices, "order in progress" is the only one you can drop without any downside. If your prep time is ten minutes, that notice shows up and disappears almost right alongside "ready," and it just adds noise to the chat. But if you're working on orders that take a full day, like a cake for a weekend event, that notice actually does something: it tells the customer their order is underway and hasn't gotten lost among another thirty.

The rule isn't to always include it or always drop it. It's to look at how long your prep takes and decide if that's long enough for someone to start wondering whether you forgot about their order.

When the notification turns into a lie

A template doesn't fail because it's badly written. It fails when it's sent on the wrong order, when what's happened with that order is no longer business as usual.

This isn't a small detail. A template notice sent at the wrong time isn't neutral: it makes things worse, because it tells the customer that everything's normal on your end when, for them, it clearly isn't. You'd rather no message arrived at all than that one. So the moment an order strays from its normal path, the first thing you do isn't write the message, it's set the template aside for that customer. That applies even if someone else on your team sends the notices, and if you have a bot answering on WhatsApp, pause it on that conversation so it doesn't reply behind your back while you write yours.

The message you write at that point doesn't need to be long. It needs to state the reason for the delay and offer a way out, something the person can choose instead of just waiting without knowing for how long.

Notice what that message doesn't include. It doesn't over-apologize or promise it won't happen again, because you can't promise that and it would sound hollow. It has three things and nothing more: how long the delay is, why, and what the customer can choose right now. That's enough. Making it longer doesn't make it more sincere; it just takes longer to read when the person is standing there waiting.

The costly mistake

With that, you've got the filter in place: four statuses with a template, one of them only if it's actually needed, and three with your personal touch. It also works for any new status you come up with tomorrow: if the text doesn't change with the order, use a template; if it does, write it yourself. Next up is what you do when it's not one order coming in but five at once, and you have to decide which one to start with.

You now know which notices use a template and which ones you write yourself. But that delay notice only works if you send it when the order actually moves, not when its turn comes up: that depends on how you order your prep queue.

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.