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.




To define the title.


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-

Hope it helps..


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..


List Rows, Select Columns, and Lookup field – Power Automate / Dataverse

Suppose we want to retrieve the value of the source campaign lookup of the lead records.

The schema name of Source Campaign is – campaignid

To get its GUID in the Select columns of list rows we can specify it as

_campaignid_value i.e. _lookupschemaname_value

The other option is if we specify the schema name in select columns then we need to use the expand property to get the GUID as well if we want any other attribute values e.g. text/label of the lookup field.

Hope it helps..


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..


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 –

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

And the intake rule of that workstream to route to the Voicemail Queue created earlier.

Hope it helps..


Enable Sound Notifications in Omnichannel (Voice and other channels) – Dynamics 365 for Customer Service

By default, this is how the notification appears for the agent when he is logged in to the app and is available.

There is no sound notification.

However, we enable sound notification here. This can be helpful in case the app is in the background and/or the agents are working on something else.

Navigate to Agent Experience >> Workspaces >> Notification Templates (Manage) in Customer Service Admin Center.

Let us enable sound notifications.

We can specify the following – Play sound, Sound to be played, whether the notification should keep on playing till the agent responds and the volume of the notification as shown below.

Here we also need to enable the Sound settings in the browser.

For the app, select Site Settings

Specify Allow for Notifications and Sound

Let us now call again, this time the agent hears the sound notifications, until he Accepts the call and that works even if the app/ the browser is minimized.

Hope it helps..

%d bloggers like this: