Abandoned cart, 20-minute delay
Still hungry, {{first_name}}?
Your order with {{cart_item}} is waiting. Free delivery if you check out in the next 30 minutes.
Industry
ReachBell for food & restaurants.
Confirm orders, push live delivery updates, run combo offers, reward loyal diners, and win back the ones who drifted — push, WhatsApp, SMS, and email from one place.
The problem
The food-ordering engagement tax.
One vendor for order SMS, another for app push, a third for the loyalty emails — and the weekend combo that needed to go out by Friday lunch slipped to Saturday night.
Most restaurant and food-delivery brands end up with a transactional SMS provider for order updates, a push tool for the app, and an email suite for offers and loyalty. Each has its own segmentation language, its own webhook contract, and its own definition of an “active customer”. A growth team can spend more time reconciling reports than running campaigns — and when a festival menu goes live, nobody is quite sure which list received which message.
The abandoned cart is the canonical example. The push provider knows a diner added biryani to the basket. The email tool knows the same person opened last week's offer. The SMS sender knows the order eventually came in. None of them know about each other, so the diner gets four near-duplicate nudges — or worse, a free-delivery code an hour after they already paid for delivery.
Order and delivery updates have the same shape: an event in your kitchen or rider app needs to reach the right diner on the channel they actually read — WhatsApp or SMS for a delivery ping, push for an in-app offer. When those live in separate systems, routing 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, WhatsApp, SMS, and email.
Order out for delivery
Order #{{order_id}} is on the way
{{rider_name}} is heading to you with your food — ETA {{eta}}. Track the rider live from your order.
Order status, kitchen accepted
{{restaurant_name}} is preparing your order
Your food is in the kitchen now. We'll ping you the moment it's out for delivery.
Combo offer, weekend window
Weekend combo: meal for two at ₹{{combo_price}}
Two mains, two sides, one dessert. Auto-applied at checkout this weekend only. No code needed.
Loyalty reward unlocked
You've earned a free {{reward_item}}
That's {{points}} points well spent, {{first_name}}. Redeem it on your next order before it expires.
Feedback request, 1 hour post-delivery
How was your meal?
Loved it, or something off? Rate your order in 10 seconds — your feedback goes straight to the kitchen.
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.
Abandoned-cart nudge (app)
Short, time-boxed sequence across push, WhatsApp, and SMS to bring hungry diners back before they pick another restaurant.
- 01Trigger: `cart.abandoned` webhook from your ordering app or website.
- 02Wait 20 minutes, then send mobile/web push: "Still hungry?" with a deep link back to the cart.
- 03If no tap after 1 hour, send WhatsApp template (opt-in only) with the cart contents and a free-delivery nudge.
- 04If still nothing by the next mealtime, send a single SMS reminder — capped so it never stacks with push.
- 05Exit the flow the moment an order is placed — webhook listens for `order.created`.
Order lifecycle updates
Keep diners informed from checkout to doorstep on the channel they actually read for time-sensitive updates.
- 01Trigger: `order.created` for a delivery or pickup order.
- 02Send "Order confirmed" instantly via WhatsApp or SMS (transactional, bypasses marketing throttle).
- 03On `order.accepted`, push "The kitchen is preparing your order" with the live status link.
- 04On `order.out_for_delivery`, send "Out for delivery" with the rider's ETA and live tracking.
- 05On `order.delivered`, wait 1 hour and send a feedback request — pickup orders get a "ready to collect" ping instead.
Win-back for lapsed diners
Re-engage customers who haven't ordered in 30 days with a tiered offer instead of letting them churn.
- 01Segment: last order > 30 days ago, opted in to marketing, lifetime value > ₹1,500.
- 02Send WhatsApp or email: "We miss you — here's 20% off your next order."
- 03Wait 4 days, then push: "Your 20% code expires tonight."
- 04If the code is redeemed, exit and tag the diner as `winback_won`.
- 05If not, drop the diner to a low-frequency weekly-offers 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 food & restaurants playbook above isn’t a hypothetical — it’s the same event-trigger-template-segment loop those products use, with order and delivery 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 “out for delivery” 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 ordering app or POS?
Yes — anything that can fire a webhook can drive ReachBell. Your app, website, or POS POSTs order, cart, and status events to a single webhook URL, and those events trigger flows. There's a REST API for custom stacks, so cloud kitchens and QSR chains on bespoke systems wire up the same way.
Which channel should order updates go on — push, WhatsApp, or SMS?
For time-sensitive order and delivery updates, WhatsApp and SMS reach diners who don't have your app open, while web and mobile push are ideal for in-app re-engagement and offers. ReachBell lets a single automation branch by channel, so "out for delivery" can go to WhatsApp while a combo promo goes to push — without rewriting the copy.
Can I personalize messages with order, rider, or loyalty data?
Yes. Every send accepts a flat JSON payload, and templates use {{merge_tags}} like {{first_name}}, {{order_id}}, {{rider_name}}, or {{points}}. The same data is available across push, WhatsApp, SMS, and email templates, so one flow can reuse it across channels.
How do I keep offers and promos from feeling spammy?
Use frequency caps per channel (e.g. max 2 marketing pushes per day) combined with quiet hours per project, so a late-night promo never wakes a diner. ReachBell skips capped messages instead of failing them, so the audit log still shows what would have sent.
Is this compliant with consent rules in India?
ReachBell is built India-first and DPDP-aware: marketing sends require opt-in, every contact gets a preference center to choose channels and frequency, and STOP/unsubscribe is honored automatically. Transactional order updates stay separate from marketing so essential delivery messages always go through.