task assignment rule salesforce

About 15 mins

Create Case Queues

Create a case assignment rule, test the case assignment rule.

• Challenge +100 points

Create Case Queues and Assignment Rules

Now that you have your basic support processes and layouts configured for cases, create case queues and assignment rules to route your cases to the correct support teams at Ursa Major Solar.

Create Product Support Tier 1 and Product Support Tier 2 queues so product support cases can be routed to one of these queues based on case criteria and how long the case has been open.

• From Service Setup, enter Queues in the Quick Find box and select Queues .
• Click New  and complete the queue details.
• Label: Product Support Tier 1
• Queue email: [email protected]
• Supported Objects: select Case and click Add .
• Queue Members: Click  User: (Your Name) in the Available Members list, and click Add to add yourself to the Selected Members list.
• Click Save .
• From the Queue   page, click New  and complete the queue details.
• Label:   Product Support Tier 2
• Queue email: [email protected]

Now, create the Inquiry queue for inquiry cases.

• From the Queues page, click New .
• Enter the queue details.
• Label: Inquiry
• Queue Email: [email protected]
• Queue Members: Click User: Ada Balewa in the Available Members list, and click Add to add her to the Selected Members list.

So, now you have case queues set up and ready to handle different types of cases as they’re created. Next, create and activate a standard case assignment rule to assign cases to the correct team members. This is how cases get sent to specific case queues, like the ones you just created.

• From Service Setup, enter Case Assignment Rules in the Quick Find box and select Case Assignment Rules .
• Click New  and enter the rule details.
• Rule Name: Standard Case Assignment
• Select the Active checkbox to make this the active case assignment rule.

Add a rule entry that assigns Product Support cases to the Product Support Tier 1 queue.

• Click the Standard Case Assignment link.

• Click Save & New .

Next, add a rule entry that assigns inquiry cases to the Inquiry queue.

Now rename the Automated Case User to System. Every time there’s an automated case change from an assignment rule, for example, the automated case user name will show up in the case history. It will now show an automated “system” change, rather than showing your name as the admin, whenever an automated case change occurs.

• Enter Support Settings in the Quick Find box and select Support Settings .
• Click Edit .

You want to make sure the assignment rules work for Ursa Major Solar by creating a case.

• Click the Contacts tab.
• Select Recently Viewed from the dropdown, and click the Pat Stumuller link.
• In the Cases   related list, click New .
• Select a record type: Product Support .

• Click the Case Number for the case you just created. Ensure that the Case Owner is Product Support Tier 1.

By setting up case queues and assignment rules, cases are now automatically routed to the correct teams. Next, escalate higher priority cases to the Product Support Tier 2 team by creating an Escalation Rule.

• Salesforce Help : Rules
• Salesforce Help : Create Queues
• Salesforce Help : Set Up Assignment Rules
• Get personalized recommendations for your career goals
• Practice your skills with hands-on challenges and quizzes
• Track and share your progress with employers
• Connect to mentorship and career opportunities

How to Create Case Assignment Rules in Salesforce

Our organization uses Salesforce as its CRM tool, and the support team assigns cases manually. As a Salesforce Administrator, I was assigned the task of automating the case assignment for new cases. In Salesforce, we can automate this process using a case assignment rule.

In this tutorial, I will explain the case assignment rules in Salesforce and their limitations, and we will also discuss how to create a case assignment rule in Salesforce.

Table of Contents

Case Assignment Rule in Salesforce

In Salesforce, the case assignment rules help automate your organization’s support processes. The rules can also determine how cases are assigned to users or queues based on criteria that we define.

The case assignment rule can assign the cases when a new case is created. Then, that case can be created manually or automatically from web-to-case , email-to-case , etc.

How to Create a Case Assignment Rule in Salesforce

For example, there is a support team with several users, and we want to automatically assign a specific user to a new case when it is created and the Case Priority is High.

We can create a case assignment rule in Salesforce using the following steps.

1. Go to Setup . In the Quick Find Box , search for Assignment Rules . Then click on the Case Assignment Rule .

2. Then click on the New button to create a new rule.

3. Enter a  Rule Name . Then, activate the rule by clicking the  Activate  button. 

We can create only one active case assignment rule at a time. So, if you have any activated case assignment rule, it will get deactivated as you activate the new rule.

Then, click on the Save button.

4. Open the rule by clicking the Rule Name .

5. Then click on the New button to add rule entry criteria.

6. As you click the new button, you need to enter the following details:

• Sort Order: Here, you need to provide the number this entry should trigger.
• Criteria: As per our scenario, we need to enter Case Priority = High .
• Select User or Queue : Here, we need to assign high priority cases to specific user.
• Email Template : We can select an email template so that when a case is assigned to a user, they will receive an email regarding the same.

Then click on the Save button.

Proof of Concept:

7. Now, to check how the case assignment rule works, navigate to the case tab. Then, create a new case record with case priority as high and save the record.

8. As you save the record, you will see that the case owner has automatically changed to another user. That means a new user has been assigned to this case.

This is how we can create case assignment rules in Salesforce.

Limitations in Case Assignment Rule in Salesforce

The following are some limitations of the case assignment rule in Salesforce:

• The case assignment rule is only used when we want to assign records automatically to a user or queue. It cannot be used to update fields .
• If we change the criteria for an existing rule, the rule will not reassign cases until we manually update the case owner.
• In the rule entry criteria, we can only use case fields. It does not allow the use of the related fields of the case object.
• We can create only one active case assignment rule at a time.

You can also read the Case Assignment Rule in Salesforce .

I hope you got an idea about case assignment rules in Salesforce. In this article, we have seen what a case assignment rule is and its limitations. We have also seen how to create case assignment rule in Salesforce with an example and step-by-step explanation.

You may also like to read:

• Auto Response Rules in Salesforce
• Web-to-Case in Salesforce
• Email To Case Salesforce
• How to Create a Case Related to an Account using Flow in Salesforce

I am Bijay Kumar, the founder of SalesforceFAQs.com. Having over 10 years of experience working in salesforce technologies for clients across the world (Canada, Australia, United States, United Kingdom, New Zealand, etc.). I am a certified salesforce administrator and expert with experience in developing salesforce applications and projects. My goal is to make it easy for people to learn and use salesforce technologies by providing simple and easy-to-understand solutions. Check out the complete profile on About us .

• AppAssessor

Articles by role:

• Consultants
• Business Analysts

By Lucy Mazalon

By Ben McCarthy

• Dreamforce Events
• Courses Login

What’s trending

Agentforce: The Next Evolution in Salesforce’s AI Story

Salesforce Winter ’25 Release Date + Preview Information

Salesforce Winter ‘25 Release: What to Expect and How to Prepare

Salesforce List Views: 7 Best Practices You Should Implement Right Away

10 Hottest Salesforce Winter ’25 Features For Admins

UPCOMING EVENTS

How to build a successful salesforce devops process, streamline lead assignment in salesforce, salesforce revops trends & insights (ask me anything), charity hackathon – third edition.

Wrocław, Poland

Unlocking Einstein Copilot: What You Need to Know

Email-to-case best practices: case assignment rules, queues & auto-replies.

By Stacy O’Leary

