Deduplicate inbound enquiries by separating the person, organisation, conversation and commercial request. Link repeated messages to the relevant request where the evidence supports it, but preserve the original messages and attachments. Do not merge every enquiry from the same email address into one opportunity.
The aim is to reduce duplicate handling without losing context. A customer sending a second attachment, correcting a date or asking about a separate project needs a visible next action, even if their contact already exists.
One contact, two genuine requests
Fictional buyer Alex sends a website enquiry about a November training day. Ten minutes later, Alex emails the same brief with an attendee estimate. The next morning, Alex asks about a separate January programme for another department.
The first two arrivals can belong to enquiry E-41, with both sources retained. The January request should become a separate enquiry linked to the same contact and organisation. A rule based only on email address would collapse distinct work.
| Record | Example identifier | What it represents |
|---|---|---|
| Contact | C-18 | Alex as a business contact |
| Organisation | O-7 | The customer account |
| Enquiry | E-41 | November training request |
| Message | M-902 | One specific arrival with attachments |
Use evidence appropriate to the record
Message identifiers can help detect repeated delivery of the same message. A form-submission identifier can prevent duplicate processing after retries. Matching two different messages to one enquiry needs business context, such as an explicit reference or confirmed relationship.
Preserve the evidence used for any suggested merge. Similar wording and a short time interval can indicate a repeat, but they are not proof. Offer staff a clear choice to link, keep separate or request clarification.
HubSpot documents contact deduplication by email and company-specific creation-path exceptions. Inspect your platform’s exact rules before implementing another layer. Contact deduplication does not automatically establish which opportunity a message belongs to.
Merge handling without erasing history
- Retain each original source and received time.
- Keep attachments linked to the message that supplied them.
- Record why two arrivals were linked.
- Preserve conflicting values for review.
- Maintain the owner and next action on the surviving enquiry.
- Provide a way to separate an incorrect link.
For E-41, the attendee estimate in the email should appear as new information, not be discarded because the form arrived first. If the email changes the date, show a conflict or revision rather than overwriting the original silently.
Include shared addresses and changing contacts
A general purchasing inbox can represent several buyers. One employee can enquire for multiple sites. Two colleagues can discuss the same project from different addresses. None of these situations is resolved reliably by a universal email-only merge rule.
Also consider forwarded messages: the forwarder may be an internal colleague, not the customer. Keep sender identity separate from the people mentioned in the content. Do not create a customer record for every address found in a signature or quoted thread.
When two enquiries are linked, inspect their task lists as well as their text. Duplicate follow-up tasks may need consolidation, but an unresolved question from either arrival must remain assigned and visible after the merge.
Test for lost work as well as duplicates
Build an authorised test set with exact resubmissions, follow-up attachments, separate projects from one contact and shared inboxes. Ask sales staff to identify the correct relationships before running the proposed matching.
Inspect false merges closely because they can hide a legitimate request. Measure duplicate records prevented, unresolved matching tasks and effort spent correcting links. Keep a reconciliation view showing every intake item and its current destination.
A CRM intake workflow should preserve more context than it removes. Start with native identifiers and reviewable suggestions, then automate only the narrow cases the team can explain and reverse.
Sources and further reading
AI-assisted research and writing, checked against the linked sources. Worked examples are fictional. Product features can change; confirm the details in your own account.