How FreJun Determines the Relevant Zoho CRM Record for a Shared Phone Number?
When multiple records in Zoho CRM have the same primary contact number, the system uses a predefined lookup order to determine which record should be displayed. This is expected behavior and can occur when different users are saved as separate contacts under the same company number.
How Does the Phone Number Lookup Work?
When a call is received or initiated, the system searches for the phone number across Zoho CRM modules in the following order:
- Contacts
- Accounts
- Leads
The system first checks the Contacts module for a matching phone number. If no matching record is found, it then checks Accounts, followed by Leads.
What Happens When Multiple Records Have the Same Number?
If the same phone number exists in multiple records within the same module, the system uses the most recently modified record to determine which record is displayed. For example, if two Contacts have the same primary phone number, the Contact that was modified most recently will be prioritized and displayed.
ExampleSuppose the same phone number is associated with:
- Contact A – modified earlier
- Contact B – modified more recently
If both records are present in the Contacts module, the system will display Contact B, as it was modified most recently. Similarly, if the number exists in both Contacts and Accounts, the Contacts record will take precedence because Contacts have a higher lookup priority.
Is This an Issue?
No. This is the default system behavior for handling multiple CRM records with the same phone number. The system follows the predefined module priority and, where multiple matching records exist within the same module, uses the most recently modified record.
Summary :-| Scenario | System Behavior |
|---|---|
| Number found in Contacts | Contacts record takes priority |
| No match in Contacts, but found in Accounts | Accounts record is displayed |
| No match in Contacts or Accounts, but found in Leads | Leads record is displayed |
| Multiple matching records in the same module | Most recently modified record is prioritized |