Candidate Follow-Up Drafter
Same-day follow-up emails for every interviewed candidate.
role recruitingfollow-updraftingtriagebeginnerpro planorigin selfupdated 2026-10-24
01Requires
what are these? skills vs memories vs plugins →
hiring voice + candidate-facing do/don't list memoriesrole pipeline stages and what each stage's email should promise memoriesgmail pluginsread access to the interview-notes doc or ATS export permissionsgmail draft scope (creates drafts, never sends) permissions
02Setup — 6 steps
- 01Create the agent. Open Grok Bot → Agents → New Agent, name it
candidate-followup. - 02Paste the prompt. Copy the prompt below into the system field.
- 03Write voice memories. Add two memories: your hiring voice rules, and what each pipeline stage promises.
- 04Connect notes source. Point the agent at the interview-notes doc, or paste notes directly into the task.
- 05Draft one first. Run on a single interview first; check tone and factual accuracy by hand.
- 06Batch the loop. After two clean runs, run per-day on all candidates who interviewed that day.
03Prompt
agent prompt · system field
You are a recruiting follow-up agent. For each candidate in the notes:
- Draft a short follow-up email in our hiring voice (see memories).
- Reference one concrete thing they said — never generic "great meeting you".
- If notes are thin or the outcome is unclear, flag for review instead of drafting.
- Never promise timelines, compensation, or decisions we haven't confirmed.
04Config
| name | example | description |
|---|---|---|
stage memory | "phone screen" | Pipeline stage decides what the email may promise |
voice memory | "warm, direct, no jargon" | Keep it in memories, not the prompt — reuse across agents |
05Sample output
Example output shape: 4 candidates → 3 drafts ready, 1 flagged (notes incomplete).
06Pitfalls
Generic praise reads automated. Force the 'one concrete thing they said' rule — it's the difference between a drafter and a mail merge.
Overpromising in rejection-adjacent mail. Keep stage-specific promises in memories, not the prompt, so rejections can't inherit 'next steps' language.
07Variants
- interview-debrief-summarizer — upstream sibling: notes → structured debrief before the email
- offer-check-drafter — same loop for offers, with comp details pulled from a sheet
- candidate-nurture-digest — weekly version for silver-medal candidates
08FAQ
Does it send automatically?
No — drafts only. Review in Grok Bot, then send from Gmail. Auto-send to candidates is a reputation risk.
Can it read from our ATS?
If the ATS exports to a sheet or doc, yes. Greenhouse/Lever APIs need a connector or MCP plugin.
What about candidates we'd reject?
Keep a 'rejection voice' memory and run a separate pass — same skeleton, different stage memory.
09Run it — or hand it to us
Tell us what you want Grok Bot to do: hello@awayhand.com
10Related templates
Interview Debrief Summarizer
Raw interviewer notes → structured, rubric-scored debrief.
recruiting · 2026-10-24
Meeting Follow-up Drafter
Turns call notes into a recap and next-step email.
sales · cs · 2026-10-24
Onboarding Nudge Drafter
Drafts activation nudges for stalled signups.
growth · 2026-10-24
↩Also referenced by
unofficial template from a community-run directory — not affiliated with the product's vendor · disclaimer
New templates as they land. No hype.
Email to subscribe →