🚧

This covers Moveworks Copilot

Moveworks Copilot is the latest conversational experience

Overview

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:

1. Provide a summarized answer by using knowledge articles or files the user has access to.
2. Send relevant forms that the user has access to.
3. Share relevant access workflows available in the channel.
4. 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).

How does Channel Resolver work?

The Channel Resolver follows these steps to understand the user's issue and then reaches out to the user directly via a message.

1. Understanding the request

   Moveworks Copilot uses its reasoning engine to understand the user request and identify which plugin can help the user with the issue. If the Moveworks Copilot is not able to find the resolution in these plugins it will not reach out to the end user through a direct message. Channel resolver only allows the following plugins to operate in a public slack channel.

   Plugin name	Plugin definition
   Knowledge Base	Search in the knowledge base and FAQs to find relevant information and summarize the answer
   Forms	Find forms and let users fill them out in the bot
   Create Group	Create a new distribution list in chat
   Add User to Group	Add one or multiple people to a distribution list
   Remove User from Group	Remove one or multiple people from a distribution list
   Owner of Group	Find the owner of a distribution list
   Group Membership Status	Check whether a user is in the distribution list
   Unlock Account	Unlock account for the user
   Reset Password	Reset password for the user
   Reset MFA	Reset MFA for the user
   Grant Software Access	Grant access to a software

2. Access control

   Moveworks Copilot also checks the user access before reaching out with a summarized answer and also check if the users role and attributes allows them to access the requested workflow.

3. Direct message reachout

   Moveworks Copilot reaches out to the user through a direct message and provides the resolution step to the end user. Once the message has been intercepted in the channel, Movework Copilot will react with an 👀 emoji which indicates Moveworks Copilot has provided some resolution in the direct message.

   In Channel

   

   In DM

   

4. Posting back the resolution in channel thread
   Moveworks Copilot updates the Slack thread with relevant messages and emoji reactions to indicate if the issue is resolved or unresolved in the direct message. Users can respond in two different ways during the DM outreach:

   1. For summarized answers (knowledge plugin), the outreach includes feedback buttons that users can click to update the status in the thread.
   2. For action plugins like Forms, Access Software, Access Account, etc., the status in the Slack thread is updated based on user actions. For example, if the user completes the access software workflow, the Moveworks Copilot marks the thread as resolved.

   Moveworks Copilot posts back with the following message in case if the issue was resolved for the user or the user needs more help in the slack thread

   Issue is resolved in direct message

   

   Issue is not resolved in direct message

   

5. Ticket creation on channel thread

   Moveworks Copilot supports ticket creation based on the following two criteria's

   1. If the user (or) agent has indicated to file a ticket by using a 🎫 emoji on the channel thread
   2. Automated ticket filing on every user question on the slack channel. In this case Moveworks Copilot will always file a ticket on slack message and adds a 🎫 emoji

   In both of the cases the ticket ID is shared on the slack channel so the agents in the channel are also aware of the ticket filed by the end user.

   

   Users are also able to file a ticket in the direct message through smart handoff. Moveworks Copilot will also post back in the slack thread if the user has not found the resolution helpful and filed a ticket regarding the issue. Copilot will also share the ticket number in that case.

   
   

6. Ticket syncing

   Moveworks Copilot synchronizes ticket comments and status updates from the ticketing system to the Slack thread, and posts messages from Slack as comments in the created ticket. This feature helps end users stay informed about ticket activity and enables agents to monitor conversations in the Slack thread.

   There is web-hook configuration required to enable ticket syncing from the end system. Moveworks currently supports the following integrations for ticket syncing

   1. Fresh-service : link
   2. Zendesk : link
   3. Jira cloud/server : link

Please note the ticket syncing only works for the tickets that are created in the channel(manual or automatic). If a users has filed a ticket through smart handoff in the direct message we don't support ticket syncing on those tickets

Configurations

Moveworks Copilot needs to be added into the slack channel as an integration where channel resolver needs to be enabled. Refer to this guide for setting up Channel Resolver in Moveworks Copilot: link.

If your Slack channels are already set up in the classic version of Channel Resolver, there's no need to set them up again.

FAQ

Can Channel Resolver support multiple slack channels ?

Yes, Channel Resolver can be configured in multiple channels with a difference in behavior where you can enable or disable certain skills

Can we use custom emoji's with Moveworks Copilot ?

Yes channel resolver can use custom emoji's as well. Please refer to this section of the emoji customization to learn more on adding custom emoji for each use-case : link

Can Moveworks Copilot control knowledge that is served in the slack channel ?

Moveworks Copilot controls the sharing of knowledge articles and DM reach out based on the user access. We don't support capability of only service knowledge from a limited pool of resources.

However, Moveworks allows turning off certain domains so the Moveworks Copilot won't respond to questions from those disabled domains.

Which plugins are supported through channel resolver?

Moveworks Copilot currently accommodates plugins for Knowledge (including Internal knowledge, Files, FAQ, and External knowledge), Forms & Access plugins within the Channel Resolver. It is capable of handling the ticketing plugin for both manual and automatic ticket submissions. However, it does not support GPT-based plugins and Creator Studio plugins within the Channel Resolver.