Lever ATS and CRM for Recruiting

Primary intent: run applicant tracking and candidate relationship management in a single platform using Lever LeverTRM as of early 2026. Where a traditional ATS treats candidates as applicants moving through a pipeline per req, Lever keeps them as contacts in an ongoing relationship: you can tag, nurture, and re-engage a pool of warm candidates across multiple reqs over months without restarting the sourcing cycle each time. That is the core value that separates Lever from ATS-only tools.

Lever's pipeline view looks like a standard ATS at the req level: stages from application to offer, scorecards per stage, and reporting on pipeline velocity. The CRM layer sits underneath: every candidate has a relationship owner, a history of interactions across all your reqs, and a nurture status. Recruiters who treat Lever only as an ATS pay for CRM features they never use; recruiters who invest in talent pool segmentation get qualified candidates back into pipelines faster than starting fresh every quarter.

If your question is whether Lever is the right platform for your team, read How it compares to similar tools before committing. If you are already on Lever and want to run your first talent pool and nurture sequence in under an hour, go straight to Practical steps.

Lever integrates natively with LinkedIn Recruiter (System Connect), major HRIS platforms (Workday, BambooHR, Personio, Rippling), background check providers, and assessment vendors. For automation between Lever and external AI tools, n8n or Make can connect the Lever API to push stage-change and application events to ChatGPT, Claude, or your HRIS without custom engineering. Broader AI stack context: ChatGPT for brief and outreach drafts, Claude for long-context synthesis, Greenhouse for structured interview discipline.

Choose your ATS against your primary hiring motion: Lever fits best when a significant share of hires comes from a warm pipeline you maintain over time. If every hire starts with fresh outbound or inbound, a leaner ATS may return equal value at lower cost and configuration effort.

Where to start (opinionated): if more than 30 percent of your hires are expected to come from a warm pool you maintain across reqs (former silver-medal candidates, conference contacts, referrals not yet in process), Lever earns its CRM seat. If your primary motion is inbound applications plus targeted outbound and you want maximum scorecard discipline, evaluate Greenhouse first. If you are a lean team hiring fewer than 30 roles per quarter without dedicated TA ops, Workable gets you live faster with less configuration risk.

A first talent pool and nurture sequence: under 45 minutes

1. Define the pool before you open Lever. Write a two-line description: who belongs here (for example: "senior engineers with distributed systems experience who were strong but behind the hired candidate in the last six months") and what you want them to do next ("re-enter for the next senior engineer req, ideally within 90 days"). Without this definition, the pool becomes a miscellaneous list.

2. Tag and archive, do not hard-reject. When a strong candidate does not advance on a req, archive with a tag that matches your pool definition instead of a hard rejection. This is the primary way to build a talent pool from existing pipeline data without a bulk import.

3. Assign a relationship owner before adding to a sequence. In the Lever contact record, set one recruiter as the named owner for this pool segment. This is the person who reviews replies and responds within one business day. Without ownership, sequences send, replies arrive, and no one follows up.

4. Create a short nurture sequence. Three touches over five to six weeks is a reasonable default for a warm candidate. First message: one sentence acknowledging the previous process and one sentence on what might bring them back. Second: one update relevant to the role or team. Third: a direct call to action. Generic messages produce low reply rates; specific, context-aware messages do not need to be long.

5. Set a 30-day check-in task. Log a Lever reminder or a task in your project tool to review pool stats: open rate, reply rate, unsubscribes. If reply rate is below five percent after two sequences, rewrite the first message before sending the third touch. A small tweak in the opening line often moves reply rates more than adding a fourth touch.

Optional: AI brief from Lever CRM history

When a warm candidate re-engages, export approved fields from their Lever record (role history, past scorecard summaries, recruiter notes) and paste into Claude or ChatGPT with the second prompt below to draft a re-engagement call brief. Export only the columns your data handling policy allows to leave the platform.

Second prompt: re-engagement brief from CRM history

You are helping a recruiter prepare for a re-engagement call with a warm candidate. Use only the facts in the HISTORY block. Do not infer tenure, motivation, or cultural fit. Label any inference clearly as INFERRED.

HISTORY (paste approved fields from Lever CRM record):
[paste: previous role the candidate interviewed for, scorecard summary notes from the last process, stage reached, how long ago, any recruiter notes tagged as strengths or gaps]

CURRENT ROLE:
[paste: role title, key differences from the previous req they interviewed for, one-line on why this role might be a better fit]

Output:
1) A two-sentence candidate recap based only on the history above
2) Three re-engagement call questions that build on previous feedback rather than repeating the same screen
3) One sentence on what makes this req different from their last process (from CURRENT ROLE only; write NOT APPLICABLE if the same req)