Duplicate CRM leads: a retry, a new order or the same customer?

Distinguish delivery retries from new orders, review matching rules and merge records safely in Bitrix24. Includes a practical integration acceptance checklist.

Discuss enquiry handling Download the checklist

The same contact does not mean the same order

Start by separating three situations: a system delivered the same enquiry again, someone placed a new order, or the database contains two customer records. Each requires a different action. Treating them alike can remove a real opportunity along with a technical duplicate.

Delivery retry: The same enquiry identifier and unchanged content. Return the result of the same operation rather than creating another order.
New order: An existing customer makes a new request. Reuse the contact where appropriate and track the order separately under an agreed rule.
Two customer records: Check whether the records really describe the same person or organisation, then choose the primary record and values to retain.

An illustrative example, not a client outcome

A buyer submits a supply enquiry twice, then asks for another delivery a week later using the same phone number. Acceptance should show one enquiry in the first case and a separate order in the second. A rule stating “one phone number = one deal” cannot distinguish these events.

Agree matching rules before cleaning the database

Define one customer, one order and an operation retry. A name alone is a weak match because different people may share it. A department email or reception phone also does not establish that two records should merge. Keep ambiguous pairs for manual review.

Choose matching fields and allowed format normalisation. Document exceptions for shared contact details and different organisations.
Assign an owner for ambiguous matches. Agree which values survive a conflict and who makes the decision.
Prepare an appropriate backup and recovery procedure before bulk changes. A basic CSV is not a full backup of relationships, files and history.
Review a small agreed sample first. Check linked orders, activities, owners and required fields before processing the wider database.

When duplicates arrive through several channels, define field precedence separately. A new form should not silently overwrite a verified contact with an unverified value. Preparation of source data is covered in the CRM data migration checklist.

What to check in Bitrix24

Bitrix24 provides automatic duplicate control for leads, contacts and companies. Availability depends on the plan; field matches, ownership and lead stage affect automatic merging. Check the conditions on your portal before enabling it. This is not a universal rule for every deal. Official automatic merging conditions

Manual merging requires choosing the primary record and the field values to retain, with appropriate update and delete permissions. Check an agreed pair of records and their linked data first rather than starting bulk processing from a single matching value. Manual merging procedure

For CRM forms, separately inspect duplicate handling and the rule for reusing an active deal. Finding a contact and deciding whether to create a new deal are different tasks. Changing a form does not automatically clean historical records. CRM form configuration documentation (Russian)

Five checks before accepting an integration

Retry one operation. Deliver the same test enquiry twice using the same key. Check record counts and the link between the stored enquiry and CRM.
A new task from an existing customer. Submit another request after the first is complete. A new order must remain available if that is the agreed rule.
Changed content with the same key. Handle the conflict explicitly under the agreed rule rather than silently replacing the original order.
A delayed CRM response. Recovery must avoid a second deal while keeping the enquiry available for review. One technical success does not prove delivery to every system.
Two channels for one customer. Check contact matching, independent orders and agreed exceptions, then verify activities and ownership after any merge.

Agree test records and notification recipients in advance. Use a separate environment or explicitly marked synthetic data without real contact details. Record expected and actual counts of enquiries, contacts and deals as three different measures.

Download the acceptance scenarios

What to include in the contractor’s scope

Separate diagnosis, integration changes and historical record review. Estimation needs incoming channels, CRM entities, new-order rules, a recovery method and the extent of ambiguous matches. Record count alone does not describe the effort: different rules and relationships may require separate checks.

On BYstudio’s own website, a retry with the same submission identifier reuses the stored record. This demonstrates verified enquiry handling, not removal of duplicates in a client’s CRM. The studio does not currently use its own sales CRM. Your CRM links and order rules require separate verification.

The initial review is free. Describe the system, channel and a problem example without customer names, phone numbers or exports. Private materials and access are arranged separately.

Questions about CRM duplicates

Can every enquiry with the same phone number be deleted?

No. One person can place several orders, and several employees may share a business phone. Establish whether the same enquiry was delivered again or a new request was made. A matching phone number is a review signal, not universal permission to delete.

Is disabling the submit button enough?

It helps the interface, but it does not test retries by the server or CRM. Acceptance should separately reproduce delivery of the same enquiry twice. A genuinely new request must remain possible after a successful submission.

Must contacts and deals be merged together?

Not necessarily. One contact can be linked to several independent orders. Decide what to do with the contact and each deal separately, taking their status and the salesperson’s next action into account.

Can the CRM be cleaned before the form is fixed?

Existing records can be reviewed separately. However, cleanup will need repeating if the cause remains active. Reproduce the cause with safe examples, then agree the order of the integration fix and historical cleanup.