← All posts

CRM

Deduplicating Follow Up Boss contacts after Ai routing

Ai lead routers create duplicate contacts in Follow Up Boss faster than any human ever did — here is how to fix the records before the damage compounds.

Every brokerage that runs an Ai lead router eventually hits the same wall. A buyer submits a Zillow form, texts a yard-sign number, and fills out a website chat widget — all within 48 hours. The Ai router treats each channel as a new lead, creates three contacts in Follow Up Boss, and assigns each one to a different agent. Nobody notices until the buyer calls the office annoyed, two agents have already followed up, and your pipeline report shows three "active" prospects who are actually one person.

This is not a hypothetical. Say a mid-size team runs 40 inbound leads a week across four channels. After six months of Ai routing without a deduplication step, they might easily have 300 ghost contacts inflating their pipeline and skewing their lead-source reporting. The fix is not to remove the Ai router — it is to build the dedup layer that the router never had.

Why Ai routers create duplicates

Most Ai routing setups — whether built on Zapier, Make, or a custom webhook — create a contact record the moment a lead arrives. The logic is simple: receive payload, parse name and phone, POST to Follow Up Boss API. The problem is that the creation step rarely includes a lookup first. Looking up an existing contact requires an extra API call, handling partial matches ("Bob Smith" vs. "Robert Smith"), and deciding what to do when a match is fuzzy. Teams skip that step to keep the router fast, and duplicates accumulate silently.

Follow Up Boss does have a built-in duplicate detection UI, but it surfaces matches only after the fact, one by one, and relies on exact email or phone matching. If a buyer used their cell for one form and their work email for another, Follow Up Boss will not catch it automatically.

Building a lookup-before-create step

The cleanest fix is to gate every contact creation behind a search call. Before the router posts a new record, it queries the Follow Up Boss API for the incoming phone number and email. If a match comes back with a confidence level you define — same phone, or same email, or same first name plus close-enough last name — the router updates the existing record instead of creating a new one and routes the lead to whoever already owns it.

In practice, the lookup step adds roughly 400 milliseconds to the routing time. That is acceptable for a lead that arrived 90 seconds ago. The router can also log a "source added" note on the existing contact so the agent knows the buyer came in through a second channel.

If you are building this in Make or a custom webhook handler, the sequence looks like this: receive the lead payload, extract phone and email, call Follow Up Boss search, evaluate the response, branch to update-existing or create-new. The branch is the piece most routers skip.

Cleaning up the records already in your CRM

The lookup step prevents new duplicates. It does not fix the ones already sitting in the database.

A cleanup audit starts with a data export. Pull every Follow Up Boss contact record — name, phone, email, assigned agent, created date, and lead source. Load that into a spreadsheet or a simple script that flags any phone number or email appearing more than once. That gives you a candidate list; a human or a second automated pass then confirms true duplicates versus people who share a phone (spouses on the same deal, say).

Once confirmed, Follow Up Boss allows contact merging through its UI, though it is manual at scale. For a team sitting on a few hundred duplicates, a CSV-driven bulk merge using the API is worth building — it takes a list of duplicate pairs, moves all notes, tasks, and deal history onto the primary record, and archives the duplicates. The result is a pipeline report you can actually trust.

This is the kind of work that is worth auditing before adding any new Ai layer to your CRM. At Real Estate Ai Group, the first step before building a router or an automated nurture sequence is to look at the state of the records in the CRM — because a clean dedup process downstream of a dirty database just moves the problem.

The reporting problem you did not know you had

Duplicate contacts do more damage than cluttered records. They inflate your lead count, which makes your close rate look worse than it is. They split activity history across two records, so an agent reviewing a contact before a call sees only half the story. And if you are running automated follow-up sequences, a buyer with two active records is getting two separate nurture tracks simultaneously — which will eventually surface in a confused or annoyed reply.

A team that cleans up 300 duplicates often finds their real pipeline is 15 to 20 percent smaller than reported, but their lead-to-appointment conversion rate looks significantly better. Neither number was wrong — the database just made it impossible to read them accurately.

Where to start

Pull a full export of your Follow Up Boss contacts, sort by phone number, and count how many numbers appear more than once. If that number is above 5 percent of your total contact count, you have a deduplication problem worth solving before you add any new automation to your CRM.

Want this appliedto your team?Ask us.

Or write to ushello@realestateaigroup.com

Skip the reading — a 30-minute call is enough to tell you what’s realistic.