how lead assignment rule works in salesforce

• AppAssessor

Articles by role:

• Consultants
• Business Analysts

By Lucy Mazalon

By Ben McCarthy

• Dreamforce Events
• Courses Login

What’s trending

Is Salesforce Still a Good Career Option in 2024?

Salesforce Acquires Own Company for $1.9B in Cash: 4 Key Takeaways from This Mega-Deal

SF Ben Salesforce Salary Survey Results 2024-25

Salesforce Announces Free Marketing and Commerce Expansion Pack to Enterprise Licenses

Official Dreamforce Parties and Events Guide 2024

UPCOMING EVENTS

Implementing omnistudio best practices for performance and scalability, dreamforce parties 2024.

San Francisco, CA

Dreamforce 2024

Dreamforce – house of cloud, dreamforce – sfb hub, salesforce lead assignment rules best practices and tricks.

By Stacy O’Leary

I confess: I love Salesforce Lead Assignment Rules almost as much as I love the Approval Process . A good set of Lead Assignment Rules will buy you endless friends in both sales and marketing, and will make your incoming data sparkle and look perfect (even if it is not!) In this guide, I’ll be talking about the initial Lead sort, upon creation.

Salesforce Lead Assignment Rule Example

• Criteria #1: If State = California, assign to Stacy
• Criteria #2: If Country = United Kingdom, assign to Ben
• Criteria #3: If Country = France, assign to Lucy
• Criteria #4: If Annual Revenue is greater than $500,000,000 USD, assign to “High Roller Queue”

Planning Lead Assignment Rules

Discovery: questions to ask.

• Where are the new Leads coming from? Marketo? HubSpot? Other integrated systems? Web forms? Are there any examples you look at? Make friends with the people who run these systems, you need to have a good relationship because you’re going to need their help.
• What fields are populated on these newly created Leads? What fields are required? If it’s minimal, can you get more information? Generally, the more information you have, the easier it is to sort.
• What if a Lead comes in from one of your Partners? What if a Lead comes in from one of your competitors? From one of your employees? Are there any kinds of Leads that should never be distributed out to your team, like students or media inquiries? (Remember – ANYONE with access to the internet can fill out your form! They do not have to be a legitimate prospect!)
• Who is covering what territories? Do you have any territories that don’t have a sales rep yet? Do all new Leads have enough data to determine territories?
• What about the Leads that don’t meet any criteria at all? Where will they go? Who will work them?

Refining the requirements

• Our new Leads, almost always, come from Marketo . They could come from a Marketo form, or a list imported from a trade show, but Marketo is the system that pushes them to Salesforce. If a person creates their own Lead, we do not want to take it away from them.
• We always have: first name, last name, lead source, email, company, state and country. We sometimes have # of Employees, but that’s pretty much all we know about them at the moment of creation.
• Any Lead that comes in from a Partner should be directed to our channel team. We don’t want to market to competitors, employees, or students.
• We have a territory plan defined by Sales, and we’d also like to separate prospects for the UK and France, though we do not have a sales rep for those areas yet.
• If something comes in that we cannot otherwise sort, let’s put it in a holding place and let marketing send out generic nurture emails. If a person in this holding place takes interest, we can always give it to the sales team later.

• Partners (any Lead that comes in from a Partner company)
• Disqualified (any Lead that comes in from a competitor, is an employee, or is a student)
• UK + France (any Lead where Country = United Kingdom, or France)
• Unsorted (any Lead that does not meet any criteria)

Creating Lead Assignment Criteria

Leads that shouldn’t be distributed, next criteria.

The Final Empty Criteria

Activate the Lead Assignment Rules

• Leads can only be sorted by a field value at the moment it was sorted.
• The Lead Router does not auto-convert Leads to Contacts
• You cannot deactivate a User license if that person is part of the Lead Assignment Rules (even if the Lead Assignment Rules have been deactivated.)
• Create a report for yourself, for that last criteria – Leads that are unsorted. This way you can review them periodically and see if there’s enough volume to justify sorting them in a certain way.

Stacy O'Leary

More like this:

Data lakes vs. data lakehouses: a salesforce admin’s guide.

By Joseph Gaska

4 Ways Leveraging Historical Data in Salesforce Can Unleash Crucial Insights

By Mike Melone

A Guide to Salesforce Duplicate Management in the Age of Data Cloud

By Mehmet Orun

Leave a Reply Cancel reply

Save my name and email in this browser for the next time I comment.

We surveyed hundreds of B2B companies about their top go-to-market challenges...

• Intelligent Lead Delivery
• Convert Signals to Revenue
• Enterprise Salesforce Orchestration
• Products Overview Discover modern Revenue Orchestration
• Integrations Connect signals to plays
• Pricing Plans for every company
• Why LeanData

Snowflake Scales Account Based Plays with LeanData Revenue Orchestration

Clockwise Supports PLG Motion with LeanData Revenue Orchestration

• Become a Partner Team up with LeanData
• Technology Partner Directory Discover ISV solutions to fit your needs
• Solutions Partner Directory Connect with our network of authorized Service Integrators

LeanData’s integration with Salesloft allows a user to route prospects to the right reps.

Slack has transformed business communication– it’s the platform where work can happen.

Expertly target and engage high-value accounts when they’re ready to buy.

LeanData’s integration with Outreach allows a user to route prospects to the right reps.

• Learning Center
• Certification
• Tips & Tricks
• Help Center
• About Us Learn more about us and our mission
• Newsroom Keep up with what’s new at LeanData
• Events Stay up to date and network with industry professionals at our upcoming events
• Careers Join the LeanData team
• Contact Us Get your questions answered - contact us now

G2 Recognizes Lead-to-Account Matching and Routing as Newest Tech Category, with LeanData the #1 Vendor

Leandata showcases power of modern revenue orchestration at opsstars 2022, leandata announces winners of the 2022 opsstars awards, what are lead assignment rules in salesforce.

Lead assignment rules are a powerful feature within Salesforce to assist your team’s automation of its lead generation and customer support processes. Assignment rules in Salesforce are used to define to whom your Leads and Cases (customer questions, issues or feedback) are assigned based on any one of a number of specified criteria you determine. 

Organizations typically develop lead assignment rules for their GTM processes or flows:

• Rules for inbound Leads
• Rules for website-generated Leads
• Rules for importing Leads from an event

For case assignments, a company might establish one case assignment rule for weekdays and another assignment rule for weekends and holidays. 

A lead or case assignment rule often consists of multiple rule entries to specify exactly how leads and cases are assigned throughout your go-to-market teams. For example, related to customer service inquiries, a standard case assignment rule might have multiple entries. Cases with “Type equals Gold” are assigned to the Gold Level service queue, cases with “Type equals Silver” are assigned to the Silver Level service” queue, and so on. 

As organizations grow and scale, they operationalize multiple GTM motions: inbound, outbound, account-based, upsell/cross-sell, and hybrid. However, many are limited to having just one rule in Salesforce.

As a work-around, many organizations create one massive lead assignment ruleset. They then wedge all of their rule entries into that one big ruleset, regardless of how many different motions that represents. Over time, Salesforce lead assignment rules can quickly become unmanageable .

This post covers the best practices for Salesforce lead and case assignment rules. The ultimate goal is to fully engaging your hard-won leads and speed up your organization’s time-to-revenue.

How to Define Assignment Rules

Your Salesforce administrator can only have one rule in effect at any particular moment in your go-to-market motions, and that assignment rule is intended to both automate lead generation processes and other customer-facing processes routed through your CRM. 

Lead assignment rules specify how leads are assigned to users or queues as they are created manually, captured from your website, or imported via SFDC’s Data Import Wizard.

Case assignment rules determine how cases are assigned to users or put into queues as they are created, either manually or through the use of Web-to-Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service portal, the Customer Portal, Outlook, or other data generation applications.

Criteria for Lead Assignment Rules

Okay, so you’ve decided that lead assignment rules in Salesforce make sense for your revenue operations team – now what?

Well, first, you’ll need to determine the edition of your Salesforce instance. Lead assignment rules are available in the Group, Essentials, Professional, Enterprise, Performance, Unlimited, and Developer Editions of SFDC. Case assignment rules, conversely, are available only in the Professional, Enterprise, Performance, Unlimited, and Developer editions.

With regard to User Permissions, to view assignment rules, you’ll need View Setup and Configuration permissions. However, to create or change assignment rules, you’ll need Customize Application. If you are not your organization’s Salesforce administrator, you should check with them before attempting to head off on your own.

How to Create Salesforce Lead Assignment Rules

Creating lead and case assignment rules in Salesforce is a relatively straightforward process. 