When you set up Email-to-case, you can take those emails and turn them automatically to Case records in Salesforce, send auto-replies, distribute them to your support team, and take other automated actions. These will save support teams a lot of energy creating Case records and managing them appropriately. Instead, you have the chance to free up the team’s time to focus on the Cases that really require intervention.

1. Who Can Use Email-to-case?

2. Set up Queues with a Catch-all Queue

3. Send Auto-replies with the Process Builder

• Subject does not contain Out of Office, OOO, out-of-office, vacation, PTO, paid time off, holiday
• Web Email does not contain @mycompanydomain

4. Add the Case Feed ID to the Case Email Templates

5. Sort Cases Based on Case, Contact, or Account Fields

Bonus Tip: Familiarize Yourself with the Support Settings

Stacy o'leary.

More like this:

4 ways to make the most of document automation in salesforce.

By Chris Mascaro

Ultimate Guide to Case Swarming in Salesforce Service Cloud

By Mariel Domingo

Leave a Reply Cancel reply

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

• Support Portals
• PRM Portals
• Member Portals
• Online Communities
• User Experience
• Accelerators
• AC Knowledge Management Enterprise 
• AC Events Enterprise
• AC Ideas Ultimate
• AC Partner Marketplace
• AC Partner Co-Branding
• AC Job Board
• AC B2B Commerce Recurring Orders
• AC MemberSmart
• AC Fundraising
• AC B2B Commerce OrderPad
• Higher Education
• Member Organizations
• Manufacturing
• IT\High-Tech
• Video library
• Success stories
• Product learning hub
• SI Partners

Book a demo

If you'd like to book a demo with us and see how our products work, please complete the form and we'll arrange a demo with you as soon as we can.

I agree to the Privacy Policy and Terms and Conditions

By submitting this form, you agree to occasionally receive guides, tips, and tricks from AC. You can unsubscribe at any time.

How to Create Salesforce Assignment Rules: a Step-by-Step Guide

Salesforce is a strong and even irreplaceable tool when it comes to modern customer relationship management, customer service, and sales. Since it has an array of functionalities, one might feel overwhelmed by them. No worries!

Today we’d like to highlight one of the most important features for your marketing and service activities: Salesforce Case Assignment Rules and Salesforce Lead Assignment Rules. What is the difference between them? Keep reading.

Assignment Rules in Salesforce Explained

First things first, assignment rules are a great instrument to better organize your sales and support teams’ work. It’s also a perfect tool for improving your lead generation. As you already know, there are two types of assignment rules in Salesforce: Lead Assignment Rules and Case Assignment Rules. By using them, you can automate the process of assigning appropriate users or queues to Leads and Cases. 

To better understand the Salesforce terminology, we’ll give you a short definition of what is a Lead and what is a Case in Salesforce:

• Lead  – this is a prospect, meaning that this is someone who is interested in your product or service, but not yet ready to buy.
• Case  – this is literally a customer’s question, complaint, or suggestion about your product or service.

How to locate Salesforce Lead Assignment Rules and Case Assignment Rules? Easy. First, go to the Setup tab in your organization. Start typing Assignment rules in the Quick Find box and there you are: you can view assignment rules under Marketing (Salesforce Lead Assignment Rules) and Service (Case Assignment Rules) tabs.

With assignment rules, you can automatically deliver specific Cases to the right people in the team or departments who are specialized in a certain area (aka subject-matter experts), so that the customers receive timely and qualified responses. A Case Assignment Rule can assign cases without the connection to the case creation source. The thing is that a case can be submitted through a customer portal, a self-service portal, or by email, to name just a few options.

Plus, assignment rules in Salesforce also enable you to sort cases by priority according to the customer’s support package (Platinum, Silver, etc.).

The same thing applies to Lead Assignment Rules in Salesforce. By leveraging lead assignment criteria, you can specify how leads will be assigned to users or queues. They can do that regardless of whether leads are created manually or imported with the Data Import Wizard.

Salesforce Classic vs Lightning Experience: Establishing the Key Differences

Assignment Rules Limitation

You can’t build as many assignment rules as you see fit. There are certain limitations in Salesforce. For instance, there are limits for the number of rules, entries, and actions allowed by the rule.

Thus, there can be up to 2,000 total rules across objects (applies to any combination of workflow, assignment, auto-response, and escalation rules, active or inactive), 50 actives rules per object (applies to any combination of active workflow, assignment, auto-response, and escalation rules, as well as record change processes), 3,000 entries per rule, and 300 formula criteria entries per rule.

Besides, there is a limitation on actions when creating assignment rules in Salesforce – up to 200 actions allowed per rule. As for filter criteria, you can specify up to 25 per rule entry.

Creating Assignment Rules in Salesforce

Now that you know what assignment rules are for, we’ll show you how to set them up. After reading this paragraph, you’ll understand how to create a Case Queue, Case Assignment Rules, and Lead Assignment Rules in Salesforce. Spoiler alert: this is no sweat!

1. Case Queue in Salesforce Creation

What is a queue? It allows groups of users to manage a shared workload more effectively. A queue is basically a location where records can be transferred for processing by a group member.

Now, let’s get the ball rolling.

• Navigate Setup in your Salesforce organization. Type “Queue” in the Quick Find box and then enter its Name and Label. 

• Leave the Queue Email field empty if you want the support employees included in the queue to receive emails when new cases are created or type the email addresses of the people who will receive this kind of notification.
• Choose Case and add it to the Selected Objects column.

• Choose members and add them to the Selected Members column. After everything is done, click Save.

2. Case Assignment Rule Creation

• To create one Case Assignment Rule, acess Setup in your Salesforce organization. Type Assignment Rules in the Quick Find box and choose Case Assignment Rules. After that, click the New button and enter the Rule Name. Once you’re done, hit Save. Make sure you tick the Activate field to make your new assignment rule legitimate. Remember that this action will deactivate any other current Case Assignment Rule.

• Click on the rule you just created. In the Rule Entries section, click the New button.

• This is when all the magic starts. The Sort Order section defines the order in which entries will be processed. If you enter “1”, it means that this entry will be processed first.
• Select the criteria for this rule entry. Here, you have several options: to run this rule if the criteria are met or if formula evaluates to true. In our case, I selected the criteria. This pretty much a standard Case Assignment Rule with such criteria as Case Number, Case Origin, and Case Reason.

• After that, you can choose the User or a queue this rule entry will be assigned to. I will select a User.
• Choose the Email Template this user will receive when the new case will be assigned to him. After that, hit the Save button.

• Do not omit the testing phase – you need to clearly understand if everything is working correctly or you need to change assignment rules.

3. Lead Assignment Rule Creation

• With Salesforce Lead Assignment Rules, the process is pretty much the same. Navigate to Setup in your Salesforce organization. As previously done, start typing Assignment Rules in the Quick Find box and select Lead Assignment Rules. Click the New button.
• Specify the lead assignment rule name and do not forget to check the Activate box.
• In the Rule Entries section, choose New. Here, you specify the order in which the rule entry will appear and define the criteria for the given rule entry. For this lead assignment, I will specify such criteria as Lead:City equals New York, Lead:Email contains examplecompany, and Lead: Lead Status equals Open – Not Contacted.

