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.
In Progress
Calls tab on user and company profiles
Add a Calls tab to user and company profiles that shows their synced customer calls, with access to the call summary and transcript. This would let support agents see recent calls held by customer success or sales and understand what was discussed, without switching tools or asking another team for context. Only show calls selected for sync and permitted for the viewer. Keep call history available alongside the customer's conversations and feedback, rather than only exposing extracted feature requests.
In Progress
Choose which calls sync from call recorder integrations
Let admins control which calls sync to Featurebase from connected call recorders, instead of importing every call the connected account can access. For Grain, allow selection of specific teams or an equivalent access scope. Provide clear controls similar to selecting folders in Granola, so only the intended customer calls are imported and private internal calls stay out of Featurebase. The selected scope should apply to both transcripts and any feedback extracted from those calls.
@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.
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.
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.
One-click Kustomer migration
Automatic importer to migrate your Kustomer knowledge base & conversation history to Featurebase.
Filter Slack ticket notifications by ticket type and category
Allow teams to filter Slack ticket notifications by ticket type and category, so each Slack channel receives only relevant ticket alerts.
Add a toggle to disable request creation from Linear
Add a separate toggle in the Linear integration settings to stop Linear issues and projects from creating new Featurebase requests, including items carrying the Featurebase label. Turning it off should preserve existing links and status syncing according to the configured rules. This would prevent unwanted requests across workspaces sharing a Linear team without requiring customers to remove their sync rules.
Unsubscribe link stays in English in translated Outbound emails
When an Outbound email uses a non-English translation, its unsubscribe link remains “Unsubscribe from future emails” in the editor and shared email templates. The built-in label should automatically follow the email’s resolved language, as it already does for Updates emails.
Separate Slack notifications for tickets
I would like a separate option to route only ticket notifications to Slack, so I can receive ticket alerts without other notification types.
Send the event ID as a Webhook-Id header
Include the payload’s event ID in a Webhook-Id header on every outbound webhook, keeping it unchanged across retries. This would let customers trigger Linear Loops directly without hosting a relay to add the required header.
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.
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.
Waiting on customer
Report on customer vs teammate activity on Requests
Show which votes, Requesters, comments and Requests come from customers and which come from our own teammates, so we can prove the feedback portal is used by customers and not only by employees. Today no built-in report or export splits Request activity by role, and customers do not know whether anything was registered on their behalf. A customer engagement view (customer-submitted vs teammate-submitted vs submitted on behalf of a customer) would let product leads report on portal effectiveness internally. Amplitude is used for product analytics but is not natively supported, so native reporting is preferred.
Add support and feedback access inside the Android app
The Android app has no entry point for contacting Featurebase support or submitting product feedback. Users must leave the app to ask questions or request improvements. An in-app entry point should let users contact Featurebase and submit feature requests directly.
Allow integrations to thread replies to externally sent receipts
Allow integrations to connect replies to receipts sent through external email services with the correct existing Featurebase conversation. This should work when the customer changes the subject or removes the visible case reference, using email threading metadata rather than guessing from the sender or subject. The capability should also cover receipts already sent with a shared reply address. Updating reply addresses for future receipts does not resolve those older emails.
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.