Data Quality Processes and New Contact Rules

To manage new contacts as they are created, the new contact rules you define can be configured to notify data stewards of new contacts added to the system as well as any data quality issues identified. You can configure InterAction to use different notification settings for different sets of rules. For example, a rule set you have configured for a new user may use a rule collection that is configured to send Data Change Management tickets for all new contacts and data quality issues.

For more information, see the following sections:

  • Data Change Management Tickets Created
  • New Contact Review Folders

Data Change Management Tickets Created

Using the rule collections provided with InterAction, you can configure InterAction to send Data Change Management tickets to data stewards when new contacts are added to InterAction.

Data Change Management Tickets Created by New Contact Rules
Ticket Description
New Contact

A new contact ticket can be sent whenever the following situations occur:

  • A new contact is added through User to Firm Contact Sync and is not matched with any contacts that already exist in the firm list.
  • A new contact is added through the new contact wizard in the Web Client or through InterAction Desktop Integration.
  • A new person contact is added or connected to a contact in the firm list, however the company listed for the person cannot be matched with any company contacts in the firm list.
  • A new contact is added to InterAction through InterAction IQ 2.x contact mining or signature capture.

The ticket created is a “notify” type of ticket that serves to alert the data steward about the new contact. Typically, a data steward should review the new contact information for accuracy and completeness, then close the ticket.

If the new contact is sourced in the New Contact Review folder, the data steward can choose an option to move the contact to the firm list.

Data Conflict

A data conflict ticket can be sent whenever a new contact that is suspect is matched with a contact already in the firm list and the two contacts have different contact information.

The ticket is a submit type of ticket that requires that the data steward take action before any contact information is updated. Typically, a data steward should review the value provided by the user and compare it to the value offered by the firm. The data steward can then decide which value is the correct value, select that value, and then choose to update the contacts.

If the data steward cannot determine which contact has the better value, he or she can close the ticket, without updating either contact. When this occurs, the user’s contact and the firm’s version of the contact remain different until either contact’s information is updated.

Possible Duplicate

A possible duplicate contact ticket can be sent whenever the following occurs:

  • One (or more) possible, but not exact, matches are found for a contact.
  • More than one exact match is found for a contact.

When the data steward is handling the ticket, he or she can review the list of possible matches and merge the contacts, as necessary.

Unassociated Company

An unassociated company ticket can be sent whenever InterAction cannot match the company listed for a person contact with any company contact in InterAction.

The ticket created is a “review” type of ticket that serves to alert the data steward about the new person contact that has no company association. Typically, a data steward should use the company association wizard to associate the contact with a company. The data steward can also choose to close the ticket, leaving the person unassociated.

Because InterAction IQ 2.x does not match companies when new contacts are added to InterAction, unassociated company tickets do not apply for InterAction IQ 2.x rule collections.

Any tickets created are assigned to the group of users assigned as the owner of the new contact rule set. For example, you can create a rule set that specifies the Data Administrators group is responsible for managing any new contacts created by Ed Roberts. In this situation, any time Ed Roberts adds a new contact, a New Contact ticket displays in the Data Manager inbox in Data Change Management.

For more instructions on how to handle Data Change Management tickets, see the InterAction for Data Stewards and Marketing Users guide.

New Contact Review Folders

In many instances, you may wish to notify data stewards about new contacts, but you may not want to flood Data Change Management inboxes with tickets. To provide for this, InterAction includes two New Contact Review folders into which contacts can be sourced or linked when they are added to InterAction.

The New Contact Review folders serve the purpose of creating a list of contacts for data stewards to review on a periodic basis to check contacts for accuracy and completeness. It is required that all users have Read access to the New Contact Review folder. This is the setting out of the box. For details on the configuration of these folders, see the Loading Data into InterAction guide. For information on New Contact rules, see What Do New Contact Rules Define?.