Automated Sapaad Table Turnover Report
Every night after close, WebRun opens Sapaad, reads the dine-in table history for the shift, calculates average seating-to-bill time and covers per table by section, and texts your floor manager's phone a short turnover summary with the slowest section flagged.
How do I track table turnover time from Sapaad automatically?
WebRun reads your Sapaad dine-in table history every night after close, calculates average seating-to-bill turnover time and covers served by section, and texts your floor manager a short summary with the slowest section flagged, so seating and staffing adjustments happen before tomorrow's service instead of after a slow week.
- Slow sections get flagged the same night, not weeks later
- Floor managers start each shift knowing where yesterday's bottleneck was
- Covers and turnover time are tracked without a manual stopwatch or spreadsheet
Built for restaurant floor managers · dine-in restaurant owners · casual dining 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 - read the shift's table history
WebRun opens Sapaad to read the shift's table history. - Open Sapaad and pull the dine-in table history for the shift just closed
- Calculate average seating-to-bill time and covers served for each table and section
- Identify the section with the longest average turnover time
Done when Average turnover time and covers are calculated for every section from tonight's shift.
-
2
Twilio - text the floor manager a summary
WebRun opens Twilio to text the floor manager a summary. - Format a short text with average turnover time, total covers, and the slowest section
- Send the text to your floor manager's phone number on file
- Leave any staffing or seating-plan changes for the manager to decide
Done when Your floor manager has tonight's turnover summary by text.
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 does it measure turnover time?
It reads the seating and bill-closed timestamps Sapaad logs for each dine-in table, then averages the seating-to-bill time per table and per section for the shift just closed.
Who receives the text message?
Whichever floor manager number you set up during onboarding. You can list more than one number and every one gets the same nightly summary.
Does it flag individual slow tables or just sections?
It reports the average by section so patterns are visible at a glance, and it calls out the single slowest section by name so you know where to look first.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.