Matching One Customer Across Channels

Every channel identifies people differently. WhatsApp uses a phone number, Instagram a handle, email an address, and a walk-in customer none of the above. Add a second channel and the same person quietly becomes two records, each holding half the story. Our guide to planning past WhatsApp treats this as the problem that decides whether multi-channel is useful or merely more work.

Why it matters more than it sounds

A split record is not just untidy. The agent answering the Instagram message cannot see that this person has an appointment on Thursday. The campaign excludes them because their opt-out is on the other record. The lifetime value calculation counts them as two small customers rather than one good one.

Every one of those is a specific, visible failure in front of a customer who assumes you know who they are — because from their side, they have been dealing with you for two years.

Pick one identifier and treat it as the key

For a business running on chat, the phone number is the natural primary key: it is stable, it is unique, and it is what the dominant channel uses. Everything else — handles, email addresses, customer numbers — attaches to the contact as an additional identifier rather than creating its own record.

That decision has consequences worth accepting deliberately. Numbers must be stored in a consistent international format, or the matching fails on formatting alone, which is the same discipline described in importing contacts from spreadsheets without duplicates.

“

From the customer's side there is one relationship. Every split record is a place where you appear not to know them.

— be digital ai team

Ask for the number naturally

When someone arrives on a channel that does not carry a phone number, you need it at some point — but asking directly, early, reads as an interrogation. Get it as part of doing something useful instead.

• Booking anything requires a contact number, so the booking step collects it without friction.
• Sending a confirmation, a quote or a delivery update is a natural reason to ask where to send it.
• Offering to continue on WhatsApp — "I can send the details there, what number should I use?" — is a request with an obvious benefit attached, and it is the natural move for the enquiries described in getting ready for Instagram DMs.

What does not work is a form-like demand at the start of a conversation, which loses exactly the casual enquirers the second channel exists to capture.

Merge carefully

Merging two records is not easily undone, so require reasonable confidence: a matching number, or a customer confirming they are the same person. A similar name is not enough, and automatic merging on name alone will eventually combine two real customers, which is a considerably worse failure than a duplicate.

When you do merge, the conversation history from both should survive on the merged contact. A merge that keeps the fields and discards half the history has solved the reporting problem and created a service one.

Deal with the duplicates you have

Every business accumulates them: the same person from two numbers, a contact created by an import next to one created by a message, a household sharing a phone. Pull the list of likely duplicates quarterly — same name, same email, similar numbers — and work through it the way you would any other data cleanup, as part of the routine in cleaning a pipeline that has gone stale.

The shared-phone problem

Some duplicates are not duplicates. A household with one phone, a small business where the owner's number is also the office number, a family where the eldest child handles everything in German — in each case one identifier legitimately covers several people.

Do not merge those. Keep separate contacts and note the shared number, because the appointment, the preferences and the consent belong to different people even though the messages arrive from the same place. What matters is that whoever answers can see the situation rather than assuming the last conversation was with the same person.

Show the whole history in the thread

Linking records is only half the job. The person answering needs to see it: previous conversations from other channels, the open deal, the appointment on Thursday, all visible without leaving the message they are replying to.

A merged record nobody can see the benefit of is bookkeeping. The value appears at the moment an agent opens an Instagram message and immediately knows this is a customer of three years with an appointment in two days — which is exactly the context the internal notes practice in keeping context between colleagues is built to preserve.

Some things must not be split

Two pieces of information have to apply to the person rather than the record: consent and deletion. If someone opts out of marketing on one channel, they have opted out — sending to their other record because it technically exists separately is exactly the behaviour that produces complaints and blocks. Email addresses belong on the same record for exactly this reason, as what still belongs in email argues. The same applies to erasure requests, which have to find every record for that person, and that obligation is the subject of how long to keep chats and customer data.