← Back to Help Center
Help Center
Budget and commission fit
Confirm financial alignment.
Updated Feb 9, 2026
Overview
Qualification prevents wasted time by confirming traffic, decision authority, and fit. Confirm financial alignment.
Diagnostics
- Confirm headcount or daily traffic.
- Verify decision-maker availability.
- Check space, power, and placement constraints.
Resolution steps
- Use a 3–5 question pre-qual checklist.
- Schedule a site walk if qualified.
- Decline low-fit locations politely.
Preventive maintenance
- Define a minimum traffic threshold.
- Use a consistent scoring method.
- Capture notes for future follow-up.
When to contact support
- Request a pilot if traffic is uncertain.
- Ask for a 60-day sales review instead of a long contract.
- Offer a smaller footprint unit.
See packages and pricing at /pricing. Start with leads at /vending-leads or /hot-leads.
Expanded guidance
- 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.
Common pitfalls
- Skipping a controlled test leads to false positives.
- Updating hardware without documenting configuration changes.
- Forgetting to verify payout, refund, or reconciliation data after changes.
Next-step checklist
- 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 -->
Additional details
Operational notes
- 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.
Field checklist
- Test with known-good inputs and controlled conditions.
- Validate telemetry, alerts, and payment logs where applicable.
- Confirm location expectations and update the site contact.
Common root causes
- Configuration drift after firmware or component swaps.
- Inconsistent power or network conditions at the location.
- Gaps in preventive maintenance routines.
Next steps
- 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.
qualificationscoringpipelinebudget