A consultant enables Conversation Intelligence for a European sales team and configures the default language for the organization as English United States. Reps in the Paris office place calls with prospects in French through the Dynamics 365 App for Outlook and Teams dialer that Conversation Intelligence already captures successfully. Recordings appear in the timeline, but transcripts and keyword insights never generate for the Paris team's calls. What is the most likely explanation?

The language-configuration explanation is the one that fits. Conversation Intelligence transcribes and analyzes calls only in the language or languages configured for the organization or the individual seller. Because the organization is set to English United States and no French language has been added, the Paris calls will keep recording successfully, since recording is language-agnostic, but they will never produce a transcript or keyword insights. The licensing claim is incorrect because transcript language support is not tied to Enterprise versus Premium licensing; both tiers support Conversation Intelligence the same way once the feature is licensed, and language coverage is a separate configuration. The contact-language-field claim is incorrect because Conversation Intelligence does not read a language field on the contact record to decide how to transcribe a call; it relies on the language settings configured for the organization or user, not contact metadata. The per-country Azure Cognitive Services claim is incorrect because Conversation Intelligence does not require the consultant or client to provision separate Azure Cognitive Services resources per country; language support is managed within Conversation Intelligence's own configuration, not through external infrastructure the customer must stand up. The fix is to add French to the supported languages in the Conversation Intelligence settings, either at the organization level or for the Paris sellers specifically.