case assignment rules limit in salesforce

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.

Best Practices for Optimizing Case Assignment Rules in Salesforce

Salesforce is a powerful customer relationship management (CRM) platform that helps businesses manage various aspects of customer interactions. One critical aspect of customer support is case management in Salesforce , where efficient case assignment rules play a vital role. Optimizing these rules can significantly enhance the effectiveness and efficiency of handling customer inquiries and issues.

Understanding Salesforce assignment rules

Salesforce assignment rules govern the distribution of incoming cases to the appropriate agents or teams. These rules ensure that each case is routed to the most suitable person for prompt resolution. Salesforce queues further facilitate this distribution by acting as virtual storage areas for cases before they are assigned.

There are two types of assignment rules in Salesforce:

• Salesforce Lead Assignment Rules primarily focus on distributing new leads among sales representatives based on predefined criteria such as geography, lead source, or lead score. 
• Case Assignment Rules are responsible for Salesforce case distribution. These rules play a pivotal role in the realm of customer support by directing incoming Salesforce support cases to agents or teams equipped with the expertise to resolve specific issues. 

As organizations strive to provide seamless experiences for both potential customers and existing clients, mastering these assignment rule types becomes crucial for optimizing customer interactions and nurturing lasting relationships.

The need for optimization

Default assignment rules might not account for specific business needs, leading to uneven case distribution, longer resolution times, and potential customer dissatisfaction. Optimizing Salesforce rules address these issues by ensuring equitable distribution, maximizing agent expertise, and expediting case resolution.

Best practices for Salesforce assignment

• Prioritizing cases . Categorize cases based on urgency or complexity to assign high-priority cases to experienced agents, ensuring quick resolutions.
• Efficient assignment techniques . Implement round-robin assignment or load-based distribution to evenly distribute cases among available agents, preventing bottlenecks.
• Role-based vs. direct assignment. Choose between role-based case assignment, where cases are directed to specific teams or direct assignment, where cases go to individual agents based on expertise.

Advanced Salesforce assignment techniques

• Multi-criteria case assignment. Combine multiple factors such as case type, priority, and customer tier for more accurate case routing.
• Automated case assignment. Leverage Salesforce automation tools like Process Builder and Flow to automate case assignments based on predefined criteria.
• Customized queues. Tailor Salesforce queues to match specific business units or case types, improving case categorization and routing.

Streamlining Salesforce case routing

Salesforce case routing logic.

Understanding Salesforce case routing logic is fundamental for ensuring that customer inquiries and issues are directed to the right personnel with the expertise to address them effectively. The case routing process involves a sophisticated interplay of various factors, such as queue membership, agent skills, workload, and availability. Salesforce’s intelligent algorithms consider these variables to determine the most suitable destination for each case, maximizing the chances of swift resolution. 

Caseload balancing

Balancing caseloads in Salesforce goes beyond equal case distribution among agents. This strategic approach boosts customer service quality and agent efficiency. Preventing overload for some and underutilization for others, it curbs burnout and enhances job satisfaction. 

Even workloads lead to swift responses, faster resolutions, and increased customer contentment. Moreover, balanced caseloads aid managers in spotting trends, optimizing resource allocation, and refining processes. This practice optimizes operations and fosters a cooperative, productive support environment.

Case escalation and reassignment strategies

Case escalation and reassignment strategies are vital for effective customer support. Escalation involves transferring cases to experienced agents or supervisors to address complex issues promptly. Case reassignment in Salesforce redirects cases to different teams or agents for specialized handling. 

These strategies prevent delays, ensure timely resolutions, and uphold customer satisfaction. With clear escalation and reassignment criteria, organizations enhance their support processes, allocate resources efficiently, and build a reputation for adeptly managing diverse customer concerns.

Configuring and customizing assignment rules

Salesforce rule configuration instructions.

• Access setup. Log in to your Salesforce account and navigate to the Setup menu located in the top-right corner of the screen.
• Search for assignment rules: In the Quick Find box, type “Assignment rules” and select what Assignment Rules you need to configure: Lead Assignment Rules or Case Assignment Rules. 
• Create a new rule. Click on the “New Assignment Rule” button to start configuring a new rule.
• Define Salesforce rule criteria. Give your rule a descriptive name and set the rule entry criteria. This includes conditions like case origin, type, priority, or other custom criteria that determine how cases are assigned.

