When a conversation starts in Microsoft Omnichannel for Customer Service app the agent typically sees a notification including the ability to reject the call. Or if they miss the notification a wait timer will eventually hide the notification. That is great but what happens after the conversation is missed or rejected??
Within Dynamics 365 we can now use effort-based routing to assign conversations or records to users. Meaning from Omnichannel for Customer Service we could route case records, web chat conversations and more to agents based on effort estimate models. I will describe this new feature in this post.
I have previously blogged about the overflow capabilities in Microsoft’s Omnichannel for Customer Service. But the recent 2022 Wave 2 release has given us some additional capabilities. So, in this blog post I will approach this subject again!
A new feature is coming to the Unified Routing feature found in Microsoft’s Dynamics 365 Customer Service app …. It will allow us to route work items to agents based on a contact having one or more preferred resources. I will describe this new feature in this post.
Since the launch of Omnichannel I have often blogged about its capabilities. In this post I will create a collection of links to all of my posts concerning Omnichannel and its related technologies.
Within Microsoft’s Unified Routing for Dynamics 365 we can route work items using AI based sentiment predictions. In this post I look at how!
Microsoft’s Omnichannel for Customer Service makes use of Unified Routing to allocate (assign) work items to agents. Typically, once a conversation or record is routed to a queue, we use either “Highest capacity” or “Round Robin” logic to assign work items to the next available agent. But we can also create custom assignment methods to handle more complex scenarios, in this post I will explain how a custom rule might be used.
I have recently written a few blog posts which describe some of the features of Unified Routing with Dynamics 365. In the main those posts have focused on scenarios connected with Omnichannel for Customer Service but in this post I will explore using Unified Routing with “just” Dynamics 365 Customer Service. As we should be mindful that Unified Routing is a “stand alone” feature that can be applied to many use cases
Microsoft’s Omnichannel for Customer Service can make use of the Unified Routing option to intelligently route items to agents. In this post I will show how I configured the ability to route cases to agents using machine learning.