• Login to Salesforce and select Setup in the upper right corner of the horizontal navigation bar.
• In the Setup search box , type “assignment rules” and then select either Lead Assignment Rules or Case Assignment Rules.
• Select New to create a new assignment rule.
• In the Rule Name box, type a name and specify whether it should be active for leads or cases created manually and by those created automatically by web and email. When done, click Save .
• Click open your newly created rule and select New in the Rule Entries to specify your rule criteria.
• Step 1 in the “Enter the rule entry” window requires you to enter an Order for your new rule (the Order is the order in which the entry is processed, like a queue).
• In Step 2, you determine whether your new rule is based on meeting a set of criteria or a formula. In the Run this rule if the dropdown box, select either “criteria are met” or “formula evaluates to true.”
• Lastly, in Step 3, select the user or queue to whom your rule will assign your new lead or case (use the lookup feature to find specific users or a queue). After completing Step 3, select Save .

Why Are Your Salesforce Lead Assignment Rules Not Working?

If you discover your lead or case assignment rules are not working, here are a few tips to quickly troubleshoot the root cause.

First, check to ensure the assignment rule is active. Remember, only one case or lead assignment rule can be active at one time. Secondly, ensure the record is assigned to the correct user or queue.

Make certain to select the checkbox Assign using active assignment rule . In support of this step, enable field History tracking on case or lead owner, as well as add object History (case or lead) in your page layout. 

One common problem is overlapping rule entries, or rule entries in the wrong order. With dozens of rule entries, many will overlap, causing records to get assigned unpredictably. For example, if entry #1 assigns California leads to John, and entry #2 assigns Demo Request leads to Jane, then John might wonder why he’s receiving Demo Requests leads who are supposed to go to Jane. 

Assignment Rule Examples

The image, below, shows sample rule entries being entered into Salesforce for a variety of “what if” situations:

• Junk leads containing “test” are sent to an unassigned queue
• Demo requests are routed directly to SDR 3
• Leads at accounts with over $100 million in annual revenue are routed to AE 1
• Leads in certain states are sent to their respective representatives

How LeanData Simplifies Salesforce Lead Assignment

Creating lead and assignment rules in Salesforce is relatively straightforward. However, as your GTM motions become more and more complex, it becomes necessary to populate that one rule with multiple defining rule entries. As you grow and scale, your rule threatens to become unwieldy. Then these problems arise:

• Difficulty in both comprehending and managing
• Poor visibility, making it difficult to troubleshoot and validate
• Restrictions allowing only the criteria on the routed record

LeanData’s lead routing flow and assignment solution is a native Salesforce application that allows users to create flows in an easy-to-understand visual graph. Its visible representation of an organization’s desired lead flow affords many benefits to users, including:

• Easier ability to visualize and understand complex flows
• Real-time visibility of the routing of leads and the ability to quickly troubleshoot and make adjustments
• At-a-glance ability to use information on matched records for routing decisions and actions

Assignment rules in Salesforce are a relatively easy-to-learn feature that can be very quickly implemented, delivering a flexible and powerful logic to your CRM processes. Automating your lead and customer processes will accelerate your GTM motions and deliver your organization a sustainable competitive advantage.

For more best practices, read the eBook, “ Best Practices for a Winning B2B Marketing Data Strategy .”

• lead assignment rules
• lead assignment rules salesforce

Ray Hartjen

Ray Hartjen is an experienced writer for the tech industry and published author. You can connect with Ray on both LinkedIn  &  Twitter .

More Related Content

How to Automate Lead Routing in Salesforce

How assignment rules work in Salesforce When leads come into your Salesforce instance, a rep needs to reach out to...

Salesforce Lead-to-Account Matching, the Easy Way

Salesforce lead-to-account matching is an important consideration in better aligning Sales with Marketing and increasing the efficiency and productivity of...

10 Best Lead Assignment Tools for Revenue Teams (2024)

Lead assignment tools optimize sales processes by building efficiency into lead distribution. Here are the top 10 lead assignment tools worth investigating.

Guide to lead assignment rules in Salesforce

Use SFDC lead assignment rules to get more done, create a better experience, and close deals faster.

Rachel Burns Jul 24, 2023

15 min read

Table of contents

Experience scheduling automation for yourself!

Create a Calendly account in seconds.

What are Salesforce lead assignment rules?

What if your sales team could spend their valuable time connecting with prospects and closing deals — instead of losing time doing admin work like assigning and organizing leads?

When you automate lead assignment and routing, your sales team can:

Boost sales team productivity and efficiency

Prevent high-quality leads from slipping through the cracks

Create a better experience for potential customers

Speed up your entire sales pipeline to close more deals, faster

In this blog post, we'll discuss the ins and outs of Salesforce lead assignment. We'll cover the benefits, how to plan your lead assignment strategy, and a step-by-step walkthrough of adding lead assignment rules in Salesforce. We'll also explore the power of scheduling automation to simplify and speed up lead assignment, routing, and qualification.

Key takeaways:

Lead assignment rules help sales teams boost productivity, respond to leads faster, and make better data-driven decisions. 

Matching leads with the right sales reps and teams creates a better customer experience by responding to leads faster and giving them personalized attention.

Before you set up your lead assignment rules, work with your sales, marketing, and RevOps teams to understand your lead generation processes and sales team structure.

Within Salesforce lead management settings, rule entries are the individual criteria and actions. A “lead assignment rule” refers to a set of rule entries. 

Automating lead routing , qualification, and booking with Calendly helps your team be more efficient and organized while creating a better experience for prospective customers.

6 benefits of creating lead assignment rules in Salesforce

Why should your team take the time to set up lead assignment rules in Salesforce? Here are six great reasons:

Ensure leads are assigned to the right reps and teams: Lead assignment rules mean each incoming lead is directed to the salesperson or team who has the relevant expertise and skills to engage and convert that lead. Automated lead assignment also prevents leads from falling through the cracks by making sure each lead is assigned to a rep or team, rather than relying on manual assignment.

Respond to leads faster: With lead assignment rules, leads are automatically assigned to the right salesperson, reducing response time and increasing the chances of converting leads into customers .

Boost sales team productivity: Automating lead assignment reduces manual work for RevOps teams and sales managers. Lead assignment rules also help identify and prioritize leads more likely to convert, saving time and resources that would otherwise be wasted on pursuing poor-fit leads. These time savings let sales teams focus on nurturing leads and closing deals.

Create a better customer experience: Leads can be assigned to sales reps who have relevant industry or product expertise, understand their unique needs, and can provide personalized solutions. This tailored approach creates a better experience for leads, which results in more conversions and higher customer satisfaction.

Improve sales forecasting: With well-defined lead assignment rules, you can gather more accurate data on lead distribution and conversion rates. This data can be used for sales forecasting, data driven decision-making, and resource allocation.

How to create lead assignment rules in Salesforce

Step 1: build your lead assignment strategy.

Before you go into your Salesforce instance and set up lead assignment rules, you need to figure out what exactly those rules will be. The options are limitless — where should you start?

It’s time to bring RevOps, sales, and marketing together to answer some questions:

Lead sources: Where do leads come from? Do we use marketing forms through Salesforce web-to-lead forms or a third-party integration? Are we importing leads via the data import wizard?

Sales team structure: How is the sales team structured? Are different teams or individuals specialized in specific products, industries, use cases, or regions?  

Lead data: What info do we request from new leads? Which standard and custom fields do we require?

Sales territories: How are sales territories defined? Are there specific regions, countries, or territories we should take into account for lead assignment?

Integrations : Do we have any third-party integrations with lead assignment or distribution features? Are we using those features?

Special circumstances: Are there any priority levels or tiers for leads that require special attention? For example, do we have a designated rep or queue for leads with complex needs and use cases?

Poor fits: What should we do with leads who don’t meet any of our criteria?

It’s a lot of information to gather and organize, but it’s important to learn as much as possible up front to cover every scenario and equip your sales team with accurate data. Putting this time and effort in now will pay off tenfold in productivity once your lead rules are in place!

Step 2: Set up lead assignment rules in Salesforce

You’re almost ready to enter your lead assignment rules in SFDC . First, let’s go over some terminology. We’ve been talking about lead assignment rules as individual directives: “If the lead matches X, then do Y.” Within Salesforce lead management settings, a “lead assignment rule” refers to a set of rule entries. Rule entries are the individual criteria and actions (“If X, then do Y”). An assignment rule can consist of up to 3,000 rule entries, and you can only have one active assignment rule at a time.

For example, a rule entry can assign all leads interested in a particular product to a queue of reps who are experts on that product. In Salesforce, a lead queue is essentially a bucket for unassigned leads, and you can choose which sales reps can pull leads from each queue.

