A sales enablement team wants to extend Conversation Intelligence so that call sentiment scores and keyword-trigger counts feed a custom Power BI dashboard used for quarterly coaching reviews, updated automatically as new calls are analyzed. Which approach should the consultant use to extend Conversation Intelligence for this purpose?
Select an answer to reveal the explanation.
Short Explanation
You should use the Conversation Intelligence Dataverse tables, such as call insights records, as a Power BI data source so sentiment scores and keyword counts refresh automatically as new calls are analyzed. You don't need to recreate the analysis or export it by hand; that just adds delay, errors, and duplicate work.
Full Explanation
The right approach is to use the Conversation Intelligence Dataverse tables, such as call insights records, as a data source in a Power BI dataflow or report connected to Dataverse. Conversation Intelligence writes call insights, including sentiment scores and keyword-trigger counts, into Dataverse tables, and those tables can be used as a source for a Power BI dataflow or report so the dashboard refreshes automatically as new calls are processed. This satisfies the requirement for an automatically updating coaching dashboard without duplicating any analysis work Conversation Intelligence already performs. Manually exporting each call's insights to a spreadsheet after every recorded call and uploading it to Power BI weekly is incorrect because a manual, weekly export process is neither automatic nor timely, and it introduces human error and delay that conflict with the stated goal. Configuring Conversation Intelligence's built-in reports to embed directly inside Power BI without any additional configuration, since both are Microsoft products, is incorrect because there is no zero-configuration embedding between Conversation Intelligence and Power BI simply because both are Microsoft products; a real data connection still has to be built and configured. Creating a custom Copilot Studio agent that reads call recordings and re-analyzes them separately to produce sentiment scores for the dashboard is incorrect because building a separate Copilot Studio agent to re-analyze call recordings duplicates work Conversation Intelligence has already done, risks producing sentiment scores that disagree with the native ones, and adds unnecessary cost and complexity instead of reusing existing insights.