Skip to main content

Follow-up cadence

Follow-up fails when the team remembers a conversation but not the promise made inside it. A cadence is the operating rule that turns follow-up from effort into accountable work: every active lead has one owner, one current stage, one dated next action, and a stop rule.

The minimum operating rule​

For every active lead:

  • One owner — a named person accountable for the next step, with a fallback for absence.
  • One current stage — the pipeline stage that describes verified customer progress.
  • One dated next action — what will happen, by whom, and by when.
  • One stop rule — when the cadence ends: closed, lost with a factual reason, or waiting on the customer with a re-engagement date.

A practical cadence​

The cadence below is a starting point. Adjust intervals to your sales cycle, but keep the sequence — acknowledge, understand, commit, act, close the loop — fixed.

  1. Acknowledge (same day) — confirm receipt and set an honest expectation for the next useful response.
  2. Understand (day 1–2) — record the requirement, timing, constraints, and unanswered question in plain language.
  3. Commit (day 1–2) — choose the next action, owner, channel, and due date. Store them on the record.
  4. Act (by the due date) — send information or complete the promised task with enough context for the customer.
  5. Close the loop — record the outcome; reschedule with a reason, or close the lead with a factual disposition.

Cadence rules worth enforcing​

  • Attempts and responses are different. Log an attempted contact separately from a customer response; a "no reply" is not a response.
  • No-response has a stop rule. Do not send an infinite reminder sequence. Define how many attempts, then close or park with a re-engagement date.
  • Consent governs the channel. Follow the customer's channel preference and consent. Do not infer consent from a stored contact.
  • Escalation identifies a decision. Escalate by naming the decision needed and its owner, not by forwarding the thread.

Weekly review​

A fixed weekly review keeps the cadence honest. Inspect:

  • Overdue next actions — who owns them and why they slipped.
  • Unowned leads — records with no owner for more than one day.
  • Stalled stages — records sitting in a stage past its maximum review age.
  • Closed leads — are the lost reasons factual and useful?
  • Re-engagement dates — what comes back into the queue this week?

Where NoxCRM fits​

NoxCRM provides the product surface for this cadence: records with owners, stages, tasks, reminders, and follow-up scheduling. It does not replace the operating rule — configuration does not create accountability. A cadence works when the team consistently updates the record and reviews overdue work. See the capability inventory for current availability, and Getting started for setup.