A sales enablement team wants Conversation Intelligence to flag whenever competitor 'Northwind Traders' is mentioned during recorded calls, in addition to the built-in brand and competitor keywords already tracked. Which action correctly extends this capability?

The correct action is adding 'Northwind Traders' as a custom keyword group in Conversation Intelligence settings so it is tracked in call analytics. Conversation Intelligence is designed to be extended by adding custom keyword groups in its settings, so registering Northwind Traders there makes it a tracked term in call analytics alongside the built-in keywords, with no separate integration work required. Retraining the underlying speech-to-text model on a sample of calls that mention Northwind Traders is incorrect because it is unnecessary and disproportionate; the transcription engine already converts the spoken name to text correctly, and the gap is only in what keywords are flagged, which is a configuration issue, not a recognition issue. Creating a Power Automate flow that scans call transcripts nightly for the string 'Northwind Traders' and emails matches to managers is incorrect because it duplicates functionality Conversation Intelligence already provides natively and introduces a delay, meaning managers would learn about mentions up to a day late instead of seeing them in near-real-time call analytics. Adding 'Northwind Traders' to the product catalog so it appears as a competitor product in opportunity records is incorrect because the product catalog is used for tracking products and pricing on opportunity records, not for configuring what Conversation Intelligence listens for in call audio, so adding an entry there has no effect on call flagging. Using the native keyword group setting is the direct, purpose-built extension.