Duplicate control is configured individually for each funnel.
On the first tab of the settings window you need to select our widget «Message Help». It is located in the sources section with limited support for duplicate control, since our widget works using the "BIG DATA" (The system recognizes the client using machine learning and amoCRM data).
BIG DATA method
When you select this option, the incoming application data is checked using machine learning algorithms and amoCRM data.
For incoming requests from chats BIG DATA will find duplicates and merge the incoming request with the existing one.
For incoming requests from other channels, check by BIG DATA works asynchronously, that is, after adding the application.
In this case, the merger will occur only if one of the duplicate entities is in the unassembled status.
It is also worth noting that the check also occurs when updating an entity (data addition), the main condition is that one of the entities that are potentially duplicates is in the unparsed status.
When checking by BIG DATA, even when an entity is updated (for example, a bot filled in a phone number in an unparsed application), a merger may occur. The main condition for the union to work is BIG DATA are:
- control enabled BIG DATA;
- duplicate control is enabled for the source from which the last request in the unsorted order comes;
- one of the entities being merged is in the unassembled status.
After selecting our widget, you can configure the duplicate control rules to suit your needs:
- You can set additional fields for transactions and contacts by which you need to compare incoming data.
In this case, amoCRM will check the presence of the selected field in the data of the transferred contact and deal and search for duplicates in your account.
If the contact field is used, then only those transactions where the found contact is the main one will be considered duplicates.
This parameter is checked when creating tickets from forms, API (only through the new /api/v4/leads/complex method) and other sources.
- You can select funnels and statuses in which duplicates will be searched, that is, if a deal is in an unselected status, it will not participate in data comparison when adding a deal to amoCRM.
- You can select the type of outcome in case of a conflict between transaction data and an incoming order
When choosing an option “Update with data from incoming request”, if a duplicate is found and there is a conflict between incoming and existing data, the existing transaction will be updated with the incoming data. The Phone and Email fields will be updated with new data.
When selecting option “Leave current transaction details”, if a duplicate is found and there is a conflict between incoming and existing data, the existing transaction will not be changed.
- If several duplicates are detected for an incoming application:
If you find more than 1 take and no more than 3, you can select the duplicate control behavior. If more than 3 duplicates are found, merging will not occur.
You can either update all deals (if you select this setting, all found deals will be updated), or update the newest deal (if you select this setting, the last created deal will be updated), or create a new deal (if you select thissettings, a new transaction will be created)
- And you can also configure the creation of a task after the data update operation is completed. The task will be assigned to those transactions that were found during the search for duplicates. If more than 3 transactions were found, then duplicate control will ignore such an incoming request.
Note:
This functionality relates directly to amoCRM and we, for our part, cannot influence the control of duplicates.
Duplicate control settings are carried out personally on your side, according to your personal needs.
Perhaps in the future this functionality will expand and we, on our part, will be able to make some additions to make duplicate control work more correctly.
More details can be found in the official article from amoCRM: https://www.amocrm.ru/developers/content/crm_platform/duplication-control