Duplicate Lead warnings
Understand soft duplicate awareness, when warnings appear, and when creating another Lead is correct.
WebPro CRM warns about a possible duplicate when the entered email address or normalized phone number matches an existing visible Lead in the same workspace.
The warning does not block you
Review the existing Lead’s number, name, company, email, and status. Choose View Existing Lead when it is the same enquiry, or Create Anyway when the new record is legitimate.
The lookup is restricted to the current workspace and to Leads the signed-in user is allowed to view. A warning never reveals a record from another workspace or bypasses Lead visibility rules.
Same company is not a duplicate
Two legitimate Leads at one company
Rahul Sharma at Acme Commerce uses rahul@acme.example.
Priya Sharma at Acme Commerce uses priya@acme.example.
These are valid separate Leads. Company name and person name alone do not trigger a duplicate warning.
Phone formatting
Formatting differences such as +91 99679 79608 and 919967979608 can identify the same underlying number. The system avoids country-specific assumptions beyond comparing a safe normalized digit representation.
Common examples
Same company, different people
Rahul Sharma and Priya Sharma may both work at Acme Commerce. If their email addresses and phone numbers differ, the company match alone does not make either Lead a duplicate.
Same email with different capitalization
Rahul@Acme.example and rahul@acme.example may refer to the same address. Email comparison is case-insensitive for duplicate awareness, so review the suggested Lead.
Same phone with different presentation
+91 99679 79608 and 919967979608 may represent the same underlying number. Spaces, brackets, and hyphens should not be used to create a second record without checking the first.
Same person, new legitimate enquiry
A returning person may start a genuinely separate sales enquiry. Review the existing Lead’s status and context. If combining the conversations would be misleading, choose Create Anyway and record enough context to distinguish the new enquiry.
Decide what to do
Use View Existing Lead when the suggested record represents the same prospect and sales conversation. Update that record, add the new interaction, and create the next follow-up instead of splitting history.
Use Create Anyway when the match is coincidental, the same person has a distinct enquiry that should be tracked separately, or a shared contact method is legitimately used by different people. Add a useful Note so colleagues understand why two records exist.
On edit, the current Lead is excluded from matching itself. A temporary duplicate-check failure does not prevent saving; validation and authorization remain server-controlled.
Avoid these mistakes
- Treating a shared Company name as proof of duplication.
- Creating another Lead only because phone punctuation changed.
- Ignoring the existing record’s status and owner.
- Assuming a warning means the CRM has merged or blocked anything.
- Entering altered contact data merely to avoid a warning.