Recruiter outreach: role context and candidate choice

Use this sequence to offer a role brief that matches preferences the candidate actually supplied. Let them choose whether to learn more.

The recruiter, employer and role below are fictional. Replace them with authorized, current information. Do not copy the claim about recruitment preferences unless it is true for that recipient.

Prepare the role before the sequence

This example concerns a fictional mid-level product designer role at Northstar. The candidate has asked to hear about product-design opportunities. The recruiter has an employer-approved description and knows which location and work-arrangement details can be disclosed.

Fill those details into the message before launch. Do not invent salary, remote work, sponsorship or urgency.

Only firstName is merged. The fallback there keeps the greeting readable. Split campaigns by materially different role information rather than sending an ambiguous “opportunity.”

Message 1: offer the actual brief

Initial subject: Product designer role brief

Hi {{firstName | there}},

You asked to hear about product-design opportunities. I am recruiting for a mid-level product designer role at Northstar. This is a permanent, on-site role in Lagos.

The team is working on its account setup experience. I have an employer-approved brief covering the role, location expectations and hiring process.

Would you like me to send it before deciding whether a conversation is useful?

Thanks,
Rowan
Recruiter

If you do not want further recruitment messages, reply and I will stop.

Use the employer name only when you may disclose it. Replace the preference statement with a truthful description of your actual relationship if different.

Message 2: clarify what a reply involves

Hi {{firstName | there}},

A clarification on my note: you do not need to send a CV or book a call to receive the role brief.

If you want to review it first, reply here and I can send the approved details. If this type of role is not relevant, I will leave it with you.

Rowan

Reply if you would like me to stop contacting you.

Send only if the role remains available and another message fits the candidate’s contact expectations. Do not send after a reply, hard bounce or opt-out.

Message 3: end this role enquiry

Hi {{firstName | there}},

I will end this role enquiry after this message.

If you want the current brief, you can reply here. Otherwise I will not keep following up about this role.

Thank you,
Rowan

Do not use a teammate’s mailbox to restart the same enquiry.

Replace every role detail before launch

After a request, a personal response could be:

Hi Alex,

Here is the approved role brief: [insert the permitted brief or link].

It covers [the actual responsibilities], [location and work arrangement], and [the current hiring steps]. Compensation information is [insert the authorized details or explain what is still unavailable].

Would you like to discuss the role after reviewing it?

Rowan

Replace every square-bracket instruction before sending. Do not describe an unavailable term as agreed. If the role has closed, explain that and end the proposal. For an address-wide stop request, follow the opt-out workflow.

Check responses and privacy

If the person requests the brief, respond manually with authorized information. If they decline this role, do not claim they consented to another one. If they ask to stop, mark them opted out.

ColdMerge’s human reply stop is campaign-specific; automatic replies continue. Follow-ups have no separate subject and stay with the original mailbox/thread. See Follow-up sequences and How unsubscribes work.

Review list origin, role disclosure and conversation ownership before launch. Use the campaign launch guide to check audience rules and preview eligible contacts.

Check opt-out controls before launch

ColdMerge’s unsubscribe footer and one-click header start off. Review and enable the appropriate controls before sending. A reply asking to stop does not automatically suppress the address across campaigns: choose Mark as opted out manually. That suppression applies across the Organization. See How unsubscribes work for the configuration and recipient behavior.