Loading
Salesforce Enforces New Security Requirements in Summer 2026Read More
Build AI Solutions for Service
Set Up Service Assistant for Case

Set Up Service Assistant for Case

Complete the required setup steps for Service Assistant for Case.

Required Editions

View supported editions.
User Permissions Needed
To set up Service Assistant for Case:

Service Planner Builder permission set

AND

Agentforce Default Admin permission set

AND

Customize Application OR System Admin

Before you begin, confirm that you've completed the general setup and created an agent with subagents and instructions. See Complete General Setup.

Turn On Service AI Grounding

Complete the steps to ground Service Assistant in the case data so it drafts a case summary and begins creating a service plan.

Service Assistant uses Service AI Grounding to analyze the active case based on the fields and objects you configure in this step. By default, Subject and Description are included as required grounding sources and can't be modified. Service Assistant uses these fields to identify the issue and assign a subagent to the case. To provide richer grounding context, you can add fields and objects such as Case Email, Case Comments, and Case Feed. Service Assistant uses these additional sources to generate the issue summary and create the plan steps.

This feature references only the active case. It doesn't use your historical case data.

Important
Important Review these considerations.
  • On the Service AI Grounding Setup page, knowledge grounding is shown as a grounding source, but it's not supported in Service Assistant. Use Agentforce Data Libraries instead.
  • Encrypted fields aren't supported for grounding.
  • Only String and Text Area type fields are supported for grounding.
  • Only text from case emails, case comments, and case feed is supported. PDFs, images, and other attachments aren't used as grounding sources.
  • If you turn on case feed grounding, provide Service Assistant access to the case feed. Service Assistant has access to case emails and case comments by default.
  • The checkbox for the case feed has an info bubble that states the object is only available for grounding that uses Einstein Case Summaries. The object is supported in Service Assistant.
  • Service plans are grounded in the case data based on the ServicePlanner User's permissions rather than the individual service reps' permissions. Service reps can view information from your selected fields and objects in case summaries and service plans, even if they don't have direct access. Set your grounding configuration so that the ServicePlanner User's permissions align with the data access intended for your service reps. See Service Assistant Grounding Data Access.
  1. From Setup, in the Quick Find box, enter and select Service AI Grounding.
  2. From the Service AI Grounding Setup page, turn on the feature.
  3. From Choose Objects and Fields for Grounding, select Case and then turn on Grounding with Cases.
  4. From the Required Fields section, set these settings.
    1. In the Subject field, select Subject.
    2. In the Description field, select Description.
  5. From the Additional Fields section, select the fields that you want as a grounding source for Service Assistant.
  6. From the Additional Object Grounding Options section, select whether you want Service Assistant to use case emails, case comments, or case feed as grounding sources.
  7. Save your work and then turn on Grounding with Cases.

Here's an example configuration. After you complete the steps, go to the Flows Setup page.

Grounded Case data configuration

Then go to the Flows Setup page to configure your eligibility criteria.

Start Your Eligibility Criteria Setup

Use an autolaunched flow to set conditions that determine which cases can have a service plan.

To complete this task, we guide you through the configuration of the Check Service Plan Eligibility flow template that you can configure to your preferences. See Service Plan Eligibility Criteria.

