Obsedia SMS Marketing Hub includes ten ready-to-customize automations. “Ready” describes the starting point for a merchant, not permission to send to every contact. Each preset belongs to a different customer moment. This map names all ten, explains why similar presets should not be merged and shows which controls to review before activation.
Ten presets, grouped by customer moment
Three presets focus on the relationship around a purchase: Welcome, Win-back and Post-purchase. Three address an unfinished or special purchase path: Cart recovery, Checkout recovery and Cash-on-delivery reminder. Four keep a buyer informed after an order: Order confirmation, Payment confirmation, Shipping update and Delivery update.
The names below describe intended use, not an invented default delay or guaranteed Shopify event. Review each automation’s actual conditions, eligible audience and message settings inside the app before enabling it.
- Welcome — introduce the store to a newly eligible SMS subscriber.
- Win-back — reconnect with an eligible customer after a quiet period chosen in the app.
- Post-purchase — follow an order with a relevant next step or offer.
- Cart recovery — respond to an eligible cart recognized through the storefront capture path.
- Checkout recovery — respond to a separate incomplete-checkout event.
- Cash-on-delivery reminder — communicate about an eligible COD order where this payment method applies.
- Order confirmation — acknowledge an order using the event and customer details Shopify provides.
- Payment confirmation — communicate a confirmed payment state when that event is available.
- Shipping update — tell an eligible buyer about a shipment update received by the store.
- Delivery update — reflect an available delivery event, not an assumed carrier milestone.
Cart recovery and checkout recovery are separate
A storefront cart can be left before a customer starts checkout. A checkout can be abandoned after contact information has been entered. Obsedia lists separate presets because these are different inputs. For the cart route, its app embed helps recognize eligible signed-in shoppers subject to Shopify privacy choices. The checkout route must be examined as a checkout event.
Turning on cart capture does not activate either SMS automation. If one recovery flow looks empty, inspect the customer journey it represents before changing message copy. The companion article on cart versus checkout recovery walks through that distinction with two controlled examples.
A preset is not permission to send
Customer eligibility is not inferred from the automation name. The product documents SMS subscription and opt-out checks, including for order updates. Shopify also distinguishes SMS marketing permission from email permission. Before turning on any preset, verify the recipient state relevant to your store and destination.
Storefront privacy permission is another question for cart capture. A visitor’s consent to the relevant storefront processing does not itself subscribe a phone number to SMS. Keep the data-capture gate and the communication gate separate in test cases and support conversations.
What the merchant still configures
Obsedia’s setup asks for a country, time zone and sending window. Merchant settings and each automation determine when a message can be considered. Use the preview to read the final personalized message as a customer would, including its unsubscribe link where applicable. Character encoding and message parts affect cost, so the cost estimate matters before confirmation.
SMS usage is separate from the subscription and uses prepaid EUR credit. A preset cannot be treated as a free message entitlement during the trial. Check recipient eligibility, destination, content and available credit before you expect delivery; then use Results to distinguish queued, sent, delivered, failed and unknown outcomes.
Order updates need real Shopify events
The order, payment, shipping and delivery presets are not interchangeable labels. A payment update should reflect a payment event, and a delivery update needs a delivery signal the store actually receives. Do not write a message that claims a parcel is on the way because an order was merely created.
The SMS Marketing Hub product information says permissions and opt-outs are still respected for order updates. Start with the event available in your Shopify store, check the wording against that event and keep the message useful rather than turning every service notice into a promotion.
Start with a single measurable workflow
If the immediate problem is an unfinished checkout, configure that preset and verify the checkout event before trying all ten. If the problem is customer uncertainty after purchase, an accurate order or shipping update may be more valuable than another discount reminder. The right starting point is the one your store can support with reliable data and the necessary permission.
Run a controlled test for the chosen workflow. Record the event, expected recipient eligibility, intended send window, message preview and actual outcome. Once those parts are understood, add another preset. That sequence gives the team a way to diagnose a quiet automation without guessing which of ten settings caused it.
The ten presets cover different moments; configure and verify one workflow at a time, with consent, source event, message content, credit and outcome kept separate.
