← Back to Help Center
Help Center

Getting past the gatekeeper

Reach the right decision maker.

Updated Feb 9, 2026

Overview

Phone calls convert best when your opener is concise and you lead with a clear benefit to the location. Reach the right decision maker.

Diagnostics

  • Confirm you reached the decision maker.
  • Identify current vending provider and pain points.
  • Note best call times by industry.

Resolution steps

  • Use a 20-second opener and request a quick evaluation.
  • Offer to send a one-page summary before a visit.
  • Set a firm follow-up time if they are busy.

Preventive maintenance

  • Call at consistent windows each week.
  • Rotate scripts to avoid sounding scripted.
  • Log call outcomes and objections.

When to contact support

  • Switch to email + voicemail combo after 2–3 attempts.
  • Request referral to facilities or HR.
  • Offer a short trial placement.

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