• Next, we need to select a User or a queue for this lead assignment. Let it be Olesia Melnichenko.
• After that, we also choose an email template and click Save.

Tips and Tricks for Creating Assignment Rules in Salesforce

• Test your assignment rule in a sandbox before running it on your production org. This way, you can prevent yourself from glitches and inaccurate data.
• Leverage custom formula fields to simplify complex assignment rules. This might be the case if you need to enlist the states by regions.
• Set up round robin assignment rules for avoiding bottlenecks in your work routine. It means that the system will allocate each new case or lead to a different user or a queue until everyone has been assigned the same amount and the process repeats.
• Consider a final rule entry with no criteria. This way, you can gather everything that didn’t match the criteria you define and assign it to a user or a queue.

Bottom Line

Hopefully, we managed to unscramble the assignment rules in Salesforce for you. They are the best for streamlining your business operations. Just imagine how sleek and error-free your work can be! Newly created leads and cases are assigned to an appropriate team member or queue, no chaos.

That is why you shouldn’t miss the benefits you can get from using assignment rules. Give them a try on your organization! In case you have any troubles, ask the Advanced Communities team . We can help you with everything from the Salesforce integration and configuration or further technical maintenance.

Subscribe to Our Newsletter

Receive regular updates on our latest blog posts, news, and exclusive content!

Rate the article

3.2 / 5. 13

Discover more articles!

Salesforce Customer Account Portal

While the retirement of Koa and Kokua templates continues, Salesforce is providing a new way to keep your customers happy – it’s a Customer Account Portal.

How Can Salesforce Experience Cloud Help You to Grow Your Business?

For all businesses, there is often a moment in their development process when they reach a certain point and get stuck. This very moment can be crucial for business growth. If you are decisive enough to turn this stagnation into something bigger and more powerful. It’s time for fresh ideas as well as new approaches, or directions.

How to Set Up Multi-Factor Authentication in Salesforce: (2023 Update)

Learn more about MFA solutions in Salesforce in order to protect your customers' data and avoid account takeovers.

AC Knowledge Management Enterprise Product Sheet

• Key features – See how AC Knowledge Management Enterprise empowers your support team.
• Benefits – Understand the value it brings to your customers.
• Real results – See the impact AC Knowledge Management Enterprise can have on your organization.

Complete the form to get your free copy.

By submitting this form, you agree to occasionally receive guides, tips, and tricks from AC. You can unsubscribe at any time.    

AC Ideas Ultimate Product Sheet

• Capture – Easily collect ideas from customers, team members, and stakeholders.
• Evaluate – Use built-in tools to score, prioritize, and review ideas based on custom criteria.
• Implement – Track progress, convert cases into ideas, and turn the best ideas into actionable projects.

AC MemberSmart Product Sheet

• Key features – See how AC MemberSmart empowers your team.
• Benefits – Understand the value it brings to your members.
• Real results – See the impact AC MemberSmart can have on your organization.

AC Events Enterprise Product Sheet

• Key features – Learn how AC Events Enterprise automates registration, marketing, and analytics.
• Benefits – Learn how it improves attendee satisfaction and helps your event shine.
• Proven results – See how the app transforms your event outcomes.

UNLOCKING MEMBERSHIP SUCCESS WITH SALESFORCE Strategies from the experts

Thursday , sep 12, 2024 at 04:00 pm gmt location: zoom.

ChatableApps

Mastering Case Assignment Rules in Salesforce – A Step-by-Step Guide for Effective Case Management

Introduction.

Effective case management is crucial for organizations that use Salesforce as their customer service platform. Salesforce offers a powerful feature called case assignment rules, which automate the process of assigning cases to the right teams or individuals. In this blog post, we’ll explore the ins and outs of case assignment rules in Salesforce and learn how they can streamline your case management workflow.

Understanding Case Assignment Rules

Case assignment rules in Salesforce are a set of criteria that determine how cases are assigned to users or queues. These rules ensure that cases are routed to the appropriate team or individual based on specific characteristics or attributes of the case. For example, you can define rules to assign high-priority cases to a specialized support team or route cases from a specific region to a regional support manager.

When a new case is created or edited, Salesforce evaluates the case assignment rules to determine the most suitable owner for the case. The rules are processed in a specified order, and the first one that matches the case criteria is applied to assign the case. It’s important to understand how these rules work and how to configure them to meet your organization’s unique requirements.

Configuring Case Assignment Rules

To access the Case Assignment Rules setup in Salesforce, go to Setup and search for “Case Assignment Rules” in the Quick Find box. This will take you to the Case Assignment Rules page, where you can create and manage your rules.

When creating or editing a case assignment rule, there are three key components to consider: rule entry criteria, assignment actions, and rule order.

The rule entry criteria define the conditions that a case must meet in order for the rule to be applied. You can specify criteria based on various attributes such as case origin, case type, case priority, or any custom fields you have added to your cases.

The assignment actions determine how the case will be assigned when the rule is applied. You can choose to assign the case to a specific user or queue, or even assign it to the case’s parent account or contact. Additionally, you can configure email notifications or escalation actions for certain cases.

It’s worth noting that you can have multiple assignment rules to handle different case scenarios. Salesforce allows you to specify the order in which these rules are evaluated. This allows for greater flexibility and ensures that cases are assigned correctly even in complex scenarios where multiple rules may apply to the same case.

In complex case assignment scenarios, you may need to use formula-based rule criteria. Formulas allow you to define more advanced conditions based on multiple attributes or calculations. This can be particularly useful when you have intricate routing requirements or need to assign cases based on a combination of factors.

Additionally, you can incorporate custom fields and objects in your case assignment rules. This means you can leverage any customizations or extensions you have made to Salesforce to tailor the assignment process to your organization’s specific needs. For example, if you have custom fields that capture region information, you can create rules to assign cases based on the region field.

Testing and Validating Case Assignment Rules

Before deploying your case assignment rules in a live environment, it’s crucial to thoroughly test and validate them. Salesforce provides several tools and best practices to help you in this process.

One effective method is to use sample test cases that cover various scenarios. Create cases that match the criteria defined in your rules and ensure that they are assigned correctly. This allows you to validate the accuracy of your rules and make any necessary adjustments.

After executing your test cases, analyze the assignment results and fine-tune your rules as needed. Keep an eye out for any unexpected or incorrect assignments and investigate the underlying rules and criteria that may have caused them. By continually monitoring and refining your rules, you can ensure the highest level of accuracy and efficiency in case assignment.

In addition to initial testing, ongoing monitoring of case assignments is vital to identify any issues that may arise. Salesforce provides reports and dashboards to help you track case assignment metrics and gain insights into potential performance bottlenecks or areas for improvement.

Optimizing Case Assignment for Efficiency

To further optimize your case assignment process, consider implementing the following best practices:

Assigning cases to queues instead of individual users: Queues allow for better load balancing and easier management of cases. Instead of assigning cases directly to individual users, create queues for different teams or roles and assign cases to these queues. This ensures that cases are distributed evenly and can be easily re-assigned if needed.

Leveraging assignment rules with round-robin or load balancing logic: If you have multiple users or teams within a queue, you can configure your assignment rules to distribute cases in a round-robin or load-balanced manner. This ensures that each user or team gets an equal share of cases and prevents any one individual from being overwhelmed with assignments.

