---
schema_version: "1"
id: b5a5414425d9150a7d082b8d34fa3f583d691f0aba9d52a19de5c05bd1396afd
title: Grounding Case Service Plans with Related Records (Optional)
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/sp_mvg.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: b2b74bc2ef977c0bbe7964d55d8ff6e0ca0d8fac20af886c6bb9d874ce929f23
description: Learn how to use Messaging Session and Voice Call records as a grounding source for Service Assistant for Case.
products:
  - Service Cloud
  - Service Intelligence
release: "264"
---
# Grounding Case Service Plans with Related Records (Optional)

Learn how to use Messaging Session and Voice Call records as a grounding source for Service Assistant for Case.

### Required Editions

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small edition">
      <colgroup>
        <col style="width:50%">
        <col style="width:50%">
      </colgroup>
      <tbody>
        <tr class="">
          <td class="slds-cell-wrap" colspan="2" style="vertical-align:top;"><a href="https://help.salesforce.com/s/articleView?id=service.messaging_editions.htm&amp;type=5&amp;language=en_US" target="_blank">View supported editions.</a></td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <a name="sp_mvg__image_scz_pgf_5cc"><!-- --></a><span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" id="sp_mvg__image_scz_pgf_5cc" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/resources-global/_corporate/images/checkmark.png" alt="Checkmark"></span> This article applies to:
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Service Assistant for Case with guidance and dynamic plans</td>

        </tr>
        <tr class="">
          <td class="slds-cell-wrap" style="vertical-align:top;">
            <span style="vertical-align:text-bottom;display:inline-block;"><img style="margin-bottom:0;" src="https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/resources-global/_corporate/images/crossmark.png" alt="X icon"></span> This article doesn't apply to:
          </td>

          <td class="slds-cell-wrap" style="vertical-align:top;">Service Assistant for Messaging and Voice</td>

        </tr>
      </tbody>
    </table>

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/images/icon_note.png)

