Keep a talent community warm with useful permission-based contact

Define who the community serves

Choose a genuine shared interest, such as a professional craft, future early-career opportunities, or a function the company hires regularly. A database of old applicants is not automatically a community. Write what participants can expect, who maintains the relationship, and what the company hopes to learn. Keep the purpose narrow enough that messages remain relevant.

Capture preferences at entry

Ask what roles, locations, or subjects interest the person and how they want to hear from the company. Record the context of the connection and follow organisational data practices. Do not preserve speculative notes or treat attendance at one event as permanent interest. Make it straightforward for someone to update preferences or leave.

Offer value between vacancies

Share useful, honest material: how a team approaches a craft problem, what a future hiring process involves, or an invitation to a relevant conversation. Avoid pretending every update is exclusive or urgent. The tradeoff is a smaller volume of more considered communication, which demands editorial care but respects why people joined.

Create a sustainable cadence

Choose a frequency the team can maintain and assign a real owner. Review engagement qualitatively, including replies and preference changes, rather than chasing a broadcast count. Pause messages when there is nothing useful to say. A reliable quiet period is better than filler that teaches people to ignore future contact.

• Shared purpose is explicit.
• Contact preference is recorded.
• Every update has a reason.
• Re-entry requires fresh interest.

Invite, do not presume

Illustrative example: a designer joined a product craft mailing list after an event eighteen months ago. A new role appears with relevant research ownership. The recruiter sends a short note connecting the role to the person’s stated interest and asks whether they would like details. The message does not imply candidacy, reveal old assessment notes, or assume their location and priorities are unchanged.

Audit community health

Quarterly, sample recent messages and ask whether each matched the stated purpose. Remove outdated segments through the company’s established process, correct ownership gaps, and inspect whether the community reaches varied backgrounds. If it exists only to advertise jobs, call it an alert list and set expectations accordingly. Clear naming is part of honest candidate communication. Ask a few consenting participants what they expected and which contact felt useful. Their answers can reveal a mismatch between internal intent and recipient experience that open or click counts cannot explain.