Establish relevance
Explain why a conversation makes sense before drafting a message.
OUTREACH-06 / OUTREACH AGENT
An AI outreach agent.
Relevance before volume.
A future specialist for researched outreach drafts and reviewable follow-up workflows.
THE MISSION
Outreach Agent.
A defined role.
Outreach is part of the wider agent-team idea, not the first SEO release. The proposed starting point is assisted drafting with strict controls, not autonomous mass sending.
Draft from real context
Use approved material and avoid invented familiarity, proof, or customer results.
Keep sending separate
Treat recipient approval and permission to send as distinct decisions.
INPUTS
What it needs.
- An approved audience and contact source
- Relevant offer and message boundaries
- Exclusions and follow-up rules
OUTPUTS
What comes back.
- Reviewable message drafts
- A reason for each proposed conversation
- A bounded follow-up plan
THE BOUNDARY
Permission is
part of the brief.
No automatic mass sending, unauthorized contact harvesting, or bypassing recipient preferences. Recipient review and sending controls need implementation before launch.
Read the control model →START SMALL. BUILD FROM THERE.
Put a specialist
on the right problem.
Share the first job you would give this agent. The initial scope should be small enough to review and useful enough to matter.
BEFORE THE FIRST WORKFLOW
Questions worth
asking first.
Will the Outreach Agent send messages without approval?
The roadmap does not give an agent unrestricted sending permission. Research and drafts should be reviewed, with separate approval for access to contact data and any sending workflow.
Is automated outreach available on this website?
No. This is a description of a roadmap role. The website has no live outreach integration, sending service, or customer campaign dashboard.