Note This section provides reference guidance for grounding Service Assistant in related messaging and voice records. Setup steps are in [Set Up Related Record Grounding for Case (Optional)](https://help.salesforce.com/s/articleView?id=service.sp_mvg_setup.htm&release=264.0.0&type=5 "Ground service plans on messaging sessions and voice call records that are associated with the case."). All documentation assumes that you have messaging or voice configured.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/images/icon_note.png)

Note The examples show a guidance service plan grounded in a Messaging Session record. The described processing and operational behavior applies to both guidance and dynamic plans for case. In addition, the processing and operational behavior applies to related Voice Call records. There's no difference in the grounding behavior for each object or plan type.

- [Enhancing Service Plans with Related Records](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5)
- [Setting Up Service Assistant Related Record Grounding](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5)
- [Grounding Scenarios](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5)
- [Required Permissions](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5)
- [Record Grounding Data Access](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5)
- [Considerations for Related Record Grounding](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5)

## Enhancing Service Plans with Related Records

When messaging session and voice call records are attached to a case, Service Assistant analyzes the transcripts to create a case summary that details what took place in the conversation and drafts a service plan that continues from where the conversation ended.

Here's an example of how related record grounding works for a case created from a messaging session.

- A service rep and customer complete a messaging session, where the service rep identifies the customer's issue and takes initial steps (1).
- The service rep creates a case from the messaging session (2).
- When a service rep drafts a guidance plan or starts a dynamic plan, Service Assistant reviews the messaging transcript from the attached record with the case's subject, description, and any other fields included in your Service AI grounding configuration (3-4).
- Using the context from both the messaging session and the case, Service Assistant drafts a service plan that builds on the progress already made in the messaging session (5). For dynamic plans, the related record information is used as context to inform the entire plan workflow. Service Assistant references the information with your other grounding sources each time it generates a new step.

![Important](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/images/icon_important.png)

Important Service Assistant grounds only on messaging sessions with the status Ended and voice calls with the status Complete. Service Assistant can't ground on active messaging sessions or voice calls. This applies to both guidance and dynamic plans.

![Record grounding processing overview](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/support_intelligence/images/service_planner/sp_msg_record_summary_state_td2.png)

Looking closer at the example, you see how Service Assistant grounds on the related record. Service Assistant uses the record transcript (1-2) to:

- Create a case summary that outlines the completed tasks from the messaging session (3).
- Start the first step from where the messaging session left off. For example, the first step is to "Verify that Craig's documents are ready for submission" (4). Service Assistant doesn't repeat the task of informing the customer of what documents they need because this step was completed in the messaging session (A).

By grounding on the record data, Service Assistant provides more context-specific case resolution guidance for service reps.

![Note](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/images/icon_note.png)

Note Service Assistant references only the text transcript from the related records as a grounding source. Attachments, such as images or files, included in the related records aren't used as grounding sources. This applies to both guidance and dynamic plans.

![Record grounding processing analysis](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/support_intelligence/images/service_planner/sp_msg_record_summary_state_td5.png)

## Setting Up Service Assistant Related Record Grounding

To ground Service Assistant in messaging and voice records, turn on the feature from the Case tab of the Service Assistant Setup page.

![Record grounding Setup page toggle](https://sf-zdocs-cdn-prod.zoominsoftware.com/tdta-service-support_intelligence-264-0-0-production-enus/dcd06a7b-b5ab-448b-a767-4e2e90481508/support_intelligence/images/service_planner/sp_msg_voice_setup_page.png)

Then, assign the ServicePlanner User the Conversation Grounding Access custom permission set. Service reps don't require any additional permissions to see record content included in a service plan, but they do require record-level access to open and view the Messaging Session or Voice Call record. See [Required Permissions](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5) and [Record Grounding Data Access](https://help.salesforce.com/s/articleView?id=service.sp_mvg.htm&release=264.0.0&type=5) for specific permissions details.

For the exact setup steps, see [Set Up Related Record Grounding for Case (Optional)](https://help.salesforce.com/s/articleView?id=service.sp_mvg_setup.htm&release=264.0.0&type=5 "Ground service plans on messaging sessions and voice call records that are associated with the case.").

## Grounding Scenarios

When the feature is turned on, Service Assistant analyzes the transcripts of the messaging and voice records attached to a case to draft service plans in these scenarios.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:30%">
          <col style="width:30%">
          <col style="width:40%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49828e254">Scenario</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49828e257">Details</th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49828e260">Considerations</th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Scenario" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e254 ">A new case is created from a Messaging Session or Voice Call.</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e257 ">The related record is automatically attached to the case. Service Assistant
              includes the information from the related record in both the plan summary and the
              drafted service plan. The preceding examples show this scenario.</td>

            <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e260 ">
              <ul>
                <li>Service Assistant grounds only on messaging sessions with the status Ended and
                  voice calls with the status Complete. This applies to both guidance and dynamic
                  plans.</li>

                <li>We recommend closing the Messaging Session or Voice Call before you create a
                  case from the Messaging Session or Voice Call. This applies to both service plan
                  types. If the case is created before the record is closed, then the service plan
                  summary won't include data from the related record. The data is only included in
                  the drafted service plan.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Scenario" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e254 ">A Messaging Session or Voice Call record is added to an existing case that
              contains a drafted service plan.</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e257 ">The record is considered new information and the Redraft Plan button shows. If
              a service rep redrafts the plan, Service Assistant analyzes the record transcript
              and updates the plan steps with data from the transcript.</td>

            <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e260 ">
              <ul>
                <li>For guidance plans, redrafting the plan to include the related record
                  information is only available when no steps in the existing service plan are
                  marked as complete. If steps are marked as complete, the service rep deselects all completed steps to show the Redraft Plan
                  button.</li>

                <li>The data from the related record is only included in a drafted guidance
                  service plan or dynamic service plans that are in progress. The case summary
                  isn't updated to include the related record information.</li>

                <li>The case summary only includes data from the related record if the record is
                  attached at the time the case is created. When the case record page is first
                  opened, the related record data is included in the summary. If the summary is
                  drafted before the record is attached, the case summary doesn't contain data
                  from the record. In this scenario, only the drafted service plan contains data
                  from the related record. This behavior applies to both guidance and dynamic
                  plans.</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Scenario" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e254 ">A messaging or voice recording is added to a case prior to turning messaging
              and voice record grounding from the Setup page <strong>and</strong> the case has an existing
              case summary or a drafted service plan.</td>

            <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e257 ">
              <p>Grounding on the record depends on the state of the service plan. </p>
              <ul>
                <li>When a case summary exists and a service plan isn't yet drafted, the related
                  record information is only included in the drafted service plan after the
                  service rep clicks Draft Plan.</li>

                <li>If a service plan is already drafted, the record is considered new information
                  and the Redraft Plan button shows. When the plan is redrafted, the related
                  record information is incorporated into the steps of the new service plan.</li>

              </ul>
            </td>

            <td data-label="Considerations" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e260 ">
              <ul>
                <li>For guidance plans, redrafting the plan to include the related record
                  information is only available when no steps in the existing service plan are
                  marked as complete. If steps are marked as complete, the service rep deselects all completed steps to show the Redraft Plan
                  button.</li>

                <li>For dynamic plans, the information is included in the plan steps. Service
                  Assistant references the information when each step is created. The case summary
                  isn't updated.</li>

              </ul>
            </td>

          </tr>
        </tbody>
      </table>

## Required Permissions

To draft and view service plans that contain information from messaging or voice records, the listed permissions are required. The permissions are specific to the use of this feature and are in addition to all mandatory permissions listed in [Permissions and Licensing for Service Assistant](https://help.salesforce.com/s/articleView?id=service.sp_permissions.htm&type=5&language=en_US).

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
        <colgroup>
          <col style="width:33.4%">
          <col style="width:20%">
          <col style="width:46.6%">
        </colgroup>
        <thead class="slds-text-title_caps ">
          <tr class="">
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49828e373">Persona </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49828e376">User License </th>
            <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d49828e379">Permissions </th>
          </tr>
        </thead>
        <tbody>
          <tr class="">
            <td data-label="Persona" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e373 ">Service Assistant Admin</td>

            <td data-label="User License" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e376 ">Salesforce</td>

            <td data-label="Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e379 ">
              <p>Service Planner Builder permission set.</p>
              <p style="margin-bottom:0;">Admins require only the Service Planner Builder permission set to turn on
                Messaging Session or Voice Call record grounding on the Service Assistant Setup
                page.</p>
            </td>

          </tr>
          <tr class="">
            <td data-label="Persona" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e373 ">ServicePlanner User (agent user)</td>

            <td data-label="User License" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e376 ">
              <p style="margin-bottom:0;">Einstein Agent</p>
            </td>

            <td data-label="Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e379 ">
              <p>Service Assistant requires a custom permission set to access the transcripts of
                messaging and voice records attached to a case for incorporation into the service
                plan.</p>
              <p>Recommended custom permission set name: Conversation Grounding Access</p>
              <p>Permissions to include:</p>
              <ul>
                <li>App Permission: Access Conversation Entries, View All Voice and Video
                  Calls</li>

                <li>Messaging Sessions Object Permissions: Read, View All Fields</li>

              </ul>
            </td>

          </tr>
          <tr class="">
            <td data-label="Persona" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e373 ">Service Rep</td>

            <td data-label="User License" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e376 ">Salesforce</td>

            <td data-label="Permissions" class="slds-cell-wrap" style="vertical-align:top;" headers="d49828e379 ">
              <p style="margin-bottom:0;">None. Conversation data from a related record attached to a case is always
                included in service plans because its incorporation is determined by the
                ServicePlanner User's permissions. See the next section.</p>
            </td>

          </tr>
        </tbody>
      </table>

## Record Grounding Data Access

When using Messaging Session and Voice Call records as a grounding source, the addition of the record information into the service plan relies on the ServicePlanner User's permissions. Therefore, the service plan can contain information from the related record that the service rep can't access.

Using the ServicePlanner User's permissions makes sure that all relevant messaging and voice record data is included, resulting in the most detailed service plan possible. For more details on plan creation using the ServicePlanner User's permissions, see [Grounding Data Access](https://help.salesforce.com/s/articleView?id=service.sp_ground_data.htm&type=5&language=en_US).

Opening and viewing the Messaging Session or Voice Call record from the case still adheres to your organization's sharing rules. Service reps need record-level access to open and view the records attached to the case.

Generally, we recommend configuring the ServicePlanner User's permissions to align with the data access and sharing rules required for your service reps.

## Considerations for Related Record Grounding

Here are a few details for grounding Service Assistant in messaging and voice records.

Supported Records for Grounding

- Messaging Sessions and Voice Calls are the only non-case related records supported for grounding.
- Service Assistant grounds on messaging and voice records created from all supported messaging channels and voice telephony models. See [Messaging Channels](https://help.salesforce.com/s/articleView?id=service.support_channels.htm&type=5&language=en_US) and [Voice Telephony Models](https://help.salesforce.com/s/articleView?id=service.voice_telephony_models.htm&type=5&language=en_US).
- A Messaging Session record needs the status Ended to be used as a grounding source.
- A Voice Call record needs the status Completed to be used as a grounding source.
- Adding multiple Messaging Sessions or Voice Call records to a case for grounding is supported.
- Adding both a Messaging Session and Voice Call record to a case for grounding is supported.
- Service Assistant processes the full transcript of a Messaging Session or Voice Call record. There's no limit on the number of conversation entries used for grounding.

Grounding Limitations

- Service Assistant references only the text transcript from the related records as a grounding source.
- Attachments (such as images or files) included in the related records aren't used as grounding sources.

#### See Also

- [_Salesforce Help_:Set Up Related Record Grounding (Optional)](https://help.salesforce.com/s/articleView?id=service.sp_mvg_setup.htm&language=en_US)
- [_Salesforce Help_: Set Up Related Record Grounding (Optional)](https://help.salesforce.com/s/articleView?id=service.sp_mvg_setup.htm&language=en_US)