Incorporating automated case escalation and reassignment: For certain types of cases or situations, it may be necessary to automatically escalate or reassign cases if they are not resolved within a specified timeframe. Salesforce provides workflow rules and escalation rules that can be used in conjunction with case assignment rules to automate these processes. This helps ensure that cases are promptly addressed and prevents any potential bottlenecks or delays.

Troubleshooting Common Case Assignment Issues

While case assignment rules are designed to streamline your case management workflow, there may be instances where issues arise. Here are some common problems that you may encounter and how to address them:

Identifying and resolving common assignment rule errors: Sometimes, case assignment rules may not function as expected due to incorrect configuration or conflicting criteria. It’s important to review your rule definitions and criteria to identify any potential errors and make the necessary corrections. Additionally, Salesforce provides detailed error messages and logs to help diagnose any issues that arise.

Handling conflicts and overlapping assignment criteria: In complex case assignment scenarios, it’s possible for multiple rules or criteria to match a single case. Salesforce has a built-in rule order feature that allows you to specify the evaluation order of your rules. By carefully organizing and prioritizing your rules, you can avoid conflicts and ensure that cases are assigned according to your desired logic.

Addressing performance concerns and bottlenecks: As your organization’s case volume grows, it’s essential to monitor the performance of your case assignment process. If you notice any bottlenecks or delays in case assignment, evaluate the efficiency of your rules and consider optimizing them. This may involve refining your rule criteria, reordering rules, or implementing performance enhancements such as custom indexing or caching.

Mastering case assignment rules in Salesforce is key to efficient and effective case management. By understanding the fundamentals of case assignment rules, configuring them correctly, testing and validating them thoroughly, and continuously optimizing their performance, you can streamline your case management workflow and provide exceptional customer service. Remember to regularly monitor and fine-tune your rules to ensure they align with your organization’s evolving needs. With the right approach and utilization of case assignment rules, you can enhance your customer support processes and deliver timely resolutions to your customers’ cases.

Related articles:

• Mastering Salesforce Assignment Rules – Simplifying Lead and Case Distribution
• Demystifying Assignment Rules in Salesforce – A Comprehensive Guide for Sales Success
• How to Set Up and Optimize Salesforce Assignment Rules for Enhanced Sales Team Efficiency
• The Ultimate Guide to Lead Assignment in Salesforce – Mastering Round Robin Distribution

Leave a Reply Cancel reply

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

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

Using apex:repeat in Visualforce Page

System.NullPointerException: Attempt to de-reference a null object

Assignment rules in Salesforce

• By Ankush Dureja in salesforce

December 6, 2018

Page Contents

What are assignment rules in salesforce ?

Assignment rules in salesforce are used to automatically assign lead or Case to owner( User Or Queue ). Assignment rule is used to automate owner assignment on Case and Lead based on conditions on Case or Lead. For example, there could on lead assignment rule for web-generated leads and one case assignment rule for the holiday use.

Types of assignment rules

There are two type of assignment rules

Lead Assignment Rules

Case assignment rules.

Specify how leads are assigned to users or queues as they are created manually, captured from the web, or imported via the Data Import Wizard.

Determine how cases are assigned to users or put into queues as they are created manually, using Web-to-Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service portal, the Customer Portal, Outlook, or Lotus Notes.

Create or Setup assignment rules

• From Setup, enter Assignment Rules in the  Quick Find  box, then select either  Lead Assignment Rules  or  Case Assignment Rules .
• Choose  New , and then give the rule a name. Specify whether you want this to be the active rule for leads or cases created manually and via the web and email. Then click  Save .
• To create the rule entries, click  New . For each entry, you can specify:
• Order : Sets the order in which the entry will be processed in the rule, for example, 1, 2, 3. Salesforce evaluates each entry in order and tries to match the criteria of the entry. As soon as a match is found, Salesforce processes the item and stops evaluating the rule entries for that item. If no match is found, the item is reassigned to either the default Web-to-Lead owner, the administrator doing a lead import, or the default case owner.
• Choose criteria are met and select the filter criteria that a record must meet to trigger the rule.For example, set a case filter to Priority equals High if you want case records with the Priority field marked High to trigger the rule. If your organization uses multiple languages, enter filter values in your organization’s default language. You can add up to 25 filter criteria, of up to 255 characters each. When you use picklists to specify filter criteria, the selected values are stored in the organization’s default language. If you edit or clone existing filter criteria, first set the Default Language on the Company Information page to the same language that was used to set the original filter criteria. Otherwise, the filter criteria may not be evaluated as expected.
• Choose formula evaluates to true and enter a formula that returns a value of “True” or “False.” Salesforce triggers the rule if the formula returns “True.” For example, the formula AND(ISCHANGED( Priority ), ISPICKVAL (Priority, “High”) ) triggers a rule that changes the owner of a case when the Priority field is changed to High. If your condition uses a custom field, the rule entry will be deleted automatically if the custom field is deleted.
• User : Specifies the user or queue to which the lead or case will be assigned if it matches the condition. Users specified here cannot be marked “inactive” and they must have “Read” permission on leads or cases.
• Do Not Reassign Owner : Specifies that the current owner on a lead or case will not be reassigned to the lead or case when it is updated.
• Email Template : We can specifies the template to use for the email that is automatically sent to the new owner. If no template is specified, no email will be sent. When assigning a lead or case to a queue, the notification goes to the Queue Email address specified for the queue and all queue members.
• Predefined Case Teams : Specifies the predefined case team(s) to add to a case when it matches the condition. A case team is a group of people that work together to solve cases.
• Replace any existing predefined case teams on the case : Specifies that any existing predefined case teams on the case are replaced with the predefined case teams on the condition, when a case matches the condition.

After creating the entry, click  Save , or  Save & New  to save the entry and create more entries.

Assignment Rule Example

Following is sample Case assignment rule which assigns case to different queues based on Billing Country, Account SLA and customer type:

For more details about assignment rules please refer to assignment rules  official link.

Assignment rules in Salesforce trailhead

Good luck for creating Assignment rules in Salesforce 🙂

• Assignment rules , Assignment rules Salesforce , Case Assignment rules , Lead Assignment Rules , salesforce , sfdc

Ankush Dureja

Permanent link to this article: https://www.sfdcpoint.com/salesforce/assignment-rules-in-salesforce/

Skip to comment form

• Stremove.com on August 2, 2020 at 9:10 am

Case Assignment Rules Determine how cases are assigned to users or put into queues as they are created manually, using Web-to-Case, Email-to-Case, On-Demand Email-to-Case, the Self-Service portal, the Customer Portal, Outlook, or Lotus Notes.

• Dayene on August 25, 2020 at 7:01 pm

Hi! What about when I want my assignment to change when the Lead status is changed? I’ve created two criterias. First when the status is new and second when the status has other values. But when the Lead is updated and the status changes the assignment doesn´t follow this change and it does not assignment the Lead Owner correctly. Thanks.

• Vrushabh LEngade on October 27, 2020 at 3:51 pm

Use Escalation Rules and escalate the case to another user or queue

• subhasini on December 23, 2021 at 6:19 pm

