Hi Chatling Team,
We are developing a custom chat frontend using your API v2 to adhere to strict WCAG accessibility standards, as the native widget is not yet compliant.
We are facing two major issues:
1. Technical Blocker (API v2): We are unable to trigger a Flow (Playbook) via the API. Even when sending specific trigger keywords associated with an Intent, the API ignores the Flow logic and returns a generic Knowledge Base response.
Question: Is there a specific parameter or method to force the API to bypass the KB and execute a structured Flow?
2. Accessibility Roadmap: We raised the issue regarding the native widget's accessibility a few months ago, and it was added to your roadmap.
Question: What is the current ETA for full accessibility support in the native widget?
Looking forward to your quick guidance.
Best regards,
Koby
Please authenticate to join the conversation.
Completed
π Bug Reports
About 1 month ago

koby
Get notified by email when there are changes.
Completed
π Bug Reports
About 1 month ago

koby
Get notified by email when there are changes.