Cantaloupe alerts and remote diagnostics

Configure alert thresholds for stockouts, temperature deviations, payment declines, and door-open events. Route alerts to email or SMS and test each rule with a known event.

Use remote diagnostics to check reader status, last transaction time, and machine communication. Build a response playbook so urgent alerts trigger the right service action.

• Verify alert rules are enabled and assigned to the correct devices.
• Test notification routing to all team members.
• Review alert history to detect repeat issues.

• Confirm reader status is online and last transaction is current.
• Perform a test vend after changing alert rules.
• Adjust thresholds based on location traffic.

• Provide alert ID, device ID, and timestamp.
• Share the action taken and outcome for recordkeeping.
• Note any recurring alerts that require hardware replacement.

• Confirm all steps are documented so the next technician can reproduce the results.
• Capture before/after metrics (errors cleared, sales restored, or uptime improved).
• Review machine, reader, or route settings to ensure they match location standards.

• Skipping a controlled test leads to false positives.
• Updating hardware without documenting configuration changes.
• Forgetting to verify payout, refund, or reconciliation data after changes.

• Run a final test with known-good inputs.
• Log the outcome with date, time, and device identifiers.
• Schedule a follow-up check if the location has high traffic or seasonal demand.

<!-- expanded:v2 -->

• Document changes with time, machine ID, and location name.
• Verify settings, pricing, and service modes after each fix.
• Capture before/after results to confirm resolution.

• Test with known-good inputs and controlled conditions.
• Validate telemetry, alerts, and payment logs where applicable.
• Confirm location expectations and update the site contact.

• Configuration drift after firmware or component swaps.
• Inconsistent power or network conditions at the location.
• Gaps in preventive maintenance routines.

• Monitor for 7 days and note any repeat errors.
• Schedule follow-up if the site is high-traffic.
• Escalate with full logs and photos if issues repeat.

• Verify the reader is paired to the correct machine ID.
• Confirm MoMa configuration and device firmware are current.

• Ensure alert thresholds align to route service windows.