Manage historical analytics reports in Customer Service
You can configure Customer Service historical analytics to give your service managers a combination of BI analytics and AI insights for their organization. The reports use natural language understanding to automatically detect the language used in your support cases and group related support cases into topics.
By default, the Customer Service historical analytics reports are enabled for the System Administrator and CSR Manager roles. To configure other user roles to access analytics and dashboards, see Configure user access to analytics and dashboards.
The historical reports include:
After you enable the reports, you can access them in one of the following ways:
In Customer Service workspace, select the hamburger menu, and then select Customer Service historical analytics in the site map.
In Customer Service Hub, in Service, in the site map, select Customer Service historical analytics.
Manage Customer Service historical analytics reports
Use the Customer Service admin center app to enable or disable the reports.
In the site map, select Insights in Operations. The Insights page appears.
For Customer Service historical analytics, select Manage.
On the Customer Service historical analytics page, set the Enable Customer Service historical analytics report toggle to On to enable the reports or set the toggle to Off to disable the reports.
Select Save or Save and Close.
This configuration also enables AI-discovered topics from cases with default settings.
Enable historical analytics for unified routing
Use the Customer Service admin center app to enable or disable the reports. The metrics are available in the report after 24 hours.
Important
Unified routing must be enabled to enable historical analytics for unified routing. More information: Provision unified routing for Customer Service
In the site map, select Insights in Operations. The Insights page appears.
For Customer Service historical analytics, select Manage. The Customer Service historical analytics page is displayed.
Select the Add historical analytics for unified routing check box.
Select Save and Close.
Enable historical analytics for Copilot
Customer Service historical analytics must be enabled and you must opt in to the Copilot help pane and Copilot summaries to turn on analytics for Copilot.
In the Customer Service admin center, go to Insights, and on the page that appears, select Manage for Customer Service historical analytics.
On the Customer Service historical analytics page, select the Add historical analytics for Copilot checkbox, and then save the changes.
The command bar displays a message that your reports are being provisioned and it might take up to 24 hours for the process to complete.
View Customer Service historical analytics reports
If you customized the Customer Service workspace app, you must complete the following steps to be able to view the reports.
- On the Customer Service workspace app tile, select the ellipsis for More Options, and then select Open in App Designer.
- Select New.
- On the New page dialog, select Dataverse Table for Customer Service historical analytics, and then select Next.
- To add a Dataverse table, select the Select existing table option, and then select Customer Service historical analytics.
- Select Show in navigation, and then select Add.
- From Navigation, select Customer Service historical analytics, and then select Settings.
- Enter the following information:
- Title: Customer Service historical analytics
- Icon: Select Use web resource.
- Select icon: msdyn_/Analytics/imgs/CustomerServiceInsights.svg
- ID: CSHistoricalAnalyticsSubArea
- Select Advanced Settings, and then select the following checkboxes:
- SKU: All, On premise, Live, and SPLA.
- Client: Web.
- Select Save, and then select Publish.
See also
Introduction to Customer Service analytics and insights
Dashboard overview
Knowledge search analytics
Historical analytics for unified routing in Customer Service
View copilot analytics report
Configure user security to resources in an environment
How access to a record is determined
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