An order-confirmation workflow sends a WhatsApp message automatically when an order comes in, using the order trigger in Workflows and a WhatsApp action step. You build it once, add the variables you want, and test it against a real order before switching it on. The part most sellers miss is the 24-hour window: outside it, only an approved template will reach the customer.
What does the order trigger actually fire on?
Workflows has a store-event trigger for orders. You choose the event, then decide which orders should enter the workflow with trigger-level filters. A filter can narrow by order value, product, or another condition the builder exposes, so a small order and a bulk order do not have to receive the same message.
Think about the event you actually want. A confirmation usually belongs to the moment the order is created or paid, not the moment it ships. If you want a shipping message, that is a different workflow with a different trigger. Mixing the two into one flow makes the copy vague and the timing unreliable.
Keep the first workflow narrow. One trigger, one audience, one message. You can add a second workflow later for a different order event, and you will find it much easier to work out which one sent what.
Which WhatsApp action should you use?
The WhatsApp step can send text, an image, buttons, or a typing indicator. Text is the default for a confirmation. An image works when the confirmation is also a receipt or a product photo. Buttons suit a choice, such as Track order or Chat with us. The typing action makes the message feel less abrupt, especially when it follows a short delay.
You can combine steps in one workflow. A typing indicator, then a text message, then a button is a normal sequence. Each step runs in order, and the workflow records what happened so you can see where a run stopped.
Do not stack every action into the first version. A confirmation that sends three messages in ten seconds feels like spam. Start with one clear message and add a second only if it earns its place.
How do variables make the message useful?
Variables pull order data into the message: the customer's name, the order number, the amount, the items. The exact list depends on what the trigger exposes, so check the variable picker in the builder rather than guessing a field name.
A good confirmation repeats back what the customer bought. That is the whole job. It reduces the did-my-order-go-through messages that eat your day and gives the customer something to screenshot.
Use a fallback for anything that might be empty. A message that starts with a bare Hi and a comma because the name field was blank looks worse than one that starts with Hi there. Test with a real order and with a sparse one.
What happens outside the 24-hour WhatsApp window?
WhatsApp allows free-form messages only within 24 hours of the customer's last message. Outside that window, you need an approved message template. Salesive lists templates live from Meta, so the templates available in the builder are the ones your account can actually use.
This matters for order confirmations because the customer may have ordered from your storefront without sending you a WhatsApp message first. In that case the window may already be closed. The workflow still runs, but the message has to be a template rather than free text.
Salesive does not approve templates for you, and a template is not guaranteed to be approved. You submit it through Meta's process and wait for the decision. Build the workflow with that dependency in mind: a free-text step for customers inside the window, and a template step for everyone else if your flow supports that branch.
Do not tell customers to expect a WhatsApp confirmation until you know which path their order will take. A promise the window cannot keep is worse than a quieter confirmation by email.
How do you test a workflow without annoying customers?
Workflows has test runs. A test run executes the flow so you can see the message, the variables and the step order before a real customer receives anything. Test runs count against the usage meter, so they are not unlimited free attempts.
Test three cases: a normal order, an order with a missing name, and an order outside the 24-hour window if your flow branches on that. The third case is the one that usually exposes a template problem.
After the test, place one real order yourself and watch the whole path. A workflow that looks right in the builder can still send at the wrong moment if the trigger is wrong.
What should the confirmation say?
Keep it short and specific. Order number, what was bought, the amount, and what happens next. If delivery is involved, say when you will contact them with a date rather than promising a date you cannot keep.
Add one route to a human. A button or a line that says reply here if something is wrong turns a confirmation into a support channel. The customer who replies is easier to help than the customer who quietly disputes a charge.
Do not put a discount in the confirmation. The customer has already paid. A discount belongs in a follow-up workflow after delivery, not in the message that confirms the sale.
A confirmation is not marketing. It is the receipt your customer reads before they trust you with the next order.
Which mistakes should you avoid?
Sending the same message twice because two workflows fire on the same event. Check your active workflows before you add another one.
Using free text for every customer and assuming it will deliver. The window decides that, not the workflow.
Leaving the workflow in draft after testing. A tested workflow that is not switched on sends nothing.
Ignoring the usage meter. Test runs and live runs both count, and a runaway loop is expensive. Check usage before a busy sales period, not after.
Frequently asked questions
Does Salesive send the WhatsApp message automatically?
Yes, once the workflow is active and the trigger fires. The message still has to be free text inside the 24-hour window or an approved template outside it.
Can I send an image with the confirmation?
Yes. The WhatsApp action supports text, image, buttons and a typing indicator, and you can combine them in one workflow.
Are templates approved automatically?
No. Salesive lists templates live from Meta, and approval is Meta's decision. Submit the template and wait for it before you rely on it.
Do test runs cost anything?
They count against the usage meter. Check your plan and usage before you run a long series of tests.
Can I use the same workflow for shipping updates?
You can add steps, but a separate workflow with a shipping trigger is usually clearer. One trigger and one message per workflow is easier to debug.
Start with one order event, one message and one test order. Once the confirmation is reliable, add the template path for customers outside the window and a follow-up workflow for delivery. The features page shows where Workflows sits in the dashboard, integrations covers the apps that feed it, and pricing covers what each plan includes. For the DM side of the same channel, read how Ola replies to WhatsApp, Instagram and Telegram DMs, and for the recovery flow that follows an abandoned cart, see abandoned cart recovery with Recart.