Channel resolver analytics in copilot
What is channel resolver?
The Channel Resolver skill enables the Moveworks Copilot to join public Slack channels and assist users with their support issues. Users can share their issues in a public channel, and the Moveworks Copilot can intercept these posts, reaching out directly to the user through DM with steps for resolution. Channel Resolver is multi-turn in nature; users can also ask follow-up questions and query for more specific details on the DM reachout. Currently, Channel Resolver is supported only on Slack, and not on other chat platforms.
The Channel Resolver can:
- Provide a summarized answer by using knowledge articles or files the user has access to.
- Send relevant forms that the user has access to.
- Share relevant access workflows available in the channel.
- File tickets for end users in two ways:
- Manual ticketing: A ticket is filed on behalf of the end user who initiated the thread when a user or an IT agent reacts with a 🎫 emoji on the thread (this is customizable).
- Automatic ticketing: A ticket is always filed for messages posted in the public Slack channel. The copilot files a ticket on behalf of the end user who started the thread and reacts with a 🎫 emoji on the thread (this is customizable).
Please refer to this documentation to understand the channel resolver experience in Copilot: https://help.moveworks.com/docs/channel-resolver-copilot
Channel resolver analytics
Moveworks also provides admin insights on channel resolver usage and details on what questions are being asked by the end users in public slack channels.
Navigate to the route section under copilot analytics to access channel resolver analytics
What are the different metrics visible on channel resolver analytics
The metrics are majorly divided into 3 buckets
- Overall channel resolver performance metrics
- Plugin performance in slack channels
- Detailed interactions table on channel interactions
The dashboard also provides functionality to filter metrics for specific channels. The dropdown menu will populate with all your channels where NGCP CR is enabled, from which a particular channel can be selected.
Summary metrics
- Channel interactions: Total number of utterances where a user has posted a message in the channel.
- Bot reach-outs: Total number of utterances where the bot has successfully reached out to the user in DM.
- Total issues resolved: Total number of utterances where the bot has reached out to the users in DM and the user has clicked on the issue resolved button in the DM reachout.
Plugin breakdown
This breakdown details which plugin the copilot used when reaching out to the user in DM. The plugins are ranked according to their usage in this metric.
This helps in understanding top plugins used in channels
Issue details (Interactions)
The issue details table deep dives into interactions recorded in the slack channels. The table covers the following attributes
This table covers only the initial interaction, which is the message sent by the user in the public Slack channel. Subsequent direct message interactions are stored in the Interactions table, accessible via the "View Interactions" button.
| Column name | Column meaning | Example values |
|---|---|---|
| Date | Date when the interaction was recorded | 2024-11-06 |
| Conversation ID | Unique identifier for the conversation. This conversation ID can be cross referenced in the interaction table to understand the follow-up questions or interactions from the end user. | E5mAMniL2qTs |
| User email | Email address of the end users. This value is obtained from the user roster. To understand the source system please verify the user mapping in moveworks setup | [email protected] |
| User interaction | User utterances in the slack channel | "My wifi is not working" |
| Copilot response | Summarized answer provided by the copilot in DM. This column only contains the initial copilot message for subsequent copilot response please refer to the interactions table | "Here are a few steps you can take to resolve your VPN access issues: 1. *Reset MFA for VPN....." |
| Plugin details | Plugins that were called & used by the LLM to find the solution and provide the summarized answer to the end users The definition of the plugin status remains the same as interactions table. Please refer this section of copilot insights to learn more. | Forms : Completed - No Results,Reset MFA : Completed - Success |
| Issue resolved | Channel resolver reachout prompts users to select if the issue is resolved or not. Please refer here to learn more on the experience This attribute indicates if the user has marked the issue as resolved or not. If the user has not interacted with buttons provided in the prompt, we will capture the value for this attribute as "false" as there is no response provided by the end user | True/ False |
| Has bot reachout | This attribute indicates if copilot reached out to the end user in DM | True/False |
| Channel name | This attribute stores the name of the channel where the user has posted the message | # it |
| User Record ID | This attribute stores the moveworks record id generated for all users. This record ID can be cross-referenced in the Ingested Users screen in moveworks setup to view more attributes on the end user | 6088985733345893014/ |
How to enable channel resolver analytics
Today enabling this dashboard is not self-servable. Please connect with your CSE or reachout to the Moveworks support team to enable this dashboard.
Updated about 1 month ago