How to Respond to a Recruiter's First Message (5 Templates That Get Replies)

First Day AI · 2026-07-16 · 6 min read

How to Respond to a Recruiter's First Message (5 Templates That Get Replies)

A recruiter sends you a message. You reply. They reply. You reply. They disappear.

The chain breaks because most replies don't answer the only question the recruiter actually has in their first 30 seconds of reading your message: should I keep reading, or should I move on to the next candidate in my queue?

The recruiter's queue is a triage list. Your reply is one of 30-80 messages in their InMail queue for the day. Every reply that doesn't move them toward a hire gets closed, archived, or marked "not responsive" in 60 seconds. The reply that does move them gets forwarded to the hiring manager within the hour.

This post is the 5 reply templates that move the recruiter forward. The framework, the templates, the line-by-line copy. No vague "thanks for reaching out" replies that die in the thread.

The recruiter's first 5 seconds

The recruiter reads your reply in this order: name, current title, current company, years of experience, last skill line. If those 5 fields don't answer their initial question — is this person real, are they qualified, do they fit the role — the recruiter closes the thread.

The 5 reply templates below are organized by what the recruiter needs in those 5 seconds. Template 1 covers the most common case (you are a fit). Templates 2-5 cover the next 4 most common cases (you're a partial fit, you're not looking yet, you need salary info, you want to decline). Each template is a direct line for the recruiter to forward to the hiring manager.

Template 1 — Referral ask (the default "yes I'm interested")

The recruiter asked if you're open to a role. You are. The reply has 4 lines:

Subject: Re: <role title> — <your name>, <years> yrs <current title>

Hi <recruiter first name>,

Thanks for reaching out. I'm interested — <one sentence on why this role fits my background, with the matching keyword from the JD>.

Could you share who I'd be working with on the team? I have a couple of questions on the charter before I send my resume over.

Best,
<your name>

Why this works: The recruiter forwards the message to the hiring manager with the subject line intact. The hiring manager sees: someone with the right title, the right experience, asking the right question. The thread moves in one message, not three.

The line that matters most: "who I'd be working with on the team." This is a referral ask disguised as a fit question. If the recruiter gives you a name, you now have an internal contact. If the recruiter doesn't, the recruiter has to go find out — and the act of finding out puts your thread on the hiring manager's desk.

Template 2 — Fit check (you might be a fit, but need to confirm)

The recruiter pinged you about a role you're not sure about. Maybe the level is wrong. Maybe the team doesn't match your background. The reply has 4 lines and ends with a question:

Subject: Re: <role title> — quick fit check

Hi <recruiter first name>,

Thanks for the note. <one sentence on which part of the role fits, and one sentence on which part doesn't>.

Before we go further: what's the level and the charter for this role? And is the team currently distributed or onsite at <city>?

Best,
<your name>

