Candidate Outreach After the Shortlist: What to Say

Candidate outreach should begin after a human has reviewed the shortlist, checked the role brief and decided that a conversation is worth inviting. The message should explain who is contacting the person, why the role may be relevant, what is known, and what the person can choose to do next.

This guide focuses on message content and sequence. The sender must check the contact basis and channel first. A public profile can provide a professional fact to verify; it is not consent, a sign of interest or permission to copy everything on the page.

Start with the sender and the reason

Name yourself, your organisation and your role in the hiring process. An external recruiter should say so; a founder or hiring manager should not hide behind a generic account. The candidate should know who is accountable for the invitation.

Use one verified professional fact that relates directly to one requirement, such as a current role, authored project or public work sample. Check the source before writing, keep the wording factual, and do not present a title as proof of ownership or capability. Exclude sensitive information and do not quote a public page as though it were a private conversation.

State the role without selling past the evidence

Give the role name and a plain-English outcome: what the person would own, improve or help deliver. Add approved scope, such as the team, reporting line or first problem to solve. Do not imply authority or results the role does not provide; say when the remit is still being shaped.

Include location, working pattern and compensation when those details are approved and useful for an initial decision. Say when a range is not approved rather than hiding it behind a call. Describe flexible arrangements and constraints accurately. Named uncertainty, such as "The team is confirming the reporting line", is better than an unsupported promise.

End with one low-pressure question and one clear next step: offer the job description, a short introduction or no further contact. Do not ask for a CV, detailed personal history or a decision before the person has enough context.

Use a simple sequence

The first message should contain the sender, verified reason, role outcome, material conditions and an optional next step. Before sending, check the source, channel and organisation identity.

If a follow-up is appropriate, refer to the earlier message and add useful information, such as the approved range or role link. Do not create urgency, invent a deadline or repeat the pitch. Follow channel rules and policy; no universal cadence fits every person or channel.

If the person declines, asks not to be contacted or says the role is not relevant, acknowledge it and stop. Record the opt-out and do not move to another channel. If there is no response, close the outreach after the policy review point. Do not imply that an interview or rejection occurred when neither happened.

Copyable templates

Use the placeholders only after a human has checked each fact and approved the conditions.

First message

Hi [Name], I am [sender and role] at [organisation]. I am reaching out because I verified [one relevant professional fact] and it relates to [specific role requirement]. We are hiring a [role] to [honest outcome], with [location and working pattern]. [Compensation range, if approved.] Would you like the job description or a brief introduction? No problem if this is not relevant, and tell me if you would prefer no further messages.

Follow-up

Hi [Name], following up once on my note about [role]. The approved details are [one useful scope, location, working-pattern or compensation detail]. If you would like to explore it, you can [clear next step]. If not, no reply is needed, and I will close this message thread.

Closure

Hi [Name], I am closing the loop on the [role] message. There is nothing you need to do. I will not send further messages about this opportunity. Thank you for reading, and please tell me if you want your contact preference recorded differently.

Fictional filled example

The following is explicitly fictional. It demonstrates the sequence and labels, not a real quote, candidate, company, job or market claim.

First message:
Hi Rowan, I am Mina, the hiring manager at fictional Northstar Tools. I am reaching out because I verified your public case study on improving a team dashboard, which relates to the product analytics work in our Product Analyst role. The role would own weekly insight reports with a small product team in Hong Kong, with two office days and a fictional approved salary range of HK$40,000-HK$48,000. Would you like the job description or a 20-minute introduction? No problem if this is not relevant, and tell me if you prefer no further messages.

Follow-up:
Hi Rowan, following up once on my note about the Product Analyst role. The team is confirming the final reporting line, but the two office days and fictional approved salary range remain as described. If you would like to explore it, I can send the job description. If not, no reply is needed and I will close the thread.

Closure:
Hi Rowan, I am closing the loop on the Product Analyst message. There is nothing you need to do, and I will not send further messages about this opportunity. Thank you for reading.

Where Talent Summoner fits

Talent Summoner is our product for upstream candidate sourcing and ranking. Candidate sourcing can help turn a role brief into a shortlist from public professional sources, while candidate ranking can organise supplied CVs for human review. Neither output authorises contact or proves interest, availability, identity, scope or accuracy.

Talent Summoner does not provide an automated outreach sender, contact database, ATS or candidate communication pipeline. Humans verify sources, choose the basis and channel, send and answer messages, handle opt-outs and interviews, and decide. See pricing for current options and keep records in the approved process.

Wrong fit for this approach

Do not use these templates for a bulk send, unapproved role conditions, an unclear contact basis or sensitive or irrelevant details. Pause when the sender cannot answer basic questions about scope, location, working pattern or next steps.

This is general process guidance, not legal advice. Check applicable channel and location rules, organisational policy and relevant privacy, marketing or employment guidance. Public availability does not remove those checks.

FAQ

Is one public profile detail enough to contact someone?

No. It can support an invitation, but it is not consent or proof of interest. Verify the contact basis, use an appropriate channel and let the person choose.

Should the first message include compensation?

Include it when approved and useful for the person's decision. If it is not approved, say it is being confirmed rather than implying a figure or hiding every material condition.

How many follow-ups should I send?

There is no universal number or schedule. Follow channel rules and policy, keep the follow-up useful and low pressure, honour opt-outs immediately, and close accurately at the chosen review point.

Does Talent Summoner send the message or manage the candidate pipeline?

It can send the message through your connected Google or Microsoft account once you review and confirm it, but it does not send anything unreviewed and does not manage a candidate pipeline. Humans verify evidence, select the channel, answer replies, manage opt-outs and interviews, and decide.

For your next reviewed shortlist, choose one candidate, verify one job-related fact and confirm the approved role conditions. Draft the first message with the template, name the human sender and next step, then record the response or closure in your approved process.

Talent Summoner product facts read from our live candidate sourcing, candidate ranking and pricing pages, verified 19 August 2026. We re-verify this page quarterly — tell us if something changed.