Refolk
October 26, 2026·9 min read

Talent Rediscovery Agents from Dayforce and Paylocity: Re-Source First

Dayforce's Ribbon deal and Paylocity's rediscovery agent match on résumés frozen at application. How to refresh past applicants before an agent texts them.

talent rediscoveryAI talent rediscovery ATSsilver medalist candidatesre-engage past applicantsDayforce Ribbon AI acquisition
Talent Rediscovery Agents from Dayforce and Paylocity: Re-Source First

If your HCM vendor is about to point an AI agent at your old applicants, the question isn't whether rediscovery works. It's whether the agent knows who those people are today.

On October 23, 2026, Dayforce agreed to buy Ribbon AI, whose talent rediscovery search has reportedly been tested on as many as 30 million candidates in a single applicant tracking system. A day earlier, Paylocity launched a Talent Rediscovery Agent of its own.

What did Dayforce and Paylocity actually ship?

Both companies shipped AI agents that search past applicant records, match them against open roles and help recruiters re-engage past applicants. In Ribbon's case that outreach runs over SMS, WhatsApp and email. Both match against the record as it stood on the day the person applied.

Talent rediscovery means finding qualified people already sitting in your ATS or CRM, usually past applicants and finalists, instead of sourcing from scratch. Here's what each vendor has said:

  • Dayforce and Ribbon AI. Dayforce announced the agreement on October 23, 2026. It didn't disclose the price or the closing date. Ribbon was founded in 2022 by CEO Arsham Ghahramani and COO Dave Vu, and raised $8.2 million in early 2025 in a round led by Radical Ventures. It claims hundreds of customers and more than one million completed interviews.
  • Paylocity Recruiting Optimizer. Launched October 22, 2026, its Talent Rediscovery Agent surfaces previous applicants who match current hiring needs and summarizes their prior application and interview activity for the recruiter to review. Paylocity says the product improves recruiter productivity by 35%, fills roles 25% faster and cuts candidate drop-off by 15%. Those are vendor numbers that nobody has checked independently.

Look at what goes into each agent. Paylocity's reads the prior application and the prior interview. Ribbon searches candidates "within their existing talent pools." Neither announcement describes pulling the person's current title, employer or public activity before the outreach goes out.

Ribbon (Dayforce)Paylocity Talent Rediscovery Agent
AnnouncedOct 23, 2026 (acquisition)Oct 22, 2026 (launch)
What it readsExisting ATS talent poolPrior application and interview activity
Stated scaleUp to 30M candidates in one ATSNot stated
OutreachSMS, WhatsApp, emailSummaries for recruiter review

Does talent rediscovery actually work?

Yes. The best evidence is Gem's 2026 Recruiting Benchmarks Report: rediscovered candidates made up 46% of sourced hires, up from 26% in 2021. But that number comes from recruiters choosing who to contact, not from automated blasts.

46%
Share of sourced hires who were rediscovered candidates
Gem's 2026 benchmark, up from 26% in 2021, counting sourced hires only, not all hires.

Check the denominator. The figure is 46% of sourced hires, meaning hires that came from outbound searches where a recruiter picked the person, read the record and decided to reach out. That's evidence that your ATS is full of good people. It isn't evidence that an agent texting thousands of them on default settings converts at the same rate.

The mechanism matters. A human sourcer opening a 2024 record checks LinkedIn almost by reflex and sees that the person is now a director, or has left the industry. The 46% includes that judgment. Take it out and the same database produces a different result.

So the Gem number supports refreshing records more than it supports auto-texting. Rediscovery works when someone looks at the person as they are now.

How fast do old applicant records go stale?

In frontline and early-career hiring, a two-year-old applicant record is more likely out of date than current. Bureau of Labor Statistics data puts median tenure at 2.7 years for workers aged 25 to 34, and leisure and hospitality had the lowest median tenure at 2.1 years as of January 2024.

GroupMedian tenureSource
All workers (Jan 2026)4.1 yearsBLS, via Rewordin
Ages 55 to 649.6 yearsBLS
Ages 25 to 342.7 yearsBLS
Leisure and hospitality (Jan 2024)2.1 yearsBLS, via Caprelo

Dayforce frames the Ribbon deal around high-volume hiring. In a sector with 2.1-year median tenure, the person behind a 2024 application has quite possibly changed jobs since.

Don't read too much into the precision. Median tenure is a snapshot of people currently in jobs, not a measure of how fast any given applicant moves. But it shows which way the error runs. The younger and more frontline your applicant pool, the more of your ATS describes people who no longer exist in that form.

What the Ceridian vs Dayforce gap reveals about stale data

Self-reported skills lag reality by years. In Refolk's index of professional profiles, US profiles listing "Ceridian" as a skill still outnumber those listing "Dayforce" 3.4 to 1, more than two years after Ceridian renamed itself Dayforce in February 2024.

