With the Dynamics 365 update late last year, I’ve seen some clients who are making timing and priority decisions for the visual update as well as what new functionality to test out. One (preview) feature that has been the center of attention for several of those conversations is the Relationship Assistant.
If you’re not already familiar, the Relationship Assistant basically provides reminders, suggestions, and insights about your relationships–based on information that you have in Dynamics 365 and Office 365. The feature uses Microsoft Azure to analyze activities and other record types to:
- Remind you about upcoming due dates / close dates
- Suggest activity if you haven’t been active with a customer or prospect
- Offer external information like stock prices or recent news (without having to go look for it)
When I first started chatting with folks about the Relationship Assistant, there was a common misconception that came up again and again: people seem to think that relationship assistant requires Server Side Sync to be enabled. While this is true for some of the relationship cards, some can be used regardless of the Server Side Sync feature. These cards fall into several categories, but only two of them (Email Cards from Exchange and Email Engagement Cards).
There is real value if you use Server Side Sync
All of that said, I’m certainly not recommending against some of the cool stuff that comes with Server Side Sync. What’s most significant here is that emails in your personal inbox can be displayed in Dynamics without the user having to physically click a “track” button. Literally, email that they may not have even seen in their inbox could be displayed in the context of an Opportunity record with that same contact.
This is the kind of feature that provides value back to users without them having to put a bunch of up-front effort in.
I’m hoping to gain a deeper understanding of how to train some of these email cards from exchange, though. Some of the cards like “Stakeholder Recommendation” that will suggest (or automatically add) a stakeholder into Dynamics if they aren’t already in the system. Being able to train this model for industry-specific keywords will make it more versatile. Maybe this is something we’ll see when it’s out of preview (I can dream, right?)
I know this isn’t a hidden feature or anything fancy like that, but it’s important for Dynamics administrators to know the tools that are available to them and their user community. While it’s not hidden, it is a Preview feature, which you’ll want to keep in mind as it doesn’t come with any official support.
Are you considering the Relationship Assistant or have you already enabled this in your organization? Share your thoughts in the comments below.
azure, customer engagement, Customer relationship management, Dynamics 365, Microsoft Dynamics, preview, relationship assistant