• Specify rule actions. Determine what happens when cases meet the specified criteria. You can assign cases to specific users, queues, or use other automation processes.
• Configure rule entry order. If you have multiple assignment rules, specify the order in which they’re evaluated. This is important when cases could meet criteria for more than one rule.

• Activate the rule. Once configured, activate the assignment rule to make it live and start directing cases accordingly.

You can also integrate Salesforce workflow rules to automate follow-up actions after case assignments, enhancing customer communication.

Enhancing case management efficiency: Salesforce support cases best practices

• Utilize case templates. Expedite responses by employing predefined case templates for common issues, ensuring consistent and swift resolutions.
• Leverage macros. Enhance agent productivity with macros that automate multiple actions, reducing manual tasks and accelerating case handling.
• Opt for case cloning. Save time on data entry by cloning similar cases, streamlining the process of creating and managing new cases.
• Update Knowledge bases . Maintain accurate and current knowledge bases to empower agents with reliable information, enabling efficient issue resolution.
• Engage collaboration tools. Employ platforms like Chatter to encourage agent collaboration, fostering knowledge sharing and teamwork for complex cases.
• Notify agents of new assignments promptly and emphasize the importance of case ownership for accountability.

Optimizing case assignment rules in Salesforce is indispensable for efficient case handling. By understanding the fundamentals, implementing best practices, and embracing advanced techniques, businesses can ensure equitable case distribution, expedite resolutions, and enhance customer satisfaction. A well-optimized case assignment system ultimately streamlines support processes and contributes to the overall success of the customer support function.

Advanced Communities is your best partner when it comes to configuring your Salesforce instance or developing a Salesforce Experience Cloud site. In case of any questions feel free to reach out to get professional support when you really need it. 

You may be interested in: Maximizing ROI with Salesforce: A Case Study

Share this:

• Renewable Energy
• Artificial Intelligence
• 3D Printing
• Financial Glossary

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 glusterfs best practices, 10 lwc best practices, 10 sql server numa nodes best practices, 10 azure policies best practices.

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.

Popular Posts

• Navigation Service in LWC(Lightning Web Components) 16 comments
• Modal/Popup Lightning Web Component(LWC) 6 comments
• Batch Apex Example In Salesforce 17 comments
• for:each template directives in LWC 1 comment
• Wrapper Class in Apex Salesforce 20 comments
• Get Record Id in Lightning Web Component 9 comments
• Lightning Web Components(LWC)Tutorial 4 comments
• template if:true Conditional Rendering LWC 8 comments
• Triggers in Salesforce 5 comments
• Lightning Web Component(LWC) Toast Messages 13 comments
• 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

Explore the Buying Group Motion! Start your journey with our Resource Center.

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

Snowflake Scales Account Based Plays with LeanData Revenue Orchestration

Clockwise Supports PLG Motion with LeanData Revenue Orchestration

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

How to Define Assignment Rules

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

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

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

Criteria for Lead Assignment Rules

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

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

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

How to Create Salesforce Lead Assignment Rules

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

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

Why Are Your Salesforce Lead Assignment Rules Not Working?

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

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

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

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

Assignment Rule Examples

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

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

How LeanData Simplifies Salesforce Lead Assignment

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

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

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

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

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

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

• lead assignment rules
• lead assignment rules salesforce

Ray Hartjen

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

More Related Content

How to Automate Lead Routing in Salesforce

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

Salesforce Lead-to-Account Matching, the Easy Way

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

10 Best Lead Assignment Tools for Revenue Teams (2024)

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

How to Apply Case Assignment Rules in Flow

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

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.

25 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!

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

Limitations on Case Assignment Rules

A case assignment rule can contain up to 3000 rule entries , including 300 formula rule entries, which contain the conditions a case must meet to be assigned to a designated assignee. A case assignee can be a user or a queue.

Does this mean that 3000 rules can have criteria for each and there is only a 300 limit if you create a formula? 

@* Service Cloud * ","contentType":"entity","entity":{"id":"0F93A0000001yCOSAY","name":"* Service Cloud *","type":"MENTION","photoUrl":null,"description":null}}"> @* Service Cloud *  

• 役に立った順で並び替え

Answer from Support:

