Sourcing Outreach Copy
Create role-accurate outreach messages, channel variants, and approved employer brand copy.
Before you start
What you’ll need
- Approved Role Requirements Brief from HR01
- Access to reviewed employer-brand language for candidate-facing claims
- Employer Brand Guidelines
- Candidate Cohort Notes
- Reviewer Feedback
Who’s involved
- Sourcer — Drafts outreach variants, adds recruiter-owned personalization placeholders, and owns the final send-ready message pack.
- Employer Brand Owner — Reviews outreach copy for approved voice, claim accuracy, and external-safe employer-brand language.
Safe use
- Data Handling — This workflow processes internal role context, team plans, compensation references, and candidate cohort notes. Do not paste confidential headcount details, replacement context, or identifiable candidate data into public or unapproved GenAI tools.
- Verification — GenAI may invent role benefits, seniority signals, flexibility, or candidate-fit claims. The sourcer and employer brand owner must verify every message against approved source material before sending.
Execution steps
Inputs
- Role Requirements BriefdownloadFrom HR01 — JD Builder
- Confirm the Role Requirements Brief is approved
- Remove confidential headcount or replacement context before prompting
- Check that must-have criteria are final
Data Handling: Abstract internal team needs, replacement context, and compensation references before prompting.
Prompt
Draft role-accurate outreach variants
CONTEXT You will be provided with an approved Role Requirements Brief for one open role. The brief contains role scope, must-have criteria, team context, and any internal notes already cleared for drafting. TASK Generate Draft Outreach Messages that translate the role truth into candidate-facing copy. Produce distinct first-pass variants without changing the underlying facts. OUTPUT FORMAT Use markdown with these sections: - LinkedIn InMail - Warm Prospect Email - Social Post For each section, include a subject or hook, message body, and one recruiter-owned personalization placeholder. EXAMPLE Personalization placeholder: [Add one observed, work-relevant reason this role may be relevant to the candidate.] CONSTRAINTS Do not invent responsibilities, benefits, flexibility, compensation, or growth claims. Only use externally safe facts from the Role Requirements Brief. Do not include confidential headcount, replacement, or internal business context.
Outputs
- Draft Outreach Messages
Verification: Verify that the drafts preserve role scope and exclude unsupported benefits or flexibility claims.
Locked — get full access to view the inputs, prompt, and outputs.
Locked — get full access to view the inputs, prompt, and outputs.
Locked — get full access to view the inputs, prompt, and outputs.
Locked — get full access to view the inputs, prompt, and outputs.
Locked — get full access to view the inputs, prompt, and outputs.
Reference
Guardrails
- Role Truth First — Ground every outreach claim in the approved Role Requirements Brief before adapting tone or channel.
- Placeholders Stay Visible — Keep candidate-specific personalization as explicit placeholders until the sourcer verifies the observation.
- Approved Claims Only — Use employer-brand proof points only when they appear in reviewed guidelines or approved role materials.
Pitfalls
- Letting GenAI turn cohort-level patterns into unsupported claims about an individual candidate.
- Using polished but generic recruiting language that does not explain why the role is relevant.
- Allowing channel edits to introduce benefits, flexibility, or seniority promises not present in the source material.
- Pasting confidential replacement context or headcount plans into an unapproved GenAI tool.
Definition of Done
- The Channel-Specific Outreach Variants adapt the same approved role facts for InMail, email, social, and follow-up use.
- The Approved Brand Variants use only reviewed employer-brand claims and remove vague recruiting language.
- The Personalized Cohort Variants keep recruiter-owned observations in explicit placeholder form.
- The Final Outreach Messages are approved by the sourcer and employer brand owner before use.
GET FULL ACCESS
Unlock every step, prompt, and downloadable example — for this playbook and the rest of AGASI AiOS, our GenAI capability framework.
We'll send a magic link — no password needed.
AGASI AiOS · HR02 v1.1 · May 6, 2026