Catch no-show online orders in Sapaad before food goes cold
During delivery hours, WebRun checks Sapaad every few minutes for online or aggregator orders marked ready for pickup that have sat uncollected past your configured time limit, and texts the branch manager the order number, platform, and minutes waiting, so a stuck order gets actioned while it is still fresh.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted to no-show online orders in Sapaad?
WebRun checks Sapaad every few minutes during delivery hours for online and aggregator orders sitting ready but uncollected past your configured wait limit, and texts the branch manager the order number, platform, and minutes waiting, so a stuck order gets remade or re-fired while it is still fresh instead of going out cold.
- Stuck orders get actioned while still fresh instead of going out cold
- Branch managers get one text per stuck order, not a flood of repeats
- Every connected delivery platform is covered by the same alert
Built for branch managers · QSR operators · delivery-heavy restaurant brands · multi-outlet restaurant operators
What does WebRun do on every run?
The exact actions WebRun takes, in order - in plain language, so you can adjust anything.
-
WebRun signs in and gets to work
Opens
www.sapaad.comin a real browser with your saved login - no setup, no API keys. -
1
Sapaad - watch for uncollected ready orders
sapaad.com How to Automate Sapaad
WebRun opens Sapaad to watch for uncollected ready orders. - Check Sapaad for online and aggregator orders marked ready for pickup
- Compare each order's ready timestamp against your configured wait limit
- Flag any order still uncollected past the limit, noting the platform and order number
Done when Every ready order that has passed the wait limit is identified with its platform and order number.
-
2
Twilio - text the branch manager
twilio.com How to Automate Twilio
WebRun opens Twilio to text the branch manager. - Send the branch manager a text naming the order number, platform, and minutes waiting
- Recheck and stop alerting once the order is marked collected in Sapaad
- Leave the decision to remake, re-fire, or cancel the order to the manager
Done when The branch manager has been texted about the stuck order while it is still fresh.
How is each run configured?
Secure by default
Connect once, stays signed in
WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.
Every action is checked against this policy before it runs.
Questions, answered
Does it cancel or remake the order automatically?
No. It only texts the branch manager once an order has sat uncollected past your wait limit. Whether to remake, re-fire, or cancel the order is the manager's call.
How long does an order have to wait before it counts as a no-show?
You set the wait limit in minutes during setup, based on how long food can sit before quality drops for your menu. WebRun only alerts once Sapaad shows an order past that limit.
Does it work across every delivery platform connected to Sapaad?
Yes. It watches every online and aggregator order flowing into Sapaad, whichever delivery platforms you have connected, and names the platform in the alert.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.