Status Update
No update yet.
Comments
pu...@google.com
ha...@terralogic.com
ar...@google.com
Hi,
Could you please provide a detailed step to reproduce any documentation which you followed and screenshot of the issue also ?
ha...@terralogic.com
This functionality is critical for our clients, and resolving this issue is a high priority. Could you please provide an alternative solution or additional guidance? Any help would be greatly appreciated.
In the chat interface, everything is working fine. However, in the voice interface, only numbers are being captured correctly. Other entities like sys.any, sys.person, sys.address, and sys.email are not functioning as expected. Could you please help address this issue?
ha...@terralogic.com
ar...@google.com
Hello,
Thank you for reaching out to us with your request.
We have duly noted your feedback and will thoroughly validate it. While we cannot provide an estimated time of implementation or guarantee the fulfillment of the issue, please be assured that your input is highly valued. Your feedback enables us to enhance our products and services.
To ensure a faster resolution and dedicated support for your issue, I kindly request you to file a support ticket by clicking
We appreciate your continued trust and support in improving our Google Cloud Platform products. In case you want to report a new issue, Please do not hesitate to create a new issue on the
Once again, we sincerely appreciate your valuable feedback; Thank you for your understanding and collaboration.
Description
-- Issue description (short summary) --
When using the phone gateway in Dialogflow CX, it struggles to recognize names and emails accurately, even with the sys.person and sys.email system entities.
-- Steps to reproduce the issue (detailed description) --
1. I tried to use call compansion but it has to the start of the conversation. My client is not having
2.
3.
-- Expected behavior --
When a user says it should understand correctly.
-- Actual behavior --
the system is not understanding then its looped in the same.
-- Workarounds (if any) --
-- Documentation consulted --
-- Other information --