So when we click on the assignment rule name simply under assignment rule then we can see the total number of rule entries. There is a column named order which shows the count of rule entries and as mentioned in the documents there limit is 3000 rule entries, including 300 formula rule entries which means up to 300 formula rule entries can be added with up to 2700 basic criteria based rule entries.

• App Building
• Be Release Ready – Summer ’24
• Integration
• Salesforce Well-Architected ↗
• See all products ↗
• Career Resources
• Essential Habits
• Salesforce Admin Skills Kit
• Salesforce Admin Enablement Kit

Home » Article » 5 Essential Questions Salesforce Admins Must Ask for Effective AI Solutions

• 5 Essential Questions Salesforce Admins Must Ask for Effective AI Solutions

You know artificial intelligence (AI) is officially everywhere when your 73-year-young mother asks you if AI can create a birthday card design for one of her friends. Which is another way of saying, it’s most likely crept into your business conversations with stakeholders and users. If not, then let’s be proactive Salesforce Admins and get ahead of the game by looking at five questions you should ask your business to build amazing AI solutions in Salesforce.

But let’s not get ahead of ourselves. First, what are the AI tools admins have at their disposal? 

Let’s start with Prompt Builder in Salesforce, which is used to integrate generative AI into various workflows, enhancing user efficiency and customizing interactions through AI-generated content. Users can create different types of prompt templates, such as Sales Email, Field Generation, and Flex, which are adaptable to various data types and use cases within the Salesforce Platform. 

These templates leverage customer relationship management (CRM) data and can be invoked via Salesforce’s platform tools, allowing users to generate personalized communications and content dynamically. The management and customization of these templates involve a user interface (UI) where admins can revise and perfect templates based on feedback and performance, ensuring the AI outputs meet the desired standards and effectiveness.

Next, we have Einstein Copilot which enables users to interact with the system using natural language to perform tasks and retrieve information, effectively enhancing productivity by drawing answers from secure company data. The tool is embedded within the Salesforce ecosystem, respecting existing access controls and integrating with the Einstein Trust Layer for ethical and secure AI operations. 

Users can engage in conversational exchanges with Copilot, asking questions and receiving context-aware responses, thus simplifying tasks like summarizing deals or drafting emails without needing advanced technical skills. Unlike Einstein Bots, which require extensive setup and operate on rigid rules, Einstein Copilot offers a more user-friendly and flexible approach, utilizing a large language model (LLM) to understand and respond to user requests in a conversational manner.

Now that we have that aside, let’s look at the five questions Salesforce Admins need to ask of their organization and its stakeholders so we can build the best, most powerful tools for our users.

1. Which mundane tasks are driving your team bonkers?

So, why are we asking this question when we could just be building cool prompts?! This is going to help us build the most useful AI solution first. 

Repetitive tasks, like sending emails for sales and service people, can add to frustration. Especially if they need to draw information from the record and offer a personalized voice in that email. Because, let’s be honest, templates work only some of the time, and most users end up customizing the output right away. Look for answers that will guide you to create the most useful prompts in Prompt Builder first, like a post-meeting follow-up thank you message.

2. How painful is it to quickly catch up on a customer record?

You probably know where I’m going with this question, but it’s the details in the answer that we really need. Do they want a summary text field on the record? And if so, which information is important? This will help you correctly ground your prompt to pull the right data in and build a summary they are expecting.

3. Are we missing the mark on collecting important data?

As Salesforce Admins, we can build some pretty sweet prompts. But if the answer to question #2 is “give me a summary of the last five customer interactions based on activities logged”, however, there is no enforcement on logging activities. Well, then the summary isn’t going to give the desired result. 

The goal with this question is for us to help the organization prioritize and enforce good data collection so that our prompts perform!

4. How can similar data turbocharge your decision-making?

Here’s where it gets interesting. If you’re in sales, finding opportunities similar to the one you just nailed can be invaluable. Or, if you’re in customer service, quickly pulling up all records for a frequent caller can save the day. 

This isn’t just about speed; it’s about making connections faster and more accurately.

5. What does success look like, and how do we track it?

It’s super easy as an admin to get caught up in rolling out a new feature or building in the latest technology. But it’s important to think about your rollout plan, your training, and how you want to evaluate the success of your prompts and Copilot actions. 

Even more important is making sure that your stakeholders agree with the plan and what success looks like. Now for some or many of your users, using an AI feature could be intimidating, which means it might not be for everyone at first. A core group of engaged early adopters who represent the larger user base will be key to helping you refine and track each feature.

Solve simple solutions along the way

It’s important to remember that there are some easy solutions we can give our users when having an AI conversation. 

For example, with question #1, let’s say your sales users answer with “I’d ask Einstein to give me my top five opportunities closing this week every day.” This is an opportunity for you to go back and offer up a list view with global variables to your sales org as a quick win. Sure, Einstein can offer that in a prompt, but now you’re saving your user from asking the same prompt every time and getting them right to the answer.

The same can be said if they find themselves asking Einstein for all the opportunities or cases related to a single Account. This could be a signal that a page layout needs to be refreshed. Maybe think about how you can use Dynamic Pages to show that relevant related list higher on the record, or on mobile. That will free up the user to have a deeper, more meaningful interaction with Einstein, so you are building better solutions.

Ready to put Einstein to action? We launched the #BuiltWithEinstein Quest to help you show off your creative AI use cases to the community for a chance to win* a Dreamforce pass or a custom #BuiltWithEinstein T-shirt! *Official rules apply. See the Trailblazer Quests page for full details and restrictions.

It’s simple. You’ll build a prompt with Prompt Builder or an action with Copilot Builder and share your use case in a screen-recorded video on X or LinkedIn with the hashtag #BuiltWithEinstein.

Visit the #BuiltWithEinstein website to view custom Einstein actions and prompts built by Salesforce Admin Evangelists and Developer Advocates. 

Learn more about the #BuiltWithEinstein Quest and be sure to complete it by June 30, 2024.

• Salesforce Site: Einstein Copilot
• Salesforce Admins Blog: Introducing Prompt Builder: Activate Prompts in the Flow of Work
• Salesforce Admins Blog: Get Hands On with AI and Showcase What You’ve #BuiltWithEinstein
• Salesforce Admins Podcast: Introduction to Einstein Copilot with Gary Brandeleer
• Salesforce Admins Blog: Harness Copilot Analytics and AI for Organizational Success

Mike Gerholdt

Mike Gerholdt is the Senior Director of Salesforce Admin Evangelism at Salesforce. He is part of a group of World-class Admin Evangelists who are helping Salesforce Admins realize their dreams by being technology leaders and advancing their careers.

• How Can Solving Sudoku and Wordle Enhance Your Critical Thinking Skills?
• Why Salesforce Community Events Are Crucial for Professional Networking
• The Dreamforce 2024 Admin Track Call for Participation Is Open!

Related Posts

How Salesforce Einstein Is Supercharging Mobile Experiences

By Keith Samuel | November 15, 2023

While its impact is widespread, one of the most exciting aspects of artificial intelligence (AI) is its ability to create conversational interactions that generate personalized experiences, supercharging productivity and efficiency. In this blog post, we’ll explore how the implementation of large language models on mobile devices is reshaping the enterprise mobile landscape and how Salesforce […]

How to Use Generative AI Tools to Write SOQL Queries

By LeeAnne Rimel | July 3, 2023

Salesforce Object Query Language (SOQL) is a powerful tool that allows you to retrieve data from Salesforce. You can use SOQL to query any Salesforce object, including custom objects, custom fields, and user permissions like profile and permission set perms. As a Salesforce Admin, I know that writing SOQL queries can be a pain. Not […]

AI Prompt Writing for Salesforce Professionals

By Tom Hoffman | June 28, 2023

The rise of the machines Machines and artificial intelligence (AI) have been part of popular discussion since Samuel Butler authored Erewhon (1872), where his satirical utopian society explored the morality of conscious machines as a natural evolution of the Industrial Revolution. One-hundred and fifty years later, OpenAI released GPT-4, introducing the world to AI that […]

Product Area

Feature impact.

• How Search Breaks Up Information
• How Search Results are Ordered
• How Does Einstein Search Use My Data
• Search for Records
• Get Personalized Results
• See Instant Actionable Results
• Natural Language Search Examples
• Enhance Natural Language Search
• Limitations for Non-English Terms
• Recommended Results
• Protect Custom Fields in Search
• Lookup Search Cheat Sheet
• Enable Natural Language Search Filters (Pilot)
• Manage Einstein Search for Knowledge Settings
• How Article Results Are Ranked
• Manage Your Article Results
• Apply Multi-Language Knowledge Search
• Use Persistent Knowledge Search Filters
• Search Answers Requirements and Considerations
• Enable Search Answers or AI-Generated Search Answers
• Give Agents Access to Standard or AI-Generated Search Answers
• Filter Out Your Knowledge Search
• Refine Search With Wildcards and Operators
• Enable Search Analytics (Pilot)
• Access the Search Analytics Dashboard (Pilot)
• Example: Cases Closed by Interaction Type (Pilot)
• Example: Cases Closed by Number of Searches (Pilot)
• Search Analytics Considerations (Pilot)
• Search Queries DMO (Pilot)
• Search Interactions DMO (Pilot)
• Search Results DMO (Pilot)
• Search Analytics Calculated Insights (Pilot)
• Manage Einstein Search Settings
• Customize Global Search for Your Users
• Customize Search in Experience Cloud Sites
• Customize Search for Service Agents
• Considerations for Rules
• Considerations for Objects to Always Search
• Edit Searchable Objects in an Experience Cloud Site Configuration
• Delete a Search Configuration
• Searchable Setup Objects
• Search Manager Considerations
• Search Layout Guidelines
• Search Layouts Limitations
• Edit Your Search Layout
• Additional Layout Configurations
• Build Your Synonym Groups
• How Federated Search Works
• Federated Search in Lightning Experience
• Federated Search Considerations
• Use an External Provider Data Source for Federated Search
• Create the Atom XSL File
• Edit and Test the Solr Query
• Publish the OpenSearch Description
• Create the External Object
• Configure the External Object
• Enable the Object in Experience Cloud Sites
• Apply Field-Level Security to Custom Fields in Search
• Limitations for Document Text, Picklists, and Restricted Fields
• Right-to-Left (RTL) Language Limitations
• Get the Results You Want
• How to Make Search Work Faster
• How Search Crowding Affects Search Results
• Common Einstein Search Cases
• Secondary Field Usage and Limitations
• Objects and Languages Affected
• Tips on Search Errors
• Configure Search Settings in Salesforce Classic
• Configure Search Layouts in Salesforce Classic
• Searchable Fields: Account Brand
• Searchable Fields: Account Relationship
• Searchable Fields: Activities (Events and Tasks)
• Searchable Fields: Address
• Searchable Fields: Asset
• Searchable Fields: Asset Relationship
• Searchable Fields: Asset Warranty
• Searchable Fields: Attachment
• Searchable Fields: Authorization Form
• Searchable Fields: Authorization Form Consent
• Searchable Fields: Authorization Form Data Use
• Searchable Fields: Authorization Form Text
• Searchable Fields: Award
• Searchable Fields: Business Account
• Searchable Fields: Business Brand
• Searchable Fields: Campaign
• Searchable Fields: Case
• Searchable Fields: Care Metric Target
• Searchable Fields: Care Pgm Prov Healthcare Provider
• Searchable Fields: Care Program Enrollment Card
• Searchable Fields: Care Program Provider
• Searchable Fields: Care Provider Adverse Action
• Searchable Fields: Care Registered Device
• Searchable Fields: Channel Program
• Searchable Fields: Channel Program Level
• Searchable Fields: Chatter Feed
• Searchable Fields: Chatter Group
• Searchable Fields: Coaching
• Searchable Fields: Code Set
• Searchable Fields: Community
• Searchable Fields: Comm Subscription
• Searchable Fields: Comm Subscription Channel Type
• Searchable Fields: Comm Subscription Consent
• Searchable Fields: Comm Subscription Timing
• Searchable Fields: Contact
• Searchable Fields: Contract
• Searchable Fields: Contract Line Item
• Searchable Fields: Contact Point Type Consent
• Searchable Fields: Credit Memo Inv Application
• Searchable Fields: Salesforce CRM Content
• Searchable Fields: Customer
• Searchable Fields: Custom Object
• Searchable Fields: D&B Company
• Searchable Fields: Data Use Legal Basis
• Searchable Fields: Data Use Purpose
• Searchable Fields: Discussion
• Searchable Fields: Document
• Searchable Fields: Email Message
• Searchable Fields: Engagement Channel Type
• Searchable Fields: Entitlement
• Searchable Fields: Expense
• Searchable Fields: Expense Report
• Searchable Fields: Expense Report Entry
• Searchable Fields: External Object
• Searchable Fields: Feed Comment
• Searchable Fields: Feed Post
• Searchable Fields: File
• Searchable Fields: Goal
• Searchable Fields: Gtwy Prov Payment Method Type
• Searchable Fields: Idea
• Searchable Fields: Individual
• Searchable Fields: Knowledge Article
• Searchable Fields: Lead
• Searchable Fields: List Email
• Searchable Fields: Live Chat Transcript
• Searchable Fields: Location
• Searchable Fields: Macro
• Searchable Fields: Maintenance Plan
• Searchable Fields: Metric
• Searchable Fields: Note
• Searchable Fields: Operating Hours
• Searchable Fields: Opportunity
• Searchable Fields: Order
• Searchable Fields: Partner Fund Allocation
• Searchable Fields: Partner Fund Claim
• Searchable Fields: Partner Fund Request
• Searchable Fields: Partner Marketing Budget
• Searchable Fields: Party Consent
• Searchable Fields: People
• Searchable Fields: Performance Cycle
• Searchable Fields: Person Account
• Searchable Fields: Price Book
• Searchable Fields: Product
• Searchable Fields: Product Consumed
• Searchable Fields: Product Item
• Searchable Fields: Product Request
• Searchable Fields: Product Request Line Item
• Searchable Fields: Product Transfer
• Searchable Fields: Product Warranty Term
• Searchable Fields: Provider Search Sync Log
• Searchable Fields: Question
• Searchable Fields: Quick Text
• Searchable Fields: Quote
• Searchable Fields: Report
• Searchable Fields: Resource Absence
• Searchable Fields: Return Order
• Searchable Fields: Return Order Line Item
• Searchable Fields: Reward Fund
• Searchable Fields: Reward Fund Type
• Searchable Fields: Self-Service User
• Searchable Fields: Seller
• Searchable Fields: Service Appointment
• Searchable Fields: Service Contract
• Searchable Fields: Service Crew
• Searchable Fields: Service Crew Member
• Searchable Fields: Service Resource
• Searchable Fields: Service Resource Capacity
• Searchable Fields: Service Resource Skill
• Searchable Fields: Service Territory
• Searchable Fields: Service Territory Member
• Searchable Fields: Shipment
• Searchable Fields: Skill
• Searchable Fields: Skill Requirement
• Searchable Fields: Social Persona
• Searchable Fields: Social Post
• Searchable Fields: Solution
• Searchable Fields: Survey
• Searchable Fields: Thanks Badge
• Searchable Fields: Time Sheet
• Searchable Fields: Time Sheet Entry
• Searchable Fields: Topic
• Searchable Fields: Unit Of Measure
• Searchable Fields: User
• Searchable Fields: WDC Feedback
• Searchable Fields: Work Order
• Searchable Fields: Work Order Line Item
• Searchable Fields: Work Type
• Searchable Fields: Work Type Group
• Get Instant Results in Salesforce Classic
• Search Your Feeds in Salesforce Classic
• Find Records Using Salesforce Classic Tags
• Lookup Search Glossary
• Tips for Using Standard and Enhanced Lookups
• Standard Lookups in Salesforce Classic
• Enhanced Lookups in Salesforce Classic
• Enable Enhanced Lookups
• Specify Lookup Search Filter Fields
• Enable Lookup Auto-Completion
• Lookup Search Auto-Completion
• Limitations for Search in Salesforce Classic
• Federated Search in Salesforce Classic
• Refine Search Results in Salesforce Classic

Filter Search with Rules

Filter out irrelevant results before your users see them by adding rules to a search configuration. Rules are hidden filters that define the scope of the search results to show. 

Required Editions and User Permissions

• From Setup, in the Quick Find box, enter Search Manager , and then select Search Manager .
• Click a configuration. You need a configuration to define rules. See Target a Search Configuration for a Channel .
• In the Objects list, select an object. If you already have one or more rules defined, click Add Rule . 
• Select a field, operator, and value.  To appear in the search results, a result must match every rule. For example, if your users only want to see active cases, define a rule in the Case object. Select the Status field, the Not Equals operator, and the Closed value. 
• Save your changes. 

The rule is immediately applied. 

• Considerations for Rules Keep a few considerations in mind when defining rules in a Search Manager configuration. 

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