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.
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.
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.
Allow dimming Product Tours overlay and not blocking the page
Product Tours should offer an option to disable background dimming and allow interaction with the rest of the page while a tooltip is visible. This would support single-tooltip feature announcements without interrupting use of the application.
Create and manage product tours via agent or API
Allow product tours to be created and managed programmatically (e.g. via an agent, MCP, or API) rather than only through the portal, with tours staying in sync automatically when the underlying site changes. The goal is to support bulk creation and continuous maintenance of many tours alongside the site's codebase, so agents can keep tours from breaking when significant UX updates ship. Related needs when scaling tours this way: A way to handle URLs containing customer-specific slugs as a tour's starting page (currently this forces a duplicate tour per customer, a better mechanism than a special redirect page is needed) A way to target pages that contain dynamic IDs, such as directing users to a specific customer record in the CRM and clicking a button on it.
Fibi launches tours for how-to questions
Enable Fibi to launch a relevant product tour when a user asks a how-to question, so tours serve as guided answers instead of text-only replies.
Image upload endpoint for Help Center articles
Provide a way to attach images to Help Center articles through the API, ideally a multipart upload endpoint that stores the file and returns a Featurebase-hosted URL for use in the article body. Alternatively, add multipart support to articles.create and articles.update, or confirm that base64 data URIs and external URLs in an article body are pulled into Featurebase storage as the changelog docs describe. Local screenshot files have no public URL, and embedding base64 bytes in the tool call is slow, error-prone and bloats the body, so the final step currently has to be done manually in the dashboard editor.
Waiting on customer
Filter a post's voters by company attributes
I want to filter the voters of a single post by company attributes such as industry or company size, directly in Featurebase. Today the only option is exporting the voter list to CSV from the post and then filtering it in Sheets or Excel. Product research teams pick voters for discovery calls and beta tests every week (for example only construction or cleaning companies out of 300 voters), so this manual step slows them down.
Show full request titles by default
Show the full request title by default in the request view instead of truncating it to five lines.
Support dynamic base URLs in the API playground
API documentation readers cannot currently enter a customer-specific base URL. Support reader-entered server URLs without requiring every URL to be listed in the OpenAPI spec. For embedded documentation, also allow the host application to pass the current site’s URL into the playground automatically.
Download blocked users’ transcripts without unblocking them
Authorized teammates should be able to view and download retained conversation transcripts while the user remains blocked. Currently, accessing Download transcript in the Inbox requires unblocking the user, which restores their ability to interact. Transcript access should remain available for record-keeping and legal purposes without lifting the block.