Please tell us what we can do to make Featurebase the best product for you.
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.
@mention Fibi in Slack to get answers
Allow customers and teammates to @mention Fibi in a Slack channel or thread to get answers from your documentation. Customers could ask Fibi before tagging your team. Teammates could bring Fibi into an existing discussion to help answer a customer's question or find information internally. Fibi should use the thread for context and reply in the same place, with a way to hand over to your team when human help is needed. Quick internal questions should not create unnecessary support conversations.
Support browser translation for public Help Center articles
Public Help Center pages currently prevent browser translation of article content. Readers can see Chrome’s Translate option, but the article remains in its original language. Allow readers to translate public documentation using their browser’s built-in translation, while preserving necessary protections for interactive elements. This would make the documentation easier to use when a reader’s preferred language is not available.
Contradiction checker for Fibi training content
Teams should be able to check existing Q&A, uploaded files, crawled websites, and Help Center articles for potential contradictions, on demand or on a schedule. Results should show the conflicting passages and links to both sources for review, without requiring a proposed Q&A.
Internal notes mention picker shows customers
The @ mention picker in internal notes should only suggest team members, but it also lists customers. Tagging a customer in an internal note is unintended and risks exposing internal context. Restrict the mention autocomplete to members.
One-click Kustomer migration
Automatic importer to migrate your Kustomer knowledge base & conversation history to Featurebase.
Category default blocks public visibility for individual requests
With Category access = Everyone and Default request visibility = Author only, the individual request dropdown offers only Author only and Internal. It does not offer Everyone. The default should apply to new requests. The team should still be able to make one request public without changing the default. The default should apply to new requests. The team should still be able to make one request public without changing the default.
Dedicated Close button for ticket-linked conversations in Inbox
Allow users to close ticket-linked conversations directly via a primary Close button in the inbox conversation header, matching the interface used for regular conversations.
Checkbox form field: option to be checked by default
Let admins set a Checkbox custom field on the request form to start checked. Teams with DPA or consent text want the box pre-selected, and users can still untick it. Today the Checkbox field only has "Require checking" (the user must tick it before submitting); it always starts unchecked.
GitHub integration: board-level sync rules and per-board repository routing
Bring the GitHub integration in line with Linear and Jira: let each Featurebase board (category) route to its own GitHub repository, and let sync rules be scoped per board. How it works today Automatic push uses one repository for the whole workspace. It can be limited to selected categories, but every pushed post lands in that single repository. GitHub sync rules map a GitHub issue state to a Featurebase status. A rule has no board field and no repository field, so rules cannot be scoped by board or by repo. The repository is only selectable at push time, on a manual push. A post can end up linked to issues in several repositories that way, one push at a time. One GitHub App installation per workspace. Requested behaviour A repository field and a board field on GitHub sync rules, so each board can drive its own repository and its own status mapping. Automatic push that resolves the target repository from the post's board instead of from one global setting. Same shape as Configure Linear integration Sync Rules per board and Jira integration sync rules with multiple projects, both already shipped. Why it matters Raised by a prospect running roughly 15 products, each with its own engineering team and its own repository. Without board-to-repository routing, only one team gets hands-off automatic sync and every other team has to push manually, or the company has to split into separate Featurebase workspaces purely to work around the integration. Related: Support for multiple GitHub organization integration, Advanced GitHub Integration Mapping (Title, Body, Board to Labels).
Read Help Center article analytics through API and MCP
Get Help Center analytics through the API and MCP: article views, reactions, and search terms, including searches with no results. This would let teams and AI agents find articles that nobody reads, articles with negative reactions, and missing content, and then keep the Help Center up to date from their own tools.
Update Help Center settings through API and MCP
Change Help Center settings through the API and MCP, such as the display name, title, description, search placeholder, navigation links, and visibility. Today these settings can be read through the API but only changed in the dashboard. This would let teams manage their whole Help Center from their own tools or AI workflows.
Send custom Slack channel messages from Workflows
Allow Workflows to send custom messages to a selected internal Slack channel, with support for user fields such as plan. Teams could use plan-based branches to send alerts like “Important topic - please prioritize” to teammates working different shifts.
Send SLA breach notifications to shared Slack channels
Allow SLA breaches to be selected as an event in shared Slack channel notification routes. Teams working different shifts could then see and act on breaches without relying on the assigned teammate’s personal Slack DMs.
Bulk manage custom email subscription memberships
Allow administrators to add imported or tagged contacts to a selected custom opt-in email subscription through CSV import, bulk user actions, and the public API, while preserving explicit opt-outs. Currently, administrators must enroll contacts individually or use a separate opt-out subscription with tag-based targeting.
Add a shared company name and postal address footer to Updates emails
Workspaces should be able to configure a company name and postal address once and include them automatically in every Updates email. This footer should appear only in emails, without adding the details to the portals post.
Remove the background around images in the Messenger image viewer
The Messenger image viewer uses a solid background that can show around transparent image edges, especially in light mode. Image previews should display without this surrounding background, without changing the rest of the Messenger’s background.
Option to disable or adjust spam filter strength
Provide a way to disable the spam filter entirely or adjust its strength. Allowlisting every individual sender is not a feasible long-term solution.
Product Tour - Primary button should link to custom URL
Primary button in a single-step Product Tour be able to link directly to a custom URL with customizable button text, instead of only closing the tour.
Reuse product tours across account-specific URLs
Allow one tour to work across paths such as /sites/{account}/walls/{id} without redirecting users to the account used during setup. Support configurable page patterns such as /sites/*/walls/*, or an option for startTour to start on the current page without navigation.