how to use salesforce lead assignment rules

Salesforce is closed for new business in your area.

Product Area

Feature impact.

• Pre-Import Checklist
• Match Your Information to Salesforce Fields in Data Import
• Fix Data Import Errors
• Migrate Accounts, Contacts, and Leads
• Migrate Opportunities, Tasks, and Events
• Keep Track of All the Details
• Know Exactly Who You're Talking To
• Close More Deals
• Track Your Open Deals
• Set Up Basic Case Management
• 5 Easy Ways to Keep Your Customers Happy
• How to Talk to Your Customers Like Real People
• Get the Details You Need
• Keep Tabs on Every Detail
• Track Your Progress with Dashboards
• Manage Your Essentials Subscription
• Get Started with the Setup Assistant
• Filter Your Lists to Find What You Need
• Keep Your Productivity Tools Handy
• Customize Salesforce Essentials
• How to Troubleshoot When Your Sales Are Down
• Take Your Sales to the Next Level
• Maintain a Healthy Sales Team
• 5 Sales Secrets from Top Sales Execs at Salesforce
• Sync Emails and Activities
• Offer Customer Support in Essentials
• Write Useful Help Articles for Your Customers and Your Team
• Prepare for Your Help Center
• Build an Effective Self-Service Help Center
• Respond to Social Media Interactions
• Phone Options in Salesforce Essentials
• Create a Company Phone for Your Team
• Optimize Tasks as an Individual Contributor
• Build an "All Open Tasks" Report
• Build an "All Overdue Tasks" Report
• Divvy Up Work On Your Team with Routing
• Offer Live Customer Support
• Automate Your Tasks with Macros
• Learn Best Practices for B2C Businesses
• Add Your Apps to Salesforce Essentials
• Create a Process to Re-engage Inactive Leads
• Manage Your Contacts with These Best Practices

Create a Round Robin Lead Assignment Rule

• Reach Out to Customers After Winning an Opportunity
• Remind Your Sales Team When a Renewal Comes Due
• Complete Pre-Work for the Email Opt-Out Flow
• Create an Email Opt Out Flow
• Create a Process to Trigger the Email Opt Out Flow
• Best Practices for Marketing Teams

Keep your team's workload even by auto-assigning new leads to each user.

Round robin assignment means that each new lead is assigned to a different user until everyone has been assigned the same amount and the cycle repeats.

For example, if you have three users:

• Lead 1 is assigned to user 1
• Lead 2 is assigned to user 2
• Lead 3 is assigned to user 3, then the cycle repeats
• Lead 4 is assigned to user 1
• Lead 5 is assigned to user 2
• Lead 6 is assigned to user 3, then the cycle repeats.

You can set up round robin lead assignment with a few custom fields and a lead assignment rule.

Create a Lead Number f+Field

Creating a Lead Number f+Field gives each new lead a unique ID.

• Open Setup.
• Search for Object Manager , and open it.
• Click Lead .
• Click Fields & Relationships .
• Click New .
• Select Autonumber , and click Next .
• Name your field Lead Number .
• In Display Format, enter {0} .
• In Starting Format, enter 1 .
• Check the box to Set this field as the unique record identifier from an external system , and click Next .

• Uncheck all Page Layout boxes, and click Save & New .

Create a Round Robin Field

The round robin field tells the system to assign each new lead to the next user in order.

• Select Formula , and click Next .
• Name your field. For example: Round Robin .
• Select Number .
• In the Decimal Places dropdown, choose 0 , and click Next .
• Select Advanced Formula .

• Click Next .
• Give user permission to the right people, and click Next .
• Uncheck all Page Layout boxes, and click Save .

Create a Lead Assignment Rule

The lead assignment rule ensures that leads are assigned evenly across users.

