Omnichannel – Page 2 – Nishant Rana's Weblog

Configure WhatsApp channel – Omnichannel (Dynamics 365)

To configure the WhatsApp channel, we need to set up the account in the Customer Service Admin Center.

Navigate to Customer Support >> Channels >> Messaging Accounts (Manage)

Select the New Account option there

Select WhatsApp as the channel

Next, we need Account SID and Authentication token.

To get this information we need to create a Twilio Account.

https://www.twilio.com/try-twilio

Navigate to the console and copy the Account ID and Authentication token

https://www.twilio.com/console

Enter Account SID and Authentication token click on Next

Next, we need to add the WhatsApp Name and Phone number

Navigate to Messaging >> Try it out >> Send a WhatsApp message to activate the WhatsApp Sandbox.

Follow the steps there to configure the Sandbox account. (scan the QR code send the Message, and test the Business and User-Initiated message/conversation).

Click on Sandbox setting tab to get more information

Copy the number.

Add the number and click on Next

Copy the URL

Paste that URL in the When a message comes in and save.

We can see our WhatsApp account created, open the record.

We can see our number being shown as Active

With the account active time to now it is time to set up the channel/workstream / queue.

Navigate to Customer Support >> Channels >> Messaging (Manage)

Click on Add Channel and add the details

Enter channel details

We are creating a new workstream

Add the WhatsApp number added

Select the language

Specify the Behaviour (automated messages and approved templates)

Specify the user features (attachments)

Review and Finish and Create the channel.

Open the workstream and specify routing rule/fallback queue/work distribution/associate bots etc details

We will create a ruleset to route the message to the queue

We have the below route-to-queue rule created to route to the default queue which has all the omnichannel agents added to it. (In an actual scenario, we would add the conditions and create a specific Advanced Queue).

We are leaving the rest of the settings/configuration as default.

Now is the time to test.

Let us log in to the Customer Service Workspace as an agent and from the registered sandbox participant number added send a message.

We are done with our configuration.

Get all the details

Hope it helps..

Advertisements

How to – switch between Enhanced and Legacy (Default) multisession workspace in Customer Service Workspace

Update – We can use the below option – Customer Service Admin Center >> Operations >> Miscellaneous >> New and upcoming features – Multisession Layout Improvements

With the Enhanced multisession layout in Customer Service Workspace, we have different sessions open in different tabs at the top and different tabs inside each session, along with the Navigation on the left.

To revert to the old default workspace or legacy navigation (deprecated), open the developer tools in the browser.

And paste the following command in the Console tab.

Xrm.Utility.getGlobalContext().saveSettingValue(“msdyn_MultiSessionLayoutImprovements”,false)

Xrm.Utility.getGlobalContext().saveSettingValue(“msdyn_MultisessionNavigationImprovements”,false)

We can see the layout changed to the legacy one–

To enable the new enhanced layout (recommended) back, in the console window of developers tools paste the below command.

Xrm.Utility.getGlobalContext().saveSettingValue(“msdyn_MultiSessionLayoutImprovements”,true)

Hope it helps..

Advertisements

Notification template in Omnichannel Voice (Dynamics 365 Customer Service)

Below is the default notification the agent receives on incoming conversations/calls.

It is defined through the below out-of-the-box template.

Property	Description
Title	To define the title.
Icon	To define the icon.
Show Timeout	Yes / No – to hide/show the timer (timer still runs in the background)
Time (seconds)	For the Phone Call / Voice workstream the maximum value = is 150 seconds.
Auto-assign work items	Auto-assign incoming work item
Accept Button	Specify the text of the Accept Button
Reject Button	To hide or show the button
Show desktop notification	Never / When the app is in the background
Notification Fields	Specify fields to be shown in the notification using Slugs.

To make changes in the notification, we need to create a new notification template as we cannot update the box notification template.

Navigate to Agent Experience >> Workspaces >> Notification Templates (Manage)

Here we will create a new notification template to be used in place of Voice call – incoming authenticated – default template

For our custom template, we have made the following changes –

Increased the timeout value, and changed the text for Accept and Reject buttons.

Added notification fields and enabled Desktop notification.

Let us update one of our workstreams to use this custom notification template.

Navigate to Customer Support >> Workstreams – Open the workstream and open the Advanced Settings and update the Incoming Authenticated template in the Agent notifications section.

We can see the changes reflected in the Notification.

And also in the desktop notification –

Get all the details here-

https://neilparkhurst.com/2020/06/29/omnichannel-for-customer-service-notifications/

Hope it helps..

Advertisements

Fixed – Power Virtual Agents bots for voice not working (Dynamics 365 Customer Service Omnichannel)

We can configure aa PVA Bot for workstreams and when we install the voice channel demo, we can see a bot already configured for the demo workstream.

Recently in our case, the bot configured was not working and we were getting the below message on calling the workstream/voice channel configured.

“Sorry, we couldn’t serve you at this moment. Please call back later”

On removing the bot the workstream/channel was working properly.

We raised the Microsoft support ticket for the same and were suggested to create/configure a new bot instead of using the existing demo/trial one as it might give an issue because of being configured in a different environment.

On configuring a new bot the issue got fixed for us.

Hope it helps..

Advertisements

Agents not receiving calls in Omnichannel Voice – Dynamics 365 Customer Service

Recently we saw a few of our agents were not receiving the calls/notification for incoming conversations.

Apart from checking the Routing Diagnostics, we can refer to the Omnichannel Ongoing Conversation Dashboard (available for the Omnichannel Supervisor role)

In our case, we realized that the ongoing conversation was in Wrap-up status for the agent.

And also as we had a work item limit of 1 along with assignment blocking defined through the capacity profile for that agent, the agent wasn’t receiving the incoming notifications.

So here we can ask the agent to close the session correctly.

Or as a supervisor, we can force close the conversation from the Omnichannel Ongoing Conversation Dashboard.

Force Close-

Hope it helps..

Advertisements

How to – Configure Voicemail Workstream and Queue – Dynamics 365 Customer Service

When we configure the Voice demo, we can see 2 workstreams and queues created for Voicemail one for individuals other for voicemail of type group.

The Default Group Voicemail Workstream has the following intake rule defined.

And following Route to Queue Rule

Configuring Voicemail – https://nishantrana.me/2023/02/23/how-to-configure-voicemail-in-omnichannel-voice-channel-dynamics-365-customer-service/

Similarly, Default Individual Voicemail Workstream has the following intake rule

And Route to Queue rule

Now say we want the voicemail of an advanced queue (type – voice) to be routed to its corresponding advanced queue (type – record) instead of the Default Group Voicemail Queue.

Say we have the below Advanced Queue of type Voice used in the Voice Workstream–

And the below Advanced Queue – My Sample Voice Mail Queue

Now let us define the Workstream that will route the voicemail to that queue.

Select Type as Record and Record Type as Voicemail.

The intake rule checks for the Queue record in the related entity of voice mail – Missed Conversation (Conversation)

So basically any conversation or voicemail generated because of a call to My Sample Voice Queue / Workstream will be routed to its corresponding Voice Mail Queue.

Overflow handling – https://nishantrana.me/2023/03/07/understanding-overflow-handling-work-item-limit-exceeds-in-voice-channel-omnichannel-dynamics-365-customer-service/