Define an eligible abandoned cart.
Use a minimum inactivity period, require usable contact details, exclude already purchased or recently recovered carts, and deduplicate by store and cart identifier. Avoid treating every checkout view as intent.
Integration-dependent
The cart event must come from an approved external source.
The current direct Shopify and WooCommerce connector releases do not expose abandoned-cart events. Confirm the authoritative trigger, consent, deduplication, and purchase stop before designing this journey.
Lifecycle workflow
Recover a cart without turning WhatsApp into a reminder machine.
A useful cart-recovery workflow starts from a reliable cart event, sends only to an eligible contact, carries enough product context to be helpful, and stops as soon as the customer buys, opts out, or needs a person.
In one line
Trigger one relevant, consent-backed template from a verified cart event; stop on purchase, reply, opt-out, or a strict frequency cap; and measure completed orders rather than clicks alone.
No credit card. No commitment.
The stop conditions are part of the workflow.
A recovery message is only useful while the cart is open and the contact remains eligible. Purchase, reply, opt-out, or frequency limits should close the sequence immediately.
Cart RC-2704
Consent-backed recovery
STEP 1
Cart event
Eligible contact and product context received
STEP 2
One reminder
Approved template with checkout link sent
STEP 3
Stop condition
Purchase, reply, opt-out or frequency cap
Order event stops the recovery sequence immediately
The problem
Most recovery flows optimise the send and neglect the state.
Stale carts, duplicate events, missing consent, and delayed purchase webhooks create irrelevant reminders. The quality of the trigger and stop logic matters as much as the copy.
- The cart identifier must be stable across retries.
- The recipient must have a valid WhatsApp messaging basis for this purpose.
- The approved template must match the category and current cart context.
- A purchase event must stop scheduled recovery messages.
Send less, with better context.
Reference the shop and cart without exposing sensitive data. Use a direct checkout link and a clear support option. One timely reminder is a safer starting point than an aggressive sequence, especially before you have quality and conversion data.
Handle every reply in the same thread.
Customers may ask about delivery, returns, payment, size, or stock instead of clicking checkout. Route the conversation to the team inbox with the cart and contact context so a person can resolve the blocker without asking the customer to repeat it.
Measure incrementality, not only attributed revenue.
Track eligible carts, messages delivered, replies, purchases after send, opt-outs, negative quality movement, and purchases that would have happened without the reminder. Use a holdout group when volume permits.
Start with a conservative operating policy.
- One reminder per cart until quality and conversion are understood
- A contact-level frequency cap across all marketing journeys
- Immediate suppression on STOP or equivalent opt-out
- No send when sender, template, or quality state is unknown
- A named owner for failed events and customer replies
FAQ
Questions worth answering.
A business can send an appropriate approved template when it has a valid basis to message the recipient and follows WhatsApp policy. Consent, template category, recipient expectation, and local law all matter.
Research notes
Evidence checked for this page.
WhatsApp's business messaging policy requires businesses to respect user choices and comply with applicable law.
WhatsApp Business Messaging Policy · Accessed 8 August 2026
Meta's template documentation describes category and review requirements for business-initiated messages.
Meta for Developers · Accessed 8 August 2026
Compare
Evaluating platforms? Every claim cited, every price dated.
Ready to ship a WhatsApp flow that doesn't break?
Apply for founding access. No credit card. Cancel anytime.