Please tell us what we can do to make Featurebase the best product for you.
Planned
Automatic Help Center updates with AI
Help center should automatically keep itself up to date with smart suggestions based on your: support conversations changelogs roadmap
Planned
Export Help Articles
It would be preferrable if we had the capability to export our help section content to maintain our own backup of this content.
Planned
Add one article to multiple collections
Often, 1 article should be ideally shown in multiple relevant collections (linear example):
In Progress
More Help Center layouts / templates
Would be great to have more possible layouts for the help center.
Planned
Search results for Help Center analytics
In Help Center analytics, show what keywords users search, their results, how many didn’t show anything, etc. Basically, everything that Intercom shows 👇
Planned
Bulk actions in help center
Select multiple Help Center articles and update them in one action. Bulk actions should include: Change visibility and access settings, including Everyone, Team members, and segments Move articles to a collection Publish, unpublish, or delete articles
In Progress
Manage article access and unpublishing through API and MCP
Control Help Center article visibility and audience access through the API and MCP, and unpublish live articles without deleting them. This would let teams manage access and take outdated content offline from their own tools or AI workflows.
Git sync for Help Center and API docs
Keep your guides and API documentation in Git, with changes synced to Featurebase. This would let your team maintain docs alongside your code, use AI coding tools to update them, and avoid copying changes between tools. Connect your repository. Choose a GitHub repository, branch, and docs folder, including private repositories. Sync your documentation. Bring across Markdown guides, API definitions, navigation, and images. Edit in either place. Keep changes made in Featurebase and Git consistent through commits and pull requests. Review before publishing. Preview changes before they go live, with clear sync status and errors when something needs attention. Handle conflicts safely. Flag conflicting edits instead of silently overwriting changes, and respect branch protection rules. GitHub would be the initial focus. Related requests include GitLab support, syncing multiple repositories, and choosing which files to include.
When changing articles parent collection - Display available collections sorted alphabetically
Currently, if you have many collections, then it seems quite chaotic. When available/selectable collections would be sorted alphabetically - finding the desired collection would be faster.
In Progress
Unified knowledge management for Help Center and Fibi AI Agent
Knowledge is currently split between Help Center articles and Fibi AI Agent Training Data. They live in separate dashboards, use different content models, and cannot be searched, maintained, or automated as one source of truth. Create one Knowledge dashboard for all reusable support content, similar in concept to Intercom's Knowledge workspace. Common content types: public Help Center article, internal article, snippet, uploaded document, and external source. Choose where each item is used: Help Center, Fibi, and Copilot. An internal or Fibi-only article must never be publicly visible in the Help Center, but should be available to Fibi when answering. Unified management: search, filters, folders, bulk actions, and configurable columns for type, collection, audience, publication status, language, author, last updated date, and where the content is used. Consistent editing and lifecycle: one formatting model, drafts and publishing where relevant, source freshness, and clear ownership. Complete API and MCP coverage: list, search, create, update, delete, publish, and manage metadata for every supported content type. The goal is to stop treating public documentation and AI knowledge as separate systems. Teams should be able to create knowledge once, control who or what can use it, and maintain everything from one place.
Planned
Help center subdirectory hosting
Hello, do you have any plans to support subdirectories? For example, using ‘helpcenter’ as a directory for my own domain, similar to: xxx.com/help. The reason for doing this is that subdirectories are more beneficial for SEO compared to subdomains.
One-click migration from Zoho Desk
Automatic importer to migrate Zoho Desk knowledge base & conversations to Featurebase.
Support importing Markdown articles
I have article files in Markdown format, and I’d like to import them to Help Center via GUI.
Planned
Help Center dashboard with filters & custom columns
We have a lot of articles. It would be nice to filter the overview page for them in the dashboard by title, author, publication status, translation status, parent collection, etc. Choose which information to display and filter by, including title, collection, author, publication status, translation status, visibility and segments, last updated date, and article views. This would make it much easier to audit and manage larger Help Centers without opening articles individually.
Help Center SEO improvements
Even better SEO optimization for the Help Center module. Better Lighthouse Score for Help Center Sitemap seems to be blocking crawlers - even when org access is public When bots try to scan the Help Center (which is public), then they get a response of 403
Help Center - Copy or duplicate articles and collections
Being able to copy collections in the Help Center e.g. to provide help for different Versions of a product.
In Progress
Improve Help Center loading times
The Help Center loading times should be improved - currently the Help Center feels less snappier than it should and sometimes loads for too long, which could make end-users bounce.
Custom CSS support for Help Center styling
This feature would allow users to apply custom CSS to further personalize the appearance of their Help Center beyond the existing branding options (logo, primary color, theme, background color, dark theme). This would enable more advanced styling and a more cohesive brand experience.