Hi Ankush Dureja, there is a interview question on assignment and the question is : What will happen if the user becomes inactive(or user is deactivated) on whom the rule is assigned. Please reply me ASAP

Leave a Reply Cancel reply

Your email address will not be published.

• May 2023  (1)
• March 2023  (1)
• January 2023  (1)
• November 2022  (1)
• October 2022  (1)
• September 2022  (2)
• August 2022  (2)
• June 2022  (1)
• February 2022  (1)
• January 2022  (1)
• September 2021  (2)
• August 2021  (1)
• June 2021  (2)
• May 2021  (2)
• April 2021  (2)
• January 2021  (2)
• December 2020  (1)
• October 2020  (1)
• September 2020  (1)
• August 2020  (2)
• June 2020  (2)
• May 2020  (20)
• April 2020  (10)
• March 2020  (6)
• February 2020  (6)
• January 2020  (2)
• December 2019  (6)
• November 2019  (3)
• March 2019  (1)
• February 2019  (1)
• January 2019  (2)
• December 2018  (7)
• November 2018  (4)
• October 2018  (2)
• June 2018  (1)
• April 2018  (1)
• March 2018  (1)
• January 2018  (1)
• December 2017  (2)
• November 2017  (1)
• October 2017  (2)
• September 2017  (2)
• August 2017  (1)
• July 2017  (1)
• May 2017  (2)
• April 2017  (8)
• October 2016  (1)
• June 2015  (1)
• February 2015  (1)
• October 2014  (1)
• August 2014  (1)
• June 2014  (4)
• May 2014  (1)
• April 2014  (2)
• March 2014  (4)
• February 2014  (22)

Recent Posts

• How Salesforce Einstein GPT is changing the Game for Small-Medium Enterprises
• What are the benefits of Salesforce health cloud?
• salesforce customer 360 overview and features
• Difference Between Workflow Process Builder and Flow
• Salesforce Integration Interview Questions And Answers
• Salesforce developer interview questions
• Salesforce Admin Interview questions
• Salesforce Lightning Interview Questions
• Salesforce Field Service Implementation
• Salesforce Course Details | Eligibility, Fees, Duration

Recent Comments

• luqmaan s on Pagination using StandardSetController with wrapper class
• Santosh on Get Record Id in Lightning Web Component
• Micky on custom label in visualforce page
• Syed Wassim on salesforce order of execution
• NoviceDev on Avoid recursive trigger in salesforce

TOTAL PAGEVIEWS

• SFDC Share Point

Our Facebook page

https://www.facebook.com/sfdcpoint

© 2024 Salesforce Blog.

Made with by Graphene Themes .

Privacy Overview

10 Salesforce.com Case Assignment Rules Best Practices

Salesforce.com's assignment rules are a powerful tool, but they can also be complex. Here are 10 best practices to follow when using them.

Salesforce.com is a powerful customer relationship management (CRM) platform that allows organizations to manage customer data, track customer interactions, and automate processes. One of the most important features of Salesforce.com is the ability to assign cases to the appropriate team or individual.

Case assignment rules are the key to ensuring that cases are assigned to the right people in a timely manner. In this article, we will discuss 10 best practices for creating and managing Salesforce.com case assignment rules.

1. Utilize the Assignment Rules Hierarchy

The Assignment Rules Hierarchy is a way to organize and prioritize the order in which Salesforce.com Case Assignment Rules are evaluated. This ensures that the most important rules are evaluated first, allowing for more efficient case assignment.

When creating an Assignment Rule, users can specify whether it should be evaluated before or after other rules. If multiple rules have the same priority, they will be evaluated in the order they were created. By utilizing the Assignment Rules Hierarchy, users can ensure that their most important rules are evaluated first.

Additionally, when using the Assignment Rules Hierarchy, users can create rules with different criteria and assign them different priorities. For example, if a user wants to assign cases based on product type first, then by region second, they can set up two separate rules with different priorities. This allows for more flexibility and control over how cases are assigned.

2. Use Roles and Profiles to Assign Cases

Roles and Profiles are a great way to assign Cases because they allow for granular control over who can access what. By assigning Roles and Profiles, you can ensure that only the right people have access to the right Cases. For example, if you want to make sure that only certain users can view or edit sensitive customer information, you can use Roles and Profiles to restrict access to those users.

Using Roles and Profiles also makes it easier to manage Case Assignment Rules. Instead of having to manually assign each Case to an individual user, you can set up Roles and Profiles so that all Cases assigned to a particular Role or Profile will automatically be routed to the appropriate user. This saves time and ensures that Cases are always assigned to the correct person.

Additionally, using Roles and Profiles allows you to easily add new users to your system without having to manually update Case Assignment Rules. When a new user is added to a Role or Profile, they will automatically be given access to any Cases associated with that Role or Profile. This eliminates the need to manually update Case Assignment Rules every time a new user is added.

3. Utilize Queues for Case Assignment

Queues are a great way to assign cases because they allow for multiple users to be assigned the same case. This is especially useful when dealing with high-volume customer service requests, as it allows for more efficient and effective management of those requests. Additionally, queues can be used to prioritize cases based on their urgency or importance, ensuring that the most important cases get addressed first.

To use queues for case assignment, you’ll need to create a queue in Salesforce.com and add members to it. You can then set up Case Assignment Rules to automatically assign cases to the queue. This ensures that all incoming cases are routed to the right people quickly and efficiently. It also makes it easier to track which cases have been assigned and who is responsible for them.

4. Leverage Apex Triggers for Complex Assignment Logic

Apex Triggers allow for more complex logic than the standard Case Assignment Rules, such as assigning cases to specific queues based on criteria like case type or customer location. This is especially useful when dealing with large numbers of cases and multiple assignment rules that need to be applied in a certain order. Apex Triggers also provide an easy way to customize the assignment process by allowing developers to write custom code to handle any special requirements. Additionally, Apex Triggers can be used to automate the assignment process, which eliminates manual intervention and ensures that cases are assigned quickly and accurately. Lastly, Apex Triggers can be used to integrate Salesforce.com Case Assignment Rules with other systems, such as ERP or CRM applications, making it easier to manage data across multiple platforms.

5. Create a Default Rule for Unassigned Cases

Creating a Default Rule for Unassigned Cases ensures that all cases are assigned to someone, even if they don’t meet the criteria of any other rule. This is important because it prevents cases from slipping through the cracks and being left unassigned.

To create a Default Rule for Unassigned Cases, go to Setup > Customize > Cases > Case Assignment Rules. Click “New” and enter a name for the rule. Set the order number to be higher than any other rules you have created. Then set the criteria so that it will always evaluate as true (e.g., “Case: Type equals Any”). Lastly, assign the case to an appropriate user or queue.

6. Automate Case Escalation with Workflow

Automating Case Escalation with Workflow allows for cases to be automatically escalated when they are not addressed within a certain time frame. This ensures that no case is left unresolved and customers receive timely responses.

Workflows can be set up in Salesforce.com to monitor the age of open cases, and if they exceed a specified amount of time, then an automated action will occur. This action could include sending an email notification to the assigned user or group, reassigning the case to another user or group, or creating a task for someone to follow up on the case. The workflow can also be configured to send out reminders at regular intervals until the case is resolved.

