In the second of our two-part Microsoft Power Virtual Agents series, we examine the difference between Chatbots and Intelligent Chatbots, and how AI can elevate chatbot capabilities and improve user experience.
Workflows are the cornerstone of process automation in Dynamics 365. They are powerful, easy to use, and are shockingly flexible. Workflows streamline work, allowing your employees to spend more time doing the work you've hired them for, and less time clicking around an application.
For instance, say you have leads coming in from a webform that are then assigned to individual reps, and the first thing you want your reps to do is make a phone call. With Workflows, it's easy to autogenerate a phone call record so that when the rep logs in, they can just grab the phone call right away.
Wonderful! And let's take a look at that phone call, just to make sure that everything is in order…
Alright, let's go ahead and set a Lead to status new and fire out our workflow!
So what happened? Why won't the workflow fire?
Phone calls are very particular about how they are set up, with specific fields needing specific values put into them. "Invalid Party Object Type 9" means that one of those fields is getting a Team rather than an acceptable value. So let's take a closer look at how we set up that phone call record.
Ah ha! When leads are coming in, they are owned by a Team, and when this workflow is activated, the team still owns the record. But teams cannot make phone calls! So what can we do about this? There are two easy solutions. The first is procedural – set the workflow to fire only after you assign records. But there's a second, more automated way. Change the workflow so that it only populates the "Call From" field if the owner of the lead is a user!
And just like that, the automation works and your reps get their first phone call generated without a hitch.
Want to learn more about workflows? Check out these recent blogs: