Skip across the chapter
Quota Playbook

Lead routing controls: 8 settings for coaching

Quota Playbook Editorial Team · Published · 11 min read

Use eight lead routing controls to set distribution, eligibility, scope, capacity, rotation, teams, history, and conditions.

Key takeaways for how to set up automatic lead assignment rules for sales teams

  • HubSpot allows you to select from load balanced, round robin, or random distribution types for record owners, according to HubSpot.
  • In HubSpot, only main team members with an assigned Sales or Service Hub Professional or Enterprise seat will be eligible for assignment, according to HubSpot.
  • Pipedrive stores automatic assignment history for seven days, according to Pipedrive.
  • Microsoft Dynamics 365 allows you to add up to 10 conditions, including conditions in groups and related entities, according to Microsoft.

Equitable lead distribution is critical for maintaining team morale and maximizing conversion opportunities in sales organizations, according to Zoho.

Configure fair lead distribution using these vendor-specific checks

Manual lead assignment often results in uneven workloads, with some salespeople overwhelmed while others remain underutilized, according to Zoho. This imbalance complicates coaching because managers cannot fairly compare rep performance when input volume varies wildly. To support your coaching and ramp efforts, you need a system that distributes work evenly. See Lead assignment rules in 6 practical checks before you lock the rules. Zoho notes that round-robin assignment eliminates manual intervention, reduces assignment errors, and provides a scalable framework that adapts as your sales team grows or changes, according to Zoho.

When configuring your CRM, focus on the eight specific controls that determine how leads flow to reps. These controls include distribution type, eligibility criteria, record scope, capacity limits, rotation logic, team requirements, history retention, and condition limits. Each setting interacts with the others to create the final routing behavior. For example, a rep might be eligible by seat type but excluded by capacity limits. Or a rule might apply to all records but only trigger at a specific deal stage.

Review your current CRM's assignment settings and verify that your team members have the required seat types for automatic routing.

A filled reference table for lead assignment settings

The table below maps the eight routing controls to the specific vendor documentation that defines them. Use this reference to verify your current configuration against the source rules before your next coaching review.

Control Publisher Setting Detail
Distribution type HubSpot You can select from load balanced, round robin, or random distribution types, according to HubSpot.
Eligibility criteria HubSpot Only main team members with an assigned Sales or Service Hub Professional or Enterprise seat will be eligible for assignment, according to HubSpot.
Record scope Zoho In the Which leads would you like to apply the rule to? section, select All Leads, then click Done, according to Zoho.
Capacity limits Microsoft Alex has a maximum capacity of 50 records, according to Microsoft.
Rotation logic Pipedrive They are distributed on a round-robin basis, meaning each team member will be assigned an opportunity in sequential order, according to Pipedrive.
Team requirements Pipedrive Team assignment requires the Teams feature, which is only available to users on the Professional and higher plans, according to Pipedrive.
History retention Pipedrive Automatic assignment history is stored for seven days, according to Pipedrive.
Condition limits Microsoft You can add up to 10 conditions, including conditions in groups and related entities, according to Microsoft.

Defining eligibility and seat requirements

Before configuring routing logic, verify that your users meet the specific seat and plan prerequisites for automatic record ownership. Different platforms enforce different access levels, so confirming these baseline requirements prevents configuration errors during setup.

HubSpot defines eligibility strictly by seat type and team membership status. According to HubSpot, only main team members with an assigned Sales or Service Hub Professional or Enterprise seat will be eligible for assignment. This rule applies specifically within the context of "Assign and rotate record owners using workflows." If a user is not a main team member or holds a different seat type, they are excluded from the assignment pool under this vendor's rules.

The team structure itself also has a minimum requirement. According to HubSpot, the team must have at least one user with an assigned Sales or Service Hub Professional or Enterprise seat. You should audit your current team composition to confirm this minimum is met before enabling any rotation features.

Pipedrive ties team assignment capabilities to its plan hierarchy rather than individual seat types alone. According to Pipedrive, team assignment requires the Teams feature, which is only available to users on the Professional and higher plans. This limitation is documented in the "Automatic assignment - Knowledge Base | Pipedrive" resource. If your organization is on a lower-tier plan, the Teams feature is not accessible, which blocks the use of team-based assignment rules.

Review your user list and identify any members who lack the required seat types. Remove ineligible users from the assignment pool or upgrade their seats to match the vendor requirements. This step ensures that your routing rules only target users who can actually receive and own records. Do not assume that all users in your CRM have the same access level; verify each seat type individually.

Choosing the right distribution method

When configuring automatic routing, you must select a specific logic that dictates how records move to users. Different platforms offer distinct mechanisms for this process, so your choice depends on the specific options available in your current system.

HubSpot allows you to select from load balanced, round robin, or random distribution types according to HubSpot. This gives you three distinct modes to choose from when building your workflow. You can pick the one that best fits your team’s current volume and structure.

Pipedrive states that they are distributed on a round-robin basis, meaning each team member will be assigned an opportunity in sequential order according to Pipedrive. The system moves to the next person in line after each assignment.