3.4x
US profiles listing "Ceridian" vs "Dayforce" as a skill
In Refolk's index, more than two years after the company renamed itself.
Skill listedUS profiles (Refolk's index)
Paylocity7,315
Ceridian (old name)4,520
Dayforce (current name)1,329
Ceridian ÷ Dayforce3.4x
Paylocity ÷ Dayforce5.5x

One caveat: the Ceridian and Dayforce groups overlap. The same employers (SPARC Group, BrandSafway) and the same titles appear in both samples, so don't add them together. The ratio is the finding.

That ratio comes from live profiles, the kind people at least occasionally open and edit. An old job application is worse, because nobody ever edits it. It's a record frozen on the day the person clicked submit. If people don't update a skill after the vendor changes its name, they won't go back to an ATS and tell you they were promoted.

A rediscovery agent matching keyword against keyword makes the same mistake at scale. Its idea of who has which skill, title and level is as old as the record.

An agent reading a frozen résumé doesn't know the candidate was promoted. It only knows they once applied.

Why defaults and per-action billing push agents toward volume

Most rediscovery outreach will run on vendor defaults: about 90% of Ribbon customers use the recommended default configuration, according to the acquisition announcement. In practice that likely means nobody on your team looks at a given message before it goes out.

Two forces push in the same direction:

  1. Defaults aren't tuned to you. A vendor default is built for the average customer. It doesn't know your tolerance for texting someone about a job two levels below where they are now.
  2. Usage-based pricing may charge per action. One secondary source on Paylocity's contracts says each automated screening, scheduling, bulk engagement or talent rediscovery action counts as an "Action" against an allocation set in the order. I could only find that one source, so treat it as unconfirmed. If it holds, every pointless message to someone who has outgrown the role costs money as well as goodwill.

The cheapest fix comes before the agent runs. Every past applicant you drop from a list because they've since become a VP, moved to another country or left the field is one less action you pay for and one less "why are you texting me about a shift lead job" reply.

How to re-source silver medalist candidates before the agent texts them

Re-check each person's current title, employer and recent public activity, then decide who the agent may contact. Silver medalist candidates are finalists who reached the last round of an earlier search and lost narrowly. A finalist from two years ago, in an age group with 2.7-year median tenure, may now be at a different level or a different employer.

A workable sequence:

  1. Export the agent's shortlist before outreach is switched on. Get between the matching and the messaging.
  2. Bucket by record age. Anything older than about two years in frontline roles, or older than 2.7 years for applicants who were 25 to 34 when they applied, should be treated as unverified.
  3. Refresh current title and employer. Check whether the person has moved up, moved sideways or left the industry.
  4. Check recent activity where it's relevant. For technical roles, recent GitHub commits or a new LinkedIn post tell you whether the skill on the 2024 résumé is still in use.
  5. Re-level the match. A former silver medalist for a senior role who is now a manager elsewhere needs a different role, a different message, or no message.
  6. Retire the old interview summary. Paylocity's agent summarizes prior interview activity. That's useful background, but an 18-month-old debrief shouldn't be the basis for a new pitch.
  7. Only then let the agent send, and only to the refreshed, re-leveled list.

Step 3 is where this usually breaks down, because checking 400 records by hand isn't anyone's job. That's the gap Refolk closes: you paste in names and last-known employers in plain English and get back each person's current title, employer and public footprint across LinkedIn, GitHub and the open web.

Sometimes the refresh brings bad news. You run the check and find that your strongest 2024 finalists are now staff engineers at better-funded companies, or have left the city, and the rediscovery list that looked like 30 warm leads is really four. Now you're back to a cold search on a hard-to-fill role, with the hiring manager expecting the speed the vendor promised, and the obvious fallback is an agency fee.

For the records that survive the refresh, write the outreach yourself or at least edit the template. "You applied for X in 2024" is the agent's default opener. "You've moved into Y since you applied, and this role is built around that" is the one that gets replies.

What Ribbon customers on Greenhouse or Workday should ask now

If you use Ribbon on top of a non-Dayforce system, ask about continuity now. Ribbon lists integrations with Greenhouse, Workday, UKG, SAP SuccessFactors, Bullhorn and others, and the October 23 announcement doesn't say whether Ribbon will keep selling to those customers.

Questions to put to your Ribbon account manager, or to Dayforce, whose founder and CEO is David Ossip:

  • Integration roadmap. Will the Greenhouse, Workday, UKG, SuccessFactors and Bullhorn connectors still be supported after closing, and for how long?
  • Data enrichment. Does the agent pull any current data on a candidate before outreach, or does it match only on the stored record?
  • Defaults. What do the recommended defaults do about record age? Is there a recency cutoff, and can you set one?
  • Message volume. How many messages did your instance send last quarter, and how many went to records older than two years?
  • Opt-outs and audit. Who reviews outreach that goes out over WhatsApp or SMS in jurisdictions with stricter consent rules?

Paylocity customers should ask the same questions about Recruiting Optimizer, whose product side is led by Melissa King, Paylocity's SVP of Products & Technology. Ask whether talent rediscovery actions count against a usage allocation, and whether the agent's summaries flag how old the underlying application is.

Whatever the answers, the refresh step belongs to you, not the vendor.

FAQ

Does AI talent rediscovery in an ATS actually produce hires?

Rediscovery as a practice clearly does. Gem's 2026 benchmark found rediscovered candidates made up 46% of sourced hires, up from 26% in 2021. That figure comes from recruiter-led sourcing, though, so it doesn't prove that automated SMS or WhatsApp outreach to old applicants converts at the same rate. Treat the agent's ranking as a starting list and verify it before anyone is contacted.

How old is too old for a past applicant record?

There's no fixed cutoff, but BLS tenure data gives a useful rule of thumb. Median tenure is 2.7 years for workers aged 25 to 34 and 2.1 years in leisure and hospitality, so records older than about two years in frontline or early-career roles should be treated as unverified until you've confirmed the person's current title and employer.

Will the Dayforce Ribbon AI acquisition affect customers on other ATS platforms?

Dayforce hasn't said. Ribbon lists integrations with Greenhouse, Workday, UKG, SAP SuccessFactors, Bullhorn and others, and the October 23, 2026 announcement disclosed neither a closing date nor plans for those connectors. If you depend on Ribbon outside Dayforce, ask for the integration roadmap in writing now.

The data behind this

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next