Use the Abandoned cart, Abandoned checkout, and Browse abandonment templates to automatically send well-timed SMS. Start from a template or build your own from scratch.
Shopify Messaging centered on 1-to-1 exchanges with customers, or individual manual sends. Well-timed re-engagement relied on separate tools.
Just turn on the Abandoned cart, Abandoned checkout, and Browse abandonment templates, and Shopify Messaging automatically sends SMS. You can also build your own.
Re-engage customers who left items in their cart via SMS.
SMS aimed at higher-intent customers who reached the payment screen but didn't complete checkout.
SMS for customers who viewed a product page but left without adding to cart. The most upstream approach.
| Item | Shopify Messaging until now | New feature (SMS Automations) |
|---|---|---|
| Delivery trigger | Mainly manual / 1-to-1 conversations | Automated Fires on cart, CO, or browse abandonment |
| Templates | Not specified | Built-in 3 pre-built / can create your own |
| Delivery timing | Up to the operator | "well-timed" = automatic timing based on behavior |
| Cost management | Not specified | Threshold Set the SMS spending threshold from Settings |
| Where to configure | Shopify Messaging (existing) | Shopify Messaging > Automations (new) |
Go to the Automations section within Shopify Messaging.
Pick from the pre-built abandoned cart, checkout abandonment, and browse abandonment flows, or build your own.
Set the SMS spending threshold from Shopify Messaging > Settings and start running.
Shopify Messaging, which until now centered on manual customer service, now also houses Automations, an automated messaging feature. Conversational and marketing-automation channels can be viewed on the same screen.
abandoned cart, abandoned checkout, and browse abandonment. Since this set of three common ecommerce "abandonment" triggers is included from the start, you can spin up a PoC right away.
SMS is a channel that incurs carrier costs per message. With an "SMS spending threshold" included in Settings as standard, you can structurally prevent cost incidents from runaway sends.
It explicitly states "create your own." Because there's room to design your own send triggers, there's also room to build in industry-specific scenarios that templates don't cover (restocks, reservations, subscriptions, etc.). No detailed specs are provided.
In the published Changelog, details such as the GraphQL Admin API, Webhooks, supported countries, required plans, and variable merge fields in the SMS text arenot documented. When you dig in on an implementation engagement, you'll need hands-on verification with the Help Center documentation and a sandbox.