A consultant is scoping a Dynamics 365 Sales implementation for a client that wants relationship health scores, who-knows-whom connection mapping, and talking points generated automatically from sellers' email and calendar activity. The client currently holds only base Dynamics 365 Sales licenses for its sellers. What should the consultant tell the client about delivering these capabilities?
Select an answer to reveal the explanation.
Short Explanation
When a client asks for relationship health scores, who-knows-whom mapping, and auto-generated talking points, that's the premium relationship analytics and Sales Insights feature set. You need to move the affected sellers to Dynamics 365 Sales Premium, because base licenses don't include it. Don't look for a settings toggle, Power BI capacity, or custom flow to replace a native premium capability.
Full Explanation
The correct answer is the licensing upgrade: relationship health scores, connection insights, and auto-generated talking points are part of the relationship analytics and Sales Insights capability set bundled into Dynamics 365 Sales Premium; sellers who need them must be licensed at that tier, so the consultant should scope a licensing upgrade for the affected users rather than expect them on the base license. The claim that these capabilities are included with every Dynamics 365 Sales license at no extra cost is incorrect because these are premium capabilities gated by licensing, not hidden settings available to every seller for free; an administrator cannot simply switch them on for base-licensed users. The claim that these capabilities require a separate Power BI Premium capacity subscription is incorrect because it confuses the feature with Power BI, a separate analytics product; relationship analytics runs natively inside Dynamics 365 Sales and does not depend on a Power BI Premium capacity to function. The claim that these capabilities cannot be delivered through native Dynamics 365 Sales features and would require a custom Power Automate flow built from scratch is incorrect because it overstates the engineering effort needed, since these are native, supported features of the premium license rather than something that must be reconstructed with custom automation. Advising the client to license the right sellers at the premium tier is both the accurate and the lowest-effort path to the outcome they are describing.