BYstudio. CRM duplicate enquiry acceptance worksheet
Version 27 October 2026. A template, not a client project report.

1. Scope
Incoming channels:
CRM entities:
Owner:
Environment and agreed test notification recipients:
Backup and recovery procedure:

2. Rules
Definition of one customer:
Definition of a separate order:
Delivery retry key and its lifetime:
Matching fields and exceptions for shared contact details:
Field precedence in conflicts:
Owner of ambiguous match reviews:

3. Scenarios: expected and actual outcomes
A. Deliver one enquiry twice with the same key and unchanged content.
B. An existing customer places another independent order.
C. Different content arrives with the same key.
D. CRM times out, then delivery recovers.
E. One customer uses two channels.
F. Two different people share business contact details.

Record for each scenario:
- Anonymised inputs and action.
- Expected counts of enquiries, contacts and deals separately.
- Actual counts and test record identifiers.
- Relationships, owner, activities, history and retained field values.
- Outcome, issues, assignee and retest date.

4. Before merging historical records
Agree a small sample and primary record.
Check retained values and linked orders.
Prepare an appropriate backup and tested recovery procedure.
Exclude ambiguous pairs from bulk changes.
Verify relationships, activities and ownership afterwards.

5. Acceptance
Integration version:
Open issues:
Accepted by:
Monitoring and review of new matches:

Do not include customer contact details, tokens or private exports in a public report.
Tests that send notifications require separate agreement.
Guide: https://bystudio.ru/en/solutions/crm-duplicate-leads/