Another rule entry can assign all leads from companies with over 5,000 employees to your top enterprise sales rep.

To create a lead assignment rule in Salesforce: 

From Setup, enter “Assignment Rules” in the Quick Find box, then select Lead Assignment Rules.

Enter the rule name. (Example: 2023 Standard Lead Rules)

Select “Set this as the active lead assignment rule” to activate the rule immediately.

Click Save.

Click the name of the rule you just created.

Click New in the Rule Entries section.

Enter an order number that tells Salesforce when to run this rule entry in relation to other rule entries. For example, if you want this to be the first criteria Salesforce looks at when assigning a lead, enter number one.

Select the rule criteria. What attributes must the lead have before Salesforce applies the rule entry? You can use any standard or custom field in the lead record for your criteria. For example, you want to assign leads to your U.S.-based enterprise sales team, so the company size field must be equal to or greater than 5,000 and the country field must equal the United States. You can include up to 25 filter criteria.

Choose the user or queue to be the assignee if the lead meets the criteria. For example, assign to the U.S.-based enterprise sales team queue.

Optional: Choose an email template to use when notifying the new lead owner. After you set up your lead rules, you can also use Salesforce Flow automations to notify lead owners via other channels. For example, at Calendly, we integrate Salesforce with Slack, and a workflow automatically notifies sales reps via Slack when a lead is assigned to them.

Salesforce goes through the rule entries in order until it finds one that matches the lead's info, then routes the lead accordingly. 

Let's say you have small business, mid-market, and enterprise sales team queues. Your first three rule entries would match company size to each of those three queues. If they don't have a company size listed, or the company size doesn't match any of the values in your rule entries, Salesforce will move on to the industry rule entries.

To make sure no leads fall through the cracks, you also need to set a default lead owner. If the assignment rules fail to locate an owner, or you don’t set up assignment rules, web-generated leads are assigned to the default lead owner.

To select a default lead owner:

From Setup, enter “Lead Settings” in the Quick Find box, then select Lead Settings and click Edit.

Define the Default Lead Owner. The Default Lead Owner can be a specific user or a queue.

Save your settings.

Salesforce lead assignment rule examples

As we mentioned earlier, your rule entries can include up to 25 filter criteria.

Simple rules include just one filter criteria:

By country or state/province: Route leads from specific states or countries to sales representatives who understand the regional market. You need this rule if your team uses sales territories to divide leads. For example, if the state/province equals Alaska, Arizona, California, Hawaii, Nevada, Oregon, or Washington, assign the lead to the West Coast queue.

By language: Assign leads to sales reps who speak the same language.

By industry: Assign leads from different industries to salespeople who have experience working with those industries.

By company size: Assign leads based on the size of the company, assigning larger companies to a dedicated enterprise sales team.

Complex rules use two or more filter criteria. For example, you could route leads from specific states or provinces to salespeople based on their sales territory and the company size. If you have a particular rep (Bob) working enterprise leads on the West Coast, your filter criteria could say: If the state/province equals Alaska, Arizona, California, Hawaii, Nevada, Oregon, or Washington, and the company size equals greater than 5,000, assign the lead to Bob.

These are just a few examples. Lead assignment rules can be customized to fit your team’s and customers’ needs. Review your strategy to choose the right combination of criteria for your sales processes, products, and customers.

What does the built-in Salesforce lead process look like in action?

A website visitor named Nora fills out a contact form to learn more about your product. She shares her name, email address, company name (Acme Inc.), and company size. You use Salesforce’s built-in web-to-lead forms , so Nora’s form submission automatically creates a lead record.

Your team has set up lead assignment rules that assign leads to sales queues based on their company size. Acme Inc. has 5,000 employees, so Nora is automatically assigned to the enterprise sales team queue.

Enterprise sales team queue members receive an email notification that a new lead has been added to the queue. Taylor, an enterprise sales rep in Acme Inc.’s territory, assigns Nora’s lead record to themself.

Taylor emails Nora to set up a qualification call.

Nora, who has been waiting to hear back from your team, agrees to meet with Taylor. After some email back-and-forth, they find a time that works.

What are the limitations of Salesforce’s built-in lead assignment rules?

Salesforce’s built-in lead assignment rules are a great place to start, but there are a few critical limitations, especially for enterprise sales teams:

Single level of evaluation: Salesforce assignment rules operate based on a single level of evaluation, meaning that once a rule matches the criteria and assigns a lead, the evaluation process stops. Your team might miss out on important info, like a complex use case or unique industry, when matching the lead with a rep.

No built-in round robin distribution: Round robin lead distribution is the process of assigning leads to reps based on factors like team member availability or equal distribution for a balanced workload. Salesforce lead assignment rules don't include an easy way to set up round robin distribution — you need an additional tool like Pardot, one of the round robin apps on AppExchange , complex Apex code , or a third-party lead routing platform .

No lead escalation settings: Lead escalation is the process of flagging a lead to higher levels of management or specialized teams for further assistance or action. This process comes into play when a lead requires additional attention or intervention beyond the assigned salesperson or team's capabilities. Unfortunately, Salesforce doesn’t have built-in settings for lead escalation rules. If your customer success team uses Service Cloud, you can set up escalation rules for customer support case escalations, but this feature isn’t included in Sales Cloud.

High maintenance for large organizations: Managing and maintaining a comprehensive set of assignment rules can become challenging and time-consuming in large organizations with complex sales structures and multiple teams or regions. Sure, you can include up to 3,000 rule entries in a single lead assignment rule, but that’s a lot to set up and keep up to date — especially if you’re trying to save your team time, not add to their workload.

Built-in Salesforce lead assignment rules and automations are a solid starting point, but what about automating lead qualification and booking? If you use Salesforce on its own, your reps might still spend a ton of time on lead reassignment to balance their workload, manual lead qualification, and email back-and-forths to schedule sales calls.

That’s where Calendly comes in.

How to automate lead assignment, qualification, and booking with Calendly

Your scheduling automation platform can be an excellent lead generation, qualification, and routing tool — especially when it integrates with Salesforce. Calendly’s Salesforce integration helps your team be more efficient and organized while creating a better experience for prospective customers.

When a lead books a meeting via a sales rep or team’s Calendly booking page, Salesforce automatically creates a new lead, contact, or opportunity. If the lead already exists in your Salesforce instance, the event is added to the lead’s existing record, so you don’t end up with duplicate lead records or time-consuming manual reassignment.

What if you don’t want to let just anyone book a meeting with your team? When you add Calendly Routing to your marketing forms, you can show scheduling pages only to leads who meet your qualifications, like prospects from specific industries or companies of a certain size. That way, your busy team can spend time on the most valuable deals.

Calendly Routing works with HubSpot , Marketo , Pardot , and Calendly forms and is built for your Salesforce CRM. You can use any form field (email, domain, company name) in any Salesforce standard object to match visitors with their account owner. Account lookups let you send known leads or customers from your website form directly to their account owner’s booking page, without needing to manually reassign leads to the right rep.

Remember the lead assignment example we walked through earlier featuring Nora from Acme Inc.? Here's what that process looks like when you add Calendly:

Nora fills out your “contact sales” form, which is already built in HubSpot, connected to Calendly Routing , and enriched with Clearbit .

She enters her email address in the form, and Clearbit fills in the company name, size, and industry. This shortens the form, so Nora only has to input her name and job title.

Calendly checks to see if Acme Inc. has an account in your Salesforce instance. They don’t, so the next step is lead qualification .

Based on Nora’s information — company size, industry, job title — she’s a highly qualified lead, so she’s automatically routed to the booking page for your enterprise sales team.

Nora is happy about that, and immediately books a meeting time that works for her, with the exact team she needs to talk to.

On the backend, Calendly’s Round Robin meeting distribution is set to optimize for availability, so it assigns the meeting to the first available sales rep — in this case, Taylor. This automation helps your team respond to meeting requests faster, hold initial sales calls sooner, and balance the workload across reps.

Calendly creates a lead record in Salesforce with the info Nora entered into your website form (including the data from Clearbit) and an activity log of any meetings she books with your team via Calendly. Salesforce automatically makes Taylor the lead owner.

If you were relying on Salesforce’s built-in lead assignment rules, Nora’s lead record would have gone to an enterprise sales queue, and she would have had to wait for a rep to pick up the lead and reach out to her to book a meeting.

“ A good tool is one that’s so simple, sales reps can basically forget about it and let the meetings roll in. That’s essentially what happened when we implemented Calendly. ”

Sales Enablement Manager at SignPost

What happens if a lead doesn’t qualify for a meeting? Instead of sending them to a booking page, you can display a custom message with next steps, ask them for more information, or redirect them to a specific URL, like a piece of gated content or a webinar signup page.

Automating lead assignment with Calendly Routing has been a game changer for RCReports , a compensation analysis solution for accountants and business valuators. Before connecting Calendly Routing with their Salesforce instance, RCReports’ AEs spent at least five hours a month reassigning leads booked on the wrong calendar. This created a disjointed customer experience and frustration for the sales and marketing teams.

“ Now that we’ve implemented Calendly’s routing feature with Salesforce integration, demos are always booked with the correct AE, reducing friction for both our team and the customer. ”

Abbie Deaver

Director of Marketing at RCReports

Users on Calendly’s Teams plan and above can connect Calendly to Salesforce. The full suite of Salesforce routing features , including routing by Salesforce ownership, is available on Calendly’s Enterprise plan.

To learn more about Calendly Routing, get in touch with our sales team .

Spend less time on manual lead assignment and more time closing deals

When you automate Salesforce lead assignment and routing, high-value leads stop slipping through the cracks, the workload is balanced across the team, leads are matched with the sales reps best equipped to help them, and team members have more time to focus on connecting with prospects and closing deals. 

The results? A more productive team, faster sales cycle, higher conversion rates, and better customer experience.

Webinar: How Calendly Uses Calendly to Close More Deals

Rachel Burns

Rachel is a Content Marketing Manager at Calendly. When she’s not writing, you can find her rescuing dogs, baking something, or extolling the virtue of the Oxford comma.

Related Articles

Read Time: 15 minutes

How to write sales follow-up emails that keep deals moving

Connect with prospects and close deals faster with these follow-up email tips and templates.

How to prep for a sales demo with confidence

Real-world tips to tackle discovery, create agendas, and manage pre-demo anxiety.

Help! What do I do after a sales demo?

A timely follow-up keeps sales momentum high and closes deals faster.

Don't leave your prospects, customers, and candidates waiting

Calendly eliminates the scheduling back and forth and helps you hit goals faster. Get started in seconds.

• Product Overview
• Select Accounts
• Assign Accounts
• Optimize Coverage
• Dynamic Books
• RevOps Resources
• Documentation

How to use Salesforce lead assignment rules

When your organization gets to the point that you have a) leads coming in on a regular basis and b) multiple sales reps, you quickly realize you need a way to divide up those leads among your reps. If you're using Salesforce, you may have noticed a built-in feature called Lead Assignment Rules. Sounds perfect, right? Sort of. We'll walk you through it.

Here's our agenda:

• The basics of lead assignment rules

Matching and assigning with rule entries

• Issues and challenges with lead assignment rules

The basics of lead assignment rules in Salesforce

Let's take a look at lead assignment rules in Salesforce. Go to your Salesforce org's Setup section and search for "lead assignment" in the Quick Find box. You'll find these buried under Feature Settings > Marketing > Lead Assignment Rules. If you don't see it, make sure you have permissions for "View Setup and Configuration" and "Customize Application".

• Unique names - Every lead assignment rule has a unique name [1].
• A lead assignment rule is really a list of "rule entries" - Salesforce calls each of the individual rules in the list a "rule entry" [2]. Each rule entry allows you to say something along the lines of: "if a lead meets these criteria, assign it to this user (or queue - more on that in a moment)".
• Rule entry order matters - The list of rule entries [2] is processed in a specific order you define. Salesforce will process each rule entry until it finds a match. Once it finds a match, it will assign the lead based on how the rule entry is configured.
• Only one active rule at a time - You can only have one lead assignment rule set to active [3].

Now that we've got a decent idea about what a lead assignment rule looks like, let's dive into rule entries.

Every rule entry has three parts:

• Order - This is a number that indicates where the entry exists in the list. Rule entries are evaluated starting at 1 and then processing until one of the rules matches.
• Matching Criteria - Leads are compared to the matching criteria for each rule to determine if the lead matches. The first rule that matches is used to determine assignment.
• Assignment - This tells Salesforce what you want to do once a lead has matched the matching criteria. Usually, you'll tell Salesforce to assign it to a user or a queue.

Order is pretty straightforward. The complexity really lies in matching criteria and assignment. let's spend some time on those.

Matching criteria

There are two types of matching criteria: filter criteria and formulas. You'll probably use filter criteria the most, so let's start with that one:

One key limitation is that you can only configure criteria using fields from the lead, the current user, and the campaign associated with the lead.

Here's what it looks like to create a formula rule entry:

hbspt.cta._relativeUrls=true;hbspt.cta.load(8216850, 'e84fc167-06c5-4b7b-bb34-42ccff0e2db4', {"useNewLoader":"true","region":"na1"});

Let's go back to the rule entry screen and focus on the assignment section:

So, what's the difference between a user and a queue?

• User - In business terms, this is a particular sales rep who will be responsible for managing the lead. In technical terms, this is an active Salesforce user configured in your Salesforce org.
• Queue - A Queue is a list of records (usually Leads, but not always) that are accessible to a specific group of users. Each of those users can take ownership of a record from the queue, removing it for the others. When you assign ownership of a Lead to a Queue, you're effectively making it first-come, first-serve for a group of users. This is not the same as a "round-robin" assignment where you assign the Lead to one person from a list of users.

There's one last thing to know about assigning ownership. Note the checkbox labeled "Do not Reassign Owner"[3]. This controls what happens when a lead is updated and matches the criteria. If this is checked, the assignment will essentially be ignored. Use this to prevent toggling users back and forth.

The last field, "Email Template" [4] allows you to specify a particular email template to use for notifying the new assignee when the assignment is complete.

Issues and challenges

Lead Assignment Rules are a reasonable choice for a small team with simple rules. They work and the only cost to you is the administrative overhead of creating and maintaining them. Unfortunately, they're extremely limited and don't cover many common use cases. They also become very brittle as your team size and lead velocity increase. Here are a few common issues and challenges:

