SalesOS.

Smart Assignment Rules

Configure intelligent lead and deal assignment using round-robin, territory, capacity, and skill-based logic.

Smart Assignment in SalesOS automates the distribution of leads, deals, and other records to the right sales representatives based on configurable rules. Instead of manually assigning each inbound lead or relying on a simple rotation, you can build sophisticated assignment logic that considers territory, workload, skills, deal characteristics, and rep availability. This ensures faster response times, balanced workloads, and higher conversion rates.

What Is Smart Assignment?

Smart Assignment is a rules engine that evaluates incoming records against a set of conditions and automatically routes them to the most appropriate rep or queue. The system supports multiple assignment strategies that can be combined and prioritized to handle any routing scenario your organization requires.

Key capabilities include:

  • Multiple assignment strategies -- Round-robin, territory-based, skill-based, load-balanced, and weighted distribution.
  • Rule chaining -- Define priority-ordered rules with fallback logic so that every record finds an owner.
  • Real-time and batch modes -- Assign instantly as records arrive or process in scheduled batches.
  • Capacity management -- Prevent rep overload by enforcing maximum active deal counts.
  • Analytics -- Track assignment effectiveness through response times and acceptance rates.

Assignment Rule Types

Round-Robin

The simplest assignment method. Records are distributed evenly across a defined group of reps in sequential order. Each rep receives the next record regardless of any other factors.

Best for: Small teams with generalist reps handling similar deal types.

Configuration options:

OptionDescription
Rep poolWhich reps participate in the rotation
Skip unavailableWhether to skip reps who are out of office or at capacity
Reset frequencyWhen to reset the rotation counter (daily, weekly, never)

Territory-Based

Records are assigned based on geographic or account-based territory definitions. When a lead comes in from a specific region, industry, or company size tier, it routes to the rep who owns that territory.

Best for: Organizations with geographic sales coverage models or named account assignments.

Configuration options:

OptionDescription
Territory fieldWhich record field determines territory (country, state, postal code, industry, company size)
Territory mapMapping of field values to assigned reps
Multi-match ruleWhat happens when a record matches multiple territories (first match, round-robin within territory)

Skill-Based

Records are routed to reps who possess specific skills or product expertise relevant to the opportunity. SalesOS matches record attributes (product interest, deal complexity, industry) against rep skill profiles.

Best for: Teams selling multiple products or serving diverse industries where specialized knowledge matters.

Configuration options:

OptionDescription
Skill tagsSkills defined in rep profiles (e.g., "Enterprise," "Healthcare," "Technical")
Match fieldWhich record field determines required skills (product interest, industry, deal size tier)
Match thresholdMinimum skill match percentage required for assignment
Tie-breakingHow to choose among equally qualified reps (round-robin, load-balanced)

Load-Balanced

Records are assigned to the rep with the lowest current workload. SalesOS counts active records per rep and routes new items to whoever has the most available capacity.

Best for: Teams where deal complexity varies and simple round-robin would create uneven actual workloads.

Configuration options:

OptionDescription
Capacity metricWhat counts toward load (open deals, active leads, pipeline value, weighted score)
Maximum capacityHard cap per rep before they stop receiving assignments
Weight by stageWhether later-stage deals count more heavily toward capacity

Weighted Distribution

Records are distributed according to percentage weights assigned to each rep. Unlike round-robin which distributes evenly, weighted assignment allows you to send more records to senior reps or reps with higher quotas.

Best for: Teams with mixed experience levels or uneven quota targets where some reps should receive more flow.

Configuration options:

OptionDescription
Rep weightsPercentage weight per rep (must sum to 100%)
Minimum per repMinimum assignments per period regardless of weight
Rebalance periodHow often to recalculate actual vs. target distribution

Creating Assignment Rules

To create a new assignment rule:

  1. Navigate to Settings > Assignment Rules from the left sidebar.
  2. Click Create Rule in the top right.
  3. Configure the rule in the creation form:

Step 1: Basic Information

  • Rule name -- A descriptive name (e.g., "Enterprise Leads - East Coast").
  • Description -- Optional explanation of the rule's purpose.
  • Record type -- Which object type this rule applies to (Lead, Deal, Account, Contact).
  • Status -- Active or Draft. Draft rules do not execute.

Step 2: Conditions

Define when this rule should trigger. Conditions use a builder interface where you specify field, operator, and value:

  • Field: Any field on the record (e.g., Lead Source, Country, Annual Revenue, Product Interest).
  • Operator: Equals, Not Equals, Contains, Greater Than, Less Than, In List, Not In List.
  • Value: The target value or list of values.

You can combine multiple conditions with AND or OR logic. For example:

  • Country equals "United States" AND Annual Revenue greater than $500,000
  • Lead Source in list ["Website," "Webinar," "Partner Referral"]

Step 3: Assignment Strategy

Select the assignment strategy (round-robin, territory, skill-based, load-balanced, or weighted) and configure its specific options as described in the rule types section above.

Step 4: Rep Pool

Define which reps are eligible for assignment under this rule:

  • Specific reps -- Manually select individual team members.
  • Team -- Select an entire team; all members are eligible.
  • Role -- All reps with a specific role (e.g., all Account Executives).
  • Dynamic -- Reps matching certain criteria (e.g., all reps with "Enterprise" skill tag who are not at capacity).

Step 5: Review and Activate

Review the complete rule configuration and click Activate to put it into effect. New rules are added at the lowest priority by default.

Rule Priority and Fallback Logic

When multiple rules could match an incoming record, SalesOS evaluates them in priority order.

Priority Ordering

Each rule has a numeric priority (1 being highest). When a new record enters the system:

  1. Rules are evaluated from highest to lowest priority.
  2. The first rule whose conditions match the record is applied.
  3. If that rule cannot assign (e.g., all eligible reps are at capacity), the system moves to the next matching rule.

Reordering Priorities

Drag and drop rules in the Assignment Rules list to change their evaluation order. Alternatively, click the priority number to enter a specific value.

Fallback Rules

Create a catch-all rule with no conditions (or very broad conditions) at the lowest priority. This ensures that records which do not match any specific rule still get assigned. Common fallback strategies:

  • Round-robin across all active reps.
  • Assign to a shared queue for manual distribution.
  • Assign to a designated team lead for triage.

Unassigned Queue

If no rule matches and no fallback is configured, the record lands in the Unassigned Queue. Managers and admins can view this queue from Settings > Assignment Rules > Unassigned and manually distribute records or adjust rules to prevent future misses.

Territory Definitions and Mapping

Territories in SalesOS define geographic or logical boundaries for assignment.

Creating Territories

Navigate to Settings > Territories to define your territory map:

  1. Click Create Territory.
  2. Name the territory (e.g., "US West Coast," "EMEA Enterprise," "Healthcare Vertical").
  3. Define the boundaries using one or more criteria:
    • Geographic: Country, state/province, postal code ranges, city.
    • Industry: Specific industries or industry groups.
    • Company size: Revenue ranges or employee count tiers.
    • Named accounts: Specific companies assigned to this territory.
  4. Assign one or more reps as territory owners.
  5. Set an optional backup rep for when the primary owner is unavailable.

Territory Hierarchy

Territories can be nested in a hierarchy. For example:

  • North America (parent territory)
    • US East (child territory)
    • US West (child territory)
    • Canada (child territory)

When a record matches a child territory, it routes to that child's assigned reps. If no child matches but the parent does, the parent's assignment logic applies.

Territory Conflicts

When a record matches multiple territories at the same level, SalesOS resolves conflicts using:

  1. Most specific match -- A named account assignment takes precedence over a geographic match.
  2. Priority -- If specificity is equal, the territory with the higher priority wins.
  3. Round-robin -- If both specificity and priority are equal, the record is distributed via round-robin among the territory owners.

Capacity Limits Per Rep

Capacity limits prevent any single rep from becoming overwhelmed with too many active records.

Setting Capacity

For each rep, you can define capacity limits in their profile or at the rule level:

  • Maximum active leads -- How many open leads a rep can hold simultaneously (e.g., 50).
  • Maximum active deals -- How many open opportunities a rep can manage (e.g., 25).
  • Maximum pipeline value -- Total pipeline dollar value cap (e.g., $2M).
  • Weighted capacity -- A composite score that accounts for deal complexity and stage.

Capacity Behavior

When a rep reaches capacity:

  • They are temporarily removed from assignment eligibility for new records.
  • Existing assigned records are not affected or redistributed.
  • They become eligible again as soon as records close, are reassigned, or are disqualified.
  • A capacity badge appears on their profile in the admin view.

Temporary Capacity Overrides

Managers can temporarily increase or decrease a rep's capacity for specific periods (e.g., during a ramping period for new hires, or when a rep is managing a large strategic deal). Navigate to the rep's profile and click Adjust Capacity to set a temporary override with an expiration date.

Assignment Queue and Notifications

Assignment Queue

All pending assignments are visible in the Assignment Queue (Settings > Assignment Rules > Queue). This shows:

  • Records waiting for assignment (if using batch mode).
  • Recently assigned records with acceptance status.
  • Failed assignments that need manual intervention.

Notifications

When a record is assigned, the receiving rep is notified through:

  • In-app notification -- A real-time alert in the SalesOS notification center.
  • Email notification -- An email with record details and a direct link (configurable per rep).
  • Mobile push -- A push notification on the SalesOS mobile app.
  • Slack or Teams -- A message in the rep's preferred channel (if integrated).

Acceptance Workflow

Optionally, you can require reps to explicitly accept or reject assignments:

  1. Enable Require Acceptance on the assignment rule.
  2. Set an acceptance timeout (e.g., 30 minutes, 2 hours).
  3. If the rep does not accept within the timeout, the record is automatically reassigned to the next eligible rep.
  4. Rejected records return to the queue and are reassigned according to rule logic.

Real-Time vs. Batch Assignment

