<!-- apps/web/src/lib/services/agentic-chat/tools/skills/definitions/cold_email_engagement_first_outreach/references/public-mode-router.md -->

# Public Outreach Mode Router

Use this reference before drafting. Cold outreach quality depends on choosing one mode and making the required inputs explicit.

## Modes

| Mode                       | Use when                                                 | Required before drafting                                                   |
| -------------------------- | -------------------------------------------------------- | -------------------------------------------------------------------------- |
| High-volume offer test     | The goal is learning across a small, coherent segment.   | Persona x signal row, deliverability floor, one artifact-shaped offer.     |
| Strategic account          | The account is high value and reputation-sensitive.      | Specific research anchor, account context, role path, smallest useful yes. |
| Single-target relationship | The goal is to start a relationship, not run a campaign. | Real reason for this person, recent anchor, low-pressure ask.              |
| Investor                   | Fundraising or investor update outreach.                 | Thesis fit, portfolio/interest anchor, clear stage/context.                |
| Recruiting                 | Candidate or advisor outreach.                           | Role fit, why this person, useful context, respectful CTA.                 |
| PR / podcast               | Pitching a story, guest, or expert source.               | Editorial fit, timely hook, proof, low-friction next step.                 |
| Partnership                | Exploring collaboration.                                 | Mutual upside, concrete first experiment, no vague synergy language.       |
| Customer research          | Learning from a market or user segment.                  | Narrow segment, research question, non-sales ask.                          |

## Required Sequence

1. Choose exactly one mode.
2. Validate the right person and right moment.
3. Select one real reason to write now.
4. Shape the offer as a useful artifact or smallest useful yes.
5. Draft one CTA.
6. Plan follow-up and reply routing before sending.

## Child Skill Handoffs

- Use ICP and signal design when the target, persona, or timing signal is vague.
- Use offer lab when the ask is meeting-first or not useful enough.
- Use research anchors when a high-value recipient needs a stronger bridge.
- Use outreach compiler only when inputs are ready.
- Use taste review when a draft could damage sender reputation.
- Use deliverability readiness before scaled sending.
- Use reply OS after replies or silence.

## Output

Return a campaign bundle or a routing decision. If the inputs are weak, return the missing input and the child skill that should handle it instead of drafting.