The quick answer
A useful recovery flow contacts an eligible customer about a real incomplete checkout, provides a safe route back and stops as soon as the order is completed or the customer opts out. A phone number in a checkout is not, by itself, permission for WhatsApp marketing.
An abandoned checkout can mean many things: an unexpected delivery fee, a question about size, a payment problem or someone simply comparing options. A discount message is not the right answer to all of them.
Build recovery around helping the customer finish a purchase they still want. That requires a dependable store connection, a clear contact preference and a flow that knows when to stop. Start with those basics before adding a long sequence of reminders.
Know which event your store actually provides
Someone adding an item to a basket is not the same as an identifiable checkout. Shopify’s abandoned checkout object describes an incomplete checkout where the customer supplied contact information, and can include a recovery URL. Some useful customer fields may still be missing.
WooCommerce recovery depends on the store and the extension or integration used to capture abandonment. Do not assume a generic order connection can identify every guest basket. Establish the event, its timing and the fields available before designing the message.
Ask a practical question during connection setup: “Can this event tell us that this specific customer has this specific incomplete checkout?” If the answer is uncertain, start with an assistance journey the customer deliberately requests instead of guessing.
Check contact preferences before a reminder
Keep the checkout contact field separate from the choice to receive WhatsApp communications. Review what the customer was shown and what they selected. An email preference or an SMS checkbox should not be silently treated as an all-channel marketing preference.
The message’s content matters too. A recovery offer encouraging a purchase is not automatically a neutral order-status update just because it mentions a basket. Use the appropriate approved template and review Meta’s current classification for the actual content.
Make the sender recognisable. A customer should immediately understand which store is contacting them and why. Provide a simple way to decline further reminders, and make sure that preference applies to the rest of the sequence.
Start with one helpful recovery message
Consider a store selling office accessories. After a sensible delay, the flow checks that the checkout is still incomplete, the customer is eligible for contact and a valid recovery link exists. It sends a short message offering help with the purchase, then waits for a response or a verified order.
The message could explain: “You left a desk organiser in your basket. If you still need it, you can return to your checkout here. Have a question about delivery?” This is an illustrative draft, not an approved template. The business must submit and use the suitable template for its setup.
Avoid including private checkout details in a public preview. Check that links point to the correct store and do not expose one customer’s checkout to another. A familiar domain and a clear message are more useful than an unexplained shortened link.
Receive the event
Identify the checkout and preserve its store reference.
Check eligibility
Review preferences, completion status, timing and template readiness.
Offer a useful next step
Use the correct recovery route or an agent-assisted answer.
Stop or hand over
Stop on purchase or opt-out; assign questions to a person.
Make purchase suppression the strongest part
An order can be completed after a reminder is scheduled but before it is sent. Recheck the store at sending time, and cancel later recovery messages when the purchase is confirmed. A confirmation from the customer is useful context, but verify the order before changing fulfilment or payment status.
Protect against duplicate events as well. Repeated store notifications should update one recovery journey rather than create several identical messages. Give every checkout a stable reference and define what happens if the customer starts a genuinely new checkout later.
When the store connection is unavailable, delay the send and surface the problem. Sending an outdated recovery message to a customer who has already paid is worse than sending the reminder later.
Measure recovery without claiming every sale
Report the eligible checkout audience, messages attempted, delivered messages, responses and purchases matched to that journey. Keep a clear time window and explain how orders are linked. A purchase after a message is an observed association, not proof that the message caused the sale.
Track discounts and refunds when assessing value. A recovered order that required an expensive incentive may contribute less than a smaller order helped by a useful delivery answer. Compare the actual contribution rather than only gross revenue.
| Signal | Useful interpretation | Common mistake |
|---|---|---|
| Recovery link used | The customer followed a tracked route | Calling it a completed sale |
| Matched order | An order was linked under your rules | Claiming certain causal uplift |
| Customer reply | A chance to resolve a buying question | Sending the remaining reminders anyway |
| Opt-out | Stop and review relevance | Trying again through another sequence |
Verify the store connection before rollout
A Shopify or WooCommerce logo on a page is not enough. Confirm the supported store version, granted access, installation route and event coverage with the Wamigos team. Connector approval and account setup can affect what is available to a particular business.
Run a small end-to-end test with a consenting team member: abandon a checkout, receive the right message, complete the order and confirm that all later reminders stop. Repeat with missing contact details, an opt-out, changed stock and a disconnected store. Only then expand the audience.
Common questions
Can every anonymous cart receive a WhatsApp reminder?
No. You need an identifiable and eligible customer, appropriate permission and a supported store event. Many visitors leave before supplying usable contact information.
Is an abandoned cart message always a utility message?
No. Classify the actual content and purpose under current Meta rules. A purchase encouragement or discount should not be disguised as an order update.
Should we offer a discount in the first reminder?
Not automatically. First understand the obstacle. Delivery details, sizing help or a payment question may be more useful than reducing the price.
How many recovery messages should we send?
Start with one useful message and evaluate the response. Any additional follow-up needs a clear reason, appropriate permission, a sensible stop rule and current purchase checks.
Will connecting my store recover orders immediately?
Connection is only the start. Verify event coverage, templates, customer preferences, suppression and reporting before activating a recovery flow.
Sources & further reading
Primary documentation reviewed 16 November 2026. Provider rules, pricing and eligibility can change. Check the linked source before making account or billing changes.






