Please tell us what we can do to make Featurebase the best product for you.
Include images and source references in Fibi API answers
We use Fibi in our own product's chat through the conversation API. We need its answers to include images and source references, so customers can see the same supporting content they would see in the Featurebase Messenger. Please return the images and source titles and URLs alongside the answer text, so we can display them in our own chat interface.
Instagram DM integration for support
Bring Instagram direct messages into the Featurebase Inbox so teams can receive, manage, and reply to customer support requests in one place. This request tracks interest in Instagram DMs.
Facebook Messenger integration for support
Bring Facebook Messenger messages into the Featurebase Inbox so teams can receive, manage, and reply to customer support requests in one place. This request tracks interest in Facebook Messenger.
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.
Reset Product Tour and Outbound engagement for selected users
Allow admins to reset engagement for a selected Product Tour or Outbound message for individual users. This would let existing users receive it again during testing or after important updates, including when previous completion, dismissal or repeat limits prevent it.
X (Twitter) DM integration for support
Bring direct messages from X (formerly Twitter) into the Featurebase Inbox so teams can receive, manage, and reply to customer support requests in one place. This request tracks interest in X direct messages.
@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.
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.
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.
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.
Add hourly frequency limits for proactive Messenger workflows
I need to limit how often a proactive Messenger workflow appears without suppressing it for a full day. The current frequency options are days, weeks, and months, or sending every time. Please add an hours-based limit, such as once every 3 hours, or a configurable cap on sends per hour or day. This would let us offer help again when a customer retries a failed payment later the same day without showing the message on every attempt.
Disable Schedule until a date and time are selected
The update scheduling picker shows an enabled Schedule button above the calendar before a date is selected, which encourages premature clicks. Disable or hide it until a valid date and time are selected. Optionally move it below the date picker for a clearer form flow.
Visually distinguish Featurebase replies in Telegram chats
Replies sent from Featurebase in Telegram chats should have a visual distinction from other messages, such as a different color. Currently they blend in with the rest of the chat, making it hard to tell which messages come from Featurebase.
Open matched posts in a new tab from the insight composer
Allow users to open the matched post in a new tab without losing their insight draft, so they can read the full post and confirm it’s a duplicate before adding the insight.
Show full descriptions and custom fields in request picker previews
The target picker preview shows a shortened description and no custom fields. Showing the full description and relevant custom fields would help teammates compare requests before merging or adding feedback as an insight, without opening each request separately.
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.
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.
Allow cookie consent management on hosted portals and widgets
Allow teams to add a cookie consent manager to Featurebase-hosted feedback portals, Help Centers and widgets. Visitors should be able to accept or reject optional cookies and change their choice later. Support integration with an existing consent platform.
Show whether Jira status changes trigger customer emails
When Jira changes a request’s status, the request view should clearly show whether a customer email was triggered or skipped, including when notifications are disabled in the matching sync rule. The send icon and count currently leave this unclear. Distinguish a triggered notification from confirmed delivery.