This automation helps ensure that all cases are handled promptly and efficiently, which leads to better customer service and satisfaction. Automating Case Escalation with Workflow also reduces manual effort and saves time by eliminating the need to manually check each case for resolution status.

7. Allow Users to Self-Assign Cases

Self-assignment allows users to take ownership of cases they are best suited to handle. This helps ensure that the right person is assigned to each case, which can help improve customer satisfaction and reduce resolution time. It also gives users more control over their workloads, allowing them to prioritize tasks based on their own expertise and availability.

To enable self-assignment, admins should create a rule with an assignment type of “User” and assign it to all users who need access to the case. The user will then be able to select themselves as the owner when creating or editing a case. Admins can also set up criteria for self-assignment, such as assigning cases only to users in certain roles or territories. This ensures that cases are routed to the most appropriate user while still giving users the freedom to choose.

8. Make Sure Your Rules are Well Documented

Documenting your rules helps ensure that everyone in the organization understands how cases are assigned and why. This is especially important when multiple users or teams are involved in case assignment, as it ensures that all parties understand their roles and responsibilities. Additionally, documenting your rules can help you identify any potential issues with the process before they become a problem.

When documenting your Salesforce.com Case Assignment Rules, make sure to include details such as who is responsible for assigning cases, what criteria should be used to assign cases, and which team members should be notified of new assignments. You should also document any changes made to the rules over time so that everyone is aware of the current version. Additionally, consider creating a flowchart or diagram to visually represent the process. This will make it easier for everyone to understand the rules and follow them correctly.

9. Monitor Performance of your Rules

Monitoring the performance of your rules is important because it allows you to identify any issues with the rule, such as incorrect criteria or an inefficient assignment process. This helps ensure that cases are being assigned correctly and efficiently, which can help improve customer satisfaction and reduce case resolution time.

To monitor the performance of your rules, Salesforce provides a number of tools. The Case Assignment Rules report shows how many cases were assigned by each rule over a given period of time. You can also use the Rule Performance dashboard to view the average time taken for each rule to assign a case. Additionally, the Assignment Debug Logs provide detailed information about the assignment process, including the criteria used to assign the case and the user who was assigned the case. By using these tools, you can quickly identify any issues with your rules and take corrective action if necessary.

10. Test, Test, Test!

Testing is important because it allows you to ensure that the rules are working as expected and that they are assigning cases correctly. It also helps identify any potential issues or conflicts with other rules, which can be addressed before they become a problem.

Testing should include creating test cases and running them through the assignment rules to make sure they are being assigned properly. This can be done manually by creating test cases in Salesforce and then running them through the assignment rules, or it can be automated using an automation tool such as Selenium. Automated testing is especially useful for larger organizations with complex assignment rules.

It’s also important to periodically review the assignment rules to make sure they are still valid and up-to-date. This includes checking for any changes in business requirements or processes that may require updating the rules. Additionally, if there have been any changes to the data model, such as adding new fields or objects, these should be tested to make sure the assignment rules are still functioning correctly.

10 Singular Value Decomposition (SVD) Best Practices

10 perl global variable best practices, you may also be interested in..., 10 javascript file organization best practices, 10 symfony folder structure best practices, 10 intune device configuration profiles best practices, 10 user profile ux best practices.

Cloud SYlla

Your Agile & Digital Partner

• Mar 2, 2023

Understanding Assignment Rules: A Comprehensive Guide

Assignment rules are an important feature of Salesforce that help businesses automate assigning records to specific users or teams based on predefined criteria. This article will discuss assignment rules, how they work, and the benefits they provide to businesses.

What are Assignment Rules?

Assignment rules are a set of criteria that are defined by businesses to determine how records should be assigned to users or teams within the Salesforce system. These criteria can be based on several factors, such as the record type, location, record status, or the user's role or territory. For example, a company may set up an assignment rule to automatically assign a new lead to the sales rep who covers that particular region or product line.

How do Assignment Rules Work?

When a record is created or updated, the assignment rules evaluate the record based on predefined criteria. The assignment rule automatically assigns the record to the designated user or team if the criteria are met. Once the record is assigned, the user or team can work on the record.

Salesforce provides a simple wizard that enables administrators to set up assignment rules. The wizard allows administrators to define the criteria for the assignment, select the user or team to assign records to, and set up any needed notifications or escalations.

How to Set Up Assignment Rules in Salesforce

Setting up assignment rules in Salesforce is a straightforward process that requires the following steps:

Identify the criteria for record assignment - Before creating an assignment rule, businesses should first identify the criteria used to assign records. It might include the record type, location, user role, or other custom fields.

Create the assignment rule - Once the criteria have been identified, businesses can create the assignment rule in Salesforce. It involves setting up a rule that evaluates the criteria and assigns records to the appropriate user or team.

Test the assignment rule - After the assignment rule has been created, businesses should test it to ensure it is working correctly. It might involve creating test records and verifying that they are assigned to the correct user or team.

Activate the assignment rule - Testing it in Salesforce will allow it to be activated. It allows it to automatically assign records to the appropriate user or team.

Types of Assignment Rules in Salesforce

Salesforce offers two types of assignment rules: standard assignment rules and lead assignment rules.

Standard assignment rules assign records to users or teams based on predefined criteria. They can be set up for various record types, including leads, cases, and opportunities.

Lead assignment rules are specific assignment rules used to assign leads to sales reps. They evaluate the criteria for a lead, such as location or product interest, and assign the lead to the appropriate sales rep based on a round-robin or customized assignment method.

Benefits of Assignment Rules

There are several benefits to using assignment rules in Salesforce, including:

Increased Efficiency

One of the most significant benefits of assignment rules is their increased efficiency. By automating the process of assigning records, sales, and customer support teams can spend less time manually assigning leads and cases to the appropriate users or teams. They can focus on more important tasks, such as following up with leads, resolving customer issues, and closing deals.

With assignment rules, businesses can streamline their processes and reduce the time it takes to respond to customer inquiries, ultimately improving their overall efficiency and productivity.

Improved Customer Satisfaction

Another important benefit of assignment rules is the improved customer satisfaction they can provide. Businesses can automatically assign cases to the appropriate user or team to ensure that customer inquiries are handled promptly and efficiently. Customers receive faster responses to their inquiries, which can help improve their overall satisfaction with the company.

In addition, by assigning cases to users with the appropriate skills and knowledge, businesses can ensure that customer issues are resolved more effectively, further improving customer satisfaction.

Accurate Data

Assignment rules also help businesses maintain accurate data in their CRM system. By automating the process of assigning records, businesses can ensure that data is entered correctly and consistently. It means that reports and analytics generated from the data are more accurate and reliable, which can help businesses make more informed decisions.

In addition, businesses can use assignment rules to enforce data validation rules, which can help prevent incorrect data from being entered into the system.

Consistency

Another benefit of assignment rules is that they help ensure consistency in record assignments. By automating the process of assigning records, businesses can ensure that records are assigned to the appropriate user or team consistently. It reduces the risk of errors or omissions occurring when records are manually assigned.

In addition, by using assignment rules to enforce a standardized process for record assignment, businesses can ensure that records are handled consistently across different teams and regions.

Flexibility

