Guide

Grok Bot for recruiting: the official guide in brief, plus our advice

By Atlas AI Resources · Published October 13, 2026 · How we make these guides

Recruiters lose hours to scorecards, prep notes, and pipeline updates that keep them away from candidates. This page summarizes the four recruiting bots in the official guide and how they hand work to each other, then adds our own fill-in templates for interview briefs, scorecard follow-ups, and outreach. We suggest keeping every message to a candidate behind your approval.

It is based on the official guide Grok Bot for Recruiting (September 24, 2026) by Holly Dyche, written from a recruiting team that uses Grok Bot every day. The workflows below are summarized in our words; read the guide for the author’s full account.

1. One assistant across your recruiting tools

The guide’s main point is that Grok Bot works across the tools a recruiting team already uses. A scorecard, a request to a hiring manager, and a stack of interview transcripts stop being three separate systems you have to open yourself. The author describes using voice mode on the drive to work to ask for an ATS change or a scorecard, and arriving to find transcripts already reviewed against the rubric, a candidate record updated, and a scorecard drafted.

The guide also describes how quickly the team took to it. Within a week, recruiters were sharing prompts and routines with each other. At a recruiting offsite, small teams each built a bot for one everyday recruiting problem, and those bots are the four described below.

You do not have to paste everything in. The guide’s advice is to tell the bot where information lives in your systems, the way you would brief a new teammate. Our advice: connect only what each bot’s job needs. A bot that writes interview briefs needs to read candidate records, but it does not need to send email.

2. The four bots

• Preppy (before the interview). Candidate context is spread across Notion, LinkedIn, and the ATS. Just before the call, Preppy posts one Slack note covering who the candidate is, why the team is excited about them, their interview stage, what to focus on, and what earlier interviews already covered.
• Pulse (after the interview). Pulse pulls the Granola transcript or meeting recording, matches it to the role’s scorecard, and drafts the feedback form in your voice. Then it stops and asks you a few follow-up questions so the form carries your judgment, not just a transcript summary. Once you answer, it redrafts and submits the scorecard to your ATS.
• Scout (sourcing). Scout reads scorecards and resumes from hundreds of past hired and rejected candidates to learn what has worked. It sources candidates overnight, adds them to the ATS as leads, and drafts multi-touch outreach sequences, so a shortlist is waiting in the morning. You approve the send; then Scout moves the candidates to Reached Out and watches for replies.
• eVal (loop analysis). eVal looks across the interview loop for where candidates fail and why, then turns that into questions recruiters can ask at the first screen. Problems surface earlier instead of using up interviewers’ time later.

The guide links a shareable version of each bot. Those listings say the bots were created by a third-party user, so read each bot’s job description and stop points before you add it, and adjust them to your own team.

3. The guide’s tips, in brief

• Onboard it like a new teammate. The first time you do a task together, such as an outreach note, walk the bot through your reasoning, then have it save that as a reusable skill.
• Feed it your voice. Point it to your best outreach, debrief notes, and offer emails before it drafts anything new.
• Turn corrections into standing rules. If outreach comes out too salesy or debrief notes too vague, say so directly, and the bot remembers.
• Let it work in parallel. A sourcing bot and a feedback bot can run at the same time across different open roles.
• Chain the bots so you are not the glue. eVal finds where people fail later in the process and sharpens the profile of who to look for. Scout sources from that profile and drafts outreach you approve. Preppy briefs the interviewer. Pulse drafts the scorecard and asks for your take. Context travels with the candidate from bot to bot, so you are not copying notes between Notion, Slack, and Ashby or explaining the same person four times.

In this chain each bot owns one lane, and you keep the parts that matter most: the candidate relationship, your own read on each interview, and the final yes on any outreach. Our guide on small AI fleets and handoffs covers how to give each stage a single owner.

4. Atlas’s advice: three fill-in templates

What follows is Atlas’s own advice, not the guide’s. Adapt the wording to your team.

Atlas’s advice: what an interview brief must include

Ask your prep bot to cover each of these, and to say “not found” rather than guess:

• Candidate and role: ____ for ____ (level, team).
• Interview stage: ____ , and who the interviewer is.
• Why we are interested: two or three points, each with where it came from (resume, screen notes, referral).
• Already covered: what earlier interviews tested, so this one does not repeat it.
• Focus for this interview: ____ (from the scorecard for this stage).
• Open questions: anything earlier interviewers flagged to dig into.
• Logistics: time, link, and anything the candidate asked for.

Atlas’s advice: the scorecard follow-up questions

The guide’s Pulse pauses for your take before it submits. A short, fixed set of questions keeps that step quick:

• Your overall rating: ____ (use your team’s scale).
• One sentence on how the interview felt.
• Anything in the draft that is wrong or overstated?
• Anything fuzzy that the transcript cannot show?
• What should the next interviewer pressure-test?
• Submit to the ATS now? Reply yes or no.

The draft is a starting point, not the interviewer’s judgment. If you do not answer, the bot should hold the draft rather than submit it.

For a ready-made prompt that keeps hiring notes tied to evidence for each candidate, see per-candidate evidence prompts.

Atlas’s advice: wording the outreach approval

Have the sourcing bot send you a request that is complete enough to answer on its own. A fill-in version you can adapt:

• Candidate: ____ (current role and company)
• Open role: ____
• Why this person: ____ (the evidence, with links)
• Sequence: ____ messages over ____ days
• Draft of the first message: ____
• After you approve: send the first message, move the candidate to Reached Out, and watch for a reply.
• Ask: Approve this sequence? Reply yes, no, or edit.

Nothing goes to a candidate without your yes. Write that stop point into the bot’s instructions in plain words, and treat anything other than a clear yes as a no. A bot’s confidence that someone is a fit is a suggestion, not permission to reach out. Patterns learned from past hires can also carry past blind spots, so keep the shortlist a starting point and keep hiring decisions with people.

5. Keep candidates and decisions behind your yes

We recommend draft-then-approve for anything that reaches a candidate or a hiring decision: outreach sequences, replies, scorecards, and offer emails. Grok Bot’s guardrails are plain-language rules checked by a review agent, not code. The current docs put them in Settings → General → Auto-review, as Ask first and Allow automatically rules (the 101 guide calls this Settings > General > Agent). Spell out each bot’s stop points (“draft only,” “ask before sending outreach,” “ask before submitting a scorecard”). An approval controls the action it is attached to; it does not undo work already done.

Recruiting bots also read a lot of text written by other people: resumes, LinkedIn profiles, candidate emails, and replies to outreach. Any of it can contain instructions aimed at your bot, so treat that content as data to read, not orders to follow, and keep sends and ATS changes behind approval. Our guide on keeping AI agents safe from prompt injection covers this in more depth.

Our advice: candidate records are personal information, so give each bot only the access its job needs, and keep compensation details and private notes out of anything it can send.

General architecture advice, not a description of how Grok Bot works: if you also run your own scripts against an ATS or email API, enforce hard limits such as send caps, allowed pipeline stages, and write scopes with exact checks in that code.

6. Where to start: our suggestions

• Pick one bot. An interview-brief bot like Preppy is a low-risk first job because it only reads and writes up. A scorecard bot like Pulse is a good second, as long as it waits for your answers.
• Connect your ATS and notes first, read-only if you can, then add email only when you reach outreach.
• Keep every outreach message and scorecard as a draft for the first few weeks, and watch what the bot proposes.
• Save what works as a skill, then schedule it. Overnight sourcing is a routine; prove it by hand first and use safe inputs for the test run, since a test run does real work. Our guide on skills before routines walks through this.
• Add the next bot only when the first one is reliable, then connect them so context moves with the candidate.
• Judge it by finished work: scorecards submitted on time, interviews that tested something new, and hours your team spent with candidates, not how many leads a bot added.

The guide closes by saying none of this replaces the recruiter; it clears away what stands between recruiters, candidates, and their stakeholders, so more of the day goes to interviews, debriefs, and calibration. Read the author’s wrap-up in Grok Bot for Recruiting.

Useful public resources

Related: Grok Bot for SDRs · Grok Bot for legal ops · Grok Bot for post-sales · Grok Bot for founder-led sales · Grok Bot for support · Small AI fleets: handoffs · Skills before routines · Scheduling AI agent routines · Keeping AI agents safe from prompt injection · What is a one-job Grok Bot? · Complete Grok Bot setup guide · Grok Bot for PMs