Feature Requests

After clicking on the “Reply and Resolve Feedback” button, a short survey is sent to the feedback sender via email. This would help us assess whether our response effectively addressed their concern and if they were satisfied with the support provided. Also, for the Reply Only Option, an additional “Reply Only” button that allows us to respond to the sender with follow-up questions or clarifications without automatically closing the feedback thread.

The language code should be customizable or at least should consider both - and _ versions. Eg: en_US is the same as en-US or even en-us Optionally, it would be good to be able to set up custom alias.

Be able to upload a CSV file for the glossary. Keep existing function but allow users to be able to upload their own glossary.

Include restricted sections when auto-translating information. Going back and manually translating is time-consuming and unnecessary when the auto-translate feature is available for an article.

Ideally, the original article should always be created in the Default language

Customer would like to have the ability to manage who is following an article, and the ability to add Followers or remove them from a specific article

The URL consisting of country and language code must be changed according to HTML ISO. E.g. en-US instead of en_US.

We wanted to share an idea that could help improve collaboration and feedback across our knowledge base. It might be helpful to introduce a native comment section within articles, something that doesn’t rely on a third-party platform. This could allow readers to easily leave insights or clarifications where needed. As an added suggestion, perhaps this could be an optional feature controlled through a checkbox in the Content Managers access, giving editors/content creators the flexibility to enable or disable comments per article.

There needs to be some pop-up or notification when a URL for a folder or article has already been used on the knowledge base. When our content was migrated from our previous platform, many of the folders had the same URL as one of the documents in the folder. Because of this if someone clicked the folder they would be taken to that one document and all of the other documents in that folder were essentially invisible and inaccessible to our customers. There needs to be a prevention method for this and a URL should not be able to be saved if it is used elsewhere in the knowledge base.

The fact that words that appear in the glossary have a bright blue underline and lose their font settings is not ideal. It makes the articles look messy and unprofessional. The way to highlight that a word has been defined needs to be much more subtle and not ruin the design and format of the articles.