CRM Lead Routing Software for Rules, Rep Pools, and Territories
Assign leads from forms, bookings, and inbound webhooks to fixed owners or round-robin pools. Use on-demand routing rules, territories, and an unassigned queue to keep lead ownership clear.
Routing rules, by priority
Enterprise EU · fixed rep
No matchCompany present · Source equals Partner
Webinar Leads · rep pool
First valid matchLead Source equals Webinar → round robin, inactive reps skipped
Catch-All · fixed rep
Not reachedNo conditions · runs last
If no rule matches
Run from the Route action on the lead record. Evaluation stops at the first rule that resolves to an active owner.
The Short Version
What Is CRM Lead Routing?
CRM lead routing is the process of assigning leads to sales owners based on predefined assignment rules, rep pools, or territory logic. It helps teams keep ownership clear instead of relying on someone to manually distribute every new lead. KudosCRM supports automatic owner assignment at selected capture points, on-demand lead routing rules, round-robin pools, territory management, an unassigned lead queue, owner notifications, and assignment auditing.
Assign at Capture
Forms, booking pages, and inbound webhooks can assign an owner as the lead enters KudosCRM.
Route with Defined Rules
Apply priority-ordered lead routing rules from the lead record when ownership needs to be resolved.
Share Leads Across Rep Pools
Use concurrency-safe round-robin assignment or leave leads unassigned for your team to claim.
Manage Territories
Assign leads, companies, and deals to structured territories with priorities, managers, dates, and overlap checks.
Automatic capture assignment and workspace routing rules are separate. Capture surfaces can assign owners when leads arrive, while the general routing-rules engine currently runs from the Route action on the lead record.
Assign New Leads at the Point of Capture
New leads do not always need to wait for a separate routing step. KudosCRM supports owner assignment directly from forms, booking pages, and inbound webhooks, with each capture path using assignment options that fit its workflow.
Assign Leads from Forms
Each form can leave the lead unassigned, assign a fixed rep, or rotate through a round-robin pool of up to 50 reps. When a submission creates both a contact and a lead, both records receive the same owner.
Protect Existing Ownership
Form assignment only fills an empty owner. If a repeat submission comes from a lead already owned by a rep, KudosCRM does not take the lead away from that rep.
Assign Ownership from Bookings
Booking pages can assign the resulting lead and contact to the meeting host, a fixed rep, or a round-robin ownership pool. The booking's CRM owner rotation is separate from meeting host selection — a host pool chooses the first available meeting host in configured order, not calendar round robin.
Resolve Owners from Inbound Webhooks
Inbound webhook events can leave the lead unassigned, assign a fixed rep, read the owner from the incoming payload, or rotate through a workspace pool. Owner values from the payload can match by email or external ID.
Respect Working Hours on Webhook Rotation
Inbound webhook pools can skip reps who are outside their working hours. If nobody is currently inside working hours, KudosCRM falls back to the full pool rather than dropping the lead. Working-hours-aware rotation currently applies to inbound webhooks only.
Keep Chats with the Existing Owner
When KudosCRM can connect an inbound chat to a known lead, deal, or open ticket, the conversation follows the rep who already owns that relationship.
Owner assignment, per capture path
Forms
Booking pages
Inbound webhooks
Assignment only fills an empty owner
A repeat submission never takes a lead away from the rep already working it.
What a rule can test
Five operators
Conditions inside one rule combine with AND. Nested OR conditions are not currently supported — use two rules instead.
Route Leads with Priority Rules and Clear Fallbacks
Lead routing rules give teams a controlled way to resolve ownership when a lead needs to be routed. KudosCRM evaluates enabled rules by priority, stops at the first valid match, and then uses a workspace fallback when no explicit rule assigns an owner.
Run Rules by Priority
Higher-priority routing rules run first. The first matching rule that resolves to an active user assigns the owner and stops further evaluation. A condition-free rule can also be used as a final catch-all.
Route on Six Lead Fields
Standard lead routing rules currently support Lead Source, Lifecycle Stage, Job Title, First Name, Last Name, and Company.
Use Five Rule Operators
Conditions support equals, not equals, present, blank, and in list. Multiple conditions inside one routing rule use AND logic. Nested OR conditions are not currently supported.
Assign a Fixed Rep or Rep Pool
Each routing rule can assign one fixed rep or rotate through a round-robin rep pool. Inactive users are skipped — if a fixed-owner rule points to an inactive rep, KudosCRM continues to the next routing rule instead of stopping.
Turn Rules On or Off
Individual rules can be enabled or disabled without deleting the configuration. Inactive rules are skipped during routing.
Route a Lead on Demand
The Route action on the lead record runs the complete routing rule set. This is the current trigger for the workspace routing-rules engine.
Decide What Happens When No Rule Matches
KudosCRM supports four workspace default strategies: Round Robin rotates across active workspace reps, Territory uses the matching territory's reps, Creator keeps ownership with the record creator, and Manual leaves the lead unassigned until someone claims or assigns it.
Use Round-Robin Pools and an Unassigned Queue to Control Lead Ownership
Not every lead needs the same assignment method. KudosCRM combines round-robin pools with a visible unassigned queue, giving teams a structured way to distribute leads automatically or let reps claim them when manual ownership makes more sense.
Rotate Leads Across Rep Pools
Forms, booking ownership, and supported webhook assignment can rotate leads through configured rep pools, preserving the order set by the admin.
Keep Concurrent Assignments Accurate
Round-robin assignment uses an atomic rotation cursor. If two submissions arrive at nearly the same time, they cannot consume the same rotation turn and accidentally assign the same slot twice.
Skip Inactive Reps
Inactive users are removed from pool resolution so deactivated accounts do not continue receiving new leads.
Leave Leads Unassigned When That Is the Right Workflow
Teams can deliberately keep leads unassigned instead of forcing ownership. The leads inbox includes All, Mine, My Team, and Unassigned views, and the Unassigned view can be shared through its filter state.
Claim a Lead in One Click
An unowned lead can be assigned using Assign to me. If the server rejects the assignment, the interface rolls the change back.
Claim or Reassign Leads in Bulk
Select multiple leads to claim them or assign them to another rep. Partial failures are reported rather than hiding which records did not change.
Change Ownership from the Inbox
An inline owner picker lets authorized users change a lead's owner or deliberately move the lead back to Unassigned.
Keep New Assignments Visible
A newly assigned lead stays marked unread for the new owner until that person opens it. A manager viewing the record does not clear the new-owner state.
Every lead shows its owner — or sits visibly in the Unassigned view until someone claims it.
Route Leads, Companies, and Deals into Managed Territories
Territory management gives larger sales teams a structured way to divide CRM ownership by market, region, customer type, or other business rules. KudosCRM supports territory hierarchies, priorities, effective dates, managers, overlap detection, performance reporting, and rules for leads, companies, and deals.
Build Territory Hierarchies
Create parent and child territories such as EMEA → DACH. Hierarchy rules prevent circular structures and allow performance to roll up through child territories.
Set Priorities and Active Dates
Each territory can have a priority, effective start and end dates, a manager, and a rep roster. If two territories match the same record, priority determines which one wins.
Assign Territories Automatically
Leads, companies, and deals can receive a matching territory when they are created or while the territory field is still empty. An existing territory assignment is not silently overwritten — changing it later is an explicit, recorded action.
Use Different Rules by Record Type
Lead territory rules can use Country, Source, Channel, Stage, Grade, Company, and Predicted Value. Company territories can use industry, size, lifecycle, revenue, and country. Deal territories can use value, status, label, industry, company size, and country.
Use Grade for Territory Assignment
Lead Grade can be used in a territory rule — for example, Grade A or B → Enterprise Territory. This assigns the territory; it does not directly route the lead owner based on Lead Score.
Detect Territory Overlap Before It Causes Confusion
KudosCRM checks active territory rules for ambiguous overlap. When two territories can match the same record, the system flags the pair and identifies which territory wins under the current priority order.
Territory hierarchy
EMEA
Priority 10Manager, rep roster, effective dates
DACH
Priority 20Rolls performance up to its parent territory
Benelux
Overlap flaggedCan match the same record as DACH — priority decides the winner
Hierarchy rules prevent circular structures. Existing territory assignments are never silently overwritten.
Notify New Owners and Keep Every Ownership Change Auditable
Ownership should be visible after the routing decision, not disappear into the background. KudosCRM notifies assigned reps, records ownership changes, and controls who has permission to change the owner of CRM records.
Notify the New Owner
When one user assigns a lead to another, KudosCRM can send an in-app notification and an OS-level Web Push notification, even when the browser tab is closed. Self-assignment notifications are suppressed.
Name the Routing Decision
When a routing rule assigns a lead, the routing record identifies the mechanism that made the decision — for example, “Lead routed via ‘Enterprise EU’ rule.”
Audit Every Lead Owner Change
Every lead ownership change creates an audit-log record containing actor, IP, previous value, and new value. The audit log is filterable and can be exported to CSV.
Keep Timeline Claims Precise
Contact owner changes appear on the contact timeline, and territory changes appear on the related record timeline. Lead assignee changes are always available in the audit log, but are not a lead timeline event in every case.
Separate Edit and Assignment Permissions
Changing ownership has its own permission, so a team member can have permission to edit a lead without automatically having permission to take ownership of it.
Keep Ownership Inside the Workspace
Owner IDs are validated against the current workspace, so a record cannot be assigned to a user from another workspace. Owner changes are also broadcast to other open KudosCRM tabs.
How It Works
How Does Lead Routing Work in KudosCRM?
KudosCRM uses different assignment paths depending on how the lead enters and how your team wants ownership handled.
Configure Your Assignment Method
Choose fixed owners, round-robin pools, territory rules, workspace defaults, or a manual unassigned workflow.
A Lead Enters KudosCRM
The lead can arrive through a form, booking page, inbound webhook, chat flow, or another CRM process.
Capture-Time Assignment Runs Where Configured
Forms, bookings, and inbound webhooks can assign an owner immediately. Territory rules can also assign a matching territory during record creation.
Run Routing Rules When Needed
Use Route on the lead record to evaluate the priority-ordered workspace routing rules. The first rule that resolves to an active owner wins.
Apply the Workspace Fallback
If no explicit rule assigns the lead, the workspace default can use Round Robin, Territory, Creator, or Manual assignment.
Notify and Record the Ownership Change
The assigned rep can receive an in-app and Web Push notification, while the owner change is written to the audit log.
What's Actually in the Box
Lead Routing and Assignment Features in KudosCRM
Priority-ordered routing rules
First valid match wins
Six lead routing condition fields
Five condition operators
AND-based rule conditions
Fixed-rep routing
Per-rule round-robin pools
Inactive-user protection
Enable and disable routing rules
On-demand Route action
Four workspace fallback strategies
Atomic round-robin assignment
Form owner assignment
Booking owner assignment
Inbound webhook owner assignment
Working-hours-aware webhook rotation
Unassigned lead queue
One-click lead claiming
Bulk claim and reassignment
Inline owner picker
Territory hierarchy and priorities
Territory effective dates and managers
Territory overlap detection
Territory assignment history
Territory performance reporting
In-app assignment notifications
Web Push notifications
Owner-change audit log
Separate owner-change permissions
Cross-workspace assignment protection
KudosCRM Lead Routing vs. Manual Lead Assignment
Give Every New Lead a Clear Ownership Path
Assign leads at capture, route them when needed, and keep unassigned leads visible until someone takes responsibility.
Lead Routing Software for Teams Sharing Inbound Leads
Keep ownership organized when several reps, teams, or territories work from the same incoming lead flow.
Connect Routing to Your Team's Tools
Notify the new owner in Slack, follow up from Gmail, or send assignment events to any system that accepts a webhook.
Slack
Gmail
Google Calendar
ZoomGo Deeper
Features That Work with Lead Routing
Lead routing is part of the Lead Qualification stage of the journey — where every captured lead is scored, graded, and given a clear owner.
All FeaturesFAQ
Frequently Asked Questions
Route With Control
Give Every Lead a Clear Owner, Territory, or Next Step
Assign leads at capture, distribute them across rep pools, manage territories, and keep every ownership change visible.