Finding Duplicates with a Blank Phone Number Field

Step 1 of Merge Duplicates is where you define which fields Insycle compares to find duplicate contacts, and which of those fields are allowed to be empty.

Configure Matching Fields

Navigate to Data Management > Merge Duplicates, and select your database and object type. Then configure your matching fields on the Simple tab.

For contacts like Sarah — where a name is consistent but a phone number may or may not be present — a common combination of matching fields is:

• First Name
• Last Name
• Phone Number

On its own, this configuration would still exclude Sarah's two records from matching, since one of them has no phone number.

Allow the Phone Number Field to Be Blank

To let a blank Phone Number field through instead of disqualifying the record:

1. After configuring your matching criteria on the Simple tab of Step 1, click the Conditions tab.
2. Locate Phone Number in the list of matching fields. It will appear with the Value Required in All Records condition selected by default.
3. Change the Condition for Phone Number to Empty Allowed in Any Record.
4. Confirm that First Name and Last Name remain set to Value Required in All Records. At least one field must always require a value in every record — this is the reliable identifier that confirms the records are genuine duplicates.

The image above shows the Conditions tab in Step 1 (Find Duplicates) of the Merge Duplicates module, with First Name and Last Name set to Value Required in All Records, and Phone Number set to Empty Allowed in Any Record.

  Note: The Empty Allowed in Any Record condition requires using at least two matching fields. The Phone Number field cannot be the only matching field if it's allowed to be blank.

With this condition in place, Sarah's two records become eligible for comparison — but that's only half the story. Now Insycle has to decide where the blank-phone record belongs.

Once your matching fields and conditions are configured, click Find to generate a list of duplicate groups.

Records that share the same values in your matching fields are grouped together into duplicate groups. When the Phone Number field is allowed to be blank, a record with no phone number can be matched with a record that has one, but exactly how it's grouped depends on how many other phone numbers are present among the matching records. With a single phone number, the match is straightforward. When more than one phone number is present, Insycle has to decide which one the blank record belongs with, and that decision is worth reviewing before you merge.

A Simple Example: Two Records, One Blank Phone Number

Consider our Sarah Chen contact. She has two records — one from her web form submission, one from her sales call — that are a straightforward case of this condition at work:

• Record 1 (Sarah's web form submission) has no phone number.
• Record 2 (Sarah's sales call) has the phone number 202-456-1234.

Because First Name and Last Name match exactly, and the Phone Number field is allowed to be blank, Insycle groups both records into a single duplicate group. There's no ambiguity here — Record 1's blank field simply doesn't conflict with Record 2's phone number, so the two are matched together.

The image above shows Step 2 (Review Duplicates) of the Merge Duplicates module, with one expanded duplicate group showing two duplicate contacts — Sarah Chen without a phone number and SARAH CHEN with the number 202-456-1234 — that are matched on First Name, Last Name, and Phone Number.

A More Complex Example: Four Records, Two Phone Numbers

How records merge gets a little more nuanced when more than one phone number is present across the group. Suppose there are four contact records sharing the same name — Marta Vaskovitch:

• Record 1 has the phone number 888-555-1200.
• Record 2 has no phone number.
• Record 3 has the phone number 888-555-1212.
• Record 4 also has the phone number 888-555-1212.

Record 2's blank phone number doesn't conflict with 888-555-1200 or 888-555-1212 — technically, it could belong with either. So Insycle has to pick a side, and the outcome plays out in one of two ways.

Outcome 1: Two Separate Duplicate Groups

Here, the blank phone number lands with the first number Insycle compares it against:

• The first duplicate group contains Record 1 (blank) and Record 2 (888-555-1200).
• The second duplicate group contains Record 3 and Record 4 (both 888-555-1212).

The image above shows two separate duplicate groups for Marta Vaskovitch: the first containing Record 1 with a blank phone number, and Record 2 with phone number 888-555-1200, and the second containing Records 3 and 4, both with phone number 888-555-1212.

Outcome 2: One Larger Duplicate Group, with One Record Left Ungrouped

Alternatively, the blank phone number could land with the matching pair instead:

• One duplicate group contains Record 2 (blank), Record 3, and Record 4 (both 888-555-1212).
• Record 1 (888-555-1200) remains on its own because its phone number differs from those of Records 3 and 4.

The image above shows a single duplicate group containing Record 2 with a blank phone number, and Records 3 and 4 with phone number 888-555-1212. Record 1 with phone number 888-555-1200 is excluded and remains ungrouped.

Important: Because either outcome is possible, always review your duplicate groups in Step 2 before merging to confirm that the grouping matches your expectations. If a blank phone number record was grouped with the wrong set of records, adjust your matching fields or conditions and run Find again.

Use the gear button in Step 2 to add more fields to the view for additional context, and review each duplicate group's records before proceeding.

In Step 3, you define how your duplicates are merged. You'll choose your operation mode, set rules for which record becomes the master, and optionally control which field values are retained after the merge. 

Choose Your Operation Mode

At the top of Step 3, select:

• Bulk mode (recommended) — Automatically merges all duplicate groups according to your master selection rules. Required for Templates, Recipes, and Automation.
• Manual mode — Lets you select specific records to merge one at a time from the Record Viewer. Reserve this for high-value records or groups where the blank phone number grouping needs individual review.

The image above shows the Bulk and Manual mode selector in Step 3 (Merge Logic) of the Merge Duplicates module, with Bulk mode selected (highlighted by a teal rectangle callout) and the Master tab active.

Configure Master Selection Rules (Automatically Decide Which Records to Merge Others Into)

On the Master tab, define which record becomes the master in each duplicate group. Insycle evaluates your rules in order from top to bottom, and the first record that uniquely matches a rule becomes the master.

Note: When a duplicate group includes a record with a blank phone number, consider whether that record should be prioritized as the master or treated as the duplicate. In most cases, it makes more sense for the record with a phone number already present to become the master. Prioritize records with a non-empty Phone Number field in your Master rules.

The image above shows the Master tab in Step 3 (Merge Logic) of the Merge Duplicates module, with Phone Number configured with an "exists" condition as a master record selection criterion.

Learn more about configuring these options in the Choosing Which Record Remains After a Merge article.

Customize Field Data Retention

On the Fields tab, control which field values are retained in the master record after the merge. By default, Insycle keeps the master record's values and fills any empty fields with values from the most recently updated duplicate — so if the master record has a blank Phone Number field, the merged record automatically inherits a phone number from another record in the group, if one exists. This means a record with a blank Phone Number field in the group — where the master might otherwise be missing that value — retains the phone number after the merge.

Learn more about configuring these options in the Keeping the Right Data When Records Merge article.

Before applying any changes to your CRM, always run a preview.

1. Under Step 4, click Review and select Preview mode.
2. On the Notify tab, select recipients for the email report.
3. On the When tab, click Run Now to generate the preview.
4. Open the CSV report from your email and confirm that duplicate groups containing a blank phone number were grouped and merged as expected.
5. If the preview looks correct, return to Review, select Update mode, and click Run Now to apply the changes to your CRM.

The image above shows the When step (Step 3) of the Merge Duplicates run dialog, on the Run Now tab, with All selected as the run scope.