WooCommerce SMS cart recovery: triggers, consent, and launch checks

1. Define what the customer actually abandoned

A shopper can add an item without visiting checkout, begin checkout without submitting an order, or submit an order that remains unpaid. Those moments need different follow-ups. A cart reminder should not tell someone their payment failed when the store has no evidence that they attempted payment.

WooCommerce distinguishes Pending payment, Failed, On hold, Processing, and Completed orders. Its documentation says On hold can mean payment confirmation is pending, including with delayed payment methods. Check the gateway and order notes before treating that status as abandonment. A Draft checkout record also does not establish that the shopper submitted or paid for an order.

2. Put permission ahead of the recovery trigger

Keep the phone number, SMS permission, and shopping event as separate facts. Someone may supply a number for delivery coordination without asking for promotional reminders. The recovery message’s actual purpose, the signup disclosure, and destination requirements determine the permission needed. Adding a discount makes the sales purpose especially clear.

Twilio’s Messaging Policy requires prior express written consent for promotional messages and limits consent to the subject the recipient agreed to. OneMoreSend’s SMS terms also require marketing permission for the store sending the text. Keep the wording shown to the shopper, collection source, date, and opt-out history available for review. An imported number without that evidence should not enter the recovery audience.

3. Write a workflow the team can explain

Use the following as a planning example, then confirm the exact rules in your account. OneMoreSend connects WooCommerce through its plugin and offers SMS cart and incomplete-payment journeys. Confirm that your storefront’s checkout implementation produces the events you need before turning a journey on.

• Entry: identify the shopping event and contact, then check that the business, message, recipient, and destination are eligible.
• Wait: give the shopper time to finish and apply the permitted sending window for that recipient. Staffed support hours are a separate consideration.
• Recheck: exclude contacts who bought, opted out, or no longer meet the journey conditions. Check for overlapping email and SMS recovery steps.
• Message: identify the store and state the relevant next action without inventing a payment problem, stock shortage, or deadline.
• Exit: stop recovery after purchase and assign a person to customer replies. Do not continue the sequence around an unresolved support issue without review.

4. Match the text to a verified next step

For an eligible promotional recovery program, a draft could read: ‘[Store]: Still considering your order? Return to our store: [reviewed store link]. Reply STOP to unsubscribe.’ This is an example to adapt, not a preapproved template. Use a truthful store destination and confirm any required disclosures before sending.

Do not promise a restored cart unless the linked experience actually restores it. Likewise, a payment reminder needs a valid unpaid order and a working payment path. Open the destination on a phone, including when logged out, and test an expired session. Never ask the customer to text card numbers or authentication codes to complete payment.

5. Test the cases that can embarrass a store

Use authorized test contacts and test orders before a broader launch. Walk through a shopper who buys during the wait, someone who opts out before the send, an unpaid order that later clears, and two devices used by the same shopper. Check what happens when the phone number is missing or the checkout sends the same event twice.

A test should confirm both the message that arrives and the message that should never arrive. OneMoreSend’s public SMS offering includes exit-on-order recovery, but your own test must establish that purchase events reach the account promptly. A broken store connection can undermine an otherwise sensible journey.

6. Measure orders alongside the cost of interruption

Review eligible contacts, attempted sends, delivery failures, clicks, orders, opt-outs, and support questions together. Decide how you attribute an order when both email and SMS were involved. A purchase following a text is not, by itself, proof that the text caused it.

Start with one clearly defined recovery use case. Use actual customer replies to improve checkout instructions and store policies, then decide whether another message adds value. The best recovery improvement may be fixing the payment confusion that caused customers to leave.

Common questions