• In Setup, search for Lead Assignment Rules , and open it.
• Name your rule Round Robin Assignment Rule , and click Save .
• Click to open Round Robin Assignment Rule.
• In the Rule Entries section, click New .
• In Sort Order, enter 1 .
• Set the rule criteria by choosing Round Robin in the Field dropdown, Equals in the Operator dropdown, and 1 in the Value field.
• Select the user this rule applies to.
• Optionally, select an email template to tell the user that the rule has been assigned to them.

Allow Round Robin Lead Assignment on Manually-Created Leads

• In Setup, click Object Manager .
• Click Page Layouts .
• Open Lead Layout .
• Click Layout Properties .
• Next to Lead Assignment Checkbox, check the box to Show on edit page , and click Okay .
• Save your changes.

Cookie Consent Manager

General information, required cookies, functional cookies, advertising cookies.

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings. Privacy Statement

Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.

Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.

Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.

Cookie List

Getting Started with Lead Assignment Rules in Salesforce

Lead Assignment Rules in Salesforce are a powerful tool that allow your GTM (Go-To-Market) teams to automate the process of generating leads and assigning them to the most suitable sales representatives based on specific criteria. Managing and assigning leads becomes key, particularly when dealing with high daily volumes and considering the priority of leads based on various factors. And, as we all know, speed to lead is crucial : if you waste even one minute, your conversion plummets by a shocking 391%.

Ideally, your organization should employ different lead assignment rules tailored to your go-to-market strategies and motions. For instance, the assignment rules for leads generated from a demo request on your website may differ from those for leads obtained through downloading an ebook.

A lead assignment rule consists of a prioritized set of rule entries that dictate how leads are assigned throughout your go-to-market motions, either to a specific user or to a Salesforce Queue. These rules are automatically triggered when leads are created and can also be applied to existing records.

However, there is one significant constraint with Salesforce assignment rules: only one can be active at any given time. This means that as your business scales and you implement multiple business processes, you'll need to consolidate all the complex logic into a single comprehensive assignment rule with multiple rule entries. As you can imagine, managing, maintaining, and updating such an operation can become increasingly challenging over time.

Salesforce Lead Assignment Rules Examples

• Leads from Enterprise Accounts with ARR greater than $200M are assigned to Enterprise SDR Queue.
• Leads from accounts with ARR greater than $50M (and less than $200M) are assigned to Mid Market SDR Queue.
• Leads reaching Nurture Lead Status are directed to SDR 1.
• Irrelevant leads with a ‘gmail.com’ domain are routed to a dummy user and disregarded.
• Distribute leads to reps based on their respective sales territories.

Salesforce Lead Assignment Rules: A step-by-step guide

Here is a step-by-step guide to help you set up Salesforce Lead Assignment Rules in keeping with your business needs and sales strategies.

Step 1: Log in to Salesforce:

Access your Salesforce account using your credentials.

Step 2: Navigate to Setup:

Click on the gear icon in the screen's upper-right corner to access the Setup menu.

Step 3: Access Lead Assignment Rules:

In the Setup menu, search for "Lead Assignment Rules" in the Quick Find box. Click on "Lead Assignment Rules" under the "Leads" section.

Step 4: Create a New Rule:

Click on the "New Lead Assignment Rule" button to create a new rule.

Step 5: Define Rule Entry Criteria:

Enter a suitable name for the rule and specify the rule's entry criteria.

You can decide whether to write a formula or build a prioritized set of rule entry criteria. The logic you define determines the conditions that need to be met for the rule to trigger.

Step 6: Specify Rule Assignments:

Choose the desired assignment method for your leads. Salesforce provides different assignment options, such as assigning leads to Queues or specific users. Select the appropriate option based on your business requirements, and (optionally) choose an email template to be sent to the new owner of the lead.

Step 7: Save and Activate the Rule:

Once you have configured all the necessary settings, click the "Save" button to save the lead assignment rule. After saving, activate the rule to make it operational.

Step 8: Test and Validate:

It is essential to test the rule and ensure that leads are being assigned as expected. Create test leads and verify their assignments based on the defined criteria. Make any necessary adjustments or refinements to the rule if required.