Why this works: Recruiters ping 200-400 candidates per role. Most replies either say "yes send my resume" (wasting the recruiter's time on a bad fit) or "no thanks" (closing a thread that could have been a fit at the right level). The fit-check reply moves the thread forward without committing your time.

The line that matters most: "what's the level and the charter for this role." The level is what makes or breaks the fit for senior candidates (Staff vs Senior, Manager vs Director, etc.). The charter is what makes or breaks the fit for candidates coming from a different vertical. The recruiter has both answers — usually in the job description — but the act of asking forces them to confirm the role is worth your time.

Template 3 — Timing move (you'd be interested, but not now)

The recruiter pinged you. The role is interesting. But you just started a new job, or you're 3 weeks from a planned move, or you're closing a quarter and can't interview until October. The reply has 3 lines and sets a follow-up date:

Subject: Re: <role title> — interested, timing

Hi <recruiter first name>,

Thanks for reaching out. The role looks like a fit, but I'm locked in until <specific date — e.g., "mid-October">. Could we reconnect the week of <specific follow-up date>?

If the timing doesn't work for this role, no worries — happy to stay in touch for future openings.

Best,
<your name>

Why this works: The recruiter has 30-80 candidates in their queue. Most "I'm interested but not now" replies die because the candidate doesn't commit to a follow-up date. The recruiter assumes the candidate is being polite and moves on. By setting a specific follow-up date ("the week of October 14"), you turn the "no" into a "yes, but later" — and the recruiter bookmarks your thread for that date.

The line that matters most: "Could we reconnect the week of October 14." Specific dates are 3x more likely to get a follow-up than vague dates ("let's reconnect in a few months"). The recruiter adds you to their calendar or CRM with the date and reaches back out.

Template 4 — Salary probe (you need comp info before you engage)

The recruiter pinged you. The role is interesting. But you're not going to spend 4-6 hours interviewing for a role that pays below your floor. The reply has 3 lines and ends with a number:

Subject: Re: <role title> — comp range

Hi <recruiter first name>,

Thanks for reaching out. The role is interesting, and my background is a fit. Before we set up a screen, could you share the comp range for the role? My floor is <specific number, e.g., ₹28L total>.

If the range is in the ballpark, I'm happy to move forward.

Best,
<your name>

Why this works: Most candidates don't ask about comp early because they're worried about "scaring off" the recruiter. The opposite is true: recruiters waste 5-10 hours per week screening candidates who fall out at the salary stage. If the role is below your floor, the recruiter needs to know early so they can pivot to other candidates — and if the role is in range, the comp question shows you're a serious candidate, not a tire-kicker.

The line that matters most: "My floor is ₹28L total." The word "floor" matters. "Floor" means "I won't go below this" — it's not a target. The recruiter knows whether the role hits the floor without negotiation.

For India specifically: comp ranges vary 2-3x by city, level, and company tier. A senior engineer in Bangalore at a product startup might make ₹35-55L, while the same role at a service company makes ₹18-28L. The comp probe saves both sides 4-6 hours of interview cycles that fall apart at the offer stage.

Template 5 — Graceful no (the role doesn't fit, but stay in touch)

The recruiter pinged you. The role is not a fit. The reply has 3 lines and ends with a referral:

Subject: Re: <role title> — not a fit, but a referral

Hi <recruiter first name>,

Thanks for the note. The role doesn't quite fit my background — <one sentence on why, briefly>.

I do know someone who'd be a strong fit: <referral name>, currently <title> at <company>. Want me to make an intro?

Best,
<your name>

Why this works: Most "no thanks" replies close the thread permanently. The recruiter moves on. But a "no with a referral" reply does two things: (1) it gives the recruiter a warm lead, which they love, and (2) it puts you in the recruiter's mental Rolodex for future roles. The next time the recruiter has a role that fits, your name is at the top of the list.

The line that matters most: "Want me to make an intro?" This is the line that converts a "no" into a relationship. If you actually know someone who's a fit, the recruiter will work with you for years.

The follow-through

The 5 templates get the recruiter's attention. The follow-through is what gets you the offer:

  • Reply within 4 hours during business hours. Recruiter reply rates drop 40% after 24 hours. The candidate who replies at 10am gets the screen at 11am. The candidate who replies at 5pm gets the screen the next morning — or never.

  • Send the resume as a PDF, named with your name and the role. Ananya-Kapoor-Senior-Engineer-2026.pdf is what the recruiter forwards. resume_final_v3.pdf is what gets renamed by the recruiter (and might get lost).

  • Calendar-link the screen. If the recruiter suggests a screen, send your Calendly or similar link with 3-4 time windows in the next 5 business days. Don't make the recruiter email back to find a time.

  • The follow-up after the screen. The recruiter sends a "great to meet you" message. Reply within 24 hours with one sentence: "Thanks for the conversation — looking forward to next steps." The reply keeps the thread warm. No reply makes the recruiter assume you're not interested.

The 5 reply templates above cover 80% of recruiter first-message scenarios. The other 20% are edge cases (you've already interviewed at the company, you're in a non-compete, the recruiter is from a known-spam agency) — for those, the safe default is a 2-line "not a fit, but thanks for the note" reply without a referral.

The job search is a volume game. The candidates who move 30-80 messages per day through their InMail queue with direct, specific replies are the ones who land offers. The candidates who send 5 vague replies per week and wait for the recruiter to chase them are the ones who spend 4-6 months in the search.

The First Day AI Job Search Plan is the production version of this system: auto-tailored resumes for each reply, auto-scheduled screens, and a weekly digest of recruiter response rates by role cluster. The recruiters are out there. The replies are short. The follow-through is the difference.

FAQ: Replying to a recruiter's first message

How fast should I reply to a recruiter's first message?

Within 4 hours during business hours. Recruiter reply rates drop 40% after 24 hours, and a reply sent at 10 am usually converts into a screen by 11 am — while the same reply at 5 pm waits until the next morning, or never gets answered at all. Speed is the single cheapest advantage you have in a thread.

What should my first reply contain?

Four things: your name, your current title, your years of experience, and one specific keyword from the job description. Keep it to 3-4 lines and end with one question so the recruiter has a reason to reply. Leave out "I'm passionate", "I'd love to apply", and the resume attachment — those are the lines that get threads archived within 60 seconds.

Should I share my salary expectations in the first reply?

Only when compensation is a genuine dealbreaker — and then share a floor, not a target ("my floor is ₹28L total"), exactly as in Template 4 above. If you're flexible, answer the recruiter's question and defer the number until you know their range. Anchoring the conversation too early caps your upside. The full offer-stage sequence is in the India salary playbook.

What if the recruiter never replies to my message?

Follow the cadence from our cold-DM templates guide: one follow-up after 4 days, one final note after 10 days, then silence. In our internal data, roughly 60% of replies land on the second or third message — candidates who send one message and stop leave most of their replies unclaimed.

Is it okay to decline a role I'm not interested in?

Yes — and decline with a referral. Template 5 above converts a "no" into a relationship: recruiters work with candidates who hand them warm leads for years afterward. A graceful no with one intro is worth more than a dozen unanswered threads.

Reading us regularly? Add First Day AI as a preferred source on Google — then our new guides surface first for you in Search, Top Stories and AI Mode.

Reviewed by the First Day AI editorial team · sources cited inline. Found a mistake? Tell us.