Cash-on-delivery orders that nobody confirms become returned parcels. That is the most expensive unanswered message in ecommerce.
A Shopify WhatsApp integration connects your store's events — orders, shipments, cancellations, failed payments and abandoned checkouts — to automated WhatsApp conversations, so customers are confirmed, updated and recovered without anyone copying an order number between two tabs.
Connecting Shopify to ConvoFly takes one click and turns six store events into things you can build flows on. It also puts order history beside the chat, so an agent answering "where is my order" is not alt-tabbing into Shopify admin.
Those six events cover the whole order lifecycle, and each one is a moment the customer is already thinking about you — which is why store-triggered messages outperform scheduled campaigns. On the $12 Starter plan you get 3 integration blocks and 500 billable automation runs a month, which is enough to run two of these flows for a store doing a few hundred orders.
Flows can also write back: tag an order in Shopify, mark a COD order confirmed, and record the outcome to Google Sheets or your own system through the Call-API block.
In markets where COD dominates, unconfirmed orders are the single biggest source of loss — you pay to ship a parcel that gets refused. The flow that fixes it is simple and worth building first:
That last branch — the if-no-reply timeout — is what separates a flow that works from one that only works on cooperative customers.
This is the highest-volume question in ecommerce and the most automatable, because the answer is entirely factual and already exists in Shopify. A flow can recognise the question, look up the customer's most recent order, and reply with its status and tracking link — no agent, no waiting, and correct every time.
The nuance is what happens when the answer is bad news. If the order is late or stuck, an automated status line is worse than nothing, so the flow should detect that case and hand to a person with the order context attached. Answering "where is my order" automatically walks through both branches.
WhatsApp's advantage over email here is that the message is actually seen. The constraint is permission: you may only message customers who have opted in to marketing messages, using an approved template. ConvoFly enforces opt-out handling and a per-contact marketing frequency cap so recovery campaigns do not turn into the reason people block your number.
Keep the sequence short. One well-timed message an hour or two after abandonment, and at most one follow-up. Anything more damages the quality rating that governs your messaging limits.
Outside COD markets the highest-value flows are quieter. An order confirmation sent on WhatsApp rather than only by email actually gets seen, which reduces the "did my order go through" messages that follow every checkout. A shipping update with tracking sent the moment the fulfilment is created removes most "where is my parcel" enquiries before they are typed.
Both are utility messages rather than marketing, which matters: Meta prices message categories differently and utility templates are generally cheaper than marketing ones — see Meta's pricing documentation for current rates in your market.
Most stores stop automating at the doorstep, which leaves the two cheapest revenue flows unbuilt.
A review request a few days after delivery arrives when the customer actually has an opinion, and WhatsApp response rates on it are far better than email — see review requests on WhatsApp after delivery for the timing and the template category to use.
A back-in-stock alert is the rare marketing message customers are pleased to get, because they asked for it. It is also cleanly opt-in by construction: the customer requested the alert, so consent is unambiguous. Back-in-stock alerts on WhatsApp covers wiring it to your inventory.
Both are worth building before any broader campaign, because both are triggered by something the customer did rather than by your calendar.
Shopify integration blocks are metered: Starter includes 3 integration blocks across your published flows, which covers a COD flow plus a shipping notification. Heavier use moves you to Growth or above. Order-writeback actions need the write permission granted at connect time, so if you connected before enabling it you will need to reconnect the store.
Plans start at $12/month with a 14-day free trial. Meta's per-conversation charges are billed by Meta separately — see Meta's pricing documentation.
| WhatsApp via ConvoFly | ||
|---|---|---|
| Needs explicit opt-in | Usually | Yes, always |
| Approved template required | ✕ No | ✓ Yes, for the first message |
| Customer can reply and be answered by a person | ✕ Rarely | ✓ Yes, same inbox |
| Store event triggers | ✓ Yes | ✓ Yes, six Shopify events |
| Write back to the order | ✕ No | ✓ Tag and confirm in Shopify |
| Per-message cost | Near zero | Meta charges per conversation |
Figures checked August 2026. WhatsApp platform limits and charges are set by Meta and can change — always confirm against Meta's own documentation.
You connect from ConvoFly's onboarding and authorise in your Shopify admin. Grant order write permission at that point if you want flows to tag or confirm orders — connecting without it means read-only, and you would need to reconnect to add it later.
No. WhatsApp marketing messages require opt-in and an approved template. ConvoFly enforces opt-out handling and a per-contact frequency cap, because sending to people who did not agree is what destroys a number's quality rating.
It fires when an order is placed with cash on delivery, sends an approved template restating items, total and address with Confirm and Cancel buttons, tags the order in Shopify based on the answer, and follows up once if the customer does not reply before flagging it for a human.
Yes. Once your store is connected, an agent sees that customer's order history beside the conversation, so answering a delivery question does not mean switching to Shopify admin.
Integration blocks are metered per plan rather than per flow. Starter includes 3 integration blocks across all published flows, which is enough for a COD confirmation plus a shipping notification. Growth and above include more.