Categories for Knowledge Base FAQs
C
Clayton Elliott
I am inputting hundreds of total FAQs into one central line that we deploy for clients and it would be much easier to build and manage and improve the FAQs if they could be simply organized into sections instead of one long endless list of FAQs that currently don't even remain in the order they are inputted. In my work doc all my FAQs are in sections, so even if they just remained in the order I input them, this would allow me to easily locate them again when I need to edit / improve them. Right now, there is not rhyme or reason to how they are inputted, storied, listed, and sorted.
This should be an easy thing to build and would make the development experience waaaaaay better!
Log In
A
Arun Chandel
Currently, there is a limit of 15 knowledgebases per account. This restriction creates challenges when working with clients who offer multiple services. For example, we create a separate bot for each service, and to keep things organized, we maintain a dedicated knowledgebase for each one.
However, because of this limit, we are unable to add more knowledgebases once the cap is reached. Removing (or significantly increasing) this limit would provide much greater flexibility for agencies and businesses managing multiple service lines.
Please remove the maximum limit on knowledgebases (or raise it substantially).