Manage fields Copilot uses for case summaries
You can modify the source case fields that Copilot uses to generate summaries or draft emails, thereby improving the context and accuracy of the results. You can also select a custom field that Copilot should use to generate responses.
Modify the fields used to generate case summaries
Copilot uses the following fields to generate case summaries:
- Customer
- Case Title
- Case Type
- Subject
- Case Description
- Product
- Priority
- Case Notes
- Email Content
- Conversation Summary
In Customer Service admin center, perform the following steps to map your preferred fields:
- Use one of the following navigation options:
- Agent Experience > Productivity > Summaries
- Operations > Insights > Summaries
- In Summaries, for Case summaries, select Manage Data Attributes. The Data Attributes pane shows the attributes that Copilot uses to generate a summary.
- Complete the following steps.
- Select the attributes that Copilot uses to generate case summaries. Copilot considers only the selected fields when it's generating a summary.
Note
- You can set Case Notes to a custom entity that is related to the Case table.
- Ensure that the Customer Service Representative or any custom role has Read permissions configured for the related entities. Otherwise, Copilot won't be able to generate a summary.
- Make sure your agents have
prvReadProduct
privilege to generate a summary that contains the Product field. - You can't modify the Email Content and Conversation Summary values that Copilot uses to generate case summaries.
- To change the default attributes, select a different source table and column. For the Customer attribute, for example, you might select Account as the source table and Account Name as the column. When Copilot generates a summary, it uses the value in the Account Name column of the Account table as the customer contact instead of Case and Contact.
- Select Save and Close.
- Select Save.
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for