Lead Routing
Part of Inbound lead routing
Preventing duplicate contact from several salespeople
Give each enquiry one external response owner, check existing conversations and stop competing sales follow-up.
Give one person responsibility for the external conversation about an enquiry. Before replying, check its owner, related requests and recent messages. Colleagues can contribute internally, but a shared notification is not permission to contact the requester.
Find the source of the overlap
Several messages can result from separate records for the same request or from several people acting on one record. Record matching can reveal possible duplicates; a contact-ownership rule determines who may reply. Both need attention.
A repeated form submission may contain a new question. Preserve its wording and received time rather than discarding it; one owner can coordinate the answer to that distinct request. Likewise, two people at one organisation may be asking about different projects, and a shared company name alone does not make their conversations duplicates.
Set a rule before outreach
The intended first responder can:
- Check the enquiry, contact and related requests.
- Review recent outbound messages, calls, bookings and open follow-up tasks visible to the team.
- Confirm who owns the external reply and whether one is already in progress.
- If ownership changes, pass on the latest context and cancel or reassign competing tasks.
- Record the next external action so colleagues know who will take it.
Check what the local system actually captures. A call or message from an unlogged channel can leave the shared record incomplete.
Understand what duplicate controls do
Review possible duplicate matches and preserve distinct new requests before treating records as duplicates. Check which record supplies ownership in the actual account before another workflow changes it.
HubSpot's Rotate record to owner workflow action can assign records to paid sales and service users. If the owner property syncs to Salesforce, the action may not work as expected; when assigning leads, the Sync lead owner with contact or company owner setting must be turned off. Subscription, paid-seat and record-type conditions apply; rotation of lead records is labelled beta.
Duplicate Control Considerations in HubSpot and Salesforce
- HubSpot Rotate Record to Owner WorkflowAssigns leads to paid sales/service users; available for lead records (beta)
- Salesforce Duplicate PreventionUses matching rules to detect potential duplicates; can be configured with custom logic
- Sync Lead Owner with Contact/Company OwnerMust be turned off in Salesforce if using HubSpot rotation to avoid conflicts
Recover after parallel replies
Stop competing follow-up, compare what was sent and appoint one person to continue. That person can give the requester an accurate next step without guessing why the overlap happened. Record whether the cause was repeated records, competing automation or a manual handoff.
After changing the process, review repeat-submission and multi-owner cases. The useful question is whether each distinct request received one coordinated response, not simply whether the database contains fewer records.
