Follow

ID735 - Duplicate Contact Records Overview & Sample

Identifies potential duplicate Contact Records

Overview | Samples | Alert Functionality | Variables | Best Practices & Tips |  Related Alerts

Click to Subscribe

 

Overview:

This alert is used to check your existing contact records for duplicates. This way you can minimize the confusion when a contact record is created twice. It will trigger on same last name, email address, etc. or 'nearly the same' for instance 'Sean' vs. 'Shawn' or near-duplicate phone numbers. It is designed to strictly report duplicates within your contact database.

The 1st run we provide a list after that we will notify the creator if that box is checked. Also see ID444 which is designed to review the list of contacts created that day. It sends a list of contacts created in eAutomate today to a specified user who is in charge of reviewing those and merging any duplicate contacts that might have been created. This also helps with training on best practices for creating contacts and will help identify the user that needs more training.

Run Schedule: Daily

Type of Output: Email

 

*  *  *

Sample

 

*  *  *

Alert Functionality

Alert considers ACTIVE Contact Records only. Alert considers Contact Records whether they are assigned to a Customer Record or not.

The first time the alert fires, we provide a list of ALL qualifying potential duplicate Contact Records. After that we will notify each day of newly created potential duplicates.

We've created extensive SQL logic to determine potential duplicates based on a point system. Any Contact Record "awarded" 5+ points will be considered a potential duplicate by this alert.

Every new Contact Record created is considered against existing Contact Records for the following:

1. Phone Number - for each Contact Record with the same phone number = 1 Point

2. Email Address - for each Contact Record with same email address or email address only different by one character = 1 Point

3. Zip Code - for each Contact Record with same zip code (first 5-digits only) = 1 Point

4. City/State - for each Contact Record with same City/State combo = 1 Point

Logic considers phonetic matches for City (not State)

5. First/Last Name - if first or last name is exact match (or phonetic)  = 2 points

Logic considers phonetic matches. For example: Shawn=Sean OR Todd=Tod OR John=Jon

 

*  *  *

Variables

This alert has no variables

*  *  *

Best Practices & Tips

Set alert to send to Creator:

This can help users see when they may have created a duplicate and address any needed corrections.

ID735SendTo.PNG 

eAuto version 17.1+

Shows users potential duplicate records at the Contact Record screen. The advantage to the CEO Juice alert is it lets you know proactively of potential duplicates; whereas, within eAuto you need to be in the ContactRecord to see possible duplicate contacts. We are also finding many eAuto users are turning this function off as it is heavy on eAuto performance since it requires eAuto to be "looking" for those duplicates each time a Contact Record is edited or viewed.

ID735EA.PNG

*  *  *

Related Alerts

ID444 - New Contact(s) created today. We suggest sending this to a specified user who is in charge of reviewing those and merging any duplicate contacts that might have been created. This also helps with training on best practices for creating contacts and will help identify the user that needs more training.

 

*  *  * 

Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk