You stop it by keeping one record per phone number and deciding in advance what happens when that number shows up again. A buyer who fills a second form should go back to the agent already working them, or move on only under rules you set. An agent who types in a number that already exists should be stopped. In Whispyr AI, a real estate CRM in Arabic and English, both happen by default: manual duplicates are refused, and a returning buyer updates the existing lead and alerts its agent (checked 3 November 2026).
How the same buyer ends up with two agents
It's rarely bad intent. Usually it's one of these:
- Two forms, two campaigns. The buyer fills your Zayed form on Monday and your October form on Thursday. Each lead goes to whoever's turn it is.
- The buyer calls the office. Whoever answers adds them as a new lead, not knowing a colleague has the same buyer.
- An old lead comes back. A buyer from last year reappears and a new agent adds them from scratch.
- A typo. One digit off, and the CRM sees a new person.
The cost is real. The buyer gets two calls with two prices, trusts neither, and you end up refereeing two agents over a commission.
Step 1: one buyer, one number
Whispyr recognises a buyer by phone number. Every lead from Facebook, Property Finder, Google Sheets or your website is checked against the numbers already in the CRM before it's created. The same number in two formats, such as with and without the leading zero, counts as the same number.
Step 2: decide what happens when a buyer comes back
When a number arrives that's already in the CRM, Whispyr follows a fixed order:
- If the buyer already has a deal, the new enquiry goes to that lead, so the agent who closed with them hears about it first.
- If the lead belongs to an admin, sales manager or sales director, it's updated, not moved.
- Otherwise your duplicate rules run in the order you set. The first rule that matches decides.
- If no rule matches, the fallback applies. By default the existing lead is updated, its priority goes up and its agent is told.
Each rule has conditions on the lead already in the CRM:
- which stage it's in, or any stage
- how long it has been in that stage
- how long since its agent last worked on it
And one action:
- update the existing lead
- create a new unassigned lead and tell the managers
- create a new lead and assign it, to anyone, inside the same team, or outside it, marking both as duplicates
- move the existing lead to a new agent, anywhere, inside the team, or outside it
- move the existing lead to the team leader
You can also leave certain agents out of a rule.
Two rules many brokerages start with:
- If the existing lead is in New Lead and its agent hasn't worked on it for 3 days, move it to a new agent inside the team. The buyer is interested again and the first agent didn't call.
- If the existing lead is in Lost Lead, create a new lead and assign it. The buyer came back, and someone fresh should try.
Step 3: stop agents retyping a number that exists
Leads that agents type in follow one of four settings:
- Block (the default). Whispyr refuses the new lead and tells the agent to contact an admin.
- Allow outside the team. A duplicate can be created, but not on a team that already has that buyer.
- Reassign if in the pool. If the existing lead is in the shared pool, it goes to the agent who tried to add it. Otherwise the new lead is refused.
- Allow anywhere. A duplicate can be created on any team.
Whatever you pick, the same agent can never hold the same number twice.
Typos are covered too. When manual duplicates are refused, you can have a new number that is one digit away from an existing lead's number held for an admin to review, instead of created.
Step 4: clean up what's already there
Admins have a duplicates page listing groups of leads that share a phone number, so you can see where two records already exist and decide which agent keeps the buyer.
What duplicate control can't catch
It matches phone numbers. A buyer who calls from his wife's phone is, to the CRM, a new person. Agents who chat with a buyer on WhatsApp without adding them to the CRM are also outside its view. Ask agents to add every buyer they speak to.
What it costs
On Free you get one duplicate rule, with the four actions that don't depend on teams: update the existing lead, create it unassigned, create and assign, or move it to a new agent. Growth adds as many rules as you need and the team-based actions. Prices from Whispyr's live price list, checked 3 November 2026:
| Plan | Per seat a month | Duplicate rules |
|---|---|---|
| Free | EGP 0, up to 5 users | One rule |
| Growth | EGP 80 | As many as you need |
| Intelligence | EGP 250, EGP 235 from 10 seats | As many as you need |
Plans are monthly with no long-term contract.
Start by keeping manual entry on Block and writing one rule for the stage where your agents fight most.