Widget / duplicates
DoubleNet
Widget for controlling duplicates in amoCRM: searching for duplicates by phone, email, company and other fields, highlighting duplicates and helping in gluing cards without clutter in the database.
What decides
Problem
- The same client ends up in CRM multiple times from forms, advertising, mail, and manual entry.
- Managers call existing leads and duplicate each other’s work.
- The manager's analytics and reports are distorted because the database is contaminated with duplicate cards.
What does the widget do?
Scenarios
- Looks for repetitions by phone, email, company and other fields even at the stage of lead processing.
- Highlights the risk of a double and helps you quickly make decisions about combining cards.
- Keeps the database clean so that the funnel, sources and managers are considered free of garbage.
What does the business get?
Result
- There are fewer conflicts between managers for the client and fewer repeated calls on the same application.
- Cleaner analytics on advertising, sources and stages of the transaction.
- Clear control of repeat leads during a long transaction and large incoming traffic.
FAQ
Frequently asked questions about finding duplicates in amoCRM
Why are duplicates in CRM not just a “cosmetic” problem?
Because they break analytics, prevent managers from properly managing the client and create chaos in touches. Business loses not only order, but also money.
Is it possible to catch duplicates in several fields at once?
Yes. Usually they look at phone, email, company name and some additional fields in order to find repeat requests before they grow into chaos.
Is DoubleNet needed only for advertising traffic?
No. It is useful wherever leads come from different channels, instant messengers, website, telephony and manual entry, and the transaction cycle does not end in one day.
Related Pages
What to watch along with take control
Audit amoCRM
If you need to understand where the database is already contaminated and how this affects reports, the funnel and the work of the team.
Integration of amoCRM with the site
A common reason for duplicates is the site and forms. Here you can configure a net incoming stream in CRM.
Losses and bottlenecks
A clean database is important if the manager wants to really see where applications are lost and where cards are simply multiplied.
Implementation Calculator
When combating duplicates needs to be included in a broader project for configuring CRM and channels.