Catch ATM cash outs before customers do
Every few minutes, WebRun checks Switch Commerce for terminals that are low on cash or already out, posts an alert to Slack with the terminal, location, and cash level, and adds a row to a Google Sheet log so repeat offenders are easy to spot.
- No credit card
- Under $0.01 per run
- Cancel anytime
How do I get alerted before an ATM runs out of cash?
WebRun checks Switch Commerce every few minutes for terminals that are low on cash or already in a cash out state. It posts an instant Slack alert naming the terminal, location, and remaining cash, tags the right driver, and logs the event to Google Sheets, so reloads go out before customers hit a dead machine.
- Cash out terminals get flagged within 15 minutes instead of a customer complaint
- The route driver or technician is tagged automatically so reloads move fast
- A running Google Sheets log shows exactly which terminals cash out the most
Built for independent ATM operators · ATM route drivers · ISO ATM deployers · cash management teams
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
switchcommerce.comin a real browser with your saved login - no setup, no API keys. -
1
Switch Commerce - watch terminal cash levels
WebRun opens Switch Commerce to watch terminal cash levels. - Open the Terminal Monitor in Switch Commerce and check the live cash level for every terminal on your routes
- Flag any terminal that has dropped below its low cash threshold or is already showing Cash Out status
- Capture the terminal ID, location name, and remaining cash for each one
Done when Every terminal below threshold or already cashed out has been identified with its location and cash level.
-
2
Slack - alert the team the moment one runs dry
WebRun opens Slack to alert the team the moment one runs dry. - Post an alert to the ops channel naming the terminal, location, and remaining cash
- Mark terminals already at Cash Out in red so they get worked first
- Tag the route driver or technician assigned to that location
Done when The team has a Slack alert for every low or cashed out terminal, with the right person tagged.
-
3
Google Sheets - log every cash out event
WebRun opens Google Sheets to log every cash out event. - Add a row to the cash out log with the date, terminal, location, and how long it sat empty
- Update the running count of cash out events per terminal
- Leave the sheet open for the team's weekly route review
Done when The cash out log has an entry for this event and an updated per terminal count.
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 fast will I know a terminal is out of cash?
Within minutes. WebRun checks Switch Commerce every 15 minutes and posts a Slack alert the moment a terminal drops below its threshold or shows Cash Out, so a reload can go out the same day.
Does it try to fix the cash out itself?
No. WebRun only alerts and logs the event. Loading cash into a terminal is a physical task, so it always stays with your route driver or technician.
Can I see which terminals cash out the most?
Yes. Every event is logged to Google Sheets with the terminal, location, and date, so patterns show up fast and you can move a route or raise a par level for repeat offenders.
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.