BRUTAL MARKETING
Pipedrive: Messengers in One Customer Card, No Duplicates
month 2026
BRUTAL MARKETING
Pipedrive: Messengers in One Customer Card, No Duplicates
month 2026
One Customer Card: How to Merge Viber, Telegram, WhatsApp and Instagram in Pipedrive Without Duplicates
Pipedrive looks for duplicates by name. That single sentence explains 80% of messenger-related problems in the system: for two records to show up under "Merge duplicates," the contact name has to match — and only then does the system look at phone, email or organisation.
Now recall what the name field looks like on a contact that arrived from Telegram.
Now recall what the name field looks like on a contact that arrived from Telegram.
Serhii
Ponomarenko
Ponomarenko
@dmytro_k. Or Dmytro. Or simply Telegram User. The same man is stored in WhatsApp as +380671112233 and in Facebook Messenger as Dmytro Kovalenko. Three records, three different names. Pipedrive won't even suspect they're one person, although two of the three hold the identical phone number.
On a project we audited in spring, a database of 7,800 people contained 1,640 of these invisible duplicates. Not one had been flagged. What follows is the mechanics: which identifiers actually reach Pipedrive from each channel, how to work around the limits of native duplicate detection, where to put automation and where to put moderation, and how to clean up what's already there.
On a project we audited in spring, a database of 7,800 people contained 1,640 of these invisible duplicates. Not one had been flagged. What follows is the mechanics: which identifiers actually reach Pipedrive from each channel, how to work around the limits of native duplicate detection, where to put automation and where to put moderation, and how to clean up what's already there.
Why One Customer Becomes Three Records
The cause is that Pipedrive's data model and the messengers' data model are built around different things. Pipedrive recognises a person by name. A messenger hands over a chat identifier, and the name is just whatever the person typed into their profile.
What Actually Reaches Pipedrive From Each Channel
First, the channels themselves. Pipedrive has a built-in Messaging inbox, and two channels connect to it natively: Facebook Messenger and WhatsApp. Everything else — Telegram, Viber, Instagram Direct — arrives through marketplace apps built on the Channels API, or through middleware such as Make and Albato.
Read the last two columns together. Only three channels out of eight deliver a phone number, and exactly one — the web form — delivers a real first and last name. In every other case the Name field holds whatever the person put in their messenger profile: emoji, a handle, an abbreviation, a business name.
That's precisely where native duplicate detection breaks, because it leans on a name match. It works well for form leads and cold lists, and barely works for messenger traffic.
That's precisely where native duplicate detection breaks, because it leans on a name match. It works well for form leads and cold lists, and barely works for messenger traffic.
Conversations Have to Be Linked to a Contact by Hand
The second Pipedrive characteristic that gets underestimated at launch: a conversation in the Messaging inbox doesn't become a record automatically. It has to be linked to a contact, lead or deal. If the rep didn't do it, the conversation sits in the inbox and the customer isn't in the database at all.
And if they did it carelessly, they create a new person instead of finding the existing one. In our experience at Brutal Marketing this produces 30–50% of all duplicates on Pipedrive projects with messengers. Not an integration failure — one extra click by a rep in the moment when speed matters.
And if they did it carelessly, they create a new person instead of finding the existing one. In our experience at Brutal Marketing this produces 30–50% of all duplicates on Pipedrive projects with messengers. Not an integration failure — one extra click by a rep in the moment when speed matters.
Three More Duplicate Sources
The customer moves between channels. Wrote on Instagram, continued on Viber, then filled in the website form. Three identifiers with no shared field.
Importing an existing database. A file gets loaded on top of contacts that already exist. Matching logic during import has to be set deliberately — what to prepare beforehand is covered in our piece on what CRM implementation involves.
Leads and people live separately. In Pipedrive, leads sit in their own inbox and only become a deal with a person after conversion. Until converted, a lead doesn't participate in matching — so the same customer comfortably exists twice, as a lead and as a person.
Importing an existing database. A file gets loaded on top of contacts that already exist. Matching logic during import has to be set deliberately — what to prepare beforehand is covered in our piece on what CRM implementation involves.
Leads and people live separately. In Pipedrive, leads sit in their own inbox and only become a deal with a person after conversion. Until converted, a lead doesn't participate in matching — so the same customer comfortably exists twice, as a lead and as a person.
What a Split Record Costs
Run the numbers on your own data. A rep spends 3–5 minutes assembling context the card doesn't hold. At 35 conversations a day and 20% duplicates, that's around half an hour daily per person — roughly ten working days a year.
Then the direct losses: two reps messaging one customer with different terms, a discount issued twice, a campaign delivered three times. And separately, decisions made on distorted numbers, covered below.
Then the direct losses: two reps messaging one customer with different terms, a discount issued twice, a campaign delivered three times. And separately, decisions made on distorted numbers, covered below.
Matching Rules: Phone, Email, Messenger ID
Deduplication is a set of rules with different reliability, stacked in sequence. Here's each key and how to apply it specifically in Pipedrive.
Name: The Key the System Relies On, and the One You Can't Trust
Start here, because nothing else in Pipedrive works without it. Native duplicate detection for people checks a name match plus one of: phone, email, or membership of the same organisation. For organisations it checks name and address. For deals there's no duplicate identifier at all — two deals with the same title aren't considered duplicates.
From which follows the rule we put first in every working policy: fill the Name field with the customer's real name, not their messenger handle. The handle goes into a dedicated custom field for that channel.
This isn't cosmetic. While @dmytro_k, Dmytro and Dmytro Kovalenko sit in the database, the native tool will show you zero duplicates — and you'll assume the base is clean.
Three actions close it technically:
From which follows the rule we put first in every working policy: fill the Name field with the customer's real name, not their messenger handle. The handle goes into a dedicated custom field for that channel.
This isn't cosmetic. While @dmytro_k, Dmytro and Dmytro Kovalenko sit in the database, the native tool will show you zero duplicates — and you'll assume the base is clean.
Three actions close it technically:
- Custom fields for channel identifiers: Telegram ID, Instagram ID, Viber ID, Messenger ID.
- An automation that moves the handle out of the name field into the channel field when a person is created.
- A line in the script: the rep confirms the name in conversation before quoting, not after.
Phone: The Most Reliable Key, and It Needs Normalising
The phone is the most precise identifier of an individual in B2C. The problem is how it gets written down.
One number lands in the database in at least five shapes: 0671234567, +380671234567, 380671234567, +38 (067) 123-45-67, 067 123 45 67. For exact comparison those are five different people. Normalise to +380XXXXXXXXX and compare the last nine digits rather than the whole string.
What to do technically:
One number lands in the database in at least five shapes: 0671234567, +380671234567, 380671234567, +38 (067) 123-45-67, 067 123 45 67. For exact comparison those are five different people. Normalise to +380XXXXXXXXX and compare the last nine digits rather than the whole string.
What to do technically:
- Use the system Phone field, not a custom text field. Text fields don't participate in matching.
- Run the existing database through normalisation before any cleanup.
- Add input masks on website forms and in LeadBooster.
- Allow multiple numbers on one person (work, personal) and match all of them, not just the first.
Email: The Second Key, Weaker Than It Looks
Email works well in B2B and badly in B2C. Small-business customers often leave no address at all, and when they do it may be a shared family mailbox or a corporate info@.
Typical traps:
Typical traps:
- Corporate mailboxes. info@company.com isn't a person. Merging on it glues the director, the accountant and the buyer into one record.
- Gmail aliases. ivan.petrenko@gmail.com and ivanpetrenko@gmail.com are one mailbox; to the CRM, two.
- Plus addressing. ivan+shop@gmail.com leads to the same person.
- The fix: keep email as a matching key, with a blocklist. Exclude every info@, office@, noreply@, sales@. For Gmail, normalise dots and plus-aliases before comparing.
Messenger ID: An Exact Key That Only Works Inside Its Own Channel
The chat identifier gives 100% precision. A Telegram ID match means the same human, guaranteed.
Two limits. First, it isn't portable — a Telegram ID says nothing about Instagram. Second, it can change: when the bot is reconnected, the WhatsApp Business number switched, or Instagram moved to another business account.
Since Pipedrive doesn't match on these fields itself, messenger ID only works paired with an automation or an external tool. But it produces the cleanest merges, so it's worth creating those custom fields even before you've decided what will do the merging.
Two limits. First, it isn't portable — a Telegram ID says nothing about Instagram. Second, it can change: when the bot is reconnected, the WhatsApp Business number switched, or Instagram moved to another business account.
Since Pipedrive doesn't match on these fields itself, messenger ID only works paired with an automation or an external tool. But it produces the cleanest merges, so it's worth creating those custom fields even before you've decided what will do the merging.
The Matching Cascade
Note the difference from the system's own logic. Native duplicate detection effectively runs at level 5 plus confirmation — that is, it makes the weakest key mandatory. A working scheme is built the other way round: the name is irrelevant when the phone or the ID matches.
Automatic Merging vs Manual Moderation
In Pipedrive this question sits differently than in systems with native inbound duplicate control. There's no mechanism that intercepts a new record before creation and glues it to an existing one. Merging always happens after the fact — either by hand or through an external tool.
What Pipedrive Does Natively
The built-in tool surfaces potential duplicate people and organisations, lets you compare records side by side — names, deals, activities, creation date, owner, visibility settings — and pick the primary record whose data takes priority in a conflict. There's also manual merging for cases the system didn't flag: open the person, organisation or deal, choose Merge, and search for the second record.
Three details to account for before you start:
Three details to account for before you start:
- Merging is available to admins or users with the specific permission. That's arguably a plus: a mass cleanup shouldn't be handed to reps.
- The potential-duplicate list depends on visibility permissions. A regular user only sees records they have access to, so the cleanup belongs on an admin account — otherwise part of the duplicates never appears in the list.
- Detection logic follows the same rules as the import tool. Which means it equally fails to see duplicates whose names differ.
What to Cover Inbound Duplicates With
Since there's no native control at the point of entry, you have to build it. Three working options, simplest first:
Budget for these alongside licences and integrations from the start. Cost benchmarks are in our piece on CRM implementation cost, timeline and types.
- Pipedrive automation plus a lookup before creation. Works for forms and telephony where the phone arrives immediately. Weak spot: messengers without a number.
- Middleware (Make, Zapier, Albato) between messenger and CRM. The scenario queries the Pipedrive API by number or messenger ID and creates a new person only when there's no match. This is the most flexible option and the one we deploy most often.
- Dedicated deduplication apps (Dedupely, Insycle and similar). They let you define your own detection and merge rules on any field, including custom ones, and run bulk operations. Worth it on databases of a few tens of thousands of records upward.
Budget for these alongside licences and integrations from the start. Cost benchmarks are in our piece on CRM implementation cost, timeline and types.
Where Automation Gets It Wrong
Four situations where automatic phone-based merging did damage on our projects.
One family, one number. A wife orders for her husband, then for herself. Automation collapses two purchase histories into one record and breaks personalisation.
A corporate number. In B2B a company often has one inbound line. Three contact persons arrive on the same reception number. Here phone matching should be off, with the organisation and email doing the work.
Dealers and intermediaries. One number places orders for dozens of end customers. Merging turns it into an unreadable record with a hundred deals.
A rep's test data. Their own number in a test deal collects everything that arrives afterwards.
One family, one number. A wife orders for her husband, then for herself. Automation collapses two purchase histories into one record and breaks personalisation.
A corporate number. In B2B a company often has one inbound line. Three contact persons arrive on the same reception number. Here phone matching should be off, with the organisation and email doing the work.
Dealers and intermediaries. One number places orders for dozens of end customers. Merging turns it into an unreadable record with a hundred deals.
A rep's test data. Their own number in a test deal collects everything that arrives afterwards.
The Three-Zone Model
The working answer isn't "automation or hands" — it's splitting by risk.
The yellow zone is 10–15% of cases and roughly 20–30 minutes a week for the manager. Cheaper than untangling a bad merge a quarter later.
A Quick Comparison
The strongest argument for moderation is irreversibility. You can't un-merge records in Pipedrive with native tools: the data is already mixed, and recovery only works from an export taken before the operation.
Our standard configuration: automation on cascade levels 1–3, moderation on level 4, a hard ban on levels 5–6. In businesses with an average deal above $1,200 we push the line further — even a phone match goes to moderation if the record already holds a closed deal.
Our standard configuration: automation on cascade levels 1–3, moderation on level 4, a hard ban on levels 5–6. In businesses with an average deal above $1,200 we push the line further — even a phone match goes to moderation if the record already holds a closed deal.
How to Obtain a Phone Number Where There Isn't One
Telegram and Instagram don't provide phone numbers. You have to get them in conversation — not "ask at some point," but built into the process.
Once a phone appears on a Telegram contact, the level-2 rule fires and the scenario merges it with the WhatsApp record holding the same number. Which is why collecting phone numbers inside messengers matters more than any deduplication tool.
- A "Share contact" button in Telegram at step one. Phrase it not as "leave your number" but as "so we can hold the booking and send confirmation." Conversion into a shared number on our projects runs 55–70% when the ask carries a concrete benefit.
- A bot or rep requests the phone before quoting. The customer gets a quote, you get a matching key.
- An order form instead of closing in chat. Even two fields solve it.
- The phone at the delivery stage. In e-commerce the number appears at checkout — the key is making sure the integration writes it onto the existing person rather than creating a new one.
- A personal promo code. Issued on Instagram and redeemed on the site, it links two identifiers without asking for a number directly.
Once a phone appears on a Telegram contact, the level-2 rule fires and the scenario merges it with the WhatsApp record holding the same number. Which is why collecting phone numbers inside messengers matters more than any deduplication tool.
What to Do With the Duplicates Already in Your Database
The most common mistake is to start deleting. Deleting a person severs links to deals, activities and conversations, and creates new disorder in place of the old. The correct action is one thing — merge.
Here's the order we use for Pipedrive cleanups.
Here's the order we use for Pipedrive cleanups.
Step 1. Take a Full Export
Export people, organisations, deals and leads to file. Merging is irreversible, and if a rule turns out wrong the export is your only way back. Keep the files at least a month.
Step 2. Measure the Scale and Find the Invisible Duplicates
The key difference in Pipedrive: don't rely on the native list of potential duplicates. It shows only the portion where names match.
The working method is to export people into a spreadsheet and count for yourself:
That last figure ranges from 8% to 25% in the databases we've audited. Those records will never merge until you obtain a phone number from those people.
The working method is to export people into a spreadsheet and count for yourself:
- how many people exist in total;
- how many groups share the same normalised phone (ignoring the name);
- how many groups share an email outside the blocklist;
- how many people have neither phone nor email — only a messenger handle.
That last figure ranges from 8% to 25% in the databases we've audited. Those records will never merge until you obtain a phone number from those people.
Step 3. Define the Master-Record Rule
Before merging, decide what wins in a conflict:
The last two get skipped most often. The database then looks clean, but the acquisition history claims every customer arrived last month.
- Owner — from the record with the latest activity, not the oldest.
- Name — the person's real name, not a messenger handle.
- Phone and email — keep every value, don't overwrite.
- Creation date — the earliest, otherwise cohort analysis breaks.
- Labels and first-touch UTMs — from the earliest record.
The last two get skipped most often. The database then looks clean, but the acquisition history claims every customer arrived last month.
Step 4. Merge in Blocks, Strongest Key First
Messenger ID matches first, then normalised phone, then email. After each block, pause and manually review a sample of 20–30 records. One wrong merge in the sample means the rule needs revisiting.
Don't do the whole cleanup in one evening on a database above 5,000 people. The safe pace is 1,000–1,500 merges a day with a result check the next morning.
Don't do the whole cleanup in one evening on a database above 5,000 people. The safe pace is 1,000–1,500 merges a day with a result check the next morning.
Step 5. Deal With Leads, Deals and Conversations
Three tails remain after people are merged. Leads in the inbox that duplicate existing customers — convert them or close them with a reason. Twin deals: merge the open ones, leave closed ones with a source label. Conversations in the Messaging inbox — verify they're linked to the right person after the merge.
Warn the team separately: don't unlink a conversation from a contact on your own. If the link is wrong, that's an admin task.
Warn the team separately: don't unlink a conversation from a contact on your own. If the link is wrong, that's an admin task.
Step 6. Close the Door on New Duplicates
Cleanup without new rules holds for four to six weeks. After that the database refills at the same rate. The final step is a lookup scenario before person creation, custom fields for channel IDs, phone masks, phone collection in messengers, and an owner for the yellow zone.
Mistakes That Make Cleanup Worse Than the Problem
- Deleting instead of merging.
- Treating the native duplicate list as complete.
- Merging on name alone with no second key.
- Cleaning from a regular user account — half the duplicates stay invisible behind permissions.
- Running a mass cleanup without pausing automations and campaigns: a merge can trigger sequences on real customers.
We covered the wider context in our guide on CRM for business — including what dirty data does to reporting.
How This Distorts Analytics and Segmentation
Duplicates distort four groups of numbers owners use to make decisions. In Pipedrive, with its strong pipeline reporting, it shows up especially clearly.
Conversion Is Understated, and You Can't Tell by How Much
Every duplicate adds one to the denominator and nothing to the numerator. At 20% duplicates, reported conversion sits roughly a quarter below reality.
The danger isn't the figure but the unevenness. Channels without a phone — Instagram, Telegram — look worse than they are. Channels with a phone — forms, calls — look better. Budget shifts toward the channel that simply identifies people more easily.
The danger isn't the figure but the unevenness. Channels without a phone — Instagram, Telegram — look worse than they are. Channels with a phone — forms, calls — look better. Budget shifts toward the channel that simply identifies people more easily.
LTV Is Understated and Repeat Sales Are Invisible
A customer with three records looks like three customers with one purchase each. Repeat-purchase rate falls, LTV falls, acquisition cost looks too high.
On one project, merging the records moved the repeat-purchase share from 19% to 31%. Nothing changed in how the team worked — the system finally saw they were the same people. That reshaped the budget conversation: retention stopped being written off as a dead end. The calculation method is in our piece on working with CRM analytics and reports.
On one project, merging the records moved the repeat-purchase share from 19% to 31%. Nothing changed in how the team worked — the system finally saw they were the same people. That reshaped the budget conversation: retention stopped being written off as a dead end. The calculation method is in our piece on working with CRM analytics and reports.
Channel Attribution Lies
When the same customer arrives three ways, the system logs three first touches. Instagram gets a lead, Viber gets a lead, the form gets a lead. The sale is credited to whichever channel hosted the last contact.
The practical consequence: the channel that genuinely brings customers looks like a channel without sales. On a merged record you see the sequence of touches inside one story instead of three truncated ones.
The practical consequence: the channel that genuinely brings customers looks like a channel without sales. On a merged record you see the sequence of touches inside one story instead of three truncated ones.
Segmentation and Campaigns
A "bought more than twice" filter won't assemble if the purchases sit on different people. A "never bought" filter fills up with customers who did. A Pipedrive Campaigns send reaches someone twice or three times, from different segments with different offers.
Deduplication is step zero: segmentation on a dirty database produces segments you can't trust.
Deduplication is step zero: segmentation on a dirty database produces segments you can't trust.
Sales Forecast
An effect specific to Pipedrive. The forecast is calculated from open deals, and duplicates almost always mean duplicated deals — the same customer sitting in the pipeline twice with the same value. The forecast is overstated by exactly the duplicate amount, and it surfaces at month end when the plan doesn't close.
Where to Start This Week
The first results show up by step two or three. Here's the order when a full implementation isn't on the table yet:
Three metrics show the result: share of people without a matching key, number of new duplicate groups per month, and the change in repeat-purchase rate. The last one usually moves most — not because customers started buying more often, but because you can finally see them.
These rules belong in the setup phase rather than a year later — the full sequence is in our article on CRM implementation stages. If you're still choosing a platform for messenger-heavy traffic, our Pipedrive vs Kommo breakdown for sales teams is relevant here: the two systems handle chats differently, and that difference lands directly on deduplication.
- Day one. Export people into a spreadsheet and count groups sharing the same normalised phone, ignoring names. Ten minutes of work reveals the real scale the native tool doesn't show.
- Day two. Create custom fields for messenger IDs and check where your integrations write the handle. If it goes into the name field, that's the first thing to change.
- Week one. Add a phone request to the Telegram and Instagram conversation script. It's the only action that reduces future duplicates instead of clearing up existing ones.
- Week two. Merge records on exact phone and messenger ID matches from an admin account, in blocks, with sample checks.
Three metrics show the result: share of people without a matching key, number of new duplicate groups per month, and the change in repeat-purchase rate. The last one usually moves most — not because customers started buying more often, but because you can finally see them.
These rules belong in the setup phase rather than a year later — the full sequence is in our article on CRM implementation stages. If you're still choosing a platform for messenger-heavy traffic, our Pipedrive vs Kommo breakdown for sales teams is relevant here: the two systems handle chats differently, and that difference lands directly on deduplication.
We at Brutal Marketing will select the best CRM program for you to use in your business. We will be happy to tell you about the program's capabilities and show you which settings will exactly help you achieve the desired financial results.
Frequently Asked Questions
Can we get by with Pipedrive's native duplicate merging alone?
Partly. The native tool handles duplicates from forms and imports well, where a proper name exists. For messenger traffic it isn't enough, because detection leans on a name match and chats deliver handles. The minimum addition you'll need is a lookup scenario before person creation in Make or Zapier.
How long does cleaning a 10,000-person database take?
In our experience, six to fourteen working days. Longer than in systems with native duplicate control, because part of the groups have to be found by exporting to a spreadsheet. Audit and rule preparation take about a third of the time.
We merged contacts and the Instagram conversation stopped showing. Is that normal?
No. That happens when one record was deleted instead of merged, or when the conversation was unlinked from the contact manually. Which is why the export matters before you start — it restores the contact data. The conversation itself has to be found in the Messaging inbox and relinked.
Should we merge records when a customer writes from a work and a personal number?
Yes, but through moderation. The signal isn't the number but whether it's the same person in the same buying process. If it is, both numbers live on one person as two field values.
What duplicate rate counts as normal?
Zero doesn't exist: some customers will always write from anonymous accounts and never share a phone. A working benchmark for messenger-driven businesses is 3–5% of records. Above 10%, the analytics can't be trusted, and cleanup pays back faster than any funnel rework.
Find Out How Many Duplicates You Have — Before You Change Anything Else
We'll audit your Pipedrive account: count how many real customers you have, surface the duplicate groups the native tool can't see, and hand you a deduplication rule set built around your channels, with an estimate of timeline and scope.
Request an audit on our Pipedrive implementation and setup page, or see how our CRM implementation process works — from the sales audit through to team training.
Request an audit on our Pipedrive implementation and setup page, or see how our CRM implementation process works — from the sales audit through to team training.
By submitting an application, you agree to the privacy policy
© 2017-2027, Brutal Marketing
All rights reserved
© 2017-2027, Brutal Marketing
All rights reserved