RevOps Playbook: Lead Routing, MQL/SQL Definitions, and Automation Across HubSpot and Salesforce

Published by Bles Software, a custom software and AI company based in Yehud-Monoson, Israel, building web apps, AI agents and API integrations for clients in Israel, the US, the UK and the EU.

Lead routing converts intent into revenue velocity. When routing fails, SLAs slip, sellers lose confidence, and marketing attribution erodes. This playbook provides a practical blueprint to define MQL and SQL unambiguously, route leads quickly and fairly, and orchestrate automation across HubSpot and Salesforce without creating brittle workflows. The goal is to optimize speed‑to‑lead while preserving data quality and seller trust.

We will cover scoring and thresholds, routing policies (round‑robin, territory, named accounts, hybrid), assignment timing, enrichment, and escalation. You will also learn how to implement routing as code—clear rules, versioned artifacts, and predictable release cycles—so the process scales beyond any single admin.

Scoring and MQL Thresholds

Scoring should be simple enough that a human can explain it in one breath but flexible enough to capture intent signals that matter. Start with three categories: demographic fit (ICP), firmographic fit (company size, industry, geography), and behavioral intent (content, pricing page, demo request). Assign points with conservative weights and review performance monthly.

Set MQL when the score passes a threshold and a qualifying action exists (e.g., demo request, repeated pricing page visits, high‑intent content). Do not MQL soft signals alone—three blog views should not trigger sales outreach. Publish the threshold and review it quarterly as your inbound volume and SDR capacity change. Keep the score modular so you can swap a signal without recalibrating the whole model.

SAL and SQL Criteria

Define SAL (Sales Accepted Lead) and SQL (Sales Qualified Lead) with objective criteria. SAL means an SDR has actively accepted ownership and begun outreach; it is not merely “assigned.” SQL means the lead meets your qualification framework (e.g., MEDDICC or BANT elements) and an AE agrees to progress the opportunity. Tie these transitions to explicit field updates in Salesforce and mirror read‑only states in HubSpot.

Use Salesforce validation rules or flows to require key fields at SQL (e.g., pain, timeline, budget proxy) and enable reporting that distinguishes between MQL volume and sales‑qualified pipeline. In HubSpot, read SAL/SQL to drive nurture suppression and sales enablement alerts.

Routing Policies

Routing policies should match your sales motion. Round‑robin is fair for general inbound within a region; territory routing honors geographic or vertical specialization; named accounts go to the assigned owner; and a hybrid model combines them. Express routing rules in a decision table you can maintain in source control and test in a sandbox.

Where possible, route in Salesforce when ownership logic depends on territory models, and route in HubSpot for rapid response to inbound forms when round‑robin is sufficient. If you route in HubSpot first, create a temporary marketing owner and then transfer ownership in Salesforce at SAL. Avoid dueling assignment logic in both systems; pick one system as the assignment source of truth.

Enrichment Before Assignment

Enrich leads before they hit the queue so SDRs spend time on conversations rather than research. Append company size, industry, and location at the time of capture. Normalize country and state to ISO standards and run domain normalization to link to existing Accounts. Set a minimum enrichment requirement before routing—if enrichment fails, route the record to a triage queue for manual review. This small delay prevents assignment churn and ownership changes a day later.

Speed‑to‑Lead and SLAs

Speed‑to‑lead correlates with win rates and deal sizes in many motions. Define SLAs by channel: demo requests within 5 minutes, contact sales within 15 minutes, content downloads within 1 hour, and ad‑driven inquiries within 2 hours. Measure SLA adherence by owner and region and coach consistently. For follow‑up sequences, provide a recommended cadence with talk tracks so outreach is consistent and on‑brand.

Automation Architecture

Automation fails when multiple uncoordinated workflows fight each other. Centralize routing logic and expose small, single‑purpose workflows that other automations call. For example, a HubSpot workflow that evaluates lead readiness sets a flag and calls a routing function; a Salesforce flow handles assignment and task creation; and a HubSpot workflow publishes enablement notifications. Keep each part contained and testable.

Version your automation the same way you version code. Use naming conventions, add comments, and maintain a change log. When changes are significant (new territory model, new product line), schedule a release window and a rollback plan so you can revert if queues misbehave.

Exception Handling and Escalation

Leads that lack mandatory context should not linger. Create an exception queue in HubSpot for incomplete leads and a Salesforce queue for routing errors. If an SDR does not touch a lead within the SLA, auto‑reassign or escalate to a team lead. For high‑intent channels like demo requests, escalate immediately if no activity occurs within the first five minutes.

Write alerts that fire on meaningful events: assignment failures, queue spikes, or repeated reassignment of the same lead. Alerts should include context and a recommended next action, not just a red light.

Testing and Sandbox Strategy

Test routing changes using sample records that represent your ICP and edge cases (personal emails, subsidiaries, ambiguous domains). Validate transitions from MQL to SAL to SQL in a sandbox and record the expected behavior as screenshots or short clips. Only then promote to production. After release, monitor assignment speed and queue balance for 48 hours and hold a quick retrospective to capture improvements.

Reporting That Reinforces Behavior

Report on the metrics you value: time‑to‑assignment, first‑touch time, conversion from MQL→SAL→SQL, and meetings booked by channel. Distinguish fast lanes (demo request) from warm lanes (content download) so coaching focuses on like‑for‑like comparisons. Share dashboards with SDRs and managers, not just RevOps, so the team can see progress and course‑correct early.

Enablement and Playcards

Enablement turns routing into outcomes. Provide SDR playcards with the definitions of MQL, SAL, and SQL; examples of qualified and unqualified leads; the SLA clock; and what to do when enrichment fails. Keep playcards short, visual, and discoverable from within Salesforce and HubSpot. Update them with each release and highlight what changed in a simple change log.

Continuous Improvement Loop

Routing and lifecycle should evolve with your pipeline, segments, and product. Review performance monthly with stakeholders, test a single improvement at a time (e.g., raising the MQL threshold for a high‑volume segment), and measure the effect for two weeks before adopting broadly. Track experiments like a product roadmap so the team understands why changes happen and can contribute ideas.

Conclusion

Clear definitions, pragmatic routing, and disciplined automation turn inbound chaos into predictable motion. By aligning MQL and SQL to observable behavior, enriching before assignment, and centralizing decision logic, you will reduce SLA misses, shrink reassignment churn, and increase sales confidence in the system—while preserving the agility to adjust as your business changes.

FAQ

Should we route in HubSpot or Salesforce?

Route where the logic is simplest and closest to the trigger. For pure inbound round‑robin, HubSpot is efficient; for territory‑heavy models tied to Account ownership, Salesforce is the better source of truth. Avoid maintaining parallel logic in both systems.

How do we prevent reassignment churn?

Enrich before routing, lock owner fields at creation, and require explicit SAL before any ownership changes. If ownership must change, propagate it through a single source (usually Salesforce) and mirror to HubSpot.

What if our scoring model is noisy?

Cull low‑value signals, increase the MQL threshold, and require a qualifying action for MQL. Review false positives with SDRs and adjust weights monthly until noise decreases and conversion improves.

How do we handle personal or free email domains?

Allow them to capture interest but require enrichment and manual review before assignment unless they meet very high intent (e.g., demo request). Maintain a list of allowable exceptions.

What is the best way to test routing changes?

Use a sandbox with representative sample records and scripted scenarios. Record expected behavior, promote during a change window, and monitor queue balance and assignment times for 48 hours post‑release.

More RevOps Playbooks from Bles Software