Automated ATM Dispenser Fault Escalations
Every few minutes, WebRun checks Switch Commerce for terminals reporting a dispenser fault, a jam, or a failed note count, pings the on-call technician on Telegram with the fault code and location, and creates an Asana task so the fix gets tracked to close.
How do I escalate ATM dispenser faults to a technician right away?
WebRun checks Switch Commerce every few minutes for terminals reporting a dispenser fault, a jam, or a failed note count. It pings the on-call technician on Telegram with the terminal, location, and fault code, then creates an Asana task assigned and due today, so the fix starts before the next scheduled route.
- A dispenser fault reaches the on-call technician within 10 minutes, not the next scheduled visit
- Every fault gets a tracked Asana task instead of a message that scrolls past unnoticed
- Duplicate tasks are skipped so the technician's board only shows unresolved faults
Built for independent ATM operators · ATM service technicians · ISO ATM deployers · field service 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 - detect dispenser fault codes
switchcommerce.com
WebRun opens Switch Commerce to detect dispenser fault codes. - Open the Terminal Monitor in Switch Commerce and check for any new dispenser fault code, jam, or failed note count
- Capture the terminal ID, location, and the exact fault code reported
- Skip any fault that already has an open Asana task from a prior run
Done when Every new dispenser fault is identified with its terminal, location, and fault code.
-
2
Telegram - ping the on-call technician
telegram.org
WebRun opens Telegram to ping the on-call technician. - Message the on-call technician for that route with the terminal, location, and fault code
- Include how long the terminal has been unable to dispense since the fault started
- Ask the technician to confirm they are heading to the location
Done when The on-call technician has been pinged on Telegram for every new dispenser fault.
-
3
Asana - create a tracked fault task
- Create a task titled with the terminal ID and fault code, assigned to the on-call technician
- Add the location, fault details, and time reported to the task description
- Set the due date to today so it shows on the technician's board
Done when An Asana task exists for every new dispenser fault, assigned and due today.
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
What counts as a dispenser fault?
Any fault code Switch Commerce reports for the note dispenser, such as a jam, a failed note count, or a reject bin that needs clearing. It's a hardware fault while the terminal is otherwise online, not the same as the terminal going offline.
Will it create a duplicate task if the same fault keeps reporting?
No. It checks for an already open Asana task for that terminal and fault before creating a new one, so the technician's board doesn't fill up with repeats of the same unresolved issue.
Does it try to reset or clear the fault remotely?
No. WebRun only alerts and tracks the fault, it never sends a remote command to a terminal. Clearing a dispenser jam is a physical fix that stays with your technician.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.