Contact configuration in Settings > Contacts gets two improvements: a new tab to decide whether repeated phone numbers and emails are allowed, and new checks that stop field rules from being misconfigured or bypassed when a contact is edited.
How to create Property logic rules and conditional options, and how they apply on the contact page and when completing a task, is explained in the Contact property logic article.
1. New Settings tab: duplicate validation
In Settings > Contacts > Settings you'll find the Duplicate validation card, which blocks saving a contact when its phone number or email already exists on another contact.
There are two independent switches:
- Block duplicate phone numbers: rejects creating or updating a contact whose phone number already exists on another contact.
- Block duplicate emails: rejects creating or updating a contact whose email already exists on another contact.
You can keep one on and turn the other off — for example, allow several contacts to share a company email while still blocking repeated phone numbers. Click Save changes to apply.
Where this applies
- When a contact is created or updated manually.
- When contacts are imported from a CSV file.
For now, this check doesn't apply to contacts synced from a connected CRM, and contacts that already exist in your account aren't affected.
What changes for your account
Both switches are on by default. If your account was already blocking duplicates, it keeps working the same way; the difference is that you can now see and change this setting yourself, separately for phone and email.
2. Rules are respected on every edit
Until now, Property logic rules were mainly checked in forms. They're now also checked every time a single contact field is saved, wherever the change comes from:
- When editing a field from the Data tab or the sidebar of the contact page.
- When a workflow fills in or changes a field.
- When a contact submits a WhatsApp Flow.
In all of these cases, the change isn't saved if it:
- Leaves empty a field that a rule has made required for that contact.
- Picks, in a select field, an option that a rule hides for that contact.
Editing a field that has nothing to do with any rule is never blocked.
If a workflow tries to make a change that a rule doesn't allow, that specific action isn't applied and the workflow's other actions run normally. No notice is shown when this happens yet.
3. Rules that can't be misconfigured
When creating or editing rules in Settings > Contacts > Property logic, the system now prevents configurations that couldn't work:
- Repeated rules: the same rule (same condition and same target field) can't be saved twice. You'll see "An identical rule (same condition and target field) already exists".
- Required fields a rule could hide: a field can't be both always-required on a stage and the target of a rule that can hide it, since a contact could end up unable to move forward. This is blocked both ways: when creating the rule and when configuring the stage's required fields.
- Valid options when changing stage: when completing a task or changing stage, besides checking that required fields are filled in, the system checks that the option chosen in each select field is still valid and visible.
- Cleanup when deleting an attribute: if you delete a custom attribute, any conditional-option conditions on other fields that depended on it are removed too, so no option stays hidden forever for no reason.
Remember that while you have an active CRM integration, managing Property logic rules isn't available; the screen itself tells you so.
Relevant scenarios
- Accounts with a high volume of contacts and frequent imports: blocking duplicate phone numbers keeps the same contact from coming in twice and ending up assigned to two different salespeople.
- Companies where several contacts share an email: you can turn off only the email block and keep the phone one.
- Processes that depend on required fields: since rules are also respected by workflows and WhatsApp Flows, the data your process requires can't be wiped along the way.
Conclusion
With the new duplicate validation and the checks on field rules, contact configuration is more reliable: you decide which data can repeat, and the rules you set up are enforced everywhere contacts are edited, without contradictory configurations.
Was this article helpful?