5 Cold Email Templates for Staffing Agencies

These five templates apply SalesTap's verifiable-trigger approach, not a measured winning formula. The sources checked contain no comparative dataset ranking staffing templates by conversion, so treat each template as a hypothesis.

Five pre-send checks

1. Source: use the company's careers page, press release, or another named official source.
2. Applicability: make sure the trigger plausibly belongs on the recipient's desk.
3. Proof: every result is true, documented, and approved externally. Delete any sentence whose brackets cannot be filled truthfully.
4. Candidate permission: do not share candidate details without agreement. GOV.UK states that an agency cannot give a work-seeker's information to a hirer without permission.
5. Lawful contact: follow the direct-marketing rules in the recipient's jurisdiction.

Five templates by trigger

Each note states what the trigger establishes and what it does not. Use the linked five-minute research checklist before filling the brackets.

1. The active vacancy

Subject: Senior Platform Engineer role

Hi [Name], I saw the [role] opening on your careers page. We recently completed [number, only if true and documented] searches for similar stacks in [vertical]. If it would help, I can outline how we would approach this one, and share profiles only once we have the candidates' permission. Worth a one-line reply?

A live posting proves only that the role is advertised. Do not infer sourcing difficulty or demand for agency help. Present documented results as your own, never as market benchmarks.

2. The funding announcement

Subject: hiring after the [round] announcement

Hi [Name], congratulations on the [round] announcement. If the raise comes with hiring plans, and the announcement states [quote the hiring detail it actually contains], we specialise in [function] searches in [vertical]. Happy to share how we scope a search at this stage. If hiring is already covered, no reply needed.

The announcement proves only what the company states. Do not infer roles or timing; quote hiring plans only when they are explicit.

3. The official expansion or competitor-hiring announcement

Subject: [function] hiring in [market]

Hi [Name], [Competitor] announced [expansion/hiring detail] in [their press release / official announcement, dated]. If that changes your own [function] hiring calculus, and our records support it, I can share a dated summary of [number, only if documented and approved] completed searches from [period], including the availability and compensation ranges we observed.

Use official announcements, not LinkedIn headcounts. LinkedIn prohibits third-party tools that scrape LinkedIn or automate activity on its website. The announcement proves only what the competitor said. Any agency observations need current, documented, externally approved records with a date range and sample size; they are not market-wide benchmarks.

4. The leadership change

Subject: sales hiring under a new CRO

Hi [Name], congratulations on the CRO role. If reshaping the team is part of your brief, we have supported [number, only if true, documented, and approved for external use] sales-leadership transitions in [vertical] and can share a non-confidential summary of how those leaders sequenced their hiring. If the team is set, no reply needed.

An appointment proves only who arrived, not that a rebuild will happen on any timetable. Keep "if reshaping the team is part of your brief" conditional.

5. The long-open vacancy

Subject: still hiring for the [role] role?

Hi [Name], the [role] position has been on your careers page since [date you can evidence]. Is it still active? If it is, and extra reach would help, we can share how we would source it and, only if our records support it, a dated summary of [number, only if documented and approved] comparable searches from [period]. If it is filled or paused, I will not follow up.

A listed vacancy may be stale, filled, paused, or sourced internally. Ask whether it remains active. Any comparable-search evidence needs a documented sample, date range, external approval, and a clear non-benchmark label.

Test the mechanics instead of trusting rules

No source checked validates a three-touch optimum, 90-character preview rule, automatic attachment penalty, or universally safe daily volume. Google's rules for personal Gmail recipients require all senders to use SPF or DKIM and keep their Postmaster Tools spam rate below 0.3%. Above 5,000 daily messages to Gmail, senders need SPF, DKIM, and DMARC; marketing or subscribed messages need one-click unsubscribe. Google also advises large-volume senders to reduce volume after bounces or deferrals and not to message people who did not sign up. Technical compliance does not make outreach lawful or wanted.

Compare like trigger cohorts and randomise one variable at a time, such as cadence, follow-up content, or subject style. The subject-line evidence is mixed, so size the test with the A/B Test Designer, measure positive replies and qualified conversations, and stop variants that increase bounces, complaints, or opt-outs.

Candidate-data and direct-marketing boundaries

Three boundaries sit around every template here. First, candidate data: get the work-seeker's permission before sharing their information with a hirer, per the GOV.UK guidance above. Treat any profile that still identifies or could reasonably identify someone as personal data under UK GDPR where it applies; removing a name alone may not achieve effective anonymisation. Second, US law: CAN-SPAM applies to B2B commercial email and, among other duties, requires accurate header information, a non-deceptive subject, clear identification as an advertisement, a valid physical postal address, and a clear opt-out mechanism that works for at least 30 days; requests must be honoured within 10 business days. Third, UK rules: under the ICO's B2B guidance, unsolicited B2B email to a corporate subscriber does not require consent under PECR, but the sender must not conceal its identity and must provide a valid opt-out address. Sole traders and certain partnerships are individual subscribers, so consent is generally required unless the soft opt-in applies. If a named contact's personal data is used, UK GDPR also requires a lawful basis, transparency, and compliance with the person's right to object to direct marketing. A public job posting does not by itself establish consent or UK GDPR compliance. None of this is legal advice.

The takeaway

• Verify every trigger and proof point. Use documented agency results, not market claims.
• Get permission before sharing candidate profiles. Removing a name is insufficient if the person remains identifiable.
• Meet the applicable legal and technical requirements, then test comparable cohorts. Stop when complaints or opt-outs rise.

Source check: 1 August 2026. The GOV.UK, LinkedIn, Google, FTC, and ICO requirements and guidance were checked against the linked official pages. The templates, trigger framings, and testing plan are SalesTap editorial guidance, not measured findings.