Alerts and uptime
Each alert names the machine, the route, how long it has been open, and what it is costing you every week. The list sorts itself into your route.
needs action
26
across 26 machines
at stake
$110
per week, if nothing changes
cleared themselves
65 of 65
100%, last 7 days
MCH-155 · Thunderbird Molding #1 NOT REPORTING
75d with no report
Thursday Route · first occurrence in 90d · machine
$0
weekly sales unseen
resolveset aside
MCH-293 · Duravend 5C NOT REPORTING
under an hour with no report
Default Route · first occurrence in 90d · machine
—
not priced
resolveset aside
An alert reads the state the machine is already in. When the machine changes state, that is the alert. There are no thresholds to set or maintain.
Alerts are ordered by dollars at stake per week. A machine with no sales to lose drops down the list, however old its alert is.
Resolve an alert or set it aside. Every alert stays on the record, with what cleared itself and the median time to clear.
Know what it costs before you drive.
Alerts are ordered by dollars at stake per week, not by time. Each one names the machine, the route, how long it has been open, and what it is costing. Resolve it or set it aside.
Questions operators ask
Questions
No. Alerts follow the status VendGogh already gives each machine, so a machine changing state is the alert. There is no threshold list to set up, and no one runs on someone else’s defaults.
Not reporting, inventory depletion, cashless flat, and firmware drift.
By the dollars at stake per week on each one, not by when it opened. The top of the list is the stop that costs you most to skip.
You resolve it or set it aside. Either way it stays on the record, and VendGogh tracks which alerts cleared themselves and the median time to clear.
Book a demo