When a lead is added in Freshsales, the lead’s data is run against the territory rule according to Freshsales.

You should review these options to see which aligns with your coaching goals. If you need strict equality, look for sequential logic. If you need flexibility based on lead attributes, look for rule-based matching. Each method has a different impact on how work is spread across your team.

Consider how each method affects your ability to track performance. A sequential method makes it easy to see who received what in order. A rule-based method requires you to understand the data fields being checked. Choose the method that makes the most sense for your specific data structure.

Do not assume that one method works for every team. The right choice depends on your team size and the complexity of your lead data. Test your chosen method with a small batch of leads before rolling it out to the entire team.

Setting capacity and rotation logic

Capacity limits define the maximum number of open records a rep can hold before the system stops routing new leads to them. In the assignment rule example from Microsoft, Alex has a maximum capacity of 50 records according to Microsoft. Susana gets the lead, and her available capacity is now 14, according to Microsoft.

Rotation logic dictates the sequence in which leads are distributed among eligible reps. Zoho advises managers to verify that each lead gets assigned to the next sales rep in the rotation according to Zoho. By checking the rotation order, you can confirm that the sequence matches your team's intended structure, such as alternating between senior and junior reps or balancing workloads across different territories.

Specific assignment rules allow for targeted routing based on predefined conditions. In the Microsoft example, Rule 1 assigns an incoming lead to Miriam according to Microsoft. This type of rule is useful when certain leads require specific expertise or when you want to route high-value opportunities to top performers. Combining specific rules with capacity limits and rotation logic gives you granular control over how leads flow through your team.

To implement these settings, start by defining the capacity threshold for each rep based on their historical performance and current workload. Next, configure the rotation order to match your team's structure, ensuring that the sequence is logical and fair. Finally, test the rules with sample leads to verify that the assignment logic works as expected. If a rep reaches their capacity limit, the system should automatically route the next lead to the next eligible rep in the rotation. Regularly review the assignment history to identify any bottlenecks or imbalances, and adjust the capacity limits or rotation order as needed to maintain optimal workflow efficiency.

Illustrative example of reading capacity

Illustrative figures only: a team of four reps is reviewed against eight controls. One rep may hold 50 open records. After one assignment, available capacity for that rep is 14. The rule uses 10 conditions. History is kept for seven days, and the list is copied on day seven. Three leads go to the first three places in the rotation. The last place waits for the next lead. Use the pass to see capacity, order, conditions, and history together.

Managing scope and condition limits

Record scope defines which objects your assignment rules actually touch. In Zoho, you specify this by selecting All Leads in the "Which leads would you like to apply the rule to?" section, then clicking Done Zoho. Pipedrive lets you set rules for newly created deals and leads and existing deals that are moved to a new stage or pipeline Pipedrive. This distinction matters for coaching because a rule that only fires on creation would not cover deals you choose to include when they move to a new stage or pipeline. See Deal stage progress: 7 checks for weekly coaching when you coach on stage moves.

Condition limits cap how complex your routing logic can get. Microsoft states you can add up to 10 conditions, including conditions in groups and related entities Microsoft. If your routing logic requires more than ten distinct checks, you must simplify the rule or split it across multiple assignment rules.

History retention affects how long you can audit who received a lead and when. Pipedrive notes that automatic assignment history is stored for seven days Pipedrive. If you need to review assignment decisions for coaching or dispute resolution beyond that window, you must export or log the data elsewhere before it expires.

Microsoft also clarifies that in Dynamics 365 Sales, assignment rules automatically distribute, or assign, new and updated leads, opportunities, and insights to your sales team Microsoft. This means your scope settings must account for updates, not just new records, if you want full coverage.

Review your current scope settings and verify that your condition count stays within the ten-condition limit stated by Microsoft Microsoft.

Do this before your next coaching talk

Review your current assignment settings and write down the distribution type, eligibility, record scope, capacity limits, rotation order, team requirement, history window, and condition count. Fix any mismatch you can change today, then bring that list to your next coaching conversation. For that conversation, open Sales One-on-One Agenda for Coaching Software Sellers.

FAQ: How to set up automatic lead assignment rules for sales teams

What distribution types are available for automatic lead assignment?

HubSpot states that you can select from load balanced, round robin, or random distribution types according to HubSpot.

How long is the automatic assignment history stored in Pipedrive?

Automatic assignment history is stored for seven days, according to Pipedrive.

What are the seat requirements for HubSpot team assignment?

HubSpot specifies that only main team members with an assigned Sales or Service Hub Professional or Enterprise seat will be eligible for assignment according to HubSpot. HubSpot also states that the team must have at least one user with an assigned Sales or Service Hub Professional or Enterprise seat according to HubSpot.

What is the maximum number of conditions allowed in a Dynamics 365 rule?

Microsoft states that you can add up to 10 conditions, including conditions in groups and related entities, according to Microsoft.

Sources

  1. Call handling: 9 rules to check before coaching
  2. Overtime errors for non-exempt sales reps: 5 fixes
  3. Check 8 sharing limits before sending coaching files

More plays