# Writing outreach candidates reply to

> Good recruiting outreach opens with one specific line about the person's own work, states the role, team, location and pay range, and asks for one small next step. Follow-ups should each add something new, come a few days apart and stop at the first reply, and every message should make it easy to opt out.

Published by Emoti Research on 2026-11-01, updated 2026-11-01. Article. For recruiters. Canonical: https://emoti.ai/articles/outreach-candidates-reply-to

## What makes a first line personal?

A personal first line names something specific the person did in their own work and connects it to the role, in one sentence.

Compare these two openings:

> I came across your impressive profile and think you'd be a great fit for an exciting opportunity.

> You rebuilt the event pipeline at your company so that late carrier data stopped breaking forecasts, and that is exactly the problem our platform team is hiring for.

The first could be sent to anyone, so it reads as if it was. The second could only be sent to one person, and it explains why you are writing. Good material for that sentence comes from the person's own descriptions of their roles, talks they have given, things they have written, and open-source work. Skip compliments that say nothing ("impressive background"), and facts about them rather than their work.

A few openings in the same spirit, for different roles:

- **A product designer:** "Your case study on simplifying the dispatch screen showed exactly the trade-offs our planning team argues about every week."
- **An account executive:** "You built the first enterprise pipeline at your last company from nothing, which is the job here too."
- **A data engineer:** "Your talk on backfilling late events without double counting describes the problem our analytics team is stuck on."

## Where is the line between personal and intrusive?

Use work facts the person published for professional reasons, and nothing else. Their job, their projects and their public talks are fair. Their family, their location history, their other social accounts and anything that suggests you have been watching them are not.

A useful test: if they asked "how did you know that?", would you be comfortable showing them where you found it? If the honest answer is "I combined three sources", leave it out.

Be careful with sensitive signals too. A profile that shows someone is open to work can tell you whom to contact, but it doesn't belong in the message. "I saw you're looking" tells the reader you noticed something they may not want discussed.

## What facts does a candidate need to decide?

The role and its level, the team and what it works on, the location and work pattern, the pay range, and who you are.

| Fact | Why it matters | Example |
| --- | --- | --- |
| Role and level | So they can tell whether it is a step up | Senior backend engineer, individual contributor |
| Team and work | So they can picture the job | The payments team, which moves money between shippers and carriers |
| Location | So they can rule it in or out | Berlin with two office days a week, or remote within Europe |
| Pay range | So nobody spends a call on numbers that don't meet | €95,000 to €115,000 base |
| Who you are | So they know who will answer | Your name and role, and who the hiring manager is |

Leaving out the pay range asks the candidate to spend a call finding out whether the job is even possible for them.

## How should you make the ask?

Ask for one small, specific next step that is easy to say yes to.

"Would you be open to a 20-minute call next week?" is easy to answer. "Let me know your thoughts" isn't. Offer an alternative for people who would rather read first: "If you'd prefer to read before talking, I can send the brief."

Don't stack asks. A call, a request for referrals and a link to an application form in one message dilute each other. Keep the whole message short enough to read on a phone without scrolling: the first line, the facts, the ask and your name.

Put together, a first message can be this short (the names and numbers are invented):

> Hi Sam, your talk on backfilling late events without double counting describes the problem our analytics team is stuck on. I'm Alex, and I recruit for Example Co.'s data platform team: a senior data engineer role, individual contributor, reporting to our head of data. It's in Berlin with two office days a week, or remote within Europe, and the base range is €90,000 to €105,000. Would you be open to a 20-minute call next week? If you'd rather read first, I can send the brief, and if you'd rather not hear from me again, reply and say so.

## How far apart should follow-ups be?

A few days apart at first, then longer, with each one adding something new, and no more than three in total.

| Day | Step | What it adds |
| --- | --- | --- |
| 1 | Email | The first line, the facts and one ask |
| 3 | LinkedIn message | A short note, in case email isn't where they read |
| 6 | Email | One new detail: the team, the process or the hardest problem |
| 10 | Email | A clear last note that says it is the last |

A follow-up that only says "just bumping this" asks for attention without giving a reason. Each one should earn its place with a fact the first message didn't have room for. Stop as soon as someone replies, whatever the reply says, and don't send the same message on two channels on the same day.

## How do you make opting out easy?

Tell people plainly how to stop hearing from you, honor it everywhere, and keep a record.

One sentence is enough: "If you'd rather not hear from me again, reply and say so, and I won't write again." When someone says no, record it where everyone on your team can see it, so that a colleague doesn't contact them next month about a different role. A person who said "not now" may welcome a note in six months. A person who said "please stop" should not get one.

There is a legal side in some places. In the EU, when you collect someone's personal data from somewhere other than the person, the GDPR requires you to tell them, among other things, where the data came from and how you will use it, and if you use it to contact them, to do so at the latest when you first contact them (Article 14). This article is not legal advice; check the rules where you recruit.

## How does Emoti draft first lines for approval?

Emoti drafts one first line per person from facts in their profile, a recruiter approves each line, and nothing is sent until the line is approved and the sequence is active.

In version 1.0, first lines are written by fixed rules rather than a language model, so every clause can be traced to the profile: the description of their current role, skills that overlap with the role's brief, background in a related industry, or a professional signal such as speaking at conferences or maintaining open-source projects. Emoti never puts "open to work" into a message, and it marks the lines it wrote.

Emails go out on weekdays within a sending window in each recipient's time zone (8:30 a.m. to 5:30 p.m. by default), under a daily limit per mailbox (60 by default). Any reply stops the sequence for that person. Emoti doesn't yet add an unsubscribe link or keep a workspace-wide do-not-contact list, so the opt-out sentence above matters. The details, including the gaps, are in [Personal outreach with a person in the loop](https://emoti.ai/research/outreach-with-approval).

## Key terms

- **First line**: In outreach, the opening sentence of the first message, written for one person from their own work. Emoti drafts one per person and a recruiter approves it before anything is sent.
- **Outreach sequence**: A planned series of messages and tasks, such as emails, LinkedIn messages, calls and waits, sent to a candidate over days or weeks until they reply or the sequence ends.
- **Reply rate**: Replies divided by people contacted in an outreach sequence or campaign. Teams should decide whether bounced messages count as contacted and use the same rule every time.
- **Passive candidate**: A person who isn't actively looking for a new job but might consider the right one. Sourcing and outreach are how teams reach them.

## Questions

### Should I mention pay in the first outreach message?

Yes, as a range. It saves both sides a call when the numbers don't meet, and in some places job postings must include a pay range anyway.

### Is it OK to say how I found someone?

Yes, and it helps. Naming the talk, project or profile you read shows the first line is real. In the EU, telling people where their data came from is also required when you didn't collect it from them.

### Should I use email or LinkedIn for outreach?

Start on the channel the person seems most active on, and use the other for one follow-up. Don't send the same message on both on the same day.

### What should I do when someone replies "not now"?

Thank them, ask when would be a better time, and record the date. In Emoti their reply stops the sequence, so set your own reminder to check back.

## Sources

- European Parliament and Council of the European Union (2016). Regulation (EU) 2016/679 (General Data Protection Regulation), Article 14. Official Journal of the European Union. https://eur-lex.europa.eu/eli/reg/2016/679/oj
- Labor Commissioner's Office California Equal Pay Act and Pay Transparency Law (Labor Code sections 432.3 and 1197.5): Frequently Asked Questions. California Department of Industrial Relations. https://www.dir.ca.gov/dlse/California_Equal_Pay_Act.htm