RevOps Playbook: Lead Routing, Duplicates, and MQL/SQL Handoffs Across HubSpot & Salesforce

Speed‑to‑lead, clean ownership, and consistent handoffs define the experience prospects have with your brand. This playbook equips RevOps to design a lead routing system that is fast, fair, and measurable, while keeping duplicates under control and lifecycle transitions unambiguous across HubSpot and Salesforce.

Outcomes That Matter

Routing is successful when the right seller gets the right lead within minutes, no duplicate record harms context, and lifecycle timestamps reflect what actually happened. The outcomes to measure are assignment latency, acceptance SLA adherence, qualification rates, and duplicate ratio.

MQL Criteria and Triggers

Define MQL as a combination of fit and intent. Fit uses ICP traits (industry, employee band, territory), while intent uses behaviors (form submissions, high‑intent page views, third‑party intent). Trigger MQL in HubSpot, write the MQL timestamp to Salesforce, and create a Lead when needed. Avoid fuzzy scores as the sole trigger; supplement with discrete actions.

Routing Strategy and Rules

Routing can be round‑robin, territory‑based, or segment‑based. A hybrid is common: territories by country/region for enterprise, round‑robin for SMB. Implement the rules in the system that creates the record (often HubSpot at MQL time) and reflect the owner consistently in Salesforce. Store the assignment reason in a dedicated field so rerouting can be audited.

Ownership and Reassignment

Ownership fields must be authoritative in one place and read‑only in the other. If Salesforce is the truth for owners, HubSpot should mirror and never overwrite. When routing changes (vacations, capacity), update the policy store rather than editing each automation.

Deduplication Approach

Duplicates degrade speed‑to‑lead and reporting. Build a layered defense:

Pre‑entry dedupe on HubSpot forms by email; warn, then enrich the existing contact.
Salesforce lead creation validation to block exact duplicates and flag near‑matches for SDR review.
A rolling dedupe job that proposes merges using email + name + domain, with confidence thresholds and human approval.

Track duplicate ratio and time‑to‑merge as data health KPIs.

SAL, SQL, and Opportunity Creation

Define SAL as an SDR acceptance event with a timestamp; SQL as a qualified meeting or discovery outcome. In Salesforce, Lead Status moves from New → Working → Qualified, or equivalent, and conversion creates a Contact/Account and optionally an Opportunity. HubSpot mirrors SAL/SQL via integration with read‑only fields and back‑filled timestamps.

Handoff Artifacts

Document what information must accompany a handoff: source, last touch, pain hypothesis, ICP attributes, and meeting details. Create Salesforce Tasks with consistent subjects and a checklist embedded in the description. HubSpot workflows can draft the task and insert context automatically.

SLA Design and Enforcement

SLA adherence is the backbone of routing credibility. Define response time targets (e.g., 10 minutes for inbound MQLs) and acceptance windows (e.g., 24 hours to accept or reroute). Build monitors that alert when SLAs breach; reroute automatically if unaccepted within the window. Communicate SLA policy directly in the assignment task and surface it on home pages.

Territories, Capacity, and Exceptions

Territory design impacts routing. Keep criteria simple: country/region, segment (SMB/ENT), and industry only if necessary. For capacity, add dynamic weighting so reps with lighter pipelines receive more leads. Exceptions—strategic accounts, channel rules—should be encoded as allow/deny lists that run before main routing.

Marketing Sources and Attribution Integrity

Each routed lead should carry explicit source metadata: original source, last touch, primary campaign, and UTM parameters. HubSpot captures these easily; ensure the integration writes them to Salesforce in fields visible on Lead/Contact and later on Opportunity. Attribution breaks when fields are partially synced or overwritten.

Operationalizing Duplicate Prevention

Make it easy to do the right thing:

Provide a “search first” home component that checks recent leads/contacts by email/domain before SDRs create new ones.
Surface possible matches inline with confidence scores and a one‑click “open record” action.
Log merges with before/after snapshots and owners so audits are painless.

Metrics and Dashboards

