AI Recruiter Reply Prep: Filter Fast Without Burning the Bridge

Turn a cold recruiter LinkedIn message into an 80-word reply that surfaces the comp band, role specifics, and a graceful exit if it is off. Copy-ready prompts plus the 2026 pay-transparency context that makes asking normal.

TL;DR

  • Reply to almost every real recruiter message, but keep it short. LinkedIn and recruiting-tool analyses consistently put the sweet spot at roughly 25-50 words and under 400 characters (one widely-cited figure is about 22% higher response rates under 400 characters); the same brevity reads as confident from your side.
  • Use AI to calibrate tone (open vs. passive) and to fold your three must-knows (comp band, manager/team, timeline) into one sentence instead of an interrogation list. Any current model handles this — GPT-5.5, Claude Sonnet 4.6, or Gemini 3.1 Pro; the trick is the instruction set below, not the model.
  • Ask for the pay band in the first reply. As of June 2026, 16 states plus DC require employers to post a good-faith pay range (Delaware’s takes effect in 2027), so recruiters expect the question.
  • Do not volunteer your current comp. As of June 2026, around 22 states plus DC bar employers from asking salary history (Virginia’s ban starts July 1, 2026); let their number land first.
  • Pre-write the polite-pass version up front so you are not composing a reply emotionally when the band comes back 20K low.

The task

A recruiter pinged you on LinkedIn about a senior IC role at a company you have heard of but never seriously considered. You are happy at your current job but always semi-open — your real bar is comp + manager + scope, and you do not want to spend 45 minutes on a discovery call only to find out the band is 20K below your current. You also do not want to ghost; this recruiter has 600 connections in your space and your name on a “responsive” list is worth more than a cold no-reply. You want one reply, under 100 words, that surfaces the qualifying info and leaves a path open if you pass.

Where AI helps — and where it does not

AI is genuinely good at calibrating tone between “open and interested” and “passive but polite” — a 15-word difference that determines whether the recruiter sends you their best roles next time or stops messaging. It can also compress your three must-knows into the same sentence without sounding like an interrogation, and pre-write the graceful-exit version for when the answer comes back wrong.

What AI cannot do: filter recruiters by quality (some externals fish without a real role), tell you which company is actually growing vs. quietly stalling, or judge whether the band they will quote is real or aspirational. It also cannot decide whether you should engage at all — that is your current-job trajectory and life context.

A specific failure mode: AI defaults to over-eager “I’d love to learn more!” energy when you ask for an “open” reply. GPT-5.5 and Gemini 3.1 Pro both lean warm by default; Claude Sonnet 4.6 runs a touch more reserved, but all three need the explicit “no exclamation marks, no ‘I’d love to’” guardrails in the prompt below. The reply that performs best in practice is one notch more reserved than any model’s default — even when you are genuinely interested, slight reserve signals that you are choosing them, not the other way around.

What to feed the AI

  • The recruiter’s full message (verbatim — the model picks up cues you missed)
  • Your current status: open / passive / not actively open but always curious
  • Your 3 must-knows before agreeing to a 30-min call (almost always: comp band, manager / team, hiring timeline)
  • Your current comp ballpark (the model uses it to anchor, you decide if it goes in the reply — usually no)
  • One specific thing you would say no to immediately (on-site only, no remote, pre-PMF, contract not FTE)
  • The vibe of recruiter outreach you have liked best in the past (formal, casual with a “happy Friday,” ultra-brief)
  • Whether you want a soft-no template ready too, in case the answer comes back off
  • How long since you last replied to a recruiter — if you have been silent for a year, lean slightly warmer

Copy-ready prompt

A recruiter sent: "{paste full message}"
My status: {open / passive / not open but curious}
My 3 must-knows before agreeing to a call: {list}
Hard no on: {one specific thing}
Tone preference: {confident-reserved / warm-but-brief / formal}

Write an 80-word reply that:
1) Acknowledges the message in one sentence — not "thanks so much for reaching out!"
2) Asks for the 3 must-knows in one sentence — folded into prose, not a numbered list.
3) Confirms interest at the level matching my status — confident, not eager. If passive, signal that I am not actively searching.
4) Leaves a clear next step (a call if the answers fit, otherwise a polite pass).

Then write a second 60-word version: the polite-pass reply for if their answers come back off. Keep the door open for future roles.

No exclamation marks. No "I'd love to." No "happy to chat."

