Catch slow kitchen tickets in Sapaad before guests complain
Throughout service, WebRun checks Sapaad's kitchen display system every few minutes for any open ticket that has passed your configured fire-to-serve time limit, and sends the shift manager a WhatsApp alert naming the ticket, table, and how far over time it is, so slow orders get chased while the table is still waiting.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted when a Sapaad kitchen ticket is running late?
WebRun checks Sapaad's kitchen display system every few minutes during service, flags any ticket that has passed your fire-to-serve time limit, and sends the shift manager a WhatsApp alert naming the table and items still outstanding, so a slow ticket gets chased while the table is still waiting instead of after a complaint.
- Slow tickets get chased while the table is still waiting, not after a complaint
- Shift managers get one alert per stuck ticket instead of a flood of repeats
- Fire-to-serve limits are enforced automatically per station
Built for kitchen managers · shift managers · QSR operators · multi-outlet restaurant groups
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 KDS ticket times
WebRun opens Sapaad to watch KDS ticket times. - Check the Sapaad kitchen display system for every open ticket
- Compare each ticket's time since fired against your configured limit per station
- Flag any ticket that has passed the limit and note the table and items still outstanding
Done when Every ticket over the fire-to-serve time limit is identified with its table and items.
-
2
WhatsApp - alert the shift manager
WebRun opens WhatsApp to alert the shift manager. - Send the shift manager a message naming the ticket, table, and minutes over time
- Repeat the alert only if the ticket is still open on the next check
- Stop alerting once the ticket is marked served or bumped in Sapaad
Done when The shift manager has been alerted on WhatsApp while the ticket is still open.
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
How do I set the time limit for a delay?
You set a fire-to-serve minute limit per station, such as the grill or the fryer, during setup. WebRun only alerts on tickets that pass that limit in Sapaad.
Will it keep messaging about the same ticket over and over?
It re-checks every few minutes but only sends a new alert if the ticket is still open, so you get one alert per still-stuck ticket instead of a flood of repeats.
Does it only work during set service hours?
Yes. You set the service hours to monitor, such as lunch and dinner service, and it only watches Sapaad's kitchen display during those windows.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.