Lead Auto-Assignment by Territory
Automatically assign new leads to sales reps based on territory, account fit, and workload balance
Salesforce integration that routes leads to the right rep based on geography, industry, company size, and current workload. Faster qualification, fairer distribution.
When a new lead arrives in Salesforce, Nora triggers instantly to read the record's location, industry, and revenue fields. It matches these values against territory and fit definitions. Next, Nora runs a SOQL query to check the open lead count for each assigned sales rep in that matched territory. It assigns the lead to the rep with the lowest current workload, logs a task on the lead record, and sends a notification with context to the assigned rep.
The sales manager who previously spent hours distributing leads manually now focuses on reviewing pipeline velocity and coaching reps. They still handle manual reassignments for conflicts of interest and evaluate performance trends, while the initial routing happens immediately upon lead creation.
Runs real-time as leads arrive using Salesforce, run by your Sales Dev Rep.
How it works
- Detect new lead — Nora listens for new lead creation events in Salesforce. It extracts the standard fields and any custom fields relevant to qualification, specifically looking at company location, industry, employee size, and reported annual revenue to begin the evaluation process.
- Evaluate qualification criteria — The extracted data is compared against the business's lead fit definitions. Nora checks if the lead falls within target parameters for employee count and revenue thresholds before proceeding with assignment, filtering out unqualified inquiries early.
- Match to territory — Using the geographic data, Nora identifies the correct territory assignment. If the location data is blank, invalid, or ambiguous, Nora assigns the lead to a default holding queue and sends a message asking a manager for manual direction.
- Query rep workload — Nora runs a SOQL query to count the currently open, unworked leads assigned to each sales representative within the matched territory. It explicitly excludes reps marked as inactive or those currently flagged as being on paid time off.
- Assign the lead — Nora updates the lead record owner to the active rep with the lowest open lead count. It logs a completed task against the lead to record the automated assignment, capturing the workload rationale for full audit visibility.
- Notify the assigned rep — Nora sends a direct message to the newly assigned rep in their designated communication channel. The notification includes the lead's name, company details, revenue size, and a direct URL to open the Salesforce record immediately.
What this replaces
A sales manager or operations lead monitors the unassigned lead queue in Salesforce. When new leads appear, they open each record to review the location and company size. They mentally map this to a territory, check a dashboard or ask around to see which rep has capacity, and manually change the record owner.
- Refresh the unassigned lead queue in Salesforce.
- Open individual lead records to review location and revenue.
- Determine the correct territory based on geographic data.
- Check rep workloads to find someone with capacity.
- Update the lead owner field and notify the rep.
Rough estimate rather than a measured figure: about 45 minutes a day, assuming 30 inbound leads and 90 seconds to review, map, and assign each one.
What it needs to run
Accounts and plans
- Salesforce edition with API access (Enterprise, Unlimited, or Professional with API add-on)
Access it asks for
- OAuth 2.0 access to Salesforce
- Read access to Lead and User objects to extract details and check workloads
- Write access to Lead object to update the owner field
- Access to run SOQL queries for workload calculation
What Nora reads
- New Lead record fields (location, industry, revenue, size)
- User records (status, territory assignment)
- Count of open leads per User
What Nora writes
- Lead Owner ID
- Task records associated with the Lead
When it goes wrong
- The lead record is created with a blank geographic location Nora stops the assignment process and routes the lead to a default unassigned queue. It sends a message to the sales manager noting the missing data and asks them to assign it manually.
- Multiple reps in the matched territory have identical open lead counts Nora assigns the lead to the rep who has gone the longest time since their last new lead assignment. It logs this chronological tie-breaker in the task history on the lead record.
- The Salesforce API rate limit is reached during a high-volume import Nora pauses operations and waits for the API quota to reset. It queues the unassigned leads internally and processes them in batches once Salesforce accepts requests again, notifying the admin of the delay.
- The lead does not meet the minimum fit criteria Nora does not assign the lead to a sales rep. It updates the lead status to disqualified or routes it to an automated marketing nurture campaign, depending on the agreed plain-language instructions.
- A rep is active but marked unavailable via a custom field Nora reads the custom availability field during the SOQL query. It excludes that rep from the workload calculation entirely and assigns the lead to the next available rep with the lowest count.
Who this is for
Worth it if
- B2B sales teams processing 20 to 100 inbound leads daily across multiple geographic regions.
- Organizations with a strict round-robin or workload-balanced routing policy that currently requires manual enforcement.
- Sales operations teams spending more than an hour a day manually checking rep capacity and updating lead owners.
Not worth it if
- Teams with very low inbound lead volume where reps self-assign from a shared queue.
- Sales processes where lead assignment requires subjective human judgement or complex relationship mapping.
- Organizations using Salesforce Essentials, which does not include the necessary API access.
A worked example
A commercial real estate software vendor receives about 40 inbound leads daily. Nora is instructed to route leads by US time zones and assign them to the rep with the fewest open records.
Salesforce Lead Record Update: - Previous Owner: Integration User - New Owner: David Chen - Status: New Activity Log: Task: Lead Auto-Assignment Comments: Assigned to David Chen. Territory: West Coast. Fit: Valid (Commercial Real Estate, $5M+ revenue). Workload: David Chen (4 open leads), Sarah Jenkins (7 open leads). Slack Notification to David Chen: New Lead Assigned: Horizon Property Group Location: Seattle, WA Industry: Commercial Real Estate Revenue: $12M You currently have 5 open leads. Link: https://[instance].my.salesforce.com/00Q8a00000abc123
Frequently asked questions
How do I change the territory definitions or fit criteria later?
You tell Nora in plain language through your chat channel. If you open a new territory in the Midwest or decide to increase the minimum revenue threshold from $5M to $10M, you send a message explaining the new rules. Nora updates its internal logic immediately and applies the new criteria to the very next lead that arrives.
What happens if a lead needs to be reassigned due to a conflict of interest?
You or the assigned rep can manually change the lead owner directly in Salesforce at any time. Nora only handles the initial assignment upon lead creation. If you tell Nora via chat that a specific rep should never receive leads from a certain competitor, it remembers that constraint for all future routing decisions.
Does Nora read all of our Salesforce data to do this?
No. Nora only accesses the specific objects and fields required for this workflow. It reads the fields on new lead records necessary for territory and fit evaluation, and it runs a targeted SOQL query to count open leads per user. It does not read your opportunity pipeline, financial data, or customer support cases.
Can we route leads based on custom fields we created in Salesforce?
Yes. Nora interacts with the Salesforce API, which exposes your custom fields and custom objects. If you qualify leads based on a custom 'Tech Stack' field or assign territories using a proprietary scoring model, you simply instruct Nora to read those specific fields and explain how they factor into the routing decision.
Connects to
Related automations
- Sales Activity Auto-Logger — Automatically log all sales emails (sent, received, replies) into a CRM activity timeline
- Lead Scoring & Qualification — Automatically score leads based on company size, engagement, and fit, surfacing hot prospects
- Deal Pipeline Auto-Advance — Automatically move deals through pipeline stages based on actions (proposal sent, demo completed, etc.)
- Contact Sync from Email & Forms — Automatically create HubSpot contacts from email senders and form submissions, no data entry
- Email Activity Auto-Sync to Salesforce — Automatically log all sales emails (sent, received, attachments) to Salesforce activities without manual work
- Opportunity Auto-Advance by Milestone — Automatically advance opportunities when milestones occur (proposal sent, demo completed, etc.)
- Sales Forecast Accuracy Tracker — Track forecast vs. actual monthly and identify which reps consistently miss targets for coaching
- Inactive Account Re-engagement — Alert you when key accounts go silent (no activity for 30+ days), triggering account review and outreach