365 Retail Markets Automated Kiosk Offline Alerts
Every hour, WebRun checks 365 Retail Markets ADM for any kiosk that has gone offline, stopped processing transactions, or shown a connectivity error, then immediately alerts the operations team in Telegram with the location name and last known status, and logs the incident to Google Sheets for uptime tracking.
How do I get instant alerts when a micro market kiosk goes offline?
WebRun checks every kiosk's connectivity and sales status in 365 Retail Markets ADM each hour, detects any unit that has gone offline or stopped processing transactions during operating hours, sends an instant alert to the operations team in Telegram, and logs each incident to Google Sheets so downtime is tracked and patterns are visible across the fleet.
- Offline kiosks are detected and reported within 60 minutes, limiting lost sales per incident
- A Google Sheets downtime log tracks incident duration and recurring problem locations
- False alerts for planned off-hours closures are filtered out automatically
Built for micro market operators · unattended retail operations teams · route supervisors · vending and market technicians
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
adm.365retailmarkets.comin a real browser with your saved login - no setup, no API keys. -
1
365 Retail Markets - check kiosk uptime and connectivity status
365retailmarkets.com
WebRun opens 365 Retail Markets to check kiosk uptime and connectivity status. - Open ADM and check the kiosk status dashboard for all active locations
- Identify any kiosk showing offline, connectivity error, or no transactions processed in the last 90 minutes during expected operating hours
- Record the location name, kiosk ID, last transaction time, and error status for each affected unit
- Skip locations that are outside their configured operating hours to avoid false alerts
Done when Any kiosk that is offline or has stopped selling during operating hours is identified with its location and status details.
-
2
Google Sheets - log offline incidents and time-to-alert
google.com
WebRun opens Google Sheets to log offline incidents and time-to-alert. - Log each offline incident with the location, kiosk ID, detection time, and error status
- Record when the kiosk came back online in a follow-up column once ADM shows it recovered
- Calculate downtime duration for each incident to track patterns by location
Done when The Google Sheets uptime log has a new row for each offline incident with detection time and location details.
-
3
Telegram - send instant alert to operations team
telegram.org
WebRun opens Telegram to send instant alert to operations team. - Send an immediate alert to the operations group with the location name, kiosk ID, and time offline
- Include the last known transaction time so the team can estimate how long the kiosk has been down
- Send a follow-up message when ADM shows the kiosk has come back online
Done when The operations team has a Telegram alert for every offline kiosk within one check cycle.
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 quickly will the team know when a kiosk goes offline?
WebRun checks ADM every hour, so the team receives an alert within 60 minutes of a kiosk going offline during operating hours. You can increase the check frequency to 30 minutes if faster detection is needed.
Will it alert for locations that are closed overnight?
No. WebRun skips locations outside their configured operating hours so the team is not woken up by expected off-hours downtime. Alerts only fire when a kiosk goes dark during a period when it should be selling.
Does it try to reboot the kiosk automatically?
No. WebRun surfaces the alert so a technician can investigate and use ADM's remote reboot feature if appropriate. Automated reboots are left as a deliberate human action to avoid disrupting a transaction in progress.
Related templates
Put this on autopilot.
Turn it on in minutes - or have our team set it up for you.