When a recruiter lets AI write part of a candidate email, the first decision is what the AI may say to a person it has never spoken to. How well it writes comes second. AI-personalized candidate outreach sequences are scheduled emails: a first message followed by follow-ups. AI writes some lines for each candidate using what the team knows about that person. This article covers where to draw the line between what the AI writes and what stays word for word, the evidence rule every generated line has to meet, and the review to run before the first email sends.
In Metaview’s 2026 AI & Hiring Alignment Report, 79% of the 505 recruiting leaders and hiring managers surveyed said they’re optimistic about AI’s future in hiring. Optimism doesn’t tell you which sentence in an email to a named candidate the AI is allowed to write, though, and that decision is still the recruiter’s.
My position is simple: I’d let the AI write only what someone can check, and I’d keep everything the team has approved exactly as approved.
What AI-personalized candidate outreach sequences write.
In an AI-personalized sequence, the AI writes the lines that change from one candidate to the next: the subject, an opening line about the person’s background, and a line connecting that background to the role. The approved role pitch and any other wording the team has approved stay the same for every candidate. The recruiter decides which lines fall on which side before the sequence starts.
A generated line can differ for every candidate, so approving the template doesn’t approve the exact sentence each person will receive. A fixed line is read and approved once, then reaches every candidate unchanged.
Keep the approved wording identical for everyone.
Some wording should never be rewritten per candidate, because someone other than the recruiter has already approved it or because it has to say the same thing to everyone. Keep these lines word for word in every email:
- The approved role pitch: what the job is, the level, and why it’s worth a conversation.
- The privacy notice, which tells candidates how their data is used.
- The opt-out line, which gives every candidate the same simple way to stop hearing from you.
- Any other sentence the team wants identical, such as how you describe location or the stage the candidate would enter.
If the pitch is regenerated for each person, the AI can drift from what the hiring manager signed off, and a candidate can end up with a version of the role no one on the team approved. A privacy notice or opt-out that changes shape from email to email is harder to stand behind if a candidate asks what they were told.
The evidence rule for every generated line.
Every line the AI writes should pass one test: could someone point to its source? A claim about the candidate has to come from their profile. One about the role has to come from the approved brief, the written description of the role that the hiring manager approved. If the relevant source doesn’t support the line, it doesn’t go out.
In practice, that separates two kinds of personalization:
- Grounded: a line about the candidate’s current role, the size of the team they work in, or a skill their profile lists, tied to something the brief says the role needs.
- Inferred: a line about why the candidate might want to leave, what frustrates them at work, or what they’re looking for next.
The second kind reads as more personal, but it’s a guess about someone you haven’t spoken to, and a wrong guess about a person’s motives is worse than no guess at all. A candidate who gets told what they’re unhappy about, by a stranger who’s wrong, has a reason not to reply.
The same rule covers thin profiles. When a profile says little, the generated line should say less, and fall back on the role itself rather than filling the gap with something invented.
Review a sample from each step before anything sends.
Because generated lines are different for every candidate, you can’t approve them by reading the template. Read real output instead. Before the sequence starts sending, read generated emails for a sample of the candidates it’ll reach, for every step: the first email and each follow-up.
Build the sample around where the evidence is weakest. Include candidates with detailed profiles and candidates with thin ones, because thin profiles give the AI less source material and more room to fill the gap. For each email, check:
- Every generated fact appears in the candidate’s profile or the approved brief.
- No line guesses at the candidate’s motives, frustrations, or plans.
- The fixed lines, from the role pitch to the opt-out, arrived exactly as approved.
- Each follow-up meets the same evidence rule.
Then name who signs off. I’d make it one person, usually the recruiter who owns the role, and I’d write the name down before the first send. If the hiring manager wants to see samples too, agree that up front, before candidates receive anything. Metaview’s co-founder and chief technology officer, Shahriar Tajbakhsh, explained why unreliable AI output still leaves recruiters with validation work:
If results aren’t reliable, AI doesn’t reduce work. It just moves it, and recruiters end up validating, correcting, and second-guessing the output.”
A person still makes the final judgment. The video below, from Metaview’s 10x Recruiting podcast, is titled “Why being human is still an edge in hiring.”
Where Metaview fits in AI-written outreach.
Metaview Outreach sends automated email sequences. Its sequence builder includes email personalization, so the same checks apply: fixed wording, sourced generated lines, and a sample review before the first send.
The approved brief is only as good as the conversation behind it. If Metaview’s Notetaker is on the intake call, it captures every spoken word, so the pitch the team fixes can be checked against what the hiring manager said rather than someone’s memory of it.
Decide the line before you turn it on.
AI-written outreach goes wrong in predictable places: an approved pitch that drifts, a line about a candidate with no source behind it, and a sequence that sends before anyone has read what it wrote. The recruiter can settle each of those before the first email goes out.
Decide which wording stays fixed, what source each generated line needs, and who signs off, then turn the sequence on. For help writing the fixed and generated lines, see the guides on improving candidate outreach copy and personalizing recruiting emails at scale.
Talk through AI-written candidate outreach with Metaview.
See Metaview Outreach’s sequence builder, email personalization, and automated email sequences.
Frequently asked.
What should AI write in a candidate outreach email?
Let the AI write the lines that change per candidate, such as the subject, an opening line about the person’s background, and a line connecting that background to the role. Each of those lines should rest on the candidate’s profile or the approved brief.
What should stay the same in every outreach email?
The role pitch the hiring manager approved, the privacy notice, the opt-out line, and any other sentence the team wants identical. Keep them word for word so every candidate receives the approved version.
Should AI guess why a candidate might want to move?
No. A guess about a candidate’s motives or frustrations isn’t supported by their profile or the brief, and a wrong guess from a stranger gives the candidate a reason not to reply. Keep generated lines to what the profile shows.
How do you review AI-written outreach before it sends?
Read generated emails for a sample of candidates at every step of the sequence, including candidates with thin profiles. Check each generated fact against the profile and the brief, confirm the fixed lines arrived unchanged, and have one named person sign off before the first send.
Does Metaview Outreach personalize sequence emails?
Yes. Email personalization is part of Metaview Outreach’s sequence builder, which sends automated email sequences. The recruiter still decides what stays fixed and reviews what the AI writes.