---
schema_version: "1"
id: 1318e25ab11ee0ba20cf2b6169fe5697f9575577759bb378e80e9cdcff5bf690
title: Set Up the Summarize Case Prompt Template
collection: admin
version: current
locale: en-us
portal_url: https://docs.salesforce.com/admin/current/en-us/service/264-0-0/sp_sc_pt.md
canonical_url: https://help.salesforce.com/s/articleView?id=service.sp_sc_pt.htm&release=264.0.0&type=5
source_site: help.salesforce.com
content_type: documentation
content_hash: 7b9581008c0f82eb778694b2698ac4c55b90c32a4d525cd1548b47da8d7f0651
description: Modify the Summarize Case prompt template to include service plan information in case summaries.
products:
  - Service Cloud
  - Service Intelligence
release: "264"
---
# Set Up the Summarize Case Prompt Template

Modify the Summarize Case prompt template to include service plan information in case summaries.

### Required Editions

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

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small permission">
          <colgroup>
            <col style="width:50%">
            <col style="width:50%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="colgroup" class="slds-cell-wrap" colspan="2" style="text-align:center;vertical-align:top;" id="d87776e61">User Permissions Needed</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="User Permissions Needed" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e61 ">To set up the Summarize Case prompt template:</td>

              <td class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e61 ">
                <p>Agentforce Default Admin permission set</p>
                <p>AND</p>
                <p>Customize Application OR System
                  Admin</p>
                <p>AND</p>
                <p>Prompt Template Manager permission set </p>
                <p>AND</p>
                <p>Service Planner Builder
                  permission set </p>
                <p style="margin-bottom:0;">AND</p>
                <p style="margin-bottom:0;">Enhanced Summaries User Permission Set </p>
              </td>

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

