What the top desks do differently
I read through the sequences of the customers with the highest reply rates before writing this. They all follow the same shape, and it's the shape from the outreach framework. Say why you reached out in one verifiable sentence. Give away the two or three things the candidate cares about, usually role, scope and money. Ask for a small yes, not a meeting. Offer something even if the answer is no. Then follow up on a second channel with a new angle, not the same message again.
Three habits stood out on top of that. Every first email carries the comp range or the location, or both. Every follow-up adds one fact the last message didn't have, about the client, the role or the timing. And every sequence ends with a referral ask, which turns a no into a lead.
One more thing worth saying up front. Nothing here works if the candidate isn't a real fit. The message opens the door. The match is what gets the reply.
The anatomy of a first-touch candidate email
The first emails that reply best share one shape.
- Subject line is the role and one anchor. "Controls Engineer, automotive manufacturer." "Project Executive, Nashville." No agency name, no "opportunity."
- Line one says who you're working with and what for. "I'm working with an established automotive parts manufacturer on a search for a Plant Controls Engineer."
- Line two says why them. "Your background at {{companyName}} looks like a strong fit." Specific if you can, honest if you can't.
- One paragraph of scope, with the money. What the role owns, the team, the tech or the territory, base range, bonus, remote or on site.
- A yes-or-no ask. "Any chance you'd like to see the full JD?" Not "are you open to a 15-minute call."
Under 130 words. No adjectives about the client that a fact could replace. "Tenured engineering team, defined technical ladder" beats "great culture."
The 15 candidate outreach templates, by scenario
Grouped by the situation you're in. The first block is the standard sequence the top desks run. The rest are the variants for specific scenarios. Swap the bracketed details for your search.
1. First touch email, the standard
Subject: Controls Engineer, automotive manufacturer
Hi {{firstName}},
I'm working with an established automotive parts manufacturer on a search for a Plant Controls Engineer. Your background at {{companyName}} looks like it could be a strong fit.
The role centers on PLC programming, HMI development and robot troubleshooting in a live production environment, Allen Bradley and Cognex vision. You'd own root cause analysis and lead controls improvements across the floor. Tenured engineering team, defined technical ladder from L4 up to full subject matter authority. Base $110K to $130K plus bonus, on site.
Any chance you'd like to see the full JD?
Why it works: client type, role, why them, scope with money, small ask. The desk running this shape replied at 9%.
2. LinkedIn connection note (day 2)
Hi {{firstName}}, I'm recruiting a Plant Controls Engineer for an automotive manufacturer, PLC, HMI and vision systems in a production environment. Thought your background at {{companyName}} might be worth a conversation. Mind if I shared more details?
Why it works: under 300 characters, the same three specifics as the email, and "mind if I shared more details" is the smallest yes there is.
3. LinkedIn message after they connect, the thing you didn't mention
Hi {{firstName}},
Thanks for connecting. One thing I didn't mention about this Controls Engineer role. The company has a structured technical leveling system, so your growth path is defined and assessed on a schedule, not left to chance. They also promote controls talent from within as the team grows.
Worth a closer look? Happy to send the JD.
Why it works: a new fact, not a repeat. Every top sequence uses the "one thing I didn't mention" move here.
4. Email two, "one more thing"
Subject: one more thing
Hi {{firstName}},
Wanted to add something about this manufacturer. They're operationally stable, well resourced, and the controls team has real backing from leadership. Budget ownership, contractor coordination and capital project involvement are all in scope.
For an engineer who wants decision-making authority and not just a title, it's a meaningful difference.
Should I send over the full JD?
Why it works: lower-case subject reads like a colleague. The body answers the question every good candidate is silently asking, which is "would I actually have room to operate there."
5. Email three, the timing piece
Subject: the timing piece
Hi {{firstName}},
Controls roles with this kind of scope, at a manufacturer that's already stable and funded, don't come up often. Most candidates hear about them after they've been posted publicly for weeks. This one isn't there yet.
Want me to send the full details before it moves forward?
Why it works: honest scarcity. Only send it when it's true. Candidates can smell a fake deadline from the subject line.
6. LinkedIn message two, the referral turn
Hi {{firstName}},
Most controls engineers I talk to only hear about plant-level roles like this after the search is nearly closed. This one's still early.
If it isn't the right fit for you, no worries at all. Would you know anyone in the Allen Bradley or FactoryTalk space who might be looking? Happy to keep you in mind for future searches either way.
Why it works: it gives the candidate an easy out and a way to help. Referral asks in the top sequences produce candidates the boards never surface.
7. The last note
Subject: quick follow-up
Hi {{firstName}},
Shortest email I'll send you. Still open to hearing about the Plant Controls Engineer role?
If the timing isn't right, I'm happy to keep you in mind for future searches. And if you know someone in the PLC or controls space who might be a fit, I'd appreciate the referral.
Either way, no pressure.
Why it works: the closing message in every top sequence is short, kind and leaves the door open. It pulls a surprising share of the total replies.
8. The passive senior candidate
Subject: Project Executive, alternative delivery, Nashville
Hi {{firstName}},
I'm working with a heavy civil contractor in the Nashville area on a search for a Project Executive, Alternative Delivery. Your background at {{companyName}} is exactly the profile.
The role owns the full alternative delivery pipeline, Design-Build, CMAR and P3, from RFQ pursuit through closeout on DOT megaprojects. Base $160K to $185K with a guaranteed structured bonus, vehicle and tech allowances. It opened on a retirement, not turnover, and the contractor has unusually high retention.
Any chance you'd like to see the full JD?
Why it works: senior people reply to scope, money and why the seat exists. "Opened on a retirement" answers the question they'd ask first.
9. The local role, no relocation
Subject: Maintenance Manager, manufacturing
Hi {{firstName}},
I'm working with an established manufacturer on a search for a Maintenance Manager. Your background at {{companyName}} looks like a strong fit.
The role owns all plant maintenance, electrical, mechanical, hydraulic and pneumatic, and leads a team of up to 10 technicians. You'd build the preventive and predictive programs and drive equipment reliability across the site.
No relocation. This is a local position.
Any chance you'd like to see the full JD?
Why it works: "No relocation" on its own line. For hands-on roles it's the first objection, so kill it before they think it.
10. The territory sales role
Subject: Fluid Power Sales, CT and MA
Hi {{firstName}},
I'm working with an established fluid power distributor on a search for an Outside Sales Engineer covering Connecticut and western Massachusetts. Your industrial sales background at {{companyName}} looks like a strong fit.
The role owns a defined territory from north of Hartford through western MA, an existing book of accounts, and a technical support team behind you. Base $85K to $100K plus uncapped commission, car allowance, remote with travel in territory.
Any chance you'd like to see the full comp plan?
Why it works: sales candidates want territory, book and comp plan. Ask if they want the comp plan, not the JD.
11. The confidential search
Subject: Controller, PE-backed services company
Hi {{firstName}},
I'm running a confidential search for a Controller at a PE-backed services company in the Twin Cities, so I can't name them in writing yet. Your background at {{companyName}} is why I'm writing.
The role owns the close, reporting to the board, and the first ERP implementation. Base $150K to $170K plus bonus and equity. The current controller is moving into an operating role, which is why the seat is open.
Worth a ten-minute call so I can tell you who it is?
Why it works: the only template that asks for a call, because you can't send a JD. Say why it's confidential and what you can share.
12. The re-engage, six months later
Subject: the role we talked about in March
Hi {{firstName}},
We spoke in March about a Controls Engineer role and the timing wasn't right. A new one just opened at a different manufacturer, similar scope, base $10K higher, and hybrid instead of fully on site.
Worth a look this time?
Why it works: it proves you remembered and it names what changed. Candidates from your own nurture list reply at multiples of cold ones.
13. The text message
Hi {{firstName}}, [Your name] from [Agency]. Sent you a note about a Plant Controls Engineer role, $110K to $130K, on site in [City]. Happy to text the JD over if easier. If not, no worries.
Why it works: only after email and LinkedIn, only with a properly sourced number. Role, money, location, one question.
14. The "not this one, but"
Subject: not this one, but
Hi {{firstName}},
Understood on the Controls Engineer role, thanks for the straight answer. Two things while I have you. The comp band for senior controls roles in [region] moved up about 8% this year, useful to know at review time. And if you ever want a read on the market, I'm easy to find.
Best of luck with everything.
Why it works: the framework's fourth move, value even with no fit. This is the message that makes them reply to you next year.
15. The second connection attempt (day 10)
Hi {{firstName}}, I'm recruiting a Plant Controls Engineer for an automotive manufacturer, Allen Bradley PLC, FactoryTalk HMI, Cognex vision in a live production environment. Thought your background might be a fit. Can I share more?
Why it works: a second request a week later gets accepted more than you'd expect. Swap one specific so it doesn't read as a resend.
Paste the job description. Talin finds the candidates, verifies contact details, and drafts every step across email, LinkedIn and SMS, personalized to each person's background.
See candidate outreach in TalinThe two-week cadence
The default order the top desks run, stopping the moment anyone replies.
- Day 1: first touch email (template 1, or 8 to 11 for the scenario).
- Day 2: LinkedIn connection note (template 2).
- On accept: the thing you didn't mention (template 3).
- Day 5: "one more thing" email (template 4).
- Day 8: the timing piece (template 5). Text if you have a proper number (template 13).
- Day 9: LinkedIn referral turn (template 6).
- Day 10: second connection attempt for anyone who didn't accept (template 15).
- Day 14: the last note (template 7).
Email, LinkedIn and text as one sequence with one memory, so nobody gets a follow-up email the day after they replied on LinkedIn. That's the multichannel rule, and it's the part worth automating. Once the email side passes 50 a day, spread it across more inboxes.
The mistakes that flatten candidate reply rates
- Hiding the money. Every top sequence states the range in the first email. Candidates skip messages that don't.
- "Exciting opportunity" and no company type. Say what kind of company. Anonymous is fine, vague isn't.
- Asking for a call in message one. Ask if they want the JD. The call comes after the yes.
- Follow-ups that repeat. "Just following up" adds nothing. Each touch carries one new fact.
- Fake urgency. Use the timing message only when the timing is real.
- Ending without the referral ask. A no with a referral is a lead. A no without one is nothing.
