9 Recruiting Messages You Can Generate in One Click

Writing recruiting messages is repetitive but never truly repeatable. Every candidate is different. Every job has different selling points. Every situation calls for a different tone.

So you end up in a loop: write a draft, open ChatGPT, paste the candidate’s info and the JD, ask for a rewrite, copy the result back, edit it, send it. Fifteen times a day. That’s easily 1.5-2 hours spent on message writing alone.

What if every message type you need — from LinkedIn outreach to salary negotiation — could be generated in one click, already personalized with the candidate’s profile and the specific job?

Here are the 9 message types that cover virtually every recruiting communication scenario.

1. LinkedIn First Touch (Short)

When to use: Initial outreach to a passive candidate on LinkedIn. This is your first impression — and you have exactly 300 characters to make it (LinkedIn InMail limit for connection requests).

What AI considers:

Candidate’s current role and company
The most compelling aspect of the job (salary range, company name, tech stack, growth opportunity)
Brevity — every character counts at the 300-char limit

Example output:

Hi Sarah — saw your work at Stripe on their payments API. We’re hiring a Senior Backend Engineer for a Series B fintech in Berlin, €85-95k + equity. Strong distributed systems focus. Interested in a quick chat?

Why it works: Specific (mentions their company and work), concise (under 300 chars), and gives enough info to spark interest without overwhelming.

The character counter is critical here. LinkedIn truncates messages that exceed the limit, which means your carefully crafted closing line — the one with the call to action — gets cut off. AI-generated messages respect the limit by default.

2. First Touch (Full)

When to use: After a candidate responds “interested” or “tell me more” to your short outreach. Now you have space to sell the role properly.

What AI considers:

Full job description (parsed requirements, company info, benefits)
Candidate’s background (to highlight relevant aspects of the role)
Compensation details (if available)
Company culture and growth story

Example output:

Hi Sarah, great to hear back from you!

The role is Senior Backend Engineer at FinFlow — they’re a Series B payments platform (think Stripe meets B2B invoicing). The team is 12 engineers, mostly backend (Go + PostgreSQL), shipping to 200+ enterprise clients.

What caught my eye in your profile: your 4 years on Stripe’s payments API maps directly to what they’re building. They specifically asked for someone who understands payment processing at scale.

Comp: €85-95k base + 0.2% equity. Berlin HQ, hybrid (2 days office). Visa sponsorship available.

Would you be open to a 15-minute call this week to go into more detail?

Why it works: Personalized to the candidate’s experience, specific about the role, transparent about compensation. Not a generic template with {name} placeholders.

3. Follow-Up

When to use: 3-5 days after your first outreach with no response. This is the most common message type — most candidates don’t respond to the first message, but many respond to a well-timed follow-up.

What AI considers:

The original outreach message (to avoid repetition)
A new angle or piece of information to add value
Timing context (acknowledging they’re busy)

Example output:

Hi Sarah — just following up on my message from last week about the Senior Backend role at FinFlow. I know inboxes get crowded, so I’ll keep this short: they just closed a $40M Series B and are scaling the payments team from 4 to 8 engineers. If the timing isn’t right, no worries at all — happy to keep you in mind for future roles too.

Why it works: Adds new information (the funding round), respects their time, and leaves the door open without pressure.

4. Soft Rejection

When to use: You reviewed a candidate and decided not to submit them to the client — but you want to maintain the relationship for future opportunities.

This is one of the hardest messages to write well. Too blunt and you burn a bridge. Too vague and they don’t know where they stand. AI helps find the right balance.

What AI considers:

The reason for not proceeding (framed constructively)
The candidate’s strengths (genuine, not patronizing)
Door-opening language for future opportunities

Example output:

Hi Sarah — thank you for taking the time to speak with me about the FinFlow role. After reviewing the team’s current priorities, I think the match isn’t quite right for this specific position — they’re looking for someone with more hands-on Kubernetes experience in production, and your infrastructure background leans more toward AWS ECS.

That said, your payments domain knowledge and backend skills are exactly what several of my fintech clients look for. I’d love to keep in touch and reach out when a better-fitting role comes up. Would that be ok?

Why it works: Honest about the gap, acknowledges their strengths, and explicitly asks to maintain the relationship.

5. Client Rejection

When to use: The client (hiring company) rejected the candidate after an interview. This requires even more care — the candidate invested time in the process and deserves a respectful response.

What AI considers:

The interview stage (screening, technical, final?)
The feedback from the client (reframed positively where possible)
The candidate’s experience level and emotional investment

Example output:

Hi Sarah — I have an update on the FinFlow position. After your technical interview, the team decided to move forward with a candidate whose experience more closely aligns with their specific distributed systems architecture. This was a close decision — your payments expertise and system design skills made a strong impression.

I’d genuinely like to keep you on my radar for similar backend roles. The fintech market is very active right now, and your profile is exactly what these companies are looking for. I’ll be in touch when I see a strong match.

Why it works: Respectful, specific enough to be helpful, and maintains the professional relationship.

6. Scheduling

When to use: Setting up a screening call or interview. Simple in concept, but surprisingly time-consuming when done 5-10 times per day.

What AI considers:

The type of meeting (screening call, technical interview, etc.)
Duration
Calendar link (if configured)
Time zone context

Example output:

Hi Sarah — excited to move forward! I’d love to set up a 15-minute screening call to discuss the FinFlow role in more detail. Here are a few slots this week:

Tuesday 2:00 PM CET

Wednesday 10:00 AM CET

Thursday 3:30 PM CET

Or feel free to grab a time that works for you: [calendar link]

The call will cover: your current situation, salary expectations, availability, and a deeper look at the role. Very casual — no prep needed.

Why it works: Clear about the purpose and duration, multiple options, and sets expectations for what the call will cover.

7. Salary Negotiation

When to use: The candidate’s salary expectation doesn’t match the client’s budget. This requires diplomacy — you need to manage both sides without losing either.

What AI considers:

The gap between expectation and budget
The role’s non-salary benefits (equity, flexibility, growth)
Market context
A constructive framing that doesn’t feel like a lowball

Example output:

Hi Sarah — I wanted to be transparent about the compensation discussion. Your expectation of €95k is above FinFlow’s current budget for this role, which is €80-85k base. I want to make sure you have the full picture before we decide on next steps:

Equity: 0.2% (4-year vest, 1-year cliff) — at their current valuation, that’s meaningful upside

Annual bonus: up to 10% based on company performance

Remote flexibility: 3 days remote per week

Learning budget: €2,000/year

The total package lands around €95-100k when you factor everything in. Would you like to explore this further, or is the base salary a hard requirement?

Why it works: Transparent, shows the full package, and asks a direct question to avoid wasting anyone’s time.

8. Grammar Fix

When to use: You’ve written a message in your own words, but English isn’t your first language and you want to make sure the grammar and phrasing are professional.

This is different from the other 8 message types. Instead of generating a message from scratch, the AI takes your existing text and fixes grammar, punctuation, and awkward phrasing — while keeping your voice and intent intact.

What AI considers:

Grammar and punctuation errors
Awkward phrasing that a native speaker wouldn’t use
Preserving the original tone and meaning (not rewriting)

Example input:

Hi Sarah, I wanted to reach to you about opportunity we have. The role is for backend developer at company in Berlin. I think you profile is match very good. Can we have short call to discuss about this?

Example output:

Hi Sarah, I wanted to reach out to you about an opportunity we have. The role is for a backend developer at a company in Berlin. I think your profile is a great match. Can we have a short call to discuss this?

Why it changes: Fixes prepositions (“reach to” → “reach out to”), articles (“at company” → “at a company”), possessives (“you profile” → “your profile”), and phrasing (“discuss about” → “discuss”). Your message, your voice — just grammatically correct.

For non-native English speakers, this feature alone can save an hour per day. Not because fixing grammar takes long per message — but because the anxiety about making mistakes slows down every single message you write.

9. Freeform

When to use: Any message that doesn’t fit the other 8 categories. You describe what you need, and AI generates it using the candidate and job context.

What AI considers:

Your custom instruction / prompt
Candidate profile data
Job context (if relevant)
Tone setting

Example prompt: “Write a message asking Sarah if she’d be open to mentoring junior developers on the team — this is a soft requirement that’s not in the JD.”

Example output:

Hi Sarah — one more thing I wanted to ask about the FinFlow role. The team has two junior backend engineers who would benefit from working closely with a senior engineer. It’s not a formal mentoring program, but the team is hoping the new hire enjoys knowledge sharing and pair programming. Is that something you’d be interested in, or would you prefer a more heads-down individual contributor focus?

Why it works: Addresses a nuanced topic that wouldn’t fit a template, using specific context from the candidate and role.

Three Tones, One Click

Every message type (except Grammar Fix and Freeform) can be generated in three tones:

Tone	Best for	Character
Formal	Senior candidates, enterprise roles, first contact with unknown preferences	Professional, structured, polite distance
Friendly	Startup roles, younger candidates, warm referrals	Conversational, warm, approachable
Short	Follow-ups, scheduling, candidates you’ve already built rapport with	Direct, minimal, respect-their-time

You pick the tone once. AI generates 2-3 variants in that tone. You pick the best one, edit if needed, send.

The LinkedIn Character Problem

LinkedIn has a hard 300-character limit for connection request messages. This causes a specific problem: you write a message, it looks great, you paste it into LinkedIn… and the last sentence is cut off.

AI-generated short messages solve this by design. The character count is calculated before generation, and the message is crafted to fit — including punctuation and spaces. No truncation, no surprises.

For InMail messages (which allow longer text), the character limit is less of a concern — but the AI still optimizes for readability and attention span. A 500-word InMail is technically possible but practically useless.

Personalization vs. Templates

The key difference between AI-generated messages and templates is context awareness. A template says:

Hi {name}, I’m reaching out about a {title} role at {company}…

An AI-generated message says:

Hi Sarah — saw your work at Stripe on their payments API. We’re hiring a Senior Backend Engineer for a Series B fintech in Berlin…

The template inserts variables. The AI reads the candidate’s profile, identifies the most relevant talking point, and leads with it. That’s why AI messages get higher response rates — they feel written by a human who actually looked at the profile.

What You’re Really Saving

Let’s do the math:

Average messages per day: 15-20
Time per message (write + ChatGPT + edit): 5-10 minutes
Time per message (one-click AI): 30 seconds (generate + review + send)
Daily savings: 1.5-2.5 hours

That’s not a marginal improvement. That’s getting your afternoon back.

Ready to stop writing messages from scratch? Try Inga CRM free — 9 message types, 3 tones, personalized to every candidate and job. One click.