A sales team wants Conversation Intelligence to transcribe their sales calls, surface keywords, and generate call summaries. Reps place all of their sales calls through Microsoft Teams. After an administrator enables Conversation Intelligence, no call insights appear for any call the reps have made. What is the most likely missing piece of configuration?
Select an answer to reveal the explanation.
Short Explanation
Before Conversation Intelligence can tell you anything about a call, it needs something to listen to, and that only exists if the call was actually recorded, with consent turned on for the Teams calling setup. If that step never happened, there is no audio anywhere in the pipeline, so nothing downstream can produce a transcript, keywords, or a summary, no matter how well everything else is configured. It is worth ruling out the more record-management sounding explanations, like whether reps are following the right records or whether a close date field got filled in, because those live in a completely different part of the system and have nothing to do with capturing audio. Same with a dashboard not being shared, that would only hide results that already exist rather than prevent them from being generated in the first place. When insights are missing across the board rather than just missing from one view, the problem is almost always further upstream, at the point where the call itself gets recorded.
Full Explanation
The correct answer is D. Conversation Intelligence generates transcripts, keyword detection, and summaries by analyzing the audio of recorded calls; if call recording and the associated consent have not been enabled for the Teams calling flow, there is no audio for the feature to process, and no insights of any kind can be produced regardless of how the feature itself is configured on the Dynamics 365 side. Option A is incorrect because record following controls notifications about changes to a record, not whether call audio is captured or analyzed, so it has no bearing on whether insights are generated. Option B is incorrect because failing to share a dashboard would only prevent people from viewing existing insights in that particular view; it would not explain why insights fail to appear anywhere at all, including directly on the call and opportunity records. Option C is incorrect because an estimated close date is a forecasting and pipeline field with no role in whether Conversation Intelligence can transcribe and analyze a call. The root cause has to be upstream, at the point where audio is captured, which is exactly what recording and consent control.