IssueTracker

Problem encountered:  
The Cantonese language is either not getting detected or is being detected incorrectly in a **Dialogflow ES** telephony-enabled voice agent. Despite configuring the agent to support Cantonese, the system fails to recognize spoken input accurately, leading to incorrect intent matching or fallback responses.  

 What you Expected to happen:  
The Dialogflow ES agent should correctly detect and interpret Cantonese speech, accurately matching user input to the appropriate intents without misclassification or frequent fallback responses.  

### Steps to reproduce:  
1. Create a Dialogflow ES agent and enable **telephony integration**.  
2. Configure the agent to support **Cantonese (zh-HK)** as one of the supported languages.  
3. Deploy the agent and initiate a voice call using a telephony client.  
4. Speak in Cantonese and observe the intent detection results in the history.  
5. Note whether the agent correctly identifies the spoken language and maps it to the appropriate intent.  

### Other information (workarounds you have tried, documentation consulted, etc.):  
- Verified that Cantonese (zh-HK) is listed as a supported language in the agent settings.  
- Tested with different variations of Cantonese speech, including formal and colloquial phrases.  
- Cross-checked the transcription accuracy in Dialogflow Es History console.  
- Consulted Dialogflow ES documentation on language support and telephony integration.  
- Reviewed Google Cloud forums and support articles but found no definitive solution.  

Below are the attached Screenshots of Dialogflow History and the utternaces we spoke.
for 非常好(very good) it got recognized as 黑山头。(Black Mountain)
for 係 (yes) it got recognised as 嘿！(Hey!)

Would appreciate any insights or potential fixes for this issue.