To setup the Summarize Case Prompt Template, you must [Set Up Enahnced Sumamries for Case](https://help.salesforce.com/s/articleView?id=service.enhanced_summaries_case_setup.htm&language=en_US&type=5).

When set up, you then make a version of the standard summarize case prompt template add the `getPlanDataEnhanced` data action to the template. The data action adds:

- A description of the original issue.
- A summary of the completed steps and uncompleted steps.
- The final resolution.

If you choose not to configure the prompt template but have Enhanced Summaries configured, service reps can still draft a case summary, but it won't contain service plan information.

1. From Setup, in the Quick Find box, enter Prompt Builder, and then select **Prompt Builder**.
2. Under All Prompt Templates, select **Summarize Case**.
3. From the Prompt Builder menu, click **Save As** and then select **Save as a New Version**.
4. From the workspace, delete the preexisting text and add this text.
    
    ```
    You are a summarization assistant. Your job is to generate a clear, professional summary of a support Case and its associated Service Plan. The summary should not include any names, greetings, subject lines, or email formatting—only the body.
           
           You will be given:
           - A **Case**, which may contain one or more communications such as CaseComment, Email, LiveChatTranscript, MessagingSession, VoiceCall, or ConversationEntry.
           - A **Service Plan**, which may be generated to assist in resolving the case.
           
           ---
           
           When a **service plan** is created to help resolve a case, it contains these components:
           - `summarySteps` – A general summary of all actions taken or to be taken. Use this **only if `steps` is empty**.
           - `planStatus` – Represents the overall plan status ( `New` means not started; `InProgress` means user has interacted with some steps and the plan is in progress;`Completed` means user has marked the plan completed)
           - `issueDescription` – A brief description of the problem. Use this to frame your opening statement.
           - `steps` – An ordered list of steps intended to address the issue.
           - `stepName` – A description of the step. Do **not** copy this directly—rephrase it in a customer-friendly, action-oriented tone.
           - `stepExecutionStatus` – Status of each step (`New` means not started; `Completed` means already executed).
           - `stepOrder` – The order in which steps should be performed.
           - `isSuggestedStep` – If the existing policies and actions are not enough to create a complete plan, the reasoning engine can create and add new steps to fill in the gaps. These are called suggested steps. For each of these steps, if isSuggestedStep is true, it indicates that the steps are newly introduced and not part of the grounding data.
           ---
           
           ### Summary Output Instructions
           
           - Start by clearly **restating the issue** from `issueDescription` in a concise, neutral tone.
           - On a new line, **list all completed steps**, rephrased into simple, declarative language and maintaining their correct order.
           - On another line, **highlight the next upcoming step** (only one), if available.
           - If the `steps` array is empty, use the `summarySteps` field to summarize progress.
           - Do **not** reference raw field names or internal labels in your summary.
           - Maintain a **professional and declarative tone**, with no assumptions or speculation.
           
           ---
           
           Service Plan Input:
           {!$SalesforceDataAction:getPlanDataEnhanced.servicePlanInfo}
           
           Case Content Input:
           {!$Flow:case_summaries__GetCaseSummaryInfo.Prompt}
    ```
5. **Optional**: Edit the Summary Output Instructions section to tailor the template with your company-specific information and resources. See the customization tips section.
    
    We don’t recommend making edits to any other sections. Don’t remove or edit the Service Plan Input or Case Content Input resources.
6. Click **Save** and then click **Activate**.
7. Assign the ServicePlanner User (agent user) and your service reps these permission sets.
    1. ServicePlanner User: Enhanced Summaries User permission set.
    2. Service Reps: Prompt Template User and Enhances Summaries User permission set.

When your setup is complete, service reps can create a case summary that includes service plan information by using the Enhanced Summaries component.

Keep in mind that the Case summary states the resolution only when the case is formally closed. If the post is drafted while the case is open, the draft includes only the Case summary and issue description.

## Tips for Customizing the Summarize Case Prompt Template

The sample prompt defines Service Assistant core task and the data it uses: the Case details and service plan information. We recommend not changing this foundational portion of the template.

The most effective way to tailor the prompt template is to add your company information to the Summary Output Instructions section. Doing so makes sure the prompt template produces summaries that are aligned with your company standards, use cases, voice, and tone. Here are a few guidelines and recommendations for editing the prompt template.

<table class="slds-table slds-table_bordered slds-max-medium-table_stacked slds-m-bottom_small ">
          <colgroup>
            <col style="width:33.33333333333333%">
            <col style="width:33.33333333333333%">
            <col style="width:33.33333333333333%">
          </colgroup>
          <thead class="slds-text-title_caps ">
            <tr class="">
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d87776e259">Guideline </th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d87776e262">Details</th>
              <th scope="col" class="slds-cell-wrap" style="vertical-align:top;" id="d87776e265">Examples</th>
            </tr>
          </thead>
          <tbody>
            <tr class="">
              <td data-label="Guideline" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e259 ">Define role and tone.</td>

              <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e262 ">
                <p style="margin-bottom:0;">Specify any voice and tone guidelines unique to your company.</p>
              </td>

              <td data-label="Examples" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e265 ">
                <ul>
                  <li>“Adopt a friendly and encouraging tone.”</li>

                  <li>“Maintain a formal and technical tone throughout the summary.”</li>

                  <li>“Write as a helpful expert, making complex steps sound simple and
                    achievable.”</li>

                </ul>
              </td>

            </tr>
            <tr class="">
              <td data-label="Guideline" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e259 ">Define the summary structure.</td>

              <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e262 ">Provide a clear, step-by-step guide on how the final summary is formatted. State
                what to do and what to avoid.</td>

              <td data-label="Examples" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e265 ">
                <ul>
                  <li>“Begin with the phrase 'Here is a summary of your case and the steps we've
                    taken:'" </li>

                  <li>“Present all completed steps under a bold heading: <strong>Work Completed</strong>.”</li>

                  <li>“Do not use bullet points. Write the summary as a single, concise paragraph.”</li>

                  <li>“After listing the next step, add a sentence explaining its importance.”</li>

                </ul>
              </td>

            </tr>
            <tr class="">
              <td data-label="Guideline" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e259 ">Ground the prompt with additional resources.</td>

              <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e262 ">
                <p>In addition to the standard service plan data add Salesforce resources to the
                  prompt. These resources can include merge fields, flows, and Apex classes.</p>
                <p>With these resources, you can insert data for customer details, product
                  information, or related case history directly into your prompt template.</p>
                <p style="margin-bottom:0;"> See
                  <a href="https://help.salesforce.com/s/articleView?id=ai.prompt_builder_ground_template.htm&amp;type=5&amp;language=en_US" target="_blank">Ground Prompt Templates with Salesforce
                    Resources</a>.
                </p>
              </td>

              <td data-label="Examples" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e265 ">
                <ul>
                  <li>To include the customer’s specific product, you can add an input like:
                    <p><code>Product Information:
                      {!$Flow:case_summaries__GetCaseSummaryInfo.Product_Name__c}</code></p>
                    <p>You
                      can then add a corresponding instruction in the output section
                      like:</p>
                    <p>“Mention the product,
                      <code>{!$Flow:case_summaries__GetCaseSummaryInfo.Product_Name__c}</code>,
                      that this case relates to.”
                    </p>
                  </li>

                  <li>To make sure the summary reflects the case’s urgency, you can add an input like:
                    <p><code>{!Case.Priority}</code></p>
                    <p>You can then add a corresponding
                      instruction in the output section like:</p>
                    <p>“Always state the
                      <code>'{!Case.Priority}'</code>. ”
                    </p>
                  </li>

                </ul>
              </td>

            </tr>
            <tr class="">
              <td data-label="Guideline" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e259 ">Include company information.</td>

              <td data-label="Details" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e262 ">
                <p style="margin-bottom:0;">State any standard company policies, contact information, or additional resources
                  that must included in the summary.</p>
              </td>

              <td data-label="Examples" class="slds-cell-wrap" style="vertical-align:top;" headers="d87776e265 ">
                <ul>
                  <li>“At the end of the summary, add our standard post-case support policy: 'If you
                    have any further questions, please reply to this email or call us at
                    1-800-555-1234.”
                  </li>

                  <li>“Include a section titled 'Helpful Resources' and add a link to our public
                    knowledge base at <u>www.yourcompany.com/support</u>.”</li>

                  <li>“Conclude the entire summary with the line: 'Thank you for being a valued
                    customer.' ”</li>

                </ul>
              </td>

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