What this lead routing agent handles
Inbound leads decay fast when ownership is unclear or triage waits for a human to review every record. A Salesforce lead routing agent handles the assignment decision while keeping an operator in control of the final write.
This setup is especially useful in three routing situations:
- Territory-based assignment. The agent reads the lead's location, industry, and segment, then proposes the correct owner based on your territory rules.
- Account-based routing. For leads from companies you already work with, the agent checks the existing account owner and proposes assignment to the same rep or the account team.
- Queue fallback. For leads that do not match any owner rule, the agent proposes queue assignment or flags the lead for manual review.
How the agent works
The table below shows the trigger, inputs, outputs, and approval logic so you can judge operational fit quickly.
| Agent stage | What happens | Output | Approval |
|---|---|---|---|
| Trigger | A new lead enters Salesforce from a form, import, or enrichment source | Routing job starts | No approval for read phase |
| Inputs | Lead source, territory, company size, product interest, account ownership rules | Ranked routing decision | No approval for data gathering |
| Proposed action | Set owner, assign queue, add notes, or flag for manual review | Prepared CRM update | Approval before any write |
| Operator review | Reviewer checks why the route was chosen and what fields will change | Approve, reject, or edit | Explicit approval required |
How to set up lead routing
Define your routing logic in plain language, including territory rules, account ownership rules, and exceptions.
Connect Salesforce with access to the lead objects and assignment fields needed for the agent.
Decide which edge cases should always surface individually for review and which proposals can be reviewed in batches.
Set notifications so the operator sees proposed routing batches quickly when inbound volume spikes.
Permissions and approval checks
- Read access should cover the lead record, owner mapping data, and relevant account context.
- Write scope should be limited to owner assignment, queue assignment, and approved note fields.
- Fallback routes should be logged clearly so manual review can improve the rule set over time.
- Approval views should show both current and proposed assignment data before commit.
Frequently asked questions
Does lead routing happen automatically or does it require approval?
By default, lead routing proposals are surfaced for review before the assignment is written to Salesforce.
How does the agent decide which owner or queue to assign?
The agent applies your assignment logic: territory rules, account ownership rules, segment criteria, and exceptions. You describe the logic in plain English, and the agent reasons over the lead data to propose the correct assignment.
What happens if the routing logic changes?
Update the agent description, review the new execution plan, and activate. The agent adapts to the new logic without requiring builder edits or Apex changes.
Can the agent route to queues, not just individual owners?
Yes. The agent can propose queue assignment, owner assignment, or a combination based on your rules. Queue assignments work the same as owner assignments: the proposal is reviewed before the write executes.