platform capability
Identity resolution:
one customer, one card.
A customer writes on Telegram, then from your site, then calls. The platform recognizes it's one person and merges every inquiry into a single card with the full history.
3 days free on any plan. No card required.
live
One card instead of three duplicates
Inquiries from Telegram, your site and the phone gather under one customer: the history is whole and the manager sees it all.
what it is
What is identity resolution in Botseller?
Identity resolution in Botseller is contact linking where the platform recognizes it's dealing with one person, even if they wrote on Telegram, then from your site, then phoned. Every inquiry merges into one customer card — with the full history, purchases and promises. Normally each channel spawns a separate "customer": the manager sees three strangers instead of one regular buyer, the history breaks, and the person is asked the same questions again. Here duplicate contacts in your CRM never appear: the system matches the phone number, the messenger name and other data at the moment of contact, not on a nightly cleanup. So the AI employee and the manager always see the whole picture — what the person asked yesterday from the site, what they bought last month on WhatsApp. One customer with two numbers is no problem: you can link the cards by hand in one action if the system didn't. It works on every plan as a core CRM function, from Start to Business.
how it works
01
The customer writes to any channel
Telegram, the site widget, WhatsApp or a call: the inquiry lands in the platform.
02
The system looks for matches
The phone number, the messenger name and other data are compared with your base at the moment of contact.
03
The inquiry lands in the card
If the person is already in the base, the new channel is added to their card instead of creating a duplicate.
04
The history stays whole
The AI employee and the manager see all of the customer's conversations and purchases, from every channel, in one place.
why it matters
Why identity resolution can't wait for the next database cleanup
The more channels a business runs, the faster the base turns into a maze. The same person writes on Telegram, leaves a request on the site, then calls, and each time a new "customer" appears in the CRM. Six months on there are three thousand records instead of a thousand real people, and nobody can say who is who anymore.
The usual answer is a spring clean. Once a quarter someone on the team sits down to compare numbers and merge the repeats by hand — a manual contact deduplication marathon. But while the cleanup runs, new duplicates pile up, and worse, the damage is already done: a regular buyer was greeted like a stranger, a promise from one channel got lost in another, and the person felt unremembered.
So identity resolution in Botseller doesn't run on a schedule — it runs on contact. The instant a person reaches out from a new channel, the platform checks them against the base. If the phone or other data match, the message lands in the card that already exists instead of spawning another. This is duplicate contact merge that happens before the mess forms: order isn't restored after the fact, the chaos simply never gets the chance to appear.
how it compares
How it differs from merging duplicates by hand
In essence it's like manually merging duplicate contacts in a CRM: the same linked cards and one whole customer history.
It happens on its own at the moment of contact, not once a month when a manager finally gets around to cleanup.
The history has no time to break: the new channel lands straight in the existing card.
The AI employee sees the whole picture from the first message and doesn't re-ask what the customer already told you.
what's inside
Matching at the moment of contact
Matches are found the instant the customer writes, not during a rare database cleanup.
Every channel in one card
Telegram, the site, WhatsApp and calls gather under one customer.
The full conversation history
The manager sees what the person asked in each channel and doesn't re-ask what's already answered.
One customer, two numbers
Wrote from a personal number and a work number: both inquiries land in the same card.
Manual linking
If the system didn't merge the cards itself, the manager links them in one action.
The AI remembers the customer
The AI employee recognizes the person in a new channel and continues the conversation with the history in view.
A clean database
Duplicates stop piling up and the base stays tidy without special cleanups.
An honest customer count
The number of customers in the CRM reflects reality, not the number of channels they wrote from.
what changes
What changes when duplicates stop appearing
Managers stop playing detective before every reply: open the card and you see everything the person wrote, asked and bought, whatever channel they came from. The customer doesn't have to retell their story from scratch, and they feel remembered, like at a favorite cafe. The conversation continues instead of starting over.
The numbers start telling the truth: the base holds exactly as many customers as there really are, each with a real purchase history — genuine customer data unification rather than a pile of fragments. The AI employee works more precisely too: it recognizes a regular in a new channel and offers what suits that person. The big database cleanup drops off the to-do list for good, along with the risk of losing something important in a manual merge.
how much it costs
$59 /mo
included in plans from Start
Identity resolution is included in every plan as a core CRM function, from Start to Business.
No card required. All plans and the annual discount
frequently asked questions
How does the system know it's one person?
By matching data: the phone number, the messenger name and other signals. The check runs at the moment of contact — the customer writes from a new channel, and the system looks for them in the base right away.
What if the cards don't merge automatically?
Link them by hand: the manager merges the cards in one action, and the full history from both channels ends up under one customer. It's the same duplicate contact merge, just manual.
What if the system merges two different people?
Merging relies on strong signals, first of all the phone number. Doubtful cases stay as separate cards: better to show the manager two contacts than to confuse two customers.
Does the AI employee see history from other channels?
Yes, and that's the main benefit: the customer writes on Telegram after a conversation on the site, and the AI picks up where it left off instead of starting the introductions over.
Do I need to set this up or buy it separately?
No. Identity resolution works out of the box and is included in every plan as a core CRM function, from Start to Business.
where to next
story
Is the customer repeating the same thing in every channel?
WhatsApp, a call, the website. To the AI it is one conversation.
where it works
for your industry
Other capabilities: Communication channels · AI CRM