Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Applies to: Dynamics 365 Contact Center—standalone and Dynamics 365 Customer Service only
Note
Copilot Studio bot is renamed as Copilot agent (agent or AI agent). Human agent is now renamed as customer service representative (service representative or representative). You might come across references to the old and new terms while we update the product UI, documentation, and training content.
You can configure Omnichannel 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 conversations and to group related conversations into topics.
By default, the Omnichannel historical analytics reports are enabled for the System Administrator, Omnichannel Administrator, Omnichannel Supervisor, and CSR Manager roles. To configure other user roles to access analytics and dashboards, see Configure user access to analytics and dashboards. The historical analytics reports include:
Note
The reports retain their current state even when you switch session tabs. However, if you customized the Copilot Service workspace app, complete the steps provided here to keep the report state.
Manage Omnichannel historical analytics reports
Use the Copilot Service admin center or Customer Service Hub app to enable or disable the Omnichannel historical analytics reports.
- In the site map of Copilot Service admin center, select Insights in Operations. The Insights page appears.
- In the Omnichannel historical analytics section, select Manage. The Omnichannel historical analytics page is displayed.
- Set the Enable Omnichannel historical analytics report toggle to On to enable the reports or set the toggle to No to disable the reports.
- Select Save or Save and Close.
This configuration enables AI-discovered topics from conversations with default settings.
Enable historical analytics for Copilot agents in Omnichannel for Customer Service
In Copilot Service admin center, you can enable the historical analytics for AI agents (agents) to give your service managers integrated reports that combine Copilot agents and Omnichannel conversation metrics.
Important
Omnichannel historical analytics must be enabled before you can enable historical analytics for agents. This feature is available only if Copilot agents are integrated with Omnichannel for Customer Service.
- If you select this option, the Omnichannel Summary and Bot dashboards appear as options in the dashboard filter for the Omnichannel historical analytics report. The Bot dashboard shows metrics specific to the Copilot agent.
- If no Copilot agents are integrated with the application or you didn't select this option, then the Bot dashboard displays the key performance indicators (KPIs) and charts for all agents.
Enable historical analytics for agents in Omnichannel for Customer Service
- In the site map, select Insights in Operations. The Insights page appears.
- In the Omnichannel historical analytics section, select Manage. The Omnichannel historical analytics page appears.
- Select the Add historical analytics for bot checkbox.
- Select Save or Save and Close.
Enable historical analytics for voice in Omnichannel for Customer Service
You can enable the historical analytics dashboard for voice in the Copilot Service admin center app. The metrics are available in the dashboard 24 hours after you enable historical analytics.
- In the site map, select Insights in Operations. The Insights page appears.
- In the Omnichannel historical analytics section, select Manage.
- The Omnichannel historical analytics page appears. Select the Add historical analytics for voice checkbox.
- Select Save or Save and Close.
In the Omnichannel historical analytics report, use the dashboard filter to go to the Voice dashboard.
Enable historical analytics for voicemail in Omnichannel for Customer Service
You can enable the historical analytics dashboard for voicemail in the Copilot Service admin center app. The metrics are available in the dashboard after 24 hours of enabling it.
- In Copilot Service admin center, select Insights in Operations.
- For Omnichannel historical analytics, select Manage.
- Select Add historical analytics for voicemail.
Enable omnichannel historical analytics for proactive outbound engagements
You can get insights about your contact center performance for proactive outbound engagements. The Proactive Outbound dashboard is available in Dynamics 365 Contact Center only.
- In the site map, select Insights in Operations. The Insights page appears.
- In the Omnichannel historical analytics section, select Manage.
- The Omnichannel historical analytics page appears. Select the Add historical analytics for proactive outbound checkbox.
- Select Save or Save and Close.
View Omnichannel historical analytics reports
If you customized the Copilot Service workspace app, you must complete the following steps to be able to view the reports.
- On the Copilot 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 Omnichannel historical analytics, and then select Next.
- To add a Dataverse table, select the Select existing table option, and then select Omnichannel historical analytics.
- Select Show in navigation, and then select Add.
- From Navigation, select Omnichannel historical analytics, and then select Settings.
- Enter the following information:
- Title: Omnichannel historical analytics
- Icon: Select Use web resource.
- Select icon: msdyn_/Analytics/imgs/OmnichannelReportIcon.svg
- ID: OCReportsSubArea
- Select Advanced Settings, and then select the following checkboxes:
- SKU: All, On premise, Live, and SPLA.
- Client: Web.
- Outlook shortcut: Offline availability.
- Select Save, and then select Publish.
Related information
Dashboard Overview
Configure user security to resources in an environment
How access to a record is determined