Skip to content
NewSee how

Recruiter playbook: source candidates, personalize with AI, schedule interviews

Build a candidate ICP by title and seniority, personalize outreach with the AI SDR, work replies in the inbox, and schedule interviews with a Meeting-goal campaign and a connected calendar.

  1. Frame recruiting as outbound with an interview goal

    Recruiting runs the same machinery as sales outbound: the “buyer” is a candidate and the “win” is a booked interview instead of a demo. That maps directly onto an Autopilot campaign with goal Meeting: the AI sources candidates, drafts personalized notes, and every email drives toward a booked call.

  2. Create an Autopilot → Meeting campaign

    Open Campaigns → Create Campaign. Set Campaign Type to Outreach, Campaign Mode to Autopilot, and Campaign Goal to Meeting. Name the campaign for the role you're hiring, so it's obvious at a glance which pipeline it feeds. See Create an Autopilot Meeting Campaign.

    Create an Autopilot → Meeting campaign
  3. Build the candidate ICP with AI Leads

    In the builder's Contact Harvester, enable AI Leads and describe the candidate profile in Target Audience: e.g. “Senior backend engineers open to new roles in the US.” Then tighten the People filters: Job Titles, Seniority, and Functional Level, so the sourced list actually matches the role band you're hiring for. See Use AI Leads to Source Contacts.

  4. Optionally ground drafts in the role story

    Add a Knowledge Base (crawled from your careers page or company site) so drafts cite real specifics about the company and role instead of generic recruiter-speak. This is optional but sharpens the copy noticeably. See Build a Knowledge Base.

    Optionally ground drafts in the role story
  5. Tune the AI SDR for a warm, candidate-first voice

    Open AI Instructions and set Persona & Voice, structure, and a low-pressure CTA: ask for a quick chat, not a hard sell. Candidates aren't buyers, and tone is the difference between a reply and a block. This is your single biggest quality lever here, same as it is for sales outbound.

    Tune the AI SDR for a warm, candidate-first voice
  6. Connect a calendar to the Meeting goal

    With Goal = Meeting, the campaign's goal config exposes a calendar picker: connect Google or Outlook so the meeting CTA offers real interview slots. Once connected, candidates can self-book directly from the email instead of a back-and-forth to find a time.

    Connect a calendar to the Meeting goal
  7. Approve the first batch, then let it run

    Set Content Approval to auto-approve to keep the pipeline moving: you're notified, and an email auto-sends after 24 hours if you don't act. Review the first drafts closely so the candidate-facing tone is right before trusting it to flow on its own.

  8. Work replies and schedule interviews

    Triage candidate replies in the Inbox and route interested candidates to a booked slot. Judge the campaign on replies and interviews booked in Analytics rather than open rate: that's what actually reflects a moving pipeline. See Read Campaign Analytics.

Pro tips

  • Seniority + Job Titles do the candidate targeting

    Tighten AI Leads' People filters to the exact role band you're hiring for; a vague "engineers" prompt sources the wrong list.

  • Warm, low-pressure CTA wins candidates

    In AI Instructions, ask for a quick chat rather than a hard sell: candidates aren't buyers, and tone is the difference between a reply and a block.

  • Connect the calendar so candidates self-book

    The Meeting goal's calendar picker turns "interested?" into a booked interview without a back-and-forth to find a time.

  • Ground drafts in the real role

    A Knowledge Base with the company story and role specifics keeps AI notes concrete instead of generic recruiter boilerplate.

Frequently asked questions

Can I use this for recruiting, not sales?

Yes: the same GA features apply with candidate framing. An Autopilot → Meeting campaign treats a booked interview as the goal instead of a sales demo.

How do I target candidates by role?

In AI Leads, describe the candidate profile in Target Audience and tighten the People filters (Job Titles, Seniority, and Functional Level) to the exact band you're hiring for.

How do candidates book interviews?

Connect a calendar (Google or Outlook) to the campaign's Meeting goal. The calendar picker then lets candidates self-book a slot directly from the email.

How do I keep the tone candidate-friendly?

Set Persona & Voice and a soft, low-pressure CTA in AI Instructions: recruiting outreach reads best as a friendly conversation starter, not a pitch.

Do I write the outreach myself?

No: Autopilot drafts every message; you tune the voice in AI Instructions. If you'd rather write your own copy, a Template campaign is the alternative.

Should I ground it in the role?

Optional but worthwhile: an attached Knowledge Base with the company and role story sharpens drafts beyond generic recruiter language.

How do I keep the pipeline moving?

Content Approval set to auto-approve keeps drafts flowing after a 24-hour review window. Review the first batch closely, then let it run.

How do I measure it?

Watch Analytics for replies and interviews booked, not opens: with a Meeting goal, that's what reflects real pipeline movement.

Getting Started

Outreach that keeps going after you log off.Leads, emails, follow-ups and replies, handled.

Connect unlimited mailboxes and let AI agents find leads, write each email and follow up. Or send your own templates in manual mode. From $29/mo.

$1 for 3 days · Cancel anytime · No contract

Install with AI

Your coding agent sets up the FirstSales CLI and skills for you.

Prompt for Claude Code

I'm setting up FirstSales (https://firstsales.io), an AI outbound sales platform: campaigns, contacts, a reply inbox, deliverability and lead signals. Help me get my workspace sending real, good emails end to end, from Claude Code.

Read these first so you know how FirstSales works:
- Developer docs and API: https://developer.firstsales.io
- CLI: https://www.npmjs.com/package/@firstsales.io/cli
- Skills for coding agents: https://github.com/firstsalesio/firstsales-skills (read README.md and GUIDE.md)

Setup
1. Install the CLI: npm install -g @firstsales.io/cli
2. Install the FirstSales skills:
   claude plugin marketplace add firstsalesio/firstsales-skills
   claude plugin install firstsales@firstsales
3. Ask me if I already have a FirstSales account. If not, send me to https://app.firstsales.io to sign up.
4. Ask me to create an API key under Settings → API → API Keys, with only the scopes we need.
   Never ask me to paste the key into this chat. Tell me to run this in my own terminal, so the key stays hidden:
   read -rs FS_KEY && firstsales auth login --api-key "$FS_KEY"; unset FS_KEY
5. Run `firstsales whoami` and tell me which workspace and organisation we are connected to.

Then ask me about my business: what I sell, who I sell to (roles, company size, countries), my best customers, and what I use today for outbound (tools, lists, mailboxes). Walk me through:
1. Teaching FirstSales my business: website, offer, proof points and case studies in the knowledge base, so the AI writes like someone who knows the product.
2. Connecting my sending mailboxes and checking my sending domain: SPF, DKIM, DMARC and warm-up. If anything is unhealthy, tell me the exact DNS record to add.
3. Bringing in contacts: import my CSV or CRM export into a clean list, remove duplicates and bad emails, and block domains I must never email (customers, competitors, my own).
4. Building my first campaign: the right list, senders, steps and timing. Write the sequence with me, show me the drafts, and do not launch until I say yes.
5. Setting up Signals if it fits: find people engaging with LinkedIn posts about topics my buyers care about, and turn them into leads.
6. Inviting my team and giving each person the right access.

Once campaigns run, show me how to work the reply inbox from here: which replies need an answer, draft responses in my voice, and move good conversations into deals. If I use Cal.com, connect it so follow-ups can offer my booking link (not the first email).

Throughout, as you learn about my business, proactively suggest and help create:
- Reply templates for the questions and objections my prospects are likely to raise, based on my product, site and codebase if you can see them.
- Campaign ideas and segments worth testing, with the reason for each.

Safety rules:
- Show every change as a dry run (--dry-run) first and wait for my yes. Never send emails, launch campaigns or delete anything without my yes.
- Tell me before anything that spends credits, and how many.

Be opinionated. If the docs give a sensible default, just use it. Don't make me choose between five options.