The views and opinions expressed in this blog are those solely of the author(s) and do not necessarily reflect Microsoft’s current policy, position, or branding. For official announcements and guidance on Dynamics 365 apps and services, please visit the Microsoft Dynamics 365 Blog.
Personalized Community is here!
Quickly customize your community to find the content you seek.
Choose your path Increase your proficiency with the Dynamics 365 applications that you already use and learn more about the apps that interest you. Up your game with a learning path tailored to today's Dynamics 365 masterminds and designed to prepare you for industry-recognized Microsoft certifications.
Visit Microsoft Learn
2020 Release Wave 2Discover the latest updates and new features to Dynamics 365 planned through March 2021.
Release overview guides and videos Release Plan | Preview 2020 Release Wave 2 TimelineWatch the 2020 Release Wave 1 virtual launch event
Ace your Dynamics 365 deployment with packaged services delivered by expert consultants. | Explore service offerings
Connect with the ISV success team on the latest roadmap, developer tool for AppSource certification, and ISV community engagements | ISV self-service portal
The FastTrack program is designed to help you accelerate your Dynamics 365 deployment with confidence.
FastTrack Program | Finance TechTalks | Customer Engagement TechTalks | Upcoming TechTalks
Recently I was asked to consider a requirement to route web chats within Omnichannel for Customer Service in a particular way. In this post I explain how I used a combination of Virtual Agents and skills based routing to achieve the requirements.
So the ask was, to route all chats to a group of first line or front line agents.
But if those front line guys were busy we’d want anyone available in the second line support term to pick up the chat.
Most of the time chats should be quickly answered with this approach. But what-if we are having a really busy day and all the agents are busy??? Well then routing to a Virtual Agent might be really useful so that details of the query could be captured. The “message” relating to the query should end up as a lead (or other entity) in Dynamics 365. So that this could later be queued for someone else to respond to the customer.
This was a very complex scenario. But actually one that could be typical of many real-world scenarios.
Just to make things extra complex I wanted to achieve all of this with no code!
In the video below I show how this challenge was answered using skills based routing within Omnichannel for Customer Service.
Business Applications communities