Real-Time Assignment

The default mode. Records are assigned immediately upon creation or when they meet rule conditions. This is ideal for:

  • Inbound leads from web forms where response speed matters.
  • High-priority records that need immediate attention.
  • Small to medium volume where instant processing does not create system strain.

Batch Assignment

Records accumulate in a queue and are distributed at scheduled intervals. Configure batch assignment by setting a schedule on the rule (e.g., every 15 minutes, hourly, twice daily). This is ideal for:

  • High-volume lead sources where instant assignment is unnecessary.
  • Imported lists that arrive in bulk.
  • Scenarios where you want to ensure perfectly balanced distribution across a batch.

Hybrid Approach

You can combine both modes. For example, configure real-time assignment for high-value inbound leads (Annual Revenue > $1M) and batch assignment for lower-tier leads that can wait for the next distribution cycle.

Assignment Analytics

SalesOS tracks detailed analytics on assignment effectiveness to help you optimize your rules.

Key Metrics

MetricDescription
Average response timeTime from assignment to first rep action (view, call, email)
Acceptance ratePercentage of assignments accepted vs. rejected or timed out
Reassignment rateHow often records are reassigned after initial assignment
Distribution balanceHow evenly records are distributed across the rep pool
Conversion by assignment typeWin rate segmented by which rule assigned the deal
Speed to contactTime from lead creation to first outreach attempt

Analytics Dashboard

Navigate to Settings > Assignment Rules > Analytics to view:

  • Trend charts showing response time and acceptance rate over time.
  • Distribution heatmaps showing workload balance across the team.
  • Rule performance comparison showing which rules produce the highest conversion rates.
  • Rep-level breakdowns for coaching and capacity planning.

Optimization Recommendations

SalesOS periodically analyzes assignment patterns and surfaces recommendations:

  • "Rep A has 40% lower response time than Rep B for Healthcare leads -- consider adjusting territory."
  • "Batch assignment at 9:00 AM produces 15% higher contact rates than 2:00 PM batches."
  • "Round-robin rule 'SMB Inbound' has uneven conversion -- consider switching to skill-based."

Override and Manual Reassignment

Despite automation, there are scenarios where manual intervention is necessary.

Manual Assignment

To manually assign a record:

  1. Open the record (lead, deal, contact, or account).
  2. Click the Owner field.
  3. Search for and select the new owner.
  4. Optionally add a note explaining the reassignment reason.
  5. The previous owner is notified of the change.

Bulk Reassignment

For reassigning multiple records at once:

  1. Navigate to the relevant list view (Leads, Deals, etc.).
  2. Select multiple records using checkboxes.
  3. Click Bulk Actions > Reassign.
  4. Choose the new owner or select "Apply Assignment Rules" to re-run automated logic.
  5. Confirm the action.

Manager Override

Managers can override any automated assignment without triggering fallback logic. Overrides are logged in the audit trail with the manager's name and timestamp. This is useful for:

  • Strategic account moves between reps.
  • Handling rep departures or territory changes.
  • Correcting assignment errors.

Assignment Lock

Mark critical records as Assignment Locked to prevent automated rules from reassigning them. Locked records remain with their current owner regardless of rule changes or re-evaluation. Only managers and admins can lock or unlock assignments.

Best Practices

  • Start simple and iterate. Begin with a single round-robin rule to establish baseline metrics, then layer in territory and skill-based logic as you understand your assignment patterns. Over-engineering rules from day one creates maintenance burden without proven benefit.

  • Set response time SLAs. Define expected response times for different lead types and use assignment analytics to monitor adherence. A lead contacted within 5 minutes converts at dramatically higher rates than one contacted after an hour.

  • Review distribution balance weekly. Check the analytics dashboard during your weekly team meeting to ensure no rep is consistently overloaded or underutilized. Adjust weights or capacity limits as needed.

  • Always configure a fallback rule. Never leave records unassigned. Create a catch-all rule that routes to a shared queue or team lead so that every record has an owner within minutes.

  • Use acceptance workflows for high-value leads. For enterprise or high-revenue leads, require explicit acceptance. This ensures the assigned rep is aware and available, rather than having the lead sit unnoticed.

  • Align territories with quota and capacity. Territory definitions should reflect the realistic capacity of assigned reps. A territory with 3x the lead volume of another creates unfair workload distribution regardless of assignment rules.

  • Audit rules quarterly. As your team grows, products change, and markets shift, assignment rules need updating. Schedule quarterly reviews to retire outdated rules, adjust territories, and align with current go-to-market strategy.

  • Leverage analytics for coaching. Use response time and conversion data by rep to identify coaching opportunities. A rep with fast response times but low conversion may need help with qualification. A rep with high conversion but slow response may need workload relief.

  • Document your rule logic. Use the description field on every rule to explain its purpose and the business rationale. When a colleague needs to modify rules six months later, clear documentation prevents errors.

  • Test before activating. Use draft mode to configure new rules, then activate them during a low-volume period so you can monitor behavior before peak lead flow arrives.