A family contacts your community through your website in early October. Your team speaks with them, enters them into the CRM, and begins the follow-up process.
Three weeks later, A Place for Mom sends you the same family as a new lead.
The same person and the same situation, but the name is spelled slightly differently (Steven versus Stephen) and nobody catches it.
That family eventually moves in and you pay A Place for Mom a move-in fee for a lead you already had in your database.
This is a systemic gap that can cost senior living communities tens of thousands (if not hundreds of thousands) of dollars a year.
Lead aggregators like A Place for Mom and Caring.com operate on a performance model where you only pay when a prospect referred by their platform moves into your community.
These platforms have duplicate lead policies, and if you can prove that a lead was already in your database before the aggregator sent it to you, and you report it within the required time window, you are not obligated to pay the move-in fee when that person converts.
A single avoided move-in fee can be $3,000, $5,000, or more.
If you multiply that across dozens of leads in a year, across a portfolio of communities, you may be looking at a six-figure exposure that you may not even be aware of.
The problem is that claiming duplicates requires someone to actually take the time to do the checking and then submit in accordance with the policies and time window that is required.
The obvious answer is time.
A senior living sales director managing 60 to 80 active leads, giving tours, handling move-in logistics, and fielding calls does not have the capacity to cross-reference every incoming aggregator lead against the full history of their database.
But time isn't the only problem.
There are three other patterns that cause communities to miss duplicates even when the intent is there.
Lead aggregators transcribe prospect information and spelling errors can happen. Steven becomes Stephen. Robert becomes Bob. Joseph gets entered as Joe. If your team is doing a simple name-match search, those variations won't surface.
A thorough duplicate check has to account for common nicknames, alternate spellings, and the difference between the contact person (often an adult child) and the potential resident, who may be listed under a different name entirely.
A family might have multiple people filling out forms across many different websites to cover their ground. They visit A Place for Mom. They also visit Caring.com. They may have also found your website directly. If all of those inquiries arrive within a short window, any one of them could become a legitimate duplicate claim against any of the others.
The policy allows you to report duplicates to both APFM and Caring for the same underlying lead, but that only helps you if someone is actually tracking the chain of events.
Each aggregator has a specific time window within which a duplicate must be reported and if you miss that window, the claim is gone, regardless of whether the lead was legitimately already yours. In a busy sales environment, that window can pass unnoticed, not because no one cares, but because no one's job is to watch for it.
"If you were to type in their name as transcribed to us by the lead aggregator, you wouldn't have caught it. But we think of other ways that name can be spelled. Robert and Bobby, Joseph and Joe. That's what saved the community the move-in fee." — Bob Torchetti, NextWave
When NextWave receives a lead from a referral aggregator, our team immediately cross-references it against the community's full database, not just the current active leads, but the complete history of every prospect who has ever been in the system.
That search runs across multiple identifiers:
When we find a match, we report it to the aggregator immediately, using their required process, and document everything in the CRM so there's a clear paper trail if proof is ever needed. Both APFM and Caring have different reporting mechanisms, and we follow each one precisely to make sure the dispute is airtight.
The result is that communities we work with catch dozens of duplicates per year.
The cumulative savings across a portfolio can exceed $100,000+ annually in avoided move-in fees.
Duplicate checking is invisible when it works.
No one throws a celebration when a duplicate is caught and reported because it doesn't show up on an occupancy dashboard or make the monthly sales summary look better.
The cost becomes visible when it doesn't happen, and a lead slips through, a window closes, and a move-in fee gets charged for a family you already had in your system. By then there is nothing you can do about it.
The challenge for most senior living communities is their capacity to do the checking. The sales director who knows this should be happening doesn't have three hours a week to run duplicate checks across multiple databases and multiple aggregators with different rules and deadlines. This is just a structural reality of how the sales role is designed.
Building a reliable duplicate checking process means having dedicated eyes on every inbound lead, every day, from someone whose only job is to catch these things before the clock runs out.
↳ Referral aggregators have duplicate lead policies. If you can prove a lead was already in your database before they sent it, you don't owe the move-in fee, but only if you report it on time.
↳ Spelling variations are the most common reason duplicates go undetected. A name search alone won't catch Robert vs. Bobby or Steven vs. Stephen. You need to account for nicknames, alternate spellings, and both the contact and resident name.
↳ The same lead can qualify as a duplicate to multiple aggregators simultaneously. Tracking source history across platforms is the only way to catch all of your valid claims.
↳ There's a hard reporting window. Miss it and the claim is gone, regardless of the facts. Speed and consistency aren't optional in this process.
↳ Communities working with NextWave save over $100,000 per year in avoided move-in fees through systematic duplicate checking, savings that compound across a portfolio.
↳ This work is invisible when done right. The cost only becomes visible when it stops happening.
Pull the last 12 months of move-in fees you paid to A Place for Mom and Caring.com. Then ask: for each of those move-ins, was the prospect already in your database before the aggregator sent the lead?
If you can't answer that question with confidence, or if you don't have documentation showing that each lead was checked and reported when applicable, you're likely carrying a duplicate exposure that nobody on your team has the bandwidth to close.
The fix isn't complicated, but it does require someone whose job it is to do this, every day, for every incoming lead, without exception.
Want more like this? Subscribe to The Follow-Up, our monthly newsletter with insights on speed-to-lead, follow-up systems, and how to turn inquiries into tours and move-ins.
NextWave helps senior living communities optimize every stage of the lead-to-tour pipeline through the Occupancy Advantage System™. Our team handles the micro-level optimization that community sales directors don't have time for — from nurture sequence testing to CTA placement to send-time analysis — across entire portfolios. Book a call to learn how small improvements in your existing lead flow can produce outsized results.