Track the leading indicators that predict conversion and pipeline health:

Median assignment time from MQL to owner.
SAL acceptance rate and time to SAL.
SQL rate by segment and source.
Duplicate ratio and merge time.
Reroute percentage and reasons.

Share these weekly with Sales and Marketing; celebrate SLA wins and fix friction.

Runbook for Operations

When issues occur, the runbook should guide responders:

If routing fails: check eligibility flag, territory rules, user capacity, and recent ownership changes.
If duplicates appear: verify pre‑entry dedupe, lead creation validation, and the dedupe job schedule.
If attribution fields are missing: audit mapping directionality and whether HubSpot fields are locked downstream.

Implementation Checklist

Define MQL triggers with fit + intent and document the rule.
Choose routing strategy (territory/round‑robin/hybrid) and encode it in one place.
Set authoritative owner field and mirror it in the other system.
Build duplicate prevention layers and weekly merge proposals.
Instrument SLAs with alerting and auto‑reroute.
Publish dashboards and a short runbook.

Advanced Routing Topics

Deterministic Precedence and Overlaps

Conflicts arise when a record matches multiple rules (e.g., an enterprise lead in a territory where a strategic rep owns the top 50 accounts). Define an ordered list of rule families—“Allow/Deny Lists → Strategic Account Ownership → Territory → Capacity Weighting → Round‑Robin”—and stop evaluating after the first match. Log the matched rule to a field for auditability.

Account‑Level and Buying Group Routing

Route net‑new people at known accounts to the existing account owner and SDR, even if their form country differs slightly. For buying groups, attribute inbound to the opportunity owner if an open opportunity exists; otherwise to the account owner. This reduces cross‑team thrash and keeps outreach consistent.

Warm Handoffs and Meeting Quality

Handoffs fail when the context is missing. Standardize Task subjects and embed a checklist: problem statement, last three touches, content consumed, ICP fit, and the call‑to‑action. Track meeting held rate and no‑show rate by owner to reinforce quality.

Experiments and Continuous Improvement

Routing is a lever you can tune. Run controlled experiments:

Compare round‑robin vs capacity‑weighted assignment for SMB.
Test a 15‑minute vs 10‑minute SLA breach alert.
Pilot a high‑intent fast track where booking a meeting bypasses SDR triage.

Measure conversion, cycle time, and rep feedback before rolling changes broadly.

Case Study: Reducing Duplicates by 70%

By adding pre‑entry dedupe and a weekly merge proposal job, a growth‑stage company cut duplicates from 6% to 1.8% in 60 days. Speed‑to‑lead improved by 22% and attribution coverage rose as Campaign Member statuses no longer split across copies of the same person.

Service Desk and Training

Create a simple intake form for routing issues with fields for email, domain, expected owner, and observed behavior. Triage daily, fix rule gaps, and publish a short “what changed this week” note. Train SDRs to search first, merge responsibly, and use notes to improve handoffs. Short Loom videos embedded in your enablement hub outperform long docs.

FAQ

Should routing happen in HubSpot or Salesforce?

Do it where the record is created. If HubSpot creates the MQL, route there and set the owner before the record appears in Salesforce. If SDRs create leads in Salesforce, route in Salesforce.

How do we handle personal email addresses?

Flag personal domains and route them to a special queue for enrichment before assigning. This prevents wasted SDR cycles on low‑quality leads while preserving true signals when a champion uses Gmail temporarily.

What is the simplest effective territory model?

Country/region and segment (SMB/ENT) cover most needs. Add industry only when it drives materially different motions and you have capacity to maintain it.

How do we know if duplicates are hurting speed‑to‑lead?

Correlate assignment latency with duplicate ratio at the daily level. If spikes in duplicates precede SLA misses, tighten pre‑entry checks and empower SDRs with better search/merge tools.

Who owns SAL and SQL transitions?

Usually SDR leadership owns SAL, Sales leadership owns SQL. Keep the authoritative system for each decision to one platform and mirror the state to the other for visibility.