Shorter variant — recruiter triage one-liner

Recruiter sent: "{paste}". I am {passive}. Write a 40-word reply that asks for comp band and timeline only, and signals I am not actively searching but will engage if the band is real. No filler.

Sample output

A useful open-but-reserved reply: “Thanks for the note — I am not actively searching but always open to a strong match. Before a call, helpful to know the comp band (base + total), the manager and team I would join, and whether the role is hybrid or fully remote. If those line up, happy to find 30 minutes next week.”

A useful passive reply: “Appreciate the outreach. Quick context: I am happy where I am, so I only take calls for roles that meaningfully clear my current comp and scope. If you can share the band and a short paragraph on the team, I can tell you quickly whether it is worth a call. If not, no offense — keep me on the list for future.”

A useful polite-pass for when the band comes back low: “Thanks for sharing the details. The band is below where I would move at this point, but I appreciate the straight answer. Please do keep me in mind for future roles in the same space — happy to stay loosely in touch.”

How to refine

  • Dial down the eagerness: “Rewrite without the words ‘love,’ ‘excited,’ ‘great,’ or ‘happy to.’ Replace with neutral language. Reserve is the signal that I am choosing them.”
  • Bundle the questions: “Fold the three must-knows into one prose sentence, not a numbered list. A numbered list reads as a screening checklist; one sentence reads as a normal candidate.”
  • Don’t share current comp: “Remove any sentence that includes my current comp or salary expectation. The first comp number to land should be theirs.”
  • Add the future-doors line: “End with one phrase that keeps the door open even on a pass: ‘keep me on the list for future,’ ‘happy to stay loosely in touch,’ or similar.”
  • Match the recruiter’s register: “If the original message used emojis or first names only, lean 10% warmer. If it was formal with a full email signature, stay formal. Mismatch in register is what reads as off.”

Common mistakes

  • Over-eager reply (“I’d love to learn more!”) — sets the negotiation anchor in their favor before you have any information; recruiters note who sounds eager and adjust expectations accordingly
  • Not asking for the comp band — and then spending 45 minutes on a call to learn you are 20K above the top of the band
  • Agreeing to a 30-min call before knowing the basics — your time is the actual scarce resource, not theirs
  • Ghosting the recruiter when the role does not fit — burns the door, and recruiters have memories; the role does not have to fit for the relationship to be worth keeping
  • Disclosing current comp without strategy — anchor on market and target, not on what you currently make; current comp is theirs to discover, not yours to volunteer
  • Treating every recruiter the same — an in-house recruiter at a company you care about deserves a different reply than an external fishing with no actual JD
  • Using a numbered list of demands — reads as a screening checklist; bundle the must-knows in one prose sentence
  • Forgetting to write the polite-pass version up front — when the band comes back low, you do not want to compose a reply emotionally; have it ready

FAQ

  • When should I share my salary expectation?: After they share their band. Anchor on market and your target, not on your current. If they push first, the line is “I want to make sure the comp range is in the right neighborhood before I anchor a number — what’s the band you’re working with?”
  • Should I always reply?: Yes, with rare exceptions (clearly templated mass spam with no role detail). Even a 20-word “not now, here’s my LinkedIn, keep me in mind” preserves the bridge and costs you nothing.
  • What if they ghost after my qualifying questions?: That tells you the role was probably not a real match or the band could not stretch. No loss — your time was saved by their silence.
  • The recruiter is in-house at a company I really want — does the strategy change?: Lean 10% warmer and 10% more flexible on the must-knows. The relationship value is higher. But still surface the band before the 30-min call; in-house recruiters are not insulted by it.
  • Is it rude to ask for comp band in the first reply?: No. The norm has shifted; recruiters expect it, and as of June 2026, 16 states plus DC require employers to post a good-faith pay range (see the Paycor 2026 pay-transparency map). The phrasing matters more than the question — “helpful to know the band before I take a call” reads as normal, “what does this pay?” reads as blunt.
  • Which AI model should I use to draft this?: Any current general model works since the output is short. GPT-5.5 (ChatGPT Plus, $20/mo as of June 2026), Claude Sonnet 4.6 (Claude Pro, $20/mo), or Gemini 3.1 Pro (Google AI Pro, $19.99/mo) all produce a usable reply from the prompt above. Claude tends to need the least de-eagering; ChatGPT and Gemini need the explicit “no exclamation marks” line.

Tags: #AI writing #Job search #Recruiter