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.
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.
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.
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.
In Progress
Manage Request prioritization, visibility, and status updates through API and MCP
Read and update Impact ratings and Value/Effort scores through the API and MCP. Include the importance, urgency, and frequency ratings used to assess customer demand. Also allow changing whether an existing Request is internal or hidden from the Feedback Portal. This would let teams automate prioritization and control which Requests are shared with customers. Also support publishing custom Request status updates through the API and MCP, with formatted text, links, and images. Allow sending an update when changing a Request's status or for its current status, with an option to notify Requesters. The message should appear as the same pinned, status-labelled update used in the dashboard and be included in the status-update notification. Currently, the public API and MCP can change a status and send the default email, or create a regular comment, but cannot publish a custom status update. This prevents teams and AI agents from completing the full update workflow.
Waiting on customer
AI moderation for comments on public posts
Automatically flag or hold destructive, spam or unhelpful comments on public feedback posts using AI (similar to the existing AI spam filtering for posts), so teams do not need a dedicated person moderating open comments. Requested during a demo by Oomnitza (Ari Stowe, VP of Product): they plan to run an open customer portal and want protection against non constructive comments.
APIv2 Support up to 500 companies per contact upsert
The POST /v2/contacts endpoint limits companies to 100 items. Supporting up to 500 would let integrations synchronize complete company memberships, including removals, in one request while keeping company data out of identity JWTs.
Waiting on customer
Slack conversation as a Workflow trigger in the support inbox
I want a Slack message or conversation to be available as a Workflow trigger. Our app posts customer feedback notifications into an internal Slack channel (around 20 per day, some of which need a customer reply). With a Slack trigger, a workflow could extract the customer email from the structured notification, create a conversation in the support inbox and let us reply by email from there. Raised by PlaynVoice during a demo on 2026-10-14, while they evaluate Featurebase against Intercom and Pylon.
Waiting on customer
Language-specific links and videos in auto-translated Help Center articles
I want to be able to use a different link or embedded video (for example a French YouTube video) per language in an auto-translated Help Center article, without breaking automatic translation for that article. Today, editing the translated version manually locks auto-translation for that article, so the workaround is a callout with a link under the German video or embedding all language videos in one article. Raised by PlaynVoice (German as base language, English and French auto-translated) during a demo on 2026-10-14, while they evaluate Featurebase against Intercom and Pylon.
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.
Improve spacing and padding in support reply emails
Add more padding around the reply content and clearer spacing between the message, ticket link, signature, and quoted history to make support emails easier to read and more professional.
Enable teammate notifications for API-created tickets
I would like a way to enable teammate notifications when tickets are created through POST /v2/tickets, so assigned teammates are alerted about new tickets just as they are for new Messenger conversations.
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.
Scope Messenger conversations to the active customer company
Messenger currently shows conversations based on participant access, regardless of the customer company active in the host application. Customers need conversations restricted to the relevant company context while preserving email To/CC participation. This would prevent threads from appearing in another customer account without requiring participants to be removed.
Exclude automated workflow messages from email notifications
Allow automated, bot, and proactive workflow messages in Messenger to be excluded from user email notifications, or provide a way to mark a workflow message as in-app only. Currently these automated messages are also delivered as emails, but some teams want only human teammate replies to trigger email notifications
Advance notice before AI model changes
Notify customers in advance before the underlying AI model behind the support agent is changed, including the lead time and the channel used, and disclose which AI model(s) are currently in use. Prompts and knowledge bases tuned to the current model's behavior can degrade in answer quality when the model changes without warning, making performance changes hard to trace. The primary use case is investigating changes in answer quality rather than gating rollout approvals, but advance notice remains a desired feature. As a possible approach, the data science team evaluating the product suggests handling model changes like software versioning: release a new version of Featurebase that uses the different model while still supporting the current version, let customers evaluate and tune their prompts for the new model, then switch to the new version, after which support for the old version ends.