Route page
Route · AI outreach
Launch one personalized outreach sequence from qualified leads with a strict linear execution handoff.
Goal + expectation
Send one personalized outreach sequence that is measurable and compliance-safe.
Time estimate: 45–90 minutes to publish one sequence and queue first sends.
Execution priority
- Run one checklist loop end-to-end before branching scope.
- Capture one proof artifact and one measurable verification signal.
Readiness gate
Start this route only when these signals are true
- One qualified lead cohort is tagged and approved for outreach.
- Campaign objective and pilot thresholds are defined.
- Deliverability and compliance settings are validated before launch.
If not ready: Complete qualification first, then return and run this outreach route end-to-end.
Execution sequence
Run in order: action → output → verification
-
Campaign framing: Lock one audience segment, one objective, and one stop rule.
Output: Campaign brief with owner, guardrail, and target.
Verify: One upside metric and one risk metric are documented.
If blocked: Pause launch until these are explicit. -
Message build: Draft one baseline message and two controlled variants.
Output: Versioned message set for the same audience and objective.
Verify: Merge fields and fallbacks validate on sample records.
If blocked: Fix data quality before sending. -
Pilot launch: Launch one controlled batch and tag every response state.
Output: Pilot report with one winner candidate.
Verify: Reply quality and unsubscribe rate stay within guardrails.
If blocked: Stop scale and correct copy before next send.
Completion trigger: Route is complete when one pilot run produces state-tagged results and a confirmed handoff to follow-up.
Steps
- Lock one audience segment and one message objective.
- Draft baseline plus two controlled personalization variants.
- Set send windows, throttling, and follow-up cadence.
- Launch pilot batch with explicit stop rules.
- Move all non-responders to the follow-up route.
Tool choice
Use the outreach automation stack for setup, then complete follow-up handoff.
Recommended tools
AI sales outreach automation stack
Build sequence flow and delivery controls.
Run outreach stackChecklist
- Lock one campaign goal.
- Write one baseline message and two controlled variants.
- Validate merge fields and fallback text before first send.
- Launch pilot to a small batch before full rollout.
- Capture reply, positive intent, and unsubscribe rates daily.
Verification
Verify pilot performance beats baseline thresholds before increasing send volume.
Expected outcome
- A live outreach sequence with controlled risk.
- Response-state tags for every pilot contact.
- One confirmed next handoff to follow-up.
Next-action protocol
Prevent dead ends after route completion
- Move no-reply and soft-reply contacts into follow-up within 24 hours.
- Keep one active outreach lane until the day-14 decision is closed.
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: Complete follow-up route next — 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.