Route page
Route · Multichannel follow-up (canonical)
Run one follow-up cycle across email + LinkedIn + CRM tasks with state-based decisions.
Goal + expectation
Canonical execution route for recovering stalled opportunities using one state-driven multichannel follow-up cycle.
Time estimate: 45 minutes setup + 14-day execution window.
Execution priority
- Run one checklist loop end-to-end before branching scope.
- Capture one proof artifact and one measurable verification signal.
Steps
- [object Object]
- Assign one message lane per state and channel.
- Launch cadence with fixed stop rules and owner.
- Review state movement on day 3 and day 7.
- Keep, refine, or retire on day 14 with documented decision.
Tool choice
Use follow-up framework by default, then compare only if channel stack remains blocked.
Recommended tools
Follow-up sequence automation framework
Use this to structure cadence and state transitions.
Open follow-up frameworkFollow-up without being annoying
Use this for message tone and cadence quality control.
Open messaging guideBest AI tools for multichannel follow-up
Use compare page when channel/tool lane is still unclear.
Open compareChecklist
- Every contact has one dominant state and owner.
- Channel order (email, LinkedIn, call task) is fixed before launch.
- Stop rules are defined and enforced.
- Day-14 keep/refine/retire checkpoint is scheduled.
Verification
Verify state movement is logged by channel and day-14 decision is documented.
Expected outcome
- One repeatable multichannel follow-up motion with owner accountability.
- Higher response recovery on stalled leads.
- Clear keep/refine/retire decision after one cycle.
Evidence instrumentation
Evidence packet and verification
Define the output packet, verify the checkpoint, and record one measurable signal before moving forward.
Checkpoint cadence: Capture baseline before execution, then verify at day-1 and day-7 checkpoints.
Handoff rule: Do not switch tools/routes until one verified packet is saved.
Decision support
Choose your next action
- Why this option: Each option maps to how quickly you need results and how much guidance you want during execution.
- For whom: Teams deciding between direct execution and compare-first self-serve paths.
- When to choose: Pick before step 1 so checklist decisions stay consistent across the route.
- What to do next: Select one path, complete this checklist once, then move to the next route.
Route handoff
Choose the next move while this output is fresh
- Primary next step: Route · Generative lead generation — continue the cluster loop with the packet from this route.
- Secondary fallback: Use this if blockers appear and you need to re-check bottleneck priority.