• Leads only - They only apply to the Lead object (there are Case Assignment Rules for Cases, but that's it). This may make them a poor fit for your sales process if you need to do lead-to-account matching or you're pursuing an account-based strategy . If you need to assign other things besides Leads, you'll need to try a more flexible automation solution like Flow .
• Hard to test - Unlike Process Builder or Flow, your Lead Assignment Rules don't provide any form of versioning or debugging so it's hard to test them without just doing it live.
• Hard to audit  - There's no record of  why a lead was assigned in a particular way. You'll have to go look through your rule entries to figure it out. This can quickly get painful as the number of rules increases.
• One rule at a time - If your company has very different rules for different leads (e.g. from different campaign sources or applicable to different product lines), it can be very challenging to craft your rule entries in a way that handles more than one lead routing flow.
• No round-robin - It's technically possible to do a very poor version of round-robin with Lead Assignment Rules, we don't recommend it. It's extremely brittle and will break without lots of maintenance.

Where to go from here?

If you've got a small team with simple processes, give Salesforce lead assignment rules a try; they may give you just what you need. If you find yourself needing to assign other objects besides Leads, perform round-robin rep assignments or maintain a full audit trail, you might want to consider Gradient Works.

Hayes Davis

Hayes Davis is co-founder of Gradient Works. Previously, Hayes was SVP of Revenue Operations at Cision, where he ran a global team of 50 supporting nearly 600 sellers. He was also co-founder and CEO of Union Metrics until its successful acquisition by TrendKite in 2018. Hayes has a background in computer science.

CONNECT WITH ME

Related posts.

Salesforce Lead Assignment Rules: How To Manage The Salesforce Lead

You're busy, and managing leads in Salesforce is a pain. You want to use the system but there's just too many hoops to jump through. This blog post will help you understand how salesforce lead assignment rules work and show you how they can make your life easier when assigning leads in Salesforce.

Lead assignment is a critical function in any sales organization and it has been our experience that many companies are not following these simple rules due to lack of understanding or poor training. 

We hope to help you avoid these mistakes by sharing some of the most common mistakes made when assigning leads in Salesforce with you.

What Are Salesforce Lead Assignment Rules

Salesforce lead assignment rules allow a user to specify rules that pick up a specific value from a custom object and assign it to the Contact Manager field of the Lead.

Lead assignment rules are created based on your business requirements, for example: If a prospect fills out an interest form or email marketing survey , you can automatically add their information as Leads in Salesforce, which makes them available for sales reps to follow up with.

Or maybe your company is growing rapidly and you need opportunities to be auto-assigned every time one is updated by an internal team member. In all these cases, lead assignment rules come in handy .

A lead assignment rule can be executed when a custom object record has been created, updated or deleted. It starts with a trigger and ends with an assignment rule.

For example: whenever a user updates the 'Lead Status' field on the 'Opportunity' object, update or delete (depending upon whether Lead Status is set to Closed/Lost or Reopened) the associated Contact record on the 'Cust Team' custom object.

To create this Lead Assignment Rule

• Navigate to Setup
• Leads  and click on New Assignment Rule. Give your lead assignment rule a name and select Sub Object as Opportunity then choose Trigger as Updated Opportunity Status.
• Leave Conditions as Blank and click Save.

The moment you save the lead assignment rules, Salesforce creates a picklist of Available Values with two options – Yes and No.

This is because a lead assignment rule can either create or update a record on another object, depending on the condition that you set.

Now, let's say you want to automatically create a new Lead record whenever the 'Lead Status' field on the 'Opportunity' object is set to Closed/Lost. To do this, we'll need to add an Assignment Rule. Select Assignment Rule as New Lead and choose the action as Create.

Under Object Type , select Lead and under Field Name , select Status . Leave Conditions blank and click Save .

You've now created a lead assignment rule that will automatically create a new Lead record whenever the 'Lead Status' field on the 'Opportunity' object is set to Closed/Lost.

But wait, this rule will create Leads for Closed/Lost Opportunities only. What if you also wanted to automatically create a lead whenever the Status is set to Reopened? 

Well, all you need to do is add another Assignment Rule and choose both rules as New Lead . Select the action Create under the object Salesforce creates a picklist with three options – Yes , No , and No Match. This signifies that it will either update or create records depending upon its conditions.

To edit an existing assignment rule, follow these steps:

• ‍ Navigate to Setup | Customize | Leads | Assignment Rules. The Assignment Rules page displays all of your existing rules together. You can filter this list by selecting a particular object, such as Accounts or Contacts, and then clicking on the Edit button.
• ‍ The Rule Details page for the selected rule displays. This page enables you to edit the rule's name, description, and conditions. You can also specify which objects the rule applies to, what type of action to take (such as Create or Update), and which fields on those objects to use.
• When you're finished editing, click Save.

You can also delete a lead assignment rule by following these steps:

• ‍ Navigate to Setup | Customize | Leads | Assignment Rules. The Assignment Rules page displays all of your existing rules together. You can filter this list by selecting a particular object, such as Accounts or Contacts, and then clicking on the Delete button.
• ‍ The Rule Details page for the selected rule displays . This page provides information about the rule, including the rule's name, description, and conditions.
• ‍ Click Delete to remove the rule from Salesforce. There are many different ways to use lead assignment rules in Salesforce. By creating rules that automatically update or create records on other objects, you can save time and ensure that your data is always up-to-date.

The Seven Rules Of Compliance: Salesforce Lead Assignment Policy

Now that we have covered the basics of Lead Assignment Policy, it's time to get into the specifics. Below are the seven rules of compliance for Salesforce Lead Assignment rules:

Rule 1: All leads must be assigned to a user. 

This is a basic rule and should go without saying. All leads must be assigned to a user in order for them to be worked. If you're not sure who should receive a lead, consult your company's sales process and procedures.

Rule 2: Leads must be assigned in a timely manner.

Leads should be assigned as soon as they are created in order to ensure that they are worked promptly. 

However, there may be cases where a lead expires before it has any activity. In these cases, you can either let the lead expire or reassign it to another user who may work it later on.

Rule 3: A user cannot belong to more than one owner-recipient pair in a single Salesforce organization.

A lead must be owned by one person, but that same lead can be assigned to one or more users within your team using owner-recipient pairs. 

However, no single user should appear in multiple owner-recipient relationship fields for different leads in your database. If this happens, then all recipients will receive every opportunity created from every new lead that's assigned to the problematic user! 

To avoid this, create a new lead assignment policy with the problematic user excluded. Then, create a new lead assignment policy without the problematic user and re-assign all of your leads to the appropriate users using owner-recipient pairs.

Rule 4: A user cannot be a recipient in more than one owner-recipient pair within a single Salesforce organization.

As shown by Rule 3 above, you can have an owner for a lead as well as multiple recipients on that same lead record. However, no single user should appear as both an owner and a recipient on different leads that are under the same qualifying rules. 

If this happens, then all of those leads will route directly to your Salesforce Inbox ! To avoid this, simply create a new lead assignment policy with the problematic user excluded and re-assign all of your leads to the appropriate users using owner-recipient pairs.

Rule 5: A recipient cannot be a member of more than one owner-recipient pair in a single Salesforce organization.

This is another rule that should go without saying, but just like Rules 3 and 4 above, it's important to ensure that you're not setting up multiple recipient relationships for the same user within your Salesforce instance. 

To avoid this problem, simply create a new lead assignment policy with the problematic user excluded and re-assign all of your leads to the appropriate users using owner-recipient pairs.

Rule 6: Recipients must own at least one opportunity to be considered valid.

If you're looking for the most basic rule to begin with, this is it. If recipients are not set up to own one or more opportunities, then they won't have any activities in Salesforce automatically created for them when a lead is assigned. 

This means that Leads will need to route directly into your Salesforce Inbox until you either create some activities for your team or manually assign the lead back to the original owner. 

To avoid this problem, simply create a new lead assignment policy with all of your existing recipients included and re-assign all of your leads accordingly!

Rule 7: You cannot add existing users as recipients if their user records contain fields that are incompatible with assignment policy criteria.

There may be one or more cases where you have users who are already in your system but are not set up to receive leads through your lead assignment policy. 

If you try to add these users as recipients for this newly created rule, then their accounts will show up in red because they won't meet the criteria defined in the assignment policy's qualifications field. 

To fix this problem, simply create a new lead assignment policy by including existing recipients in your Salesforce instance. Then, re-assign all of your leads accordingly!

What Are The Drawbacks Of Using Salesforce Lead Assignment Rules?

Lead Assignment rules are an extremely powerful tool inside Salesforce. They enable business users to control who can view and respond to leads, while also streamlining workflows and ensuring that important leads aren't being ignored.

However, as with all features in Salesforce, there are several drawbacks or limitations that need to be taken into account when a lead assignment rule is put into use:

• A lead has to meet the criteria of all lead assignment rules assigned to it, which might not always be possible. Imagine a Business Development Manager using a Lead Assignment Rule so they receive all high priority leads from two queues - one for new accounts and one for existing customers. But what if the lead doesn't have an account? In this case both queues would be evaluated, even though the lead should only go to one of them.
• Rules can be time consuming and complex to set up. The business user has to have a good understanding of how the rule works in order to create it.
• Rules can be overridden by other users if they have access to the lead. This means that although the Lead Assignment Rule was supposed to ensure that a specific person received the lead, it could end up going to someone else if they're faster at responding or have more seniority.

Overall, Lead Assignment Rules are an extremely valuable tool for controlling workflows and ensuring that important leads don't fall through the cracks. 

However, it's important to be aware of the drawbacks and limitations when using them in order to make sure they're being implemented in the most effective way possible.

Salesforce Lead Assignment Rules are an extremely powerful tool inside Salesforce. They enable business users to control who can view and respond to leads, while also streamlining workflows and ensuring that important leads aren't being ignored.

Himangi Lohar

Get paid for your time, join the marketplace for b2b pitches, meetings, and connections, see cliently in action, start engaging with your prospects, start engaging with your users and clients today, don't miss out, sign up for our newsletter.

September 30, 2021

Speed Up and Sell More: Salesforce Lead Assignment Rules Best Practices

Get the latest RevOps insights

When a lead comes in, an opportunity should come knocking.

But there’s a lot more under the hood. You need solid lead assignment rules in place, and one key variable to keep in mind.

Time. According to LeadSimple, responding to a lead in the first 5 minutes is 21x more effective.

No surprises here. If you’re a scaling business, you know that responding first to a lead is mission-critical.

If you’re manually triaging leads or waiting for IT to make business-critical changes to your lead assignment rules, it’s not scalable. Nor fast.

As an operations leader, you feel this pain across your entire organization. 

Demand teams work hard to generate incoming leads, so it doesn’t make sense to abandon them just because they’re not getting to the right rep in real-time. Your leads, after all, are directly tied to sales revenue.

Automating the process doesn’t solve the problem alone, either. It’s an important piece to speeding up, but not the only piece to the lead assignment puzzle.

You’re inundated with the notion often – speed is everything!

Well, we’re here to tell you:

Respond right is the new respond first.

Shotgun responses don’t help if your lead happens to work for a target enterprise account of yours. You definitely want your Enterprise sales rep, Rachael putting her best foot forward.

Setting the right lead assignment rules also helps with what ‘future you’ couldn’t know ahead of time.  Say a lead comes in from a territory that doesn’t have a rep assigned – It’s going to sit in a queue. A potential quality lead slipped through the cracks of time because there’s no accountability or rule in place.

Complex business processes and go-to-market efforts add additional layers of friction. How can you get it right if you’re constantly evolving at scale?

Your lead assignment process could be stunting your growth potential.

It’s time to speed up, starting with smarter lead assignment rules. 

Give your operations teams their sanity back, and set your sales reps up for speed-to-lead success.

Go ahead and skip the next section if you’re already aware of the challenges to overcome as a scaling business, and want to get right to Salesforce lead assignment rules for success.

Businesses Quickly Outgrow Native Salesforce Lead Assignment Rules

Asana, a project management platform, was scaling fast.

They were grappling with increasing volumes of leads, lagging response times, and complex assignment rules that became impossible to keep up within Salesforce.

As more leads came in from a variety of sources, and with complex territory assignments and hundreds of sales reps that change frequently, lead assignment became a nightmare to manage in native Salesforce.

That’s because creating and changing lead assignment rules can quickly become very complex:

Only a dozen or so lead assignment rules are implemented here, primarily basic rule sets like location, company size, industry, or lead quality. You can imagine how cluttered your rules would get as you continued to add more criteria.

Asana knew that not having a more sophisticated Salesforce workflow automation process meant they didn’t have the flexibility to adapt at scale.

There were two problems Asana needed to overcome:

1. Complex, evolving go-to-market rules

You wouldn’t want sales reps responding to a lead that’s not in their sales territory. You also wouldn’t want junior reps following up with your largest target accounts.

But it happens.

Typical go-to-market (GTM) models are unique by company and can vary by:

• Named account
• Role or product focus
• Partner channels and more

How a company sets up their go-to-market strategy informs how they need to route or assign leads to reps. SaaS sales teams are regularly selling into different territories, market segments (SMB, mid-market, enterprise), verticals, and industries.

What’s more, lead assignment rules often require changing daily with large enterprise businesses. 

Asana, for example, consistently had leads assigned to reps that no longer worked with them.

Imagine juggling complex territory assignment rules and hundreds of sales reps that change frequently?

It can take weeks or months for IT to get involved whenever a Salesforce lead assignment rule needs to be changed:

• IT has to define the required changes, scope them, slot those into a sprint, which may occur weeks or months later
• During the sprint, the team will make the changes, validate them, test them
• Push them from the development environment to the QA environment, and perhaps a staging environment, and then finally into production

Doing things manually, or not at all, is not a scalable alternative.

You can automate to help you move faster, but speed is sidelined when you don’t have the flexibility to adapt to your changing assignment or routing environment.

And it only gets worse as your lead volume climbs.

2. Massive volumes of incoming leads and lagging response times

When too many cars are trying to get to various destinations, traffic jams occur, with some drivers giving up and going somewhere else altogether.

If companies are slow to respond, the chances of those leads sticking around drops with every. passing. minute. Someone else will hop on a plane instead and get facetime sooner.

You need to move faster.

On average, it took companies 42 hours, or almost two days, to respond to a lead .

That’s basically a lifetime:

Dramatics aside, it means most B2B companies are still falling behind and not responding to leads within the five-minute-or-less sweet spot. But it’s there for the taking.

In the past, we had people manage catchall queues, trying to figure out who should own each lead. – Jim Maddison, Veracode

In Xant’s Lead Response Study 2021 of 5.7 million inbound leads at 400 plus companies, they found that 57.1% of first call attempts occurred after more than a week of receiving a lead.

So why are most companies lagging behind? They need to automate and create more adaptable lead assignment rules that actually reflect their go-to-market.

Speed might be serving up the silver platter, but you’re only going to get the deal if you implement effective salesforce lead assignment rules.

Here are some best practices to help set yourself up for success.

Lead Assignment Rules Best Practices For High-Growth Companies

You’ve got massive volumes of incoming leads and ultra-complex go-to-market rules. You’re in the right place.

First things first.

Automate, automate, automate. 

Let’s get to that golden window of 5-minutes. Picture Tesla’s “Come to Me” app (it comes to you and eliminates a long trek to your parking spot).

It requires one tap.

Once a lead enters Salesforce, they follow the defined rule roadmap according to lead assignment rules that you set and ultimately land with the correct salesperson in record time.

You’re giving back those precious minutes to your revenue and sales operations teams.

Now about those rules.

Define Your Go-To-Market Rule Baseline

Carving out territories based on geography, segments, verticals, industries, named accounts, or whatever your go-to-market strategy is, is the first step. This is your baseline.

Any lead that falls into a sales rep’s territory should be assigned to them based on these defined rules, but that’s easier said than done. They’re constantly changing based on several factors.

You need to define your criteria  

In other words, the set of criteria that you will be implementing – you know the drill. To do so, you ask all the necessary questions:

• Which rep will take on what territories?
• What happens if new reps are hired and old ones leave?
• What happens if someone goes on vacation? Or doesn’t work on Fridays?
• A lead comes in from a partner, where do you want this to go?

The beauty is that the sky is the limit.

But how do you get there with native Salesforce constraints lacking the required sophistication?

We had about 800 or 900 rule criteria. We needed something flexible and something that could change, or help us change as we change our business a year to year. – Jim Maddison, Veracode

The next step:

Create customer rule criteria 

Veracode, a security company, had incredibly complex criteria. They had to hire a developer to manually code changes to lead assignment rules. Things changed daily for them, and they grappled with how to adapt.

Ditching the code for the intuitive drag and drop Complete Lead’s interface gave Veracode more flexibility to create assignment rules on the go.

Remember when we said the sky’s the limit?

Implement Nested Flows to Tackle Ultra-Complex Rule Sets

If there were a way to make it easier, you do it right?

Nested flows keep your rules organized. 

At a high level, think of it like nesting dolls: each “nested” or child assignment flow sits within a bigger, or parent assignment flow.

These parent-child relationships can span far beyond just one or two levels, giving you the freedom to allow each business unit to oversee their own GTM processes and territories.  This is a huge win for Rev Ops organizations looking to simplify and speed up ultra-complex lead management.

Department Managers can even set and keep track of rules for their own set of assignment flows, for different GTM teams and within different nested flows. That means lines are drawn in the sand but teams still have visibility and control of how a lead is tracked for their particular team.

Your business depends on data getting where it needs to go, fast. That’s why no matter how complex, your assignment rules should never feel out of hand.

Leverage Powerful Account-Based Assignment

Account-based strategies should be a cornerstone to your go-to-market strategy, and you want to know that your strategic investments are being implemented successfully.

• In a survey conducted by ITSMA , 87% of B2B marketers said that ABM initiatives outperform their other marketing investments.
• COVID-19 caused companies t o rush to create ABM strategies to respond to an increased need for a strong digital presence.
• 56% of the 800 B2B marketers that LinkedIn surveyed said that they are using ABM. Over 80% said that they plan to increase their ABM budget over the next year.

Use account-based assignment.

Account-based marketing targets specific companies, so setting up account-based rules in your lead flow process allows you to route leads from these target accounts to your most experienced reps quickly and easily.

The rule of thumb is that leads from target accounts need to go to the account rep that owns the account. The account owner has the deepest knowledge of the account and the highest chance to convert. Simply put, account based routing  has a positive impact on your bottom line.

With a more robust lead assignment solution to align with their account-based selling and marketing strategies, Alfresco was able to increase their close/won rate by 10%!

Enterprise hierarchy assignment is a no-brainer for account selling.

Imagine if you could automatically visualize all the related customer accounts including subsidiaries, and assign one strategic rep to the parent enterprise account?

You can and you should. Complete Hierarchies gives you the ability to automatically build and visualize complex account hierarchies, so that you’re able to route leads to the right rep no matter how complex the account structure.

Let’s say a new lead comes in from Hulu, but you’ve no idea that it’s a subsidiary of The Walt Disney Company. Chances are the same rep won’t be assigned the account if other go-to-market rules are in place.

Also, you’ve already given a discount to The Walt Disney Company, and this information is not available to the rep who gets the new lead. Account Hierarchies can be a trick up the sleeve when it comes to account-based assignment.

But what happens if a lead comes in and it’s not associated with any account or go-to-market territory?

Set Up A Sophisticated Round Robin

You’re leaving revenue on the table when you let leads sit and die without a timely response.

Native Salesforce just isn’t sophisticated enough to handle more complex round-robin criteria that’s required to keep your leads flowing when they hit a snag.  It’s limited and cumbersome to manage – major setbacks when it comes to your speed-to-lead.

For certain territories or situations, you may have multiple reps covering the territory or a catch-all queue for leads that don’t have enough information to assign properly.

In those cases, businesses often have someone dedicated to manually triaging and assigning leads. This is an incredibly time-consuming operational nightmare and a good way to tank your response times.

And with a lack of accountability, reps often cherry-pick the ideal leads and leave others to the crows.

To avoid these assignment pitfalls you need to push leads to a chosen pool of sales reps and evenly distributed to your sales team, giving everyone an equal opportunity to generate a sale. But you also need more flexible options.

Use sophisticated dynamic round-robin assignment to:

• Set sophisticated criteria like rep speciality or languages
• Use availability settings to ensure leads can be responded to immediately (e.g. office hours)
• Automatically notify reps when new leads are pushed through
• Enforce SLAs on response times to make sure leads are responded to as quickly as possible
• Pair with a rep response dashboard that gives you a complete view to help you monitor how fast a rep is following up with their round-robin leads

Weighted round-robin:

Give your best-performing reps more leads, and improve your overall chance at generating more pipeline. Based on:

• Performance
• On their speciality
• Any desired field

If you’ve found that reps have hit their max capacity for being able to manage any more leads, you can cap the number of records assigned to your team members in the round-robin.

Hit a snag? Re-route your leads:

If reps aren’t responding within their SLA, you can reroute the lead and assign it to someone who will respond. This helps prevent further roadblocks and keeps data flowing, even when there’s a bottleneck.

It’s typical for our team to get four to five requests a week to change territories for a user. Onboarding and offboarding now takes just a few minutes to run all our leads back through the system and automatically get reassigned. – Jim Maddison, Veracode

The ultimate speed-to-lead tactic to keep in your back pocket.

Go Beyond Leads, Assign Any Object

Just imagine that feeling you get if you could create assignment flow, beyond leads. It’s a whole new world.

Assign any object

Go beyond leads and create any assignment flow across any object. You can assign any record, update any field, and trigger any action.

It works similarly to the assignment flow you create for leads, so define your goals and determine your set of criteria for each particular object.

No more manual effort!

This presents endless opportunities to customize your assignment flows, resulting in streamlined processes and less manual administrative time spent manually sifting through information.

What Are You Waiting For?

It’s time to speed up and sell more. 

Speed is crucial, but there’s so much more than that underpinning your speed-to-lead. You need the flexibility to handle your go-to-market complexity and to keep your leads flowing to the right reps in real time.

When you’re scaling fast, you can’t afford to let good leads slip through the cracks.

Interested in hearing more?

We’re happy to talk you through how you can elevate your lead assignment rules in Salesforce, and dramatically improve your speed-to-lead game.

Book a personalized demo with one of our experienced team members today.

Don’t let data hold you back. Build a better way with Complete Leads.

Related Posts

Why we built this: Multi-SLA timers

Why we built this: Visual history log

MQL vs. SQL: Definition, Examples, and Best Practices for Salesforce

3 lead routing plays to boost pipeline for marketing operations

• Salesforce Admin

Salesforce Lead Assignment rules

• Dec 28, 2023

Salesforce Lead Assignment rules automate your org lead generation and support processes. Lead Assignment Rules are a powerful tool that enables the automatic assignment of leads to the right sales representatives based on specific criteria.

What is Salesforce Lead Assignment rules?

Lead assignment rules are used to specify how leads are assigned to users or queues. This is used to assign the owner of leads based on lead generation, like leads created from the web or imported from a data loader.

Type of Assignment Rule 

There are two types of assignment rules we have in Salesforce.

• Lead Assignment Rules
• Case Assignment Rule

How to create lead Assignment Rules

Let’s see the step-by-step guide to set up the lead assignment rules.

• Creating Lead Assignment Rule
• Creating Lead Assignment Criteria
• Specify the lead assignment method
• Activate the lead assignment rules
• Test the lead assignment rules

Consideration for Lead Assignment Rules

• We can create as many assignment rules as possible, but only one can be active.

Lead Assignment Rules can help streamline your lead management process, improve lead conversion rates, and increase sales productivity by ensuring that the right leads are assigned to the right representatives.

Related Posts

How to Sync Data from Microsoft Excel to Salesforce: Use Cases

Revenue Lifecycle Management (RLM) Training

Einstein Copilot Standard and Custom Actions

Leave a reply cancel reply.

Your email address will not be published. Required fields are marked *

Name  *

Email  *

Add Comment  *

Notify me of follow-up comments by email.

Notify me of new posts by email.

Post Comment

Automation Champion

Automating Salesforce One Click at a Time

Running Lead Assignment Rules From Salesforce Flow

Last Updated on February 14, 2022 by Rakesh Gupta

To understand how to solve the same business use case using Process Builder . Check out this article Getting Started with Process Builder – Part 49 (Running Lead Assignment Rules From Process Builder) .

Big Idea or Enduring Question:

How do you run the lead assignment rule from the Salesforce flow? Lead assignment rules allow us to automatically assign Leads to the appropriate queue or user. A Lead assignment rule consists of multiple rule entries that define the conditions and order for assigning cases. From a Salesforce User interface, a user can trigger assignment rules by simply checking the Assign using the active assignment rules checkbox under the optional section.

The problem arises when you need to insert or update the Leads from Salesforce Flow and wants to trigger assignment rules. Using the Salesforce Flow a Lead will be inserted or updated but the assignment rule will not be triggered as there is no check box to use the organization’s assignment rule or a prompt to assign using the active assignment rule.

Let’s start with a business use case.

Objectives:

After reading this blog post, the reader will be able to:

• Running the lead assignment rules from Salesforce Flow
• Understand @InvocableMethod Annotation
• How to call an Apex method using Salesforce Flow

Business Use Case

Pamela Kline is working as a System administrator at Universal Containers (UC) . She has received a requirement from the management to update the following Lead fields when Lead Source changed to Partner Referra l .

• Status = Working – Contacted
• Rating = Hot

As data changed by the process, she wants to fire the assignment rule as soon as the process updates the lead record.

Automation Champion Approach (I-do):

Guided Practice (We-do):

There are 4 steps to solve Pamela’s business requirement using Salesforce Flow and Apex. We must:

• Setup a lead assignment rule
• Create Apex class & Test class
• Define flow properties for record-triggered flow
• Add a decision element to check the lead source
• Add an assignment element to update status & rating
• Add a scheduled path
• Add a decision element to check if lead source changed
• Add action – call an Apex class to invoke lead assignment rule

Step 1: Setting Up Lead assignment Rule

• Click Setup .
• In the Quick Find box, type Lead Assignment Rules .
• Click on the Lead Assignment Rules | New button .
• Now create an assignment rule, as shown in the following screenshot:

Step 2: Create an Apex class and Test class

Now, we have to understand a new Apex annotation i.e . @InvocableMethod . This annotation lets us use an Apex method as being something that can be called from somewhere other than Apex . The AssignLeadsUsingAssignmentRules class contains a single method that is passing the ids of the Leads whose Lead Source changed to Partner Referral . Create the following class in your organization.

• In the Quick Find box, type Apex Classes .
• Click on the New button .
• Copy code from GitHub and paste it into your Apex Class.
• Click Save.

Step 3.1: Salesforce Flow – Define Flow Properties for Before-Save Flow

• In the Quick Find box, type Flows .
• Select Flows then click on the New Flow .
• How do you want to start building : Freeform
• Object : Lead
• Trigger the Flow When : A record is created or updated
• Condition Requirements: None
• Optimize the Flow For : Fast Field Updates
• Click Done .

Step 3.2: Salesforce Flow – Using Decision Element to Check the Lead Source

Now we will use the Decision element to check the lead source to ensure that it is equal to Partner Referral.

• Under Toolbox , select Element .
• Drag-and-drop Decision element onto the Flow designer.
• Enter a name in the Label field; the API Name will auto-populate.
• Under Outcome Details , enter the Label the API Name will auto-populate.
• Resource: {!$Record.LeadSource}
• Operator: Equals
• Value: Partner Referral
• When to Execute Outcome : Only if the record that triggered the flow to run is updated to meet the condition requirements

Step 3.3: Salesforce Flow – Adding an Assignment Element to Update Rating and Status

• Drag-and-drop the Assignment Element element onto the Flow designer.
• Enter a name in the Label field- the API Name will auto-populate.
• Field: {!$Record.Rating}
• Add Condition
• Field: {!$Record.Status}
• Value: Working – Contacted

• Click Save .
• Enter Flow Label the API Name will auto-populate.
• Click Show Advanced .
• API Version for Running the Flow : 53
• Interview Label : Record-Trigger: Lead Before Save {!$Flow.CurrentDateTime}

Step 4.1: Salesforce Flow – Define Flow Properties for After-Save Flow

• Field : Lead Source
• Operator: Euqals
• Optimize the Flow For : Action and Related Records

Step 4.2: Salesforce Flow – Add Scheduled Paths

• Under SCHEDULED PATHS , click on the New Scheduled Path .
• Under Scheduled Path Details , enter the Label the API Name will auto-populate.
• Time Source : Lead: Last Modified Date
• Offset Number : 1
• Offset Options : Minutes After

Step 4.3: Salesforce Flow – Adding an Action to Call Apex class to Trigger Lead Assignment Rule

• Drag-and-drop the Actions element onto the Flow designer.
• Select the AssignLeadsUsingAssignmentRules Apex class.
• Field: LeadIds
• Value: {!$Record.Id}

• Interview Label : Record-Trigger: Lead After Save {!$Flow.CurrentDateTime}

Proof of Concept

Now onward, if a business user updates the Lead Source to Partner Referral , Process Builder will automatically update Status , Type , and Assign it to the right user or queue based on the lead assignment rule.

Monitor Your Schedule Flow

To monitor Flows that are scheduled, navigate to the following path:

• Navigate to Setup (Gear Icon) | Environments | Monitoring | Time-Based Workflow .

• Use the Delete button to delete the time-based Flow job from the queue.

Formative Assessment:

I want to hear from you! What is one thing you learned from this post?  How do you envision applying this new knowledge in the real world? Let me know by Tweeting me at @automationchamp , or find me on LinkedIn.

Submit Query!

Similar Posts

Elevate Your Screen Flows with a Customizable Counter Component

Dynamic Progress Bar for Form Completion in Salesforce Flow

Launch a Flow from CRM Analytics Dashboard Text Widget

9 thoughts on “ running lead assignment rules from salesforce flow ”.

It ran repeatedly, every minute, over and over again. I was getting notification email every minute when testing. I did the same steps as you mentionned, with a record triggered flow containing the apex action.

I found that this ran repeatedly, every minute, over and over again. Was easy to spot because I modified the Apex to include sending the user notification email as well – so I was getting notification email every minute when testing.

When I updated the ‘Time Source’ in the flow scheduled path from ‘Time Source: Lead: Last Modified Date’ to ‘Time Source: When Lead is Created or Updated’ that seems to have solved the problem.

Was curious if you had the same experience or if there was some other nuance happening.

It also looks like you had originally intended to use a decision element in step 4.3 but changed that to flow entry requirements, likely because the scheduled path can’t assess the prior and current values the same way the starting node can.

Thank you for sharing your valuable feedback. I have a quick question for you: When executing the Apex class, do you utilize a Record-triggered Flow or a Scheduled-triggered Flow?

after the apex class fires, noticed the lead owner is assigned to default lead owner, instead of using lead assignment rule. Any clue?

Thank you for an excellent tutorial 🙂 you solved my problem! Very much appreciated

Anyone getting issues with an error on mass updates “Apex error occurred: System.QueryException: List has more than 1 row for assignment to SObject “? if each one is called individually, I don’t understand how there is more than 1 row for assignment. Sometimes I get an email with this error only to see that the trigger actually worked for the specified record so a bit odd. Thanks!

Thank you for the great tutorial. Why add the 1 minute wait? Is that just to take avoid too much synchronous automation? Or is it required for another reason?

You’re right Kevin (to make the process asynchronous).

• Pingback: Getting Started with Process Builder – Part 49 (Running Lead Assignment Rules From Process Builder) - Automation Champion

Leave a Reply Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed .

Discover more from Automation Champion

Subscribe now to keep reading and get access to the full archive.

Type your email…

Continue reading

Salesforce is closed for new business in your area.

Stack Exchange Network

Stack Exchange network consists of 183 Q&A communities including Stack Overflow , the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.

Q&A for work

Connect and share knowledge within a single location that is structured and easy to search.

How to stop a Lead Assignment Rule for certain Leads?

I'd like to stop Lead Assignment Rules from activating for a particular type of Lead, for example, if a Lead is from a particular Country.

What are some force.com tools I could use to accomplish this?

• assignment-rules

• You can bypass assigment rule like create a checkbox called bypass in lead.In assignment rule with your criteria add like bypass = false.If you want to by pass assignment rule through trigger update bypass=true in specific lead. Let me know @R.Rakesh –  Pavan tej Commented Aug 3, 2016 at 17:14

4 Answers 4

Could you just set a rule in your lead assignments of "Country = X" Assign to Same User? This more or less would bypass the Lead Assignment.

• Hi Dan, Thanks for quick reply , in my scenario I want to assign the owner for particular type of lead by apex trigger and if the lead is of other type then go for lead assignment rule. –  R.Rakesh Commented Aug 3, 2016 at 16:57
• Why not just have everything assign via Assignment rules? Why rebuild the wheel? Are you talking about re-assignment AFTER creation? In that case a Trigger or WFR can do the job. –  Dan Commented Aug 3, 2016 at 16:59
• Yes we can do that but in my case I have to further divide the criteria based on zip code so it will take my active rules to more than 50.This is why I have made a list of zip codes with owners that need to be assigned.This will be accomplished with the help of Apex Trigger for a particular type of lead.. –  R.Rakesh Commented Aug 3, 2016 at 17:13

I was able to successfully bypass the lead assignment Rule with the help of workflow rule . As per the order of execution workflow comes after triggers and when we update fields of lead by workflow then triggers execute again but not Assignment rule, thus we can achieve our goal.

• 1 ? Assignment rules (step 8) run before workflow rules (step 10) so some elaboration would be nice –  cropredy Commented Aug 9, 2016 at 21:18

This problem can be a bit tricky

• If the Lead comes in with DMLOptions indicating to use Lead Assignment (such as from Marketo/Eloqua/HubSpot), then the SFDC will execute the assignment rules regardless of what you do.
• Hence, if you have use the assignment rule 'email' checkbox, then the assignee will get notified.
• Should no assignment rule be true, the Lead will get assigned to the default Lead owner.

To avoid the email notification to the wrong person - you will need an assignment rule that assigns the "dont use assignment rules" Lead to a queue InterimQ . Then, using ProcessBuilder/workflow or trigger, reassign the Leads owned by InterimQ to the owner you desire.

If you want to avoid the assignment rules execution programmatically, you can use in the before insert:

Database.DMLOptions dmo = new Database.DMLOptions(); dmo.assignmentRuleHeader.useDefaultRule= false; lead.setOptions(dmo);

Here you have the DMLoptions official doc: https://developer.salesforce.com/docs/atlas.en-us.apexref.meta/apexref/apex_methods_system_database_dmloptions.htm

You must log in to answer this question.

Not the answer you're looking for browse other questions tagged assignment-rules ..

• The Overflow Blog
• The evolution of full stack engineers
• One of the best ways to get value for AI coding tools: generating tests
• Featured on Meta
• User activation: Learnings and opportunities
• Site maintenance - Mon, Sept 16 2024, 21:00 UTC to Tue, Sept 17 2024, 2:00...

Hot Network Questions

• How will the Polaris Dawn cabin pressure and oxygen partial pressure dovetail with that of their EVA suits? (100% oxygen?)
• What film is it where the antagonist uses an expandable triple knife?
• Would it be illegal for Companies House to require a response to a letter on registration?
• Should I change advisors because mine doesn't object to publishing at MDPI?
• How to make conditions work in Which?
• LaTeX labels propositions as Theorems in text instead of Propositions
• Spacing between mathrel and mathord same as between mathrel and mathopen
• What would the natural diet of Bigfoot be?
• Can a V22 Osprey operate with only one propeller?
• Two sisters live alone in a house after the rest of their family died
• Is there mathematical significance to the LaGuardia floor tiles?
• Paying a parking fine when I don't trust the recipient
• What came of the Trump campaign's complaint to the FEC that Harris 'stole' (or at least illegally received) Biden's funding?
• How can I analyze the anatomy of a humanoid species to create sounds for their language?
• BASH - Find file with regex - Non-recursively delete number-only filenames in directory
• What is the rationale behind 32333 "Technic Pin Connector Block 1 x 5 x 3"?
• Inequality involving finite number of nonnegative real numbers
• Please help me identify my Dad's bike collection (80's-2000's)
• "Truth Function" v.s. "Truth-Functional"
• How to prove that the Greek cross tiles the plane?
• What is the shortest viable hmac for non-critical applications?
• Taylor Swift - Use of "them" in her text "she fights for the rights and causes I believe need a warrior to champion them"
• Why the \VerbatimInput of the .aux file is empty?
• How is switching of measurement ranges in instruments, like oscilloscopes, realized nowadays?