The email nobody reads
Order placed. Confirmation email sent. Shipped. Another email. Out for delivery. Another email.
The customer checks none of them. They either track directly on the courier's website, or they message your support team asking where their order is — because the emails went to promotions, got lost in an inbox with 300 unread messages, or just weren't noticed.
This sequence plays out dozens or hundreds of times a day for active e-commerce businesses. And it drives a support load that is almost entirely preventable.
The fix is not a better email. It is a different channel.
Why WhatsApp works differently for transactional updates
WhatsApp has an unusual property for a messaging platform: people check it. Not occasionally — compulsively. The average WhatsApp user in India opens the app multiple times per day. A message that arrives there gets seen within minutes, not hours.
Industry benchmarks for transactional WhatsApp messages consistently show open rates between 85-95%. Email open rates for the same type of content — order confirmations, shipping updates — typically sit between 20-35% for good senders, lower for average ones.
That gap matters for support volume. If customers are reading the delivery update, they are not messaging to ask where their order is. We see this consistently: businesses that move order updates to WhatsApp report meaningful reductions in "where is my order" support contacts within the first month.
The other advantage: no login required. Your customer does not need to find the email, click the tracking link, create an account, and wait for a page to load. The update arrives in the same app they use to talk to family. The friction difference is significant.
The five messages that cover 90% of e-commerce order journeys
Most D2C and e-commerce operations can get to 90% coverage of order communication with five well-built WhatsApp templates.
1. Order confirmation
Sent immediately when an order is placed. Contains: order number, product summary (not the full receipt), and estimated dispatch date. Optional: a brief reassurance message if it is a first purchase from a new customer.
What to avoid: loading this message with marketing content. The customer just bought something — they want confirmation, not an upsell. Keep it clean. There is time for cross-sell later.
2. Order confirmed and being packed
For businesses with same-day or next-day dispatch, this message is sometimes skipped. For businesses with longer fulfilment windows (custom products, pre-orders, anything that takes 2+ days to pack), a "we have your order and it is being prepared" message significantly reduces enquiry contacts. Customers who receive this message in the gap between order and dispatch are considerably less likely to message asking what is happening.
3. Order shipped
The most important message in the sequence. Contains: the courier name, tracking number as text, and a deep link to the tracking page if the courier supports it. Keep the message short — the tracking link does the work.
One thing that improves this message: adding the expected delivery date rather than just "your order has been shipped." "Expected delivery: April 3rd" is more useful than "shipped on April 1st." If the courier API provides delivery estimates, pull that data into the template variable.
4. Out for delivery
Sent on the delivery day. Simple message: "Your order is out for delivery today. Someone should be available to receive it." This message has a measurable impact on first-attempt delivery success rates because it primes the customer to be available.
For businesses where failed deliveries have meaningful cost implications — return shipping, re-delivery fees, lost revenue — this single message pays for the entire WhatsApp integration.
5. Delivered
Sent when the courier marks the order as delivered. Confirms delivery, invites the customer to reach out if there is any issue, and creates a natural transition point to post-purchase communication.
This message is the right moment for a review request — not a week later by email. A customer who just received their order and is satisfied is at peak advocacy. We have seen review request conversion rates from post-delivery WhatsApp messages run significantly higher than from follow-up email sent days later. For the review collection side of this, AutoChat integrates with post-delivery WhatsApp flows to handle the timing and collection automatically.
Building the flows: what to think about
Template approval comes first
All five of these messages need to be submitted as WhatsApp message templates and approved by Meta before they can be sent. For well-written utility templates — transactional messages that clearly identify the business and provide relevant order context — the approval process is typically straightforward.
Category matters: all five of these should be submitted as Utility templates. They are clearly transactional, clearly expected by the recipient, and clearly relevant to a specific order. Do not categorise order updates as Marketing — it will get rejected and slow down your launch.
Trigger points and timing
Each message is triggered by an event: - Order confirmation → immediately on order placement - Packed → when fulfilment team marks as packed in the system - Shipped → when courier generates tracking number - Out for delivery → morning of delivery day (pull from courier status API or webhook) - Delivered → when courier confirms delivery
The trigger architecture depends on your e-commerce platform. Shopify and WooCommerce both have webhook support that makes event-based triggers straightforward. Custom platforms need API integration between your order management system and the WhatsApp Business API.
Handling replies
When you send a customer a delivery update on WhatsApp, some percentage will reply. "Can I change the delivery address?" "There is a problem with the order." "Is the product original?"
Your flow needs to handle replies — either routing them to a human agent, or using automated response logic for common questions. An order update that goes out to 300 customers with no reply handling and no one monitoring the inbox is a customer experience failure waiting to happen.
A simple setup: an automated acknowledgement that sets expectations ("we received your message and will respond within X hours") plus routing to the team member responsible for post-purchase support. AutoChat's flow builder handles this with a keyword-triggered routing rule on the order update number.
Do not send from the same number as marketing broadcasts
This is a mistake that creates real operational risk. If your promotional broadcasts generate complaints or lower your account quality rating, it affects all messages from that number — including order updates that customers genuinely need.
Keep transactional order communication on a separate WhatsApp Business number from marketing broadcasts. The cost of maintaining two numbers is trivial compared to the risk of having order updates affected by marketing quality issues.
A note on opt-in requirements
WhatsApp order update templates require that the customer has opted in to receive WhatsApp messages from your business. For e-commerce operations, the standard opt-in mechanism is a checkbox at checkout: "Send order updates via WhatsApp" with the mobile number pre-filled or entered.
The opt-in rate from a clear, well-placed checkout checkbox is typically 60-80% for Indian e-commerce. The customers who opt in are more engaged and generate fewer support contacts. The ones who do not opt in can still receive email updates — you are not removing their communication channel, just adding a better one for those who want it.
Document your opt-in data. Meta requires that you can demonstrate opt-in for contacts receiving templated messages, and your BSP (Business Solution Provider) may ask for this during account review.
Getting this live
The practical path: start with just three messages — order confirmation, shipped, and delivered. Those three cover the highest-value moments in the order journey and are enough to see the impact on support volume before building out the full five-message flow.
Measure "where is my order" contact rate before and after. That metric will tell you whether the flow is working faster than any other signal.
For businesses building this on WooCommerce, the AutoChat WooCommerce integration handles the trigger → template logic without custom development. Shopify integration works via webhooks. For custom platforms, the AutoChat API covers the send-side once your triggers are in place.
*Image suggestion: a linear flow diagram showing the five order stages (Placed → Packed → Shipped → Out for Delivery → Delivered) with example WhatsApp message bubbles at each stage — show the actual message content, not just labels.*