← Back to Help Center
Help Center

5-email lead sequence

Run a short sequence for cold leads.

Updated Feb 9, 2026

Overview

Email sequences work when the subject is clear and the body is skimmable with a single ask. Run a short sequence for cold leads.

Diagnostics

  • Validate the email address and role.
  • Confirm the location type is a good fit.
  • Review any existing vending provider info.

Resolution steps

  • Send a 3–5 email sequence with clear CTAs.
  • Include a one-page PDF or short bullet list.
  • Ask for a 10-minute call or quick walk-through.

Preventive maintenance

  • Personalize the first line with location context.
  • Avoid attachments if deliverability is poor.
  • Use consistent follow-up spacing.

When to contact support

  • Move to phone outreach after two opens without reply.
  • Ask for the correct contact if you have the wrong person.
  • Offer a short on-site demo.

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.
emailsequencefollow-up