CRM's Identity Crisis: Duplicate Contacts, Part 2

CRM systems have contacts. E-mail systems have contacts. Web servers collect contact information. How do you keep them all in sync? It's harder than it looks...and the more data sources, the harder it gets. Here's a look at how to prevent duplicates and avoid confusing identities.

By David Taber
Mon, February 22, 2010

CIO

At the core of customer relationship management is "who am I talking with?" In a simple SFA or CRM system, it's obvious: you called them, or they called you. But in Enterprise CRM, it's tricky to identify exactly whom the interaction is with, and every new data source seems to make it harder. Last week, we dealt with the blurring of contact information from multiple contact lists. This week, we're dealing with avatar confusion from multiple entry points into your company's web and social networking sites.

CRM's Identity Crisis: Duplicate Contacts

Multiple Avatars

Your prospects and customers will typically have multiple avatars. Most executives have several e-mail accounts, a Twitter persona, a LinkedIn ID, and a Facebook page. Even if they allow cookies into their browser, they typically use more than one PC and contact your company from several IP addresses. So you don't really know who is coming to your web site or sending you mail unless they explicitly let you know.

Sure, the fancier web tracking software vendors claim to identify (or at least categorize) these avatars, but you don't get much information that's worth storing in your CRM system until the person registers, calls, or e-mails you.

CRM Definition and Solutions

It's all too common, though, for your registration system to not be properly configured to support clean identity management. The classic problems:

• The registration page asks for too much information, practically begging the registrant to put in bogus entries or just leave fields blank. The exact number of items you can ask for varies by market, but typically asking for more than five items on an initial registration is counterproductive.
• The logic behind the registration page doesn't validate the data, or enrich it with obvious extrapolation (e.g., the registrant's phone number starts with the same exchange as the company's main number, so they work at headquarters).
• The registration system doesn't dedupe entries and record each registration as a campaign response in the CRM system.
• The registration page doesn't collect an e-mail address, and doesn't validate it with a "round trip" confirmation mail.

The last bullet is the most important, as a valid e-mail address is the only simple path to resolving the multiple avatar problem. People won't give you their e-mail address unless there's a good reason to do so. It's best not to ask for it until they have identified something of value that you offer them in exchange: a trial version of your product, a free book excerpt, a newsletter or podcast subscription, etc. But when you do ask them for the e-mail address, don't give them access to the offered item until they have replied to the confirmation e-mail you've sent them. Essentially, create a user account on your site so that they can get more of your offers without the bother of re-registering...and so that you know who they are even if they're just browsing without downloading.

Continue Reading

Our Commenting Policies