Follow-up sequence framework (support page for the canonical route)

Problem this page solves in the route

Inside the canonical route (/hubs/ai-for-sales/multichannel-follow-up/), teams often know they should follow up but do not have a clean state-based cadence. That causes over-sending on no-reply leads and under-handling of objection leads.

Direct answer

Use this page after you choose the canonical multichannel follow-up route to structure one 14-day cadence by state:

• No-reply: persistence with controlled spacing and low-friction asks.
• Soft-reply: clarification and commitment nudges.
• Objection: focused response + proof + escalation trigger.

This page is not a separate route. It is the cadence structure layer for the canonical route.

One concrete next action

Pick 10 stalled leads from your current pipeline and assign each lead to exactly one state (no-reply, soft-reply, objection) before writing any message.

Useful insight

Cadence quality comes more from state transitions than message volume. If a lead changes state, the lane must change too; if state does not change, repeating a stronger version of the same message usually reduces response quality.

14-day support structure (inside canonical route)

State 1 — No-reply lane

• Day 0: original message with one clear value point.
• Day 2–3: short follow-up with one new detail (proof, example, or result).
• Day 6–7: channel change (LinkedIn or call task) with a smaller ask.
• Day 10–14: close-the-loop message with respectful opt-out.

State 2 — Soft-reply lane

• Trigger: replies like “maybe later,” “send details,” “busy this week.”
• Response pattern: confirm context, reduce decision friction, propose one concrete next step.
• Timing: keep cadence active, but switch from reminder language to decision language.

State 3 — Objection lane

• Trigger: explicit pushback (price, timing, fit, trust).
• Response pattern: acknowledge objection, answer directly, add proof, request one next decision.
• Escalation: if objection repeats twice, use the objection support page: /posts/2026-03-18-sales-objection-library/.

Stop rules (must stay active)

Stop or pause the sequence if:

• explicit “no” is given,
• no valid channel remains,
• the opportunity is clearly out of ICP,
• compliance or deliverability risk appears.

Related canonical pages

• Canonical route: /hubs/ai-for-sales/multichannel-follow-up/
• Messaging-quality support: /posts/2026-03-12-follow-up-without-being-annoying/
• Objection-state support: /posts/2026-03-18-sales-objection-library/
• Compare (only if stack is blocked): /compare/best-ai-tools-for-multichannel-follow-up/