What to do when the answer is too long for one Output Node – Cognigy.AI Help Center
What to do when the answer is too long for one Output Node
Cognigy Support
April 26, 2022
In projects it happens from time to time that answers are defined that are longer than usual.
Long answers can scare users and lead to poorer information acquisition.
On the other hand, users also want all relevant information on a topic when they ask for it.
In endpoints like Webchat, it is quite possible to combine both points by using HTML.
Create a response that is small and manageable at first glance, but folds out so interested users can get all the relevant information.
How this can look like:
What to do when the answer is too long for one Output Node
Are you interested?
<details><summary>press for more Infos!</summary><span>This text ist hidden behind the "more Infos!" option. The first look is good, but user can get all these Infos, that are provided here. </span></details>
Best Practices
- Cognigy.AI Bot Building Checklist
- Cognigy’s NLU Execution Order Explained
- Difference Between Go To and Execute Node
- Explaining No-Translation Markers
- Best Practices: Testing your Virtual Agents with Playbooks
- Voice: Strategies for Hard to Understand Phrases
- Universal skills for Chat and Voice
- Avoid customer frustration
- Get the conversation going
- Best Practices: Building a Deployment Pipeline for Cognigy AI Agents