---
title: "Matching Mobile Phone Numbers in Consolidate Records"
slug: "matching-mobile-phone-numbers-in-consolidate-records"
updated: 2026-07-21T20:40:57Z
published: 2026-07-21T20:40:57Z
canonical: "knowledge.technolutions.net/matching-mobile-phone-numbers-in-consolidate-records"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://knowledge.technolutions.net/llms.txt
> Use this file to discover all available pages before exploring further.

# Matching Mobile Phone Numbers in Consolidate Records

Custom person-scoped fields marked as unique for merging can be used as additional matching criteria in Consolidate Records. To match on mobile phone number, create a custom field to store a normalized phone value, then use a rule to populate that value from the person mobile phone number.

> [!WARNING]
> 📝 Note
> 
> Only use a phone value as unique for merging when it fits your institution’s duplicate review practices. Shared household phone numbers, recycled phone numbers, and international number formatting can affect match quality.

> [!TIP]
> ⭐ Get Inspired
> 
> This article was adapted from [a post by Technolutions staff](https://community.technolutions.net/get-inspired/post/workaround-for-matching-on-mobile-phone-in-consolidate-records-u23RfLfaWGNrx6M) in the Slate Community Forums' Get Inspired space. Have a great idea for a Get Inspired post? [Let us know](https://community.technolutions.net/get-inspired/new?post_type=gnHx7As1gZ8r6Ld)!

## Create the custom field

1. Go to **Database → Fields**.
2. Create a person-scoped field to store the normalized mobile phone value.
3. Set **Unique for Merging** to **Value contains a unique ID which identifies a single record for merging**.
4. Select **Save**.

![Person-scoped Mobile ID field configured as unique for merging](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/01-SepTyOlvD3vlhwskTvGOo.webp?sv=2026-02-06&spr=https&st=2026-11-15T17%3A39%3A12Z&se=2026-11-15T18%3A39%3A12Z&sr=c&sp=r&sig=sEOI08GvyleepKKHbb0bkMkgXWdn8nI4x9emF1AhA10%3D)

After creating the field, refresh the Fields cache, the Configurable Joins library, and the template library.

## Create the rule

1. Create a rule that sets the custom Mobile ID field when a mobile phone number exists.
2. In the rule action, configure the custom field with **Replace Values from Formula**.
3. Add an export for the mobile phone number and rename it to a friendly variable, such as `Person-Mobile-Phone`.
4. Edit the export and set **Format Type** to **Formula/Custom SQL**.
5. Use `@val` in the formula and remove common phone number formatting characters.

```Formulamask
replace(replace(replace(replace(replace(replace(@val,'-',''),'(',''),')',''),',',''),'+',''),' ','')
```

![Rule action configured to replace Mobile ID values from a formula](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/02-95T43kcLp8Qbv4M7EJbmH.webp?sv=2026-02-06&spr=https&st=2026-11-15T17%3A39%3A12Z&se=2026-11-15T18%3A39%3A12Z&sr=c&sp=r&sig=sEOI08GvyleepKKHbb0bkMkgXWdn8nI4x9emF1AhA10%3D)

![Mobile phone export formatted with a Formula Custom SQL mask](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/03-V8Bl08r5nyAHmXUadK4m2.webp?sv=2026-02-06&spr=https&st=2026-11-15T17%3A39%3A12Z&se=2026-11-15T18%3A39%3A12Z&sr=c&sp=r&sig=sEOI08GvyleepKKHbb0bkMkgXWdn8nI4x9emF1AhA10%3D)

#### Try a Slate example 💼

Copy this [Suitcase](https://knowledge.technolutions.net/docs/en/suitcase) ID and paste it in **Database → Suitcase Import** to import an example Mobile ID rule:

```SuitcaseID
8375ac55-31a8-4610-825d-0092111154bb:slate-kente-test
```

## Refresh existing records

After the rule is active, run a retroactive refresh for the records that should receive the normalized Mobile ID value.

## Review duplicate matches

After records have Mobile ID values, go to Consolidate Records. When duplicate values exist, a **Mobile ID** section appears under Persons, similar to the standard Email matching section.

![Consolidate Records showing a Mobile ID section for person duplicate matching](https://cdn.us.document360.io/cd8ea7a6-07f3-4846-a554-627ac016d3e3/Images/Documentation/04-IugerL4TFd4wa7DIyKaTc.webp?sv=2026-02-06&spr=https&st=2026-11-15T17%3A39%3A12Z&se=2026-11-15T18%3A39%3A12Z&sr=c&sp=r&sig=sEOI08GvyleepKKHbb0bkMkgXWdn8nI4x9emF1AhA10%3D)