Skip to main content

Share your product feedback!

Please tell us what we can do to make Featurebase the best product for you.

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.

Markus PalminHelpdesk13 days ago

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.

Markus PalminHelpdesk13 days ago

Restrict users to one active conversation at a time

Do not let the same user open multiple conversations at the same time. Opening several conversations in parallel wastes AI credits and adds to the workload. This is seen as a basic feature that should be quick to implement.

An Anonymous UserinHelpdesk6 days ago
1
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.

1

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.

MirellinOutbound9 days ago
User management
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.

DonalinGeneral21 days ago

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.

Markus PalminHelpdesk13 days ago

Restore company members’ access to shared ticket conversations

With Private between company, colleagues can see tickets but can no longer read or continue their linked conversations. Previously supported company access was removed by the Messenger owner-only change, preventing colleagues from taking over during an absence. Restore ticket-scoped company access while preserving privacy for unrelated Messenger and email conversations.

Make request analytics easy to find (not under Legacy Analytics)

We couldn’t find any reporting on our feature request board until we were shown it sits under Legacy Analytics. The name makes us think it is being removed. We’d like request analytics (top requests, votes, which customers asked for what) in the main Reports area, next to support analytics, and to know it is staying.

SarahinReports4 hours ago

Custom AI skills (saved prompts / slash commands) in Copilot

We want to build our own AI skills in Copilot and run them on a conversation with a slash command. Today we do this in Pylon: one command investigates the ticket, drafts the reply, classifies it as a bug or feature request, and drafts the Linear issue for us to confirm. This cuts our ticket handling time roughly in half, and it is the main reason we can’t move our support from Pylon to Featurebase yet. Copilot today only suggests replies based on past conversations, and we can’t define our own steps or prompts.

SarahinFibi AI Agent4 hours ago

Clearer ticket list in the Ticket Portal: ticket number, status, unread and filters

Our users have to open tickets one by one in the Ticket Portal to find the right one and see its latest status or updates. We’d like the ticket list itself to show: Ticket number Ticket name Current status A reliable new/unread indicator (today the dot can stay visible after the message was read) How long the ticket has been open Filters by ticket status and read/unread

End-users to send product feedback to Featurebase via MCP

Support for submitting product feedback directly to Featurebase via MCP. This would let end-users send feature requests and suggestions from their AI agent without switching to support chat or the feedback portal.

Reactions & Comments in Messenger

It would be useful to have an option to enable reactions and comments inside the Messenger Updates tab, especially when the Messenger is used on the Featurebase public portal, where we can't use the Changelog widget. Users could then interact with Updates from within the Messenger, without leaving it for the Featurebase public portal.

Filter Triage by AI-detected potential spam and duplicates

Add filters in Triage for requests flagged by AI as potential spam or possible duplicates. This would let teammates review potentially straightforward decisions first, using the AI’s reasoning and suggested matches to help clear the queue before moving on to more complex requests.

Control URLs collected by the SDK

Applications can contain sensitive information in URL query strings and fragments. Allow customers to select path-only collection or supply a sanitized URL consistently across Messenger and Product Tours SDK requests.

Option to auto-expand comment threads by default

Option to expand comment threads automatically by default Add a configuration option to set comments/threads as auto-expanded by default. Currently, users have to click to expand comment threads and view longer replies, and some users accidentally miss parts of the conversation because they assume they've read the full comment when looking at the initially visible portion. Auto-expanding by default would ensure all context is immediately visible and improve overall readability for users.

@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.

Integrations

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.

Alex ZinOutbound27 days ago
1

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.

Alex ZinFibi AI Agent27 days ago

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.