Finally, assignment rules provide businesses with great flexibility in assigning records. Businesses can define complex rules based on various criteria, such as record type, location, or user role. Businesses can customize their assignment rules to fit their specific needs and workflows.

In addition, assignment rules can be updated or modified as needed, allowing businesses to adapt to changes in their business or industry.

Best Practices for Using Assignment Rules in Salesforce

Businesses should follow these best practices to ensure Salesforce assignment rules are working effectively:

Define clear assignment criteria: Before setting up assignment rules, businesses should define clear criteria for record assignments. It will help ensure that records are assigned accurately and consistently.

Test assignment rules before activation: Before activating assignment rules, businesses should test them to ensure that they are working correctly. It will help prevent errors and ensure that records are assigned to the appropriate user or team.

Monitor and adjust assignment rules: It is important to monitor them regularly to ensure they are working properly. Businesses should also be prepared to adjust assignment rules as needed to accommodate changes in their business or industry.

Communicate changes to users: When changes are made to assignment rules, businesses should communicate with them to ensure they are aware of any changes in their workload or responsibilities.

In conclusion, assignment rules are a powerful feature of Salesforce that helps businesses automate assigning records to specific users or teams. The benefits of assignment rules include increased efficiency, improved customer satisfaction, accurate data, and consistency.

By using assignment rules, businesses can streamline their processes, improve their overall effectiveness, and achieve their goals more efficiently.

At Cloud Sylla, our sole focus is on assisting businesses in achieving success through digital transformation. Our goal is to aid customers in making the crucial shift to digital technologies, enabling them to bolster their strategies, multi-channel distribution, and internal operations.

Recent Posts

What is Orchestration Flow in Salesforce? Detailed Guide

What is Record-Triggered Flow in Salesforce? Detailed Guide

How to Get & Reset Security Token in Salesforce? (Detailed Guide)

How to Apply Case Assignment Rules in Flow

May 18, 2023 Yumi Ibrahimzade Actions , Automation , Flow , Flow Actions , Flow Packages , Packages 29

The case object is a core part of the Salesforce platform. It helps manage and track customer issues and inquiries. You can use this standard object to handle support requests effectively. The case object acts as a central repository for recording and monitoring customer interactions. It allows you to streamline your customer service processes. In order to improve the support efficiency, it is important to assign cases to the right teams or individuals. Although you can manually assign the record, it is possible to use the standard case assignment rules as well. Case assignment rules determine how cases are assigned to users or put into queues.

When you create a new case record, you can just mark "Assign using active assignment rule" to run case assignment rules.

However, if you are creating the case record using Salesforce Flow, there is no standard option to run the case assignment rules. This option exists just for lead assignment rules. Moreover, when you create a case using flow, you have to set the correct owner id. Otherwise, the system doesn't run the case assignment rules and assigns the case to the current user. If you really want to use the logic that you have in your assignment rule, you will have to build the same logic again in the flow.

In this post, you can find a custom invocable action (Apex class) that runs case assignment rules for any case record that you want.

How to Use the Action

1-  Install the action using the installation links below.

2-  Add a new action to your flow and search for "Apply Case Assignment Rules", this is the name of the action that you installed.

3- Give a name to the action and provide the id of the case record that you want to assign.

You can use this action in any flow type that supports the action element.

Here is a screen flow that clones a case record with its related records. It uses this custom action to assign the new case record. Read this post to learn how to create a flow to clone a record with its related records.

Installation Links

Use this link to install in production or developer edition environments.

Use this link to install in sandbox environments.

28 Comments

Is that a future method or synchronous?

It is synchronous.

Hi Yumi, I tried using this on a case after save flow as an immediate action on create and it doesn't work. However, if I add a scheduled path of 0 min after creation, it works. Do you know of this limitation? Thanks!

I'm also noticing that this doesn't work when a guest executes a screen flow from a public page which creates the case.

Is your screen flow working in system context - view all data?

Hi Jay, It works in asynchronous path as well. I will check if it is possible to use it in the immediate path.

Thank you, I don't have to code this now.

You are welcome!

Hey Yumi, Case is assigned but email is not fired to members of queue? Any suggestions?

Hi Priyanshu, You are right. I just added it to the code and uploaded the package again. Can you please try with the new version?

Thanks Yumi, Can you please provide the url for new version?

Yumi, waiting for your response.

Is there a way to verify (in a flow decision), using a formula or some other way, if the "Assign using active assignment rule" is checked? I have a user case where the Assignment rules need to be triggered within the flow ONLY when the checkbox "Assign using active assignment rule" is checked, but I cannot find a way to do so. Any ideas?

"Assign using active assignment rule" is not a field on the object, so I think unfortunately it is not possible to get this information.

Hey Yumi Ibrahimzade, Not working in production or can you please provide url for update version? Thanks in advance 🙂

Thank you so much for this package. I just came across the need for this and then found your solution. It works exactly as expected.

I am glad that you found it useful!

Thanks Yumi, It helped me a lot to resolve my issue!

I am glad that you liked it Nadia!

Thanks for the post, Yumi, would you be willing to publish the code in a code snippet?

You are welcome Andy. Here is the code:

public class ApplyCaseAssignmentRules { @InvocableMethod (label='Apply Case Assignment Rules') public static void CaseAssign(List CaseId) { Database.DMLOptions dmo = new Database.DMLOptions(); dmo.assignmentRuleHeader.useDefaultRule= true; dmo.EmailHeader.TriggerUserEmail = true; Case Cases=[Select id From Case Where Case.id in:CaseId]; Cases.setOptions(dmo); update Cases; } }

I am using this action in a trigger flow (After Save), but it's not working, I should a scheduled path if I wanted to work, any suggestions please ? Thank you

Hi, You should use this action in a scheduled or asynchronous path.

I am trying to install in sandbox and getting this error: ApplyCaseAssignmentRulesTest: Method does not exist or incorrect signature: void startTest() from the type Test

Worked perfect in a screen flow with no Scheduled or Asynchronous path.. Thanks!

Hi Yumi! We have installed the packaged and worked perfectly well in a flow that creates cases. Thank you so much for this. We are facing another situation: we have a flow that reopens a case and we need to go through assigment rules again only when the case user owner is not active. We added the apex code to the flow but it didn´t work in this scenario. Does it trigger only for new cases? Is it possible to use it for updated cases? Can you help? Thank you in advanced.

It works on update too, can you try to run this action in async path?

Hi, I've used the component in Screenflow without any issue, but now I'm getting this one : "The "ApplyCaseAssignmentRules" element in your flow has validation errors." Is there a way to know more about the error ? It works in my previous flow version and the output, Case record variable as Id, is the same in both version. With further tests, I've noticed that the flow needed to be activated in order for the Apex Class to work.

1 Trackback / Pingback

• Integrating ChatGPT with Salesforce: A Real-Life Example

Leave a Reply Cancel reply

Your email address will not be published.

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

Copyright © 2024 | SalesforceTime.com

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

• AppExchange Listings
• Contact Sales
• Contact Support

APPS FOR SALESFORCE

• All Ortoo Apps for Salesforce

Overview and pricing details for all Ortoo apps

• Case Orchestrator

AI-powered Salesforce assignment and email automation

• Lead Assignment
• Case Assignment

Discover the application potential of Q-assign and Email-to-anything and how they revolutionize task management and email integration.

FEATURED USE CASES

• Salesforce email to case - the ultimate upgrade, with AI-powered triaging
• Optimizing service team effectiveness with intelligent case assignment rules

Case Studies

Explore success stories and discover the transformative impact of Q-assign and Email-to-anything as they empower businesses to streamline operations andenhance productivity.

FEATURED CASE STUDIES

• Sage Intacct

Featured eGuide

• Unlocking Salesforce ROI

Featured article

Customer service automation: now is the time.

Discover how customer service automation in Salesforce can transform your case resolution process and reduce the burden on your human resources

• About Ortoo
• Workforce Effectiveness

Efficiency is doing things right; effectiveness is doing the right things.

Peter Drucker, ‘Father of management thinking’

• Learn about Ortoo's suite of productivity apps -
• Watch the videos

Optimizing Service Team Effectiveness With Intelligent Case Assignment Rules in Salesforce

Featured case study

App: Q-assign for Service Industry: Applies to all industries

To transform your case management process in Salesforce by implementing Q-assign’s intelligent case assignment rules for improved effectiveness and customer service outcomes.

Pre-conditions:

• Salesforce CRM operational with a focus on customer service.
• Q-assign installed and configured within Salesforce.
• Case assignment rules established based on agent expertise, case complexity, and priority.
• Comprehensive training for service agents and managers on Q-assign functionalities.
• Case Manager – Manages the assignment and delegation of cases among the Service Team.
• Customer Service Agent – First point of contact for customers.
• Tier-2 Support Agent – Specialized agent responsible for dealing with more complex cases.
• Salesforce Administrator – Ensures the configuration and maintenance of Salesforce systems, including Q-assign.
• Configuration of Case Assignment Rules : Set up and customize case assignment rules in Q-assign.
• Case Receipt and Logging : Log and track customer cases in Salesforce.
• AI-Driven Case Triage : Utilize Q-assign’s AI capabilities to categorize and prioritize cases.
• Automated Case Assignment : Implement dynamic rules for distributing cases to appropriate agents.
• Agent Response and Handling : Enable agents to efficiently manage cases, informed by AI-driven insights.
• Performance Monitoring and Analysis : Use Salesforce reporting tools to track case management efficiency and agent performance.

Post-conditions:

• Cases are intelligently assigned, ensuring quick and effective resolutions.
• Agents are better equipped with relevant case information, improving service quality.
• Enhanced data analytics for ongoing service optimization.

Exceptions:

• Manual intervention for cases requiring special attention or falling outside standard parameters.
• Alerts for system discrepancies or operational issues.

Metrics for Success:

• Decreased average case resolution times.
• Higher customer satisfaction ratings.
• Improved agent efficiency and performance metrics.
• Strategic Case Assignment: Boosts efficiency through intelligent case distribution.
• Operational Excellence: Streamlines case management with automated assignments.
• Insightful Data Utilization: Offers actionable insights for continuous service enhancement.

Optional Enhancements:

• Automated Case Triage: Triage, categorize and prioritize cases as soon as they come into the business, prior to assignment
• Advanced AI Integration : Incorporate deeper AI functionalities for predictive case management.
• Multi-faceted Case Analysis : Expand case analysis criteria, including customer history and agent performance.
• Automated Response Templates : Implement AI-driven response templates for common case scenarios.
• Enhanced Reporting Tools : Upgrade reporting capabilities for more detailed performance analysis.

Conclusion:

Implementing Q-assign’s intelligent case assignment rules significantly elevates the efficiency and effectiveness of customer service teams. And by strategically utilizing AI Actions, Q-assign not only streamlines case management but also ensures a higher standard of customer service, reflecting a modern and responsive approach to customer needs.

All Use Cases

Featured use cases

Use AI to Enrich Leads in Salesforce

The ultimate it support ticketing system: transform your support function, with case orchestrator, how to convert leads automatically in salesforce.

From $21 per user per month

Assign any work item to the best available Salesforce user via intelligent rules and dynamic Plug-in Actions

Q-assign pricing details

Email-to-anything

From $19 per user per month.

Effortlessly manage emails in Salesforce. Send to distribution lists, capture replies. Auto-create, auto-update 

Email-to-anything pricing details

How to achieve Workforce Effectiveness

Ortoo enables teams to effectively work towards organizational goals with intelligent solutions that allow them to focus on the tasks that really matter.

See related case studies

• +44 (0) 20 3111 1323

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.

Is there a way to update Case Assignment Rules in bulk?

I'm working with an organisation that has 200+ Case Assignment rules and we have to update all of them to add a new criteria. It's going to be a bit of a pain-staking task to update each one individually, so I'm wondering... is there a way to edit these Assignment Rules in bulk?

Assignment Rules are just metadata in the system right? I don't know much about using the metadata API or working with the package.xml file, but surely there is a way to make this process quicker and easier? I suspect it won't be the last time we have to make changes to lots of Assignment Rules (and they might scale even more in the future).

Thanks in advance!

• servicecloud
• assignment-rules

As you mentioned before you can indeed use the metadata api to retrieve your assignment rules thorugh the package.xml file like this

for this it is easiest to use visual studio code and the salesforce CLI for which you can find instructions on how to install it here

once VSC and the CLI are installed you can create your project and add the case assignment rules to your package.xml Once this is done you can right click in your package xml to do a "retrieve source from manifest file" and update your rules before doing a deploy source to org.

and always be sure to test everything first on a sandbox environment before making such changes on production

You must log in to answer this question.

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

• The Overflow Blog
• Mobile Observability: monitoring performance through cracked screens, old...
• Featured on Meta
• Announcing a change to the data-dump process
• Bringing clarity to status tag usage on meta sites

Hot Network Questions

• Expensive constructors. Should they exist? Should they be replaced?
• What is happening when a TV satellite stops broadcasting during an "eclipse"?
• Flight delayed, risk of missing connection, can I cancel and get refund?
• Did Gandalf know he was a Maia?
• How many ways can you make change?
• Functor composition rule necessary?
• If Starliner returns safely on autopilot, can this still prove that it's safe? Could it be launched back up to the ISS again to complete its mission?
• Can we idiomatically say "Jack is an ordered person" to mean he is an organized person?
• Explain how π – 1 + 50 + ⅔ × 1000 is PLONK
• I have two identical LaTeX files, with different file names. Only one yields "undefined references." Why is this happening?
• Percentage changes versus absolute changes when comparing rankings
• Do passengers transiting in YVR (Vancouver) from international to US go through Canadian immigration?
• Converting pipe-separated file containing GeoJSON geometries to GeoJSON with ogr2ogr
• decode the pipe
• Create random points using minimum distance calculated on the fly using ModelBuilder in ArcGIS Pro
• Can an APK be installed from a URI via `adb`?
• Is consciousness a prerequisite for knowledge?
• Does an airplane fly less or more efficiently after an mid-flight engine failure?
• How can I use DihedralAngle to get correct result?
• Why is Namibia killing game animals for food rather than allowing more big game hunting?
• Seinfeldisms in O.R
• Is it a date format of YYMMDD, MMDDYY, and/or DDMMYY?
• Why is simpler prose more popular these days?
• Lore reasons for being faithless