Salesforce editions and permissions for Lead Assignment Rules

After gaining an understanding of how lead assignment rules can benefit your business and determining their suitability, you may wonder, "Do I have the appropriate Salesforce edition?" The short answer is, “Yes.” Salesforce has now made this feature available in every edition.

In terms of user permissions, certain requirements must be met to view and edit lead assignment rules in Salesforce. Users must have the "Manage Leads" permission and the ability to "View Setup and Configuration" in order to access lead assignment rules. For editing purposes, users need the "Customize Application" permission along with either the "Modify All Data" or "Modify Leads" permission. If you are unable to locate this section in Salesforce or encounter difficulties with viewing or editing assignment rules, reach out to your Salesforce administrator to verify that you have the necessary permissions in place.

Assignment rules limits and challenges

Salesforce Lead Assignment Rules, while suitable for small teams with straightforward rules, come with significant limitations that can hinder efficiency for larger teams. These limitations become more apparent as the volume of leads increases and more complex use cases arise.

One major drawback is the stringent limits imposed by Salesforce on the number of rules, entries, and actions allowed per rule. These limits are illustrated in the following table:

However, there are additional factors to consider when utilizing assignment rules in Salesforce. It is crucial to be aware of the following challenges before embarking on building your entire logic using Salesforce's native functionality:

• Limited to Leads and Cases: Assignment rules only apply to the lead and case objects. While this may suffice for simple and initial use cases, it falls short when implementing ABM (Account Based Marketing) strategy or when the need to route Opportunities arises.
• Complex QA and Audit: Salesforce's native functionality lacks versioning or debugging tools, making testing and troubleshooting assignments a laborious task. Additionally, there is no built-in record of why a lead was assigned in a particular way, further complicating the auditing process.
• Limited Assignment Options: When using assignment rules, you can only assign a Lead record to a specific user or a Salesforce Queue. Managing more intricate assignments, such as round-robin distribution, becomes challenging and costly to implement within the confines of assignment rules.
• Single Active Rule: As mentioned previously, Salesforce restricts the use of only one active lead assignment rule at a time. This means that despite having multiple processes with distinct underlying logic, you are forced to consolidate them into a single, busy rule, making management and updates cumbersome.

Considering these challenges, it becomes evident that relying solely on assignment rules may not provide the flexibility and functionality required for more complex lead management scenarios.

How Sweep Simplifies Salesforce Lead Assignment

Although assignment rules in Salesforce offer a powerful solution with a short learning curve, we recognize that the drawbacks can become a significant pain point as businesses grow and the native Salesforce tools may not fully support your team's needs.

To address these challenges, we have developed Sweep's Assignment tool, a visual no-code solution designed to simplify the implementation of assignment logic within Salesforce. This empowers organizations to build their go-to-market motions while maximizing assignment efficiency. The benefits of using Sweep's Assignment capabilities include:

• Assigning any object: From Opportunities to Accounts & Contacts and custom objects, you can apply assignment logic across various Salesforce objects.
• Achieving full visibility: Gain a comprehensive understanding of your business processes and easily track where assignments are taking place.
• Managing round-robin groups: Distribute leads equally among sales representatives using round-robin assignment to ensure fairness, or add weights to better control assignments between reps.
• Simplifying territory management and assignment: Streamline the process of managing territories and assigning leads based on specific territories.
• End-to-end lead routing capabilities: Enhance the lead routing process with advanced features such as Lead Deduplication and Lead-to-Account Matching, ensuring that leads always receive a seamless buying experience.

If you have any questions or would like to learn more about how Sweep Assignment can assist your business as it scales, please don't hesitate to contact me at [email protected]. I would be delighted to show you around or provide further insights into Salesforce Lead Assignment Rules.

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.

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

Automatically Refresh Your Salesforce Dashboard Every Hour or Minute

Easiest Way to Find if a Record Is in the Approval Process Using Salesforce Flow

Beyond Text: Exploring Image Use Cases in Salesforce Flows

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

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