Cart abandonment, 1-hour delay
Still thinking about it, {{first_name}}?
Your cart with {{cart_item}} is waiting. Free delivery if you check out in the next 2 hours.
Use case
ReachBell for e-commerce.
Recover carts, send order updates, ping wishlist shoppers when prices drop, and run flash sales — push, email, and WhatsApp from one place.
The problem
The e-commerce engagement tax.
Three vendors, three dashboards, three bills — and the campaign that needed to ship before the weekend slipped to Tuesday.
Most online stores end up with a cart-recovery tool from one vendor, an email-marketing suite from a second, and a transactional sender from a third. Each tool has its own segmentation language, its own webhook contract, and its own definition of an “active subscriber”. A growth team can spend more time reconciling reports than running campaigns — and when a Diwali sale goes live, nobody is quite sure which list received which message.
Cart abandonment is the canonical example. The push provider knows a visitor browsed a product. The email tool knows the same person opened a newsletter last week. The transactional sender knows the order eventually came in. None of them know about each other, so the shopper gets four near-duplicate messages — or worse, gets a 10%-off code an hour after paying full price.
Back-in-stock and price-drop alerts have the same shape: an event in your store needs to fan out to whoever cared about that SKU, on whatever channel they accepted. When the alert lives in a separate system from the segments, fan-out becomes an ETL job instead of an automation step.
Templates
Notifications you can ship today.
Drop these into the composer and adjust the merge tags — every template works across web push, mobile push, and email.
Order shipped
Order #{{order_id}} is on the way
Out for delivery today via {{courier}}. Track it from your account — ETA {{eta}}.
Back-in-stock alert
{{product_name}} is back
The size you wanted is in stock again. Limited inventory — first-come, first-served.
Flash sale, 4-hour window
Flash sale: 40% off ends at 9 PM
Sitewide discount auto-applied at checkout. No code needed. Excludes new arrivals.
Wishlist price drop
Price drop on something you wishlisted
{{product_name}} just dropped to ₹{{new_price}} — down from ₹{{old_price}}.
Review request, 7 days post-delivery
How was your order?
Took it home, used it, loved it? Drop a quick review — 50 reward points if you do.
Automation flows
Three flows worth their weight in revenue.
Built from the visual flow builder — each node is a send, a wait, or a condition. No code.
Cart abandonment recovery
Three-touch sequence across push, email, and WhatsApp to bring shoppers back without burning the list.
- 01Trigger: `cart.abandoned` webhook from your store (Shopify, WooCommerce, custom).
- 02Wait 1 hour, then send web/mobile push: "Still thinking about it?" with deep link back to the cart.
- 03If no click after 6 hours, send email with the cart contents and a 10% nudge code.
- 04If still nothing after 24 hours, send WhatsApp template (opt-in only) with a final reminder.
- 05Exit the flow as soon as the order is placed — webhook listens for `order.created`.
New customer onboarding
Welcome new buyers, set expectations, and surface the categories they actually browsed.
- 01Trigger: first `order.completed` for a customer.
- 02Send "Order confirmed" email immediately (transactional, bypasses marketing throttle).
- 03Wait 2 days, then push: "Your order is on the way" with tracking deep link.
- 04After delivery webhook, wait 3 days and send "How to care for {{category}}" email.
- 05After 14 days, branch on browse behaviour and send a tag-segmented recommendation email.
Win-back for dormant shoppers
Re-engage customers who haven't purchased in 60 days with a tiered offer.
- 01Segment: last purchase > 60 days ago, opted in to marketing, lifetime value > ₹2,000.
- 02Send email: "We miss you — here's 15% off your next order."
- 03Wait 5 days, then push: "Your 15% code expires tonight."
- 04If the code is redeemed, exit and tag the customer as `winback_won`.
- 05If not, drop the customer to a low-frequency monthly segment instead of unsubscribing.
In the wild
Who's using it.
We dogfood ReachBell on our own products before recommending it to yours.
ReachBell powers push, email, and automation for our internal portfolio — including VedHoroscope (a daily-horoscope app where personalisation needs to read like it came from your astrologer, not a CRM), StumpScore (a cricket-scores site that has to push score updates within seconds of a wicket without hammering subscribers off the list), and OmegleCo. (a chat product whose re-engagement loops live entirely on push and email).
The e-commerce playbook above isn’t a hypothetical — it’s the same event-trigger-template-segment loop those products use, with merchandise events swapped in for scores or horoscopes. If a cricket site can push score updates inside 5 seconds of a boundary without burning its list, your “back in stock” alert can land in time too.
FAQ
Questions, answered.
Everything teams usually ask before switching. Something missing? Email us — a human replies.
Can ReachBell connect to my Shopify or WooCommerce store?
Yes — both platforms can fire ReachBell webhooks for cart, order, refund, and inventory events. For WooCommerce we also ship a WordPress plugin that wires up the events automatically; Shopify connects via a private app and a single webhook URL.
How do I keep cart-recovery messages from feeling spammy?
Use frequency caps per channel (e.g. max 2 marketing pushes per day) and combine them with quiet hours per project. ReachBell skips capped messages instead of failing them, so the audit log still shows what would have sent.
Can I personalize messages with order, product, or customer data?
Yes. Every send accepts a flat JSON payload, and templates use {{merge_tags}} like {{first_name}}, {{cart_item}}, or {{order_id}}. The same data is available across push, email, and WhatsApp templates so a single automation can branch by channel without rewriting copy.
What about back-in-stock alerts when I have a million SKUs?
Subscribers attach to a `product_id` tag rather than a separate list per SKU. When inventory crosses zero-to-positive, your stock service POSTs to ReachBell with the product id and we fan out to everyone who tagged it — no pre-creating campaigns per product.
Will this play nicely with my existing email tool?
It can — many stores keep their transactional sender (SES, Postmark) and use ReachBell only for push, WhatsApp, and marketing email. The transactional API mirrors common providers so you can move whichever flows you want, when you want.