Follow-up site visit request

Follow-up drives most conversions and should be scheduled, not random. Convert interest into a site walk.

• Confirm last contact attempt and response.
• Check preferred contact method.
• Review any promised next steps.

• Use a 3-2-1 follow-up cadence (3 days, 2 weeks, 1 month).
• Send a short summary of benefits.
• Ask for a simple yes/no response.

• Use reminders and templates in your CRM.
• Avoid over-contacting in a short window.
• Track open and reply rates.

• Switch channels after 2–3 no-responses.
• Offer a specific time window for a call.
• Pause and re-engage next quarter.

See packages and pricing at /pricing. Start with leads at /vending-leads or /hot-leads.

• 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.