Your customers are DMing “where is my order” — your agent should answer before they ask

The DM that arrives every morning

Open any Egyptian e-commerce brand's WhatsApp business number at 9am and you'll find the same twenty messages waiting. "Where is my order?" "I ordered two days ago, no update." "Is my package coming today?" "Order number 18602, what's the status?"

These are not complaint messages. They're information-gap messages. The customer placed an order, got a confirmation email they may or may not have opened, and then — silence. They have no idea if their package is at a warehouse, on a truck, or in a return pile. So they message.

Each of these messages takes your support team one to three minutes to handle: look up the order in Shopify, find the Bosta tracking link, copy it, paste a response. At thirty messages a day, that's thirty to ninety minutes of support time answering the same question with information that was already available and could have been sent automatically.

What the workflow actually does

The Wassel blueprint hooks into Shopify fulfilment events and Bosta shipment status updates:

On every order status change — confirmed, shipped, out for delivery, delivered, failed delivery attempt — send the customer a WhatsApp message with the relevant update. For failed delivery attempts, include a link for them to reschedule or confirm their address.

Five status messages, all triggered automatically:

Order confirmed — sent the moment the order is placed and payment clears. The customer knows you received it and when to expect it. This alone eliminates a large share of the "did my order go through?" contacts.

Shipped — sent when the Bosta waybill is created and the package is handed off. Includes the tracking link. This is the message customers actually want — it tells them the package is moving.

Out for delivery — sent the morning Bosta marks the shipment as "out for delivery". This one sets expectations for the day and reduces failed-delivery attempts, because the customer knows to be available.

Delivered — sent when Bosta marks delivery as complete. Brief, includes a link to leave a review if you've configured that.

Failed delivery attempt — sent when Bosta marks a delivery as failed. This message does real work: it tells the customer what happened, asks them to confirm their address or provide a better time window, and routes their reply into your support queue as a flagged ticket. Without this message, failed deliveries often become silent churners — the customer assumes the brand messed up and doesn't reorder.

Why it matters

1. Support volume drops measurably. "Where is my order?" is typically the most common support contact for Egyptian e-commerce brands. Proactive updates make the question unnecessary for most customers. A 40 to 60% reduction in inbound order-status contacts is a realistic outcome within the first month.
2. Fewer failed deliveries. The out-for-delivery message alone recovers shipments. Customers who know their package is coming today are more likely to be home or make arrangements. Every recovered delivery is a fee you don't pay for a second attempt.
3. Failed-delivery recovery rate improves. The failed-attempt message with a reschedule link converts a significant share of failed deliveries into successful second attempts, rather than losing the order to a return.
4. Customer experience improves without adding headcount. The customers who currently DM you at 9am are not annoyed with you — they just want information. Give it to them proactively and they don't need to DM at all.

On WhatsApp template messages

WhatsApp Business API requires that outbound messages sent to customers who haven't messaged you in the last 24 hours use pre-approved templates. This is not a Wassel limitation — it's WhatsApp's policy for all businesses on the API.

The good news: template approval for transactional messages (order updates, shipping notifications) is straightforward and typically approved within 24 hours. The Wassel blueprint includes the five message templates with the required formatting, ready to submit. You copy them into your Meta Business Suite, wait for approval, and go live. The approval process is a one-time step.

If a customer replies to any of your order-update messages, their reply starts a 24-hour window where you can respond freely — no templates required. Your support team can continue the conversation naturally inside that window.

Copy this into your own agent

The blueprint connects Shopify webhooks, Bosta status webhooks, and WhatsApp Cloud. You'll need your WhatsApp Business Account ID and phone number ID from Meta Business Suite, and you'll need to submit the five templates before going live.

If you're already running the Bosta waybill automation blueprint, this blueprint shares the same Bosta webhook connection — no duplicate setup. The two blueprints are designed to run side by side.