Optionally, you can use your own flow, which must be an autolaunched flow that has one string input and one boolean output. If you use your own flow, skip this step and go to the next one.

  1. From Setup, in the Quick Find box, enter and select Flows.
  2. From Flows Setup, under All Flows, select Check Service Plan Eligibility.
  3. From the Flow Builder canvas, select the Decision element, and then click Edit Element.
  4. Under Outcome Details, in the Yes tab, delete the ineligibilityReason resource. By default, a condition is set to Priority = High. You can keep or remove the condition.
    Example: Outcome details resource removal
  5. Add any other conditions that you want the case to meet.

    Here's an example set of conditions.

    • CaseOrigin= Email
    • Escalated = False
    • OwnerId = {Queue ID}
    • AccountId = {Account number}
    Example: Service Assistant flow decision element configuration
  6. Optional: From the Manager Tab, under Text Templates, select DefaultIneligibilityReasonTextTemplate to modify the default body text.
    The text tells service reps that a case can't have a service plan because it doesn't meet the eligibility criteria. The message that the service rep sees is based on the eligibility criteria that you've set in the flow. For example, if a condition set in the Decision element isn't met, service reps get a message such as "You can't create a service plan because the case isn't part of the specified queue."
    Example: Service Assistant flow text template configuration
  7. Click Save as New Flow.
  8. In the Save As window, provide a name and optional description, and then click Save.
  9. Activate your flow.

After activating your flow, exit Flow Builder and go to the Service Assistant Setup page.

Complete Your Eligibility Criteria Setup

Complete your eligibility criteria setup by adding your configured flow to the Service Assistant Setup page.

  1. From Setup, in the Quick Find box, enter and select Service Assistant.
  2. Go to Step 4: Customize Your Experience by Object, and in the Case tab, go to the Add Eligibility Criteria section.
  3. From the Flow Label field, select your configured eligibility flow.
  4. From Input variables, select your variable.
  5. From Output Variables, set the fields for Eligibility Result Variable and Ineligibility Reason Variables.
  6. Save your work.

    Here's an example configuration of eligibility criteria set on the Service Assistant Setup page.

    Example: Service Assistant eligibility criteria setup page configuration

After you complete your eligibility criteria setup, go to the Turn on Service Assistant for Case section. We recommend that you skip the Find and Show Similar Cases, Setup Quick Actions, and Turn on Service Plan Translation sections. These features are optional, and you can set them up anytime after you complete all general setup.

Choose Your Plan Type and Turn on Service Assistant

Choose your service plan experience: guidance plans or dynamic plans.

In the Define Service Plan User Experience section, you see two columns that list the features available for both guidance plans and dynamic plans. You can use only one plan type at a time.

Define Service Plan User Experience section with guidance and dynamic plan columns

Guidance plans provide a static checklist of steps that doesn't update automatically. Guidance plans are turned on by default, and there's no toggle to indicate that they're turned on.

Dynamic plans provide a step-by-step conversational workflow where steps are created and updated in real time. For more details, see Service Plans. Turning on dynamic plans automatically turns off guidance plans.

Dynamic plans automatically include the agent chat box in the Service Assistant component. For guidance plans, turn on Chat with Service Assistant manually. We include a step to turn it on.

If you choose guidance plans, you have access to optional features: similar cases and quick actions. For setup guidance, see Extend Service Assistant for Case.

  1. From the Define Service Plan User Experience section, select a plan type.
    1. If you want to use guidance plans, no action is needed. The plan type is turned on by default.
    2. Optionally, for guidance plans, turn on Chat with Service Assistant. All other listed features are optional.
    3. If you want to use dynamic plans, turn on the plan type.
  2. At the bottom of the Case tab, turn on Service Assistant for Case.
    Service Assistant enabled on Case record page

Next, add the Service Assistant component to the Case record page.

Set Up the Service Assistant Component

