Outreach Readiness System: Decide When a Candidate Is Ready to Contact
Do not confuse “found a candidate” with “safe and useful to contact.”
Last reviewed: 2026-09-06
Ask SourcingOS about this page
Inputs
- Candidate evidence dossier
- Identity confidence
- Resolved contact observations
- Prior recruiting/candidate state
- Role-specific verification needs
- Outreach authorization/policy
1. Confirm candidate identity
Do not send outreach against ambiguous identity records or contact values that may belong to another person.
2. Confirm minimum role evidence
Require enough role-relevant evidence to justify why the candidate is being contacted. Missing noncritical evidence can become a conversation question; missing hard requirements should remain visible.
3. Resolve the contact channel
Use the strongest appropriate channel with verification, freshness, provider/source context, and prior bad-outcome suppression.
4. Check state and suppression rules
Review recent contact, prior declines, do-not-contact/opt-out state, duplicate campaigns, recruiter ownership, and other workflow rules before queuing outreach.
5. Keep the send boundary explicit
AI can draft and prioritize, but the actual send should follow the configured human-approval and authorization boundary rather than being triggered by candidate discovery alone.
What to measure
- Identity-ready rate
- Verified/usable contact rate
- Duplicate outreach prevented
- Suppression-rule hits
- Bounce/wrong-person rate
- Recruiter-approved send rate
Failure modes to avoid
- Auto-emailing every discovered profile
- Sending before identity resolution
- Ignoring prior decline or do-not-contact state
- Using low-confidence contact values without context
- Treating AI-generated messaging as authorization