Recruitment Industry

Database Reactivation in a Tighter Talent Market: Turning Dormant Candidates and Clients into 2026 Placements

By Andrew Nicholson · Published 24 June 2026 · 6 min read

Hiring hasn't got easier this year - it's just changed shape. Application volumes are up, but the candidates and clients worth chasing are harder to identify, and everyone is being more selective about who they engage with and why. In that environment, the most expensive thing an agency can do is keep paying for new leads while ignoring the database it already owns.

Most agencies are sitting on years of candidates who were never placed, clients who went quiet after one campaign, and contacts who simply went cold because nobody followed up at the right moment. That database is usually the single largest, cheapest, and most underused source of placements available.

Key findings

  • A generic, unsegmented reactivation blast performs like spam - because functionally, it is.
  • Re-engaging old contacts carries genuine PECR compliance risk if consent has gone stale - "they were already in our database" isn't a defence on its own.
  • Pulling live ATS status, not a static export, is what separates a relevant message from an embarrassing one.
  • A short sequence of 2-3 emails converts far better than a single send to a cold contact.

Why "Spray and Pray" Reactivation Doesn't Work Anymore

The instinct when someone says "reactivate the database" is to export the list and blast everyone with the same template. Two things go wrong with that approach.

It performs badly. A generic "we haven't spoken in a while" email to thousands of contacts with no segmentation typically gets treated as spam, because it is, functionally, spam - it ignores everything you actually know about each person.

It carries real compliance risk. Re-engaging old contacts under PECR rules isn't the same as emailing someone who opted in last week. If you can't show a legitimate basis for re-contacting someone, or you're relying on consent that's gone stale, you're exposed - and "they were in our database already" is not a defence on its own. Any reactivation campaign should be checked against your current compliance position before it goes out.

What a Proper Reactivation Playbook Looks Like

  1. Segment by status, not just recency. A candidate placed elsewhere six months ago needs a completely different message to one who simply went quiet mid-process. Pulling current status from your ATS - rather than working off a static export - is the difference between a relevant message and an embarrassing one ("are you still looking?" to someone who's been in a new role for a year).
  2. Check engagement data before you trust it. If you're prioritising who to reactivate first based on old open and click data, make sure that data reflects real human behaviour rather than security scanners and email previews. Otherwise you'll end up calling the wrong people first, which defeats the point of segmenting at all. See our piece on why your engagement data might be lying to you for more on this.
  3. Personalise off history, not just name and job title. What role were they last in process for? What did they tell a consultant about their reasons for moving (or not moving)? A message referencing the actual context lands completely differently to a generic "checking in."
  4. Sequence rather than one-and-done. A single email to a cold contact is easy to ignore. A short sequence of two or three emails, spaced out and each building on the last, followed by a call to contacts who showed genuine signs of life, converts far better than a single blast.
  5. Feed outcomes back into the ATS automatically. Whatever happens (replied, booked a call, opted out, came back as a live candidate) should write back into Vincere, Firefish, or Bullhorn without someone manually updating records. Otherwise the next campaign starts from the same stale data as this one.

The Same Logic Applies to Dormant Clients

Everything above applies just as well to client-side reactivation. A hiring manager who used you once two years ago and went quiet isn't a dead lead - they're a warm relationship that needs the right trigger. The most reliable trigger is usually sitting in your own data already: a contact who opens an email after months of silence, clicks through to content for the first time in a year, or shows fresh activity on their ATS record. Reaching out automatically the moment that happens - rather than days later when someone notices manually - converts far better than a generic "just checking in" email sent on no particular schedule.

Why This Is Harder Than It Sounds Without the Right Setup

None of this is conceptually difficult. It's operationally difficult, because it requires your marketing platform and your ATS to actually agree on who's who, what's current, and what's already been said. Bolt-on tools that work from a CSV export go stale the moment someone's status changes. A genuinely bidirectional sync with Vincere, Firefish, or Bullhorn means your reactivation segments, your messaging, and your compliance position are all working off the same live picture - not a snapshot from three months ago.

In a market where new leads are more expensive and harder to qualify than they used to be, the agencies that do well in 2026 won't be the ones sending the most outreach. They'll be the ones doing the best job of remembering - and acting on - everyone they already know.

If you want to see what a proper reactivation segment of your own database looks like - based on live ATS status, not a static export - we're happy to run it as part of a demo.

Frequently Asked Questions

Why doesn't a generic database reactivation email campaign work?

A single templated email sent to thousands of dormant contacts with no segmentation typically performs like spam, because it ignores everything already known about each contact. It also carries real PECR compliance risk if there's no clear, current legitimate basis for re-contacting people whose consent may have gone stale.

What should a proper database reactivation playbook include?

Segmentation by current ATS status (not just recency), engagement data that's been filtered for bot activity, personalisation based on real history rather than just name and job title, a multi-email sequence rather than a single send, and automatic write-back of outcomes into the ATS.

Andrew Nicholson

Andrew Nicholson

Co-founder & CEO at Kulea. Guest lecturer in digital psychology and behavioural economics at the University of Buckingham.

Ready to put your database back to work?

Book a demo