To finalize your setup, add the Service Assistant component to the Case record page.

  1. From the App Launcher, select Service.
  2. From the tabs menu of the Service page, select Cases.
  3. From the Cases page, open a case record. Ideally, select a case that meets your eligibility criteria.
  4. From the record page, click the gear icon, and then select Edit Page.
  5. From the Components menu, search for and select Service Assistant, and then add the component anywhere on the canvas.
  6. Click Save, and then click Activate.
  7. Exit Lightning App Builder to go back to the Case record page.
  8. From the Case record page, confirm that you see the Service Assistant component on the page. There's no indication that a service plan is in progress. A service plan summary shows automatically and can take up to a minute to show.
    In this example, you see Start Plan, which indicates that dynamic plans are turned on. If you have guidance plans turned on, you see Draft Plan.
    Component with no progress indicator and drafted plan summary
  9. Optional: If the plan summary fails to generate or you see error messages, review the troubleshooting steps in Troubleshoot Service Assistant Error Messages.
  10. When you see a plan summary, click Draft Plan or Start Plan in the component and review the service plan.

    Review the service plan to confirm that the steps are relevant to the case details and your subagents and instructions. We provide general detail here on how to test. Generally, this step serves as a validation check that Service Assistant produces a summary plan and generates a guidance plan or starts a dynamic plan.

    Keep in mind that Service Assistant summarizes the wording used in your grounding sources, and it can combine several pieces of information in a step, including procedural information. There isn't an exact match to the wording and language used in your grounding sources.

    For more detailed testing guidance, see Test Service Assistant.

    Reviewing Guidance Plans

    For guidance plans, click Draft Plan. Guidance service plans are separated into several sections to guide case resolution: Gather Information, Work The Issue, Resolve The Issue, and Wrap Up. "Gather Information" is always included, and the other sections appear based on the amount and clarity of your subagents and instructions in relation to the case data from your Service AI Grounding configuration. The more detailed your instructions and case data, the more comprehensive the plan.

    If your plan isn't detailed enough or doesn't align with your subagents and instructions or your grounding configuration set in Service AI Grounding, review your configuration for these grounding sources. When you update subagents and instructions or the grounding fields on the case record, the Redraft Plan button shows. Click the button to draft a new plan. If you don't see the Redraft Plan button, refresh the page.

    Service Assistant can propose its own steps that aren't based on your grounding sources. For guidance plans, such steps are indicated with an asterisk (*), as shown in the first step under Work The Issue. Proposed steps show when there isn't enough information in your grounding sources.
    Example service plan

    Reviewing Dynamic Plans

    For dynamic plans, click Start Plan and work through the step-by-step workflow. Service Assistant automatically walks you through the resolution process step-by-step. It surfaces the first step and tells you what needs to be completed.

    As you work through the plan, each step is created in real time. Service Assistant reviews the current record data and does a fresh retrieval of all your grounding sources to make sure that each step is relevant to the current record context. Make sure that each step aligns with your subagent instructions and grounding sources and follows a real-world pattern of how service reps resolve the issue.

    When steps are created outside of your grounding sources, Service Assistant uses language such as "There's no information found in company documents. Here's what I suggest."

    Example dynamic service plan

After you verify that you can draft or start a service plan, go to the Permission Sets Setup page to complete permission assignments.

Give Users Access

Assign your users their specific permissions according to the provided permissions table.

When you create a Service Assistant agent, the ServicePlanner User (the agent user) is automatically assigned the Service Planner Agent User and Agentforce_Service_Assistant Permissions permission sets.

Manually assign the Data Cloud User standard permission set only if you choose to use the knowledge grounding or similar cases features.

If you turn on case feed grounding in your Service AI Grounding configuration, provide the ServicePlanner User (the agent user) access to the case feed. Service Assistant has access to case emails and case comments by default when you turn on the objects for grounding.

Persona User License Standard Permission Sets
Service Rep Salesforce
  • Service Planner User
  • Access Agentforce Default Agent
ServicePlanner User (agent user) Einstein Agent
  • Agentforce_Service_Assistant Permissions*
  • Service Planner Agent User
  • Data Cloud User**

*This is a default name provided by Agentforce. If you provided your agent a specific name in the Agent Creator, then the permission set name matches your agent name.

After you complete the general setup for Service Assistant for Case, you can set up knowledge grounding if you haven't already attached a data library to your agent. See Set Up Knowledge Grounding. Knowledge grounding requires extra permissions plus additional testing and validation to make sure that your service plans are grounded in your knowledge base.

You can also set up additional optional features specific to case. See Extend Service Assistant for Case.

 
Loading
Salesforce Help | Article