Automated Car Wash Downtime Alerts
Every hour, WebRun checks your wash count tracking sheet in Google Sheets for any tunnel or site that has logged zero washes during a window when cars should be coming through, then immediately posts a downtime alert to Slack for management and to Telegram for on-site staff so the issue can be investigated and resolved fast.
How do I get automatic alerts when a car wash site goes down?
WebRun checks your Google Sheets wash count data every hour and flags any tunnel or site that records zero washes during normal operating hours. It sends an immediate alert to Slack for management and to Telegram for on-site staff, naming the affected tunnel and the duration of the outage window so your team can investigate and restore service fast.
- Site and tunnel outages are caught within one hour, limiting revenue loss
- On-site staff are alerted via Telegram so they can investigate immediately
- Extended outages escalate automatically to ops leadership without manual follow-up
Built for car wash operators · multi-site owners · operations managers
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
sheets.google.comin a real browser with your saved login - no setup, no API keys. -
1
Google Sheets - check wash counts for zero-activity windows
google.com
WebRun opens Google Sheets to check wash counts for zero-activity windows. - Open the wash count tracking Google Sheet and read the most recent hourly count for each tunnel and site
- Check whether the current time falls within expected operating hours for each location
- Flag any tunnel or site showing zero washes for the past hour during normal operating hours
- Record the alert time and location in the sheet for downtime history tracking
Done when Any site or tunnel with a suspicious zero-count window is flagged and logged.
-
2
Slack - alert management immediately
slack.com
WebRun opens Slack to alert management immediately. - Post an immediate downtime alert to the management Slack channel naming the affected site and tunnel
- Include the duration of the zero-count window and the last recorded wash time
- Escalate to the ops leadership channel if the outage window exceeds 30 minutes
Done when Management has a Slack alert with the affected site, tunnel, and duration of the outage window.
-
3
Telegram - ping on-site staff
telegram.org
WebRun opens Telegram to ping on-site staff. - Send a concise downtime alert to the on-site Telegram group for the affected location
- Keep the message short enough to read on a phone in seconds
- Include the tunnel name and the start time of the zero-count window so staff can investigate immediately
Done when On-site staff have the downtime alert on Telegram and can begin investigating.
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 know when a zero count is actually a problem versus a slow period?
WebRun only flags zero-count windows that fall within your defined operating hours. Slow periods during expected lulls can be excluded by narrowing the monitoring window in your Google Sheet settings.
Can it monitor multiple tunnels at one site separately?
Yes. WebRun reads each tunnel's count as a separate row in your sheet and sends a tunnel-specific alert, so you know exactly which piece of equipment stopped processing cars rather than just the site overall.
Will it keep alerting every hour if a site stays down?
WebRun sends an initial alert and then escalates to the ops leadership Slack channel if the outage extends beyond 30 minutes, but does not flood every channel with repeated identical alerts during the same incident.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.