Planned
114Committed and queued
Enlarge conversation drawer on search page
Make the conversation drawer opened from the search page larger, or provide an option to resize or expand it. The current drawer is too small to comfortably review tickets, which matters when working through open tickets one by one with customers on calls.
Show Update categories in in-app widgets
Update categories should be visible across all in-app Update surfaces, including the Messenger Updates tab, Update popup, Update card, and standalone Update widget. Showing categories such as New feature, Improvement, Beta, or Maintenance helps users immediately understand what an Update is about. On compact cards, additional categories can be collapsed into a +N categories label. The full Update view should show every assigned category using its configured name and color.
Sorting & filtering in the Users directory
I want to be able to sort the Companies list in the Users directory. At minimum, this should include: Company name A-Z and Z-A Company code or ID Other standard and custom Company attributes where possible When working with a large number of Companies, the current order makes it difficult to find and review records.
Fibi follow-up setting customization
There should be a way to configure Fibi's follow-up behavior, including options like: Fibi will confirm whether the user still needs assistance - Fibi asks a short follow-up question after answering, such as “Did that answer your question?” Fibi will offer escalation - Fibi checks in and offers to connect the user with a teammate if they still need help. No follow-up - Fibi sends only the main answer and does not send follow-up prompts or idle nudges. Fibi, currently always sends follow-up prompts and idle nudges based on internal logic, but there is no surfaced setting to disable or customize that behavior.
Manual SLA adjustment from Inbox
I would like the ability to manually change an assigned Service Level Agreement (SLA) directly within the user interface. Currently, SLA changes are only possible through workflows. Our use case involves situations where a customer might raise a critical ticket, but upon review, we deem it to be a medium priority - or vice-versa. We need to be able to downgrade or upgrade the SLA in the UI, similar to how other ticket attributes can be adjusted.
AI-detected conversation tags
Allow Fibi to automatically set conversation tags based on conversation context, similar to how conversation attributes can currently be detected and updated by AI. Today, tags can be applied through workflow rules such as keywords or explicit tag actions, which does not cover cases where the correct tag depends on understanding the full conversation.
Ticket filters in Inbox search
Teams need a faster way to find and organize tickets from the Inbox search panel. Right now, tickets can be filtered by fields like Assignee and Team, but there is no easy way to filter or search by ticket-specific details such as Ticket ID or Ticket Type. Requested filters Ticket ID / ticket number Ticket Type Why this matters When a customer or teammate references a specific ticket number, admins should be able to jump directly to that ticket instead of searching by title keywords or manually scanning the Inbox. Adding ticket-specific filters to Inbox search would make it easier to: Find a ticket by its numerical ID Filter tickets by type Build more useful ticket views Manage support conversations faster from one place
Separate toggles for changelog comments and reactions
I want to be able to disable comments on the changelog while keeping reactions enabled. Currently, the "Disable Collaboration" toggle is binary and disables both, but I only want to moderate/disable the comments.
Recover deleted items (posts, users, articles, changelogs, etc.)
Would be great to be able to see and recover deleted Featurebase items, such as posts, users, articles, and changelogs, from some kind of an Archive view.
Company segments
Just like you can create user segments, it would be crucial to be able to create company segments. Sometimes you need to quantify numbers on the company level, especially as a B2B company.
Next up
18Committed and queued
Filter/sort/hide completed tickets in the Ticket portal
I want to be able to filter out or hide closed/resolved tickets on the "Support Tickets" tab in the customer portal. For clients who raise a high volume of quick Q&A requests, open/ongoing tickets can easily get pushed down the list and "off screen" by closed ones. Having a toggle or button to "hide closed tickets" would keep active/open tickets visible.
Add 'Fibi closes a conversation' workflow
We need a new Workflow trigger called ‘Fibi clsoes a conversation’ that is triggered when a conversation is auto-closed by Fibi, so we can run appropriate automation when the conversation is closed without human interaction.
Fibi AI Table Parsing in Help Center
I want the AI agent (Fibi) to be able to read and extract information from tables in the help center. Currently, it seems to only process plain text, which means important data stored in tables is missed during AI searches and chat interactions. This is important because many of our technical specifications and pricing details are in tables.
Automatically capture feedback from Slack with AI
Have a “Featurbease agent” you can @mention in Slack discussions that automatically creates issues (or add insights to existing issues) based on the conversation’s context. Or even a Slack agent that continuously monitors a #feedback channel and automatically identifies and submits feedback to the Featurebase board. If there’s already a post about an issue, it could add it as an insight to the existing post.
Allow End-Users to Filter and View Their Own and Company-Only Feature Requests
End-users on the public portal should be able to view and search feature requests submitted by themselves (author-only) or by others within their company (company-only). This would enable customers with multiple contributors to easily see what they or their organization have already requested, without requiring admin dashboard access. Filters for Author and Company, along with search across these scoped views, should be available to logged-in end-users to improve visibility, reduce duplicate requests, and provide clearer feedback ownership.
Support 'Select' & 'Multi-select' attribute types for user data
It’s crucial that we support 'Select' & 'Multi-select' type of attributes where you can create multiple options to chose from. The attribute options for ‘Users’ and ‘Companies’ should be the exact same as Conversation Data Attributes:
Have Fibi index content from Help Center's FAQ elements
Currently, Fibi (and probably Help Center AI) doesn’t index and use info from the Help Center accordion elements used for FAQ. It’s super important to get this fixed, as we’re getting questions that are not answered but are documented.
Accordion element cuts text with long questions
In case of longer FAQ questions, the accordion element cuts off the text:
Add User Tags & User Segments to Conversation details panel
Add User tags and User segments sections under the conversation details panel, and allow assigning user tags right from the inbox. Adding tags would enable support people to tag customers with relevant tags, like “Ask testimonial” or “High priority” straight from the conversation inbox. Seeing user segments would enable support teams to see whether a customer is part of any segments that they’ve created.
Microsoft Teams integration for support module
Fully bring the Featurebase messenger experience to your Microsoft teams and provide support seamlessly to users wherever they are. Answer to customers in Microsoft Teams thorugh Featurebase inbox interface Create posts from requests in Microsoft Teams automatically etc.
In Progress
21Actively being built
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.
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.
Disabling the Help Center should also stop article suggestions and public access
Today, "disabling" the Help Center only removes the module from the portal menu (Settings → Branding → Portal menu → Delete). The content itself stays live, so after disabling it customers still see: Articles suggested during ticket and conversation creation. Articles reachable and indexable on the public Help Center URL. The expectation is that deactivating a module makes its content and all linked functionality inactive, in one action. Requested behaviour A single workspace-level switch that takes the Help Center fully offline: no article suggestions in the Messenger or ticket forms, no public article URLs, no search-engine indexing. Apply the same principle to the other modules, so turning one off never leaves a surface still serving its content. Make the current behaviour explicit in the interface, since the existing control is a navigation change rather than a content switch. Current workarounds are partial: the Messenger Help module and article search card can be turned off individually in Settings → Support → Messenger → Customization, and articles can be restricted to Team members one at a time, which removes them from suggestions and search indexing but cannot be applied in bulk. Raised by a customer evaluating Featurebase who deactivated the Help Center and found the articles still active.
Series - multi-step Outbound campaigns
Support building automated multi-step customer journeys by connecting chats, banners, emails, and surveys in a visual flow. Each step should support delays, conditions, and different paths based on user attributes, events, or interactions with earlier messages. This would make it easy to create onboarding, activation, upgrade, and re-engagement campaigns without managing every message separately.
Outbound MCP & API support
Manage and analyze all of Outbound, Chats, Banners, Emails, Updates, and Surveys, programmatically and with AI. Today, the Featurebase API and MCP only partially cover Outbound, and only some message types under their old names. Full Outbound coverage would let you: Create, update, schedule, and send any Outbound message (Chat, Banner, Email, Update, Survey) via the API Build and manage audiences and targeting programmatically Pull Outbound performance and survey responses into your own tools and dashboards Access user-level Outbound engagement data, including user Ids and timestamps, to match message interactions with purchases, product usage, and other outcomes in your own systems. Analyze, and even draft, Outbound content with AI through the MCP Etc.
Slack Broadcasts
Send outbound messages directly to Slack channels. We’d love to support Slack as an Outbound channel, so teams can broadcast product updates, incident notices, onboarding messages, survey prompts, and other announcements directly into connected Slack channels. This would make it easier to reach customers where they already work, especially for B2B teams that manage customer communities or shared Slack Connect channels. Ideal support would include: Choosing connected Slack channels as the audience Sending rich messages with links, images, and variables Previewing the message before sending Tracking replies, reactions, and link clicks Letting replies create or link back to Featurebase conversations
Use as CvDAs as conditions/filters in Workflows
I want to use CVDAs to create conditional logic in the Workflows branch conditions and trigger settings to route conversations differently based on attribute values.
"Ask Featurebase" AI for the whole workspace
Featurebase should have a workspace-wide internal AI assistant that can answer questions and help teammates understand what is happening across their workspace. Instead of separate “AI support copilot” and “Ask feedback”, teammates should be able to ask questions from a single “Ask Featurebase” chat across support conversations, tickets, feedback, customers, product requests, and other workspace data. Example questions What were customers most unhappy about this week? Which support conversations need attention? What topics came up most often, and how were they resolved? Which customers are asking for the same thing? What feedback should we prioritize based on recent conversations? Are any teammates handling conversations in a way that needs review? What changed in this workspace since I was last online? Teams need a fast way to understand patterns across many customer interactions without manually reading through every conversation, ticket, or feedback post. A workspace-wide "Ask Featurebase" experience would make Featurebase feel more like an intelligent operating layer for customer feedback and support. Similar to how Linear Agent, Ask Attio, and PostHog AI are grounded in each product’s workspace data, Featurebase could help teams ask questions, find patterns, summarize context, and take action from one place.
Multi-brand support for the Feedback Portal & Updates
Support multiple brands within a single Featurebase workspace and portal.
Show linked issue trackers in the Requests list
Make it easy to see which requests are linked to issue trackers (such as Linear, Jira, and ClickUp) without opening each request. Add an ‘Integrations’ toggle under ‘Display properties’: Show the integration’s icon beside requests linked to an external issue, task, or project. On hover, show the linked item’s title and identifier. Clicking the icon should open the linked item. Show each integration when a request has multiple connections. Leave the property empty when no issue tracker is linked.
Done
527Recently shipped
Live chat & help desk module
Update: the support platform is now out of closed beta and available for everyone! You can enable it from Settings → Support → General.
Bring codebase context into Featurebase support
Teams want Featurebase support AI to understand their product through their codebase, not only through manually maintained documentation. Allow teams to securely connect selected code repositories so Fibi and Copilot can use code context to: Answer product and technical questions more accurately. Draft better support replies. Help investigate customer-reported issues. Stay current as the product changes. The specific solution could use GitHub, GitLab, Cursor, MCP, or another integration. The core job is to bring the knowledge contained in the codebase into Featurebase.
Audit log / change history for feedback posts
Requesting a per-post activity log showing who changed what and when: status changes, merges, edits, deletions, assignee changes, etc. Important for larger teams that need accountability and traceability over how feedback is triaged and prioritized, especially with multiple admins working the same boards.
Urgency UI overlaps post details
Repro: Go to https://mynewcompany.featurebase.app/p/hello-world Click on Urgencyh Urgery component then replaces the properties tab by overlapping it. Other things like importance/usage frequency do same thing.
Grain integration
Support a native integration between Grain and Featurebase. Automatically turn customer call and meeting insights captured in Grain into structured feedback and feature requests in Featurebase, so what customers say on calls feeds straight into the roadmap.
Reliable bulk upload of Fibi training files
Uploading more than two training files at once in Dashboard → Automations → Training Data is unreliable. Files fail very quickly and land in a Failed state, even for small files (for example a 1.8 KB Markdown file that reported 0 words). Failed files then have to be removed one by one and re-uploaded, which makes seeding an agent with a real documentation set slow and error prone. Requested behaviour Multi-file selection should upload reliably, with queueing or throttling instead of parallel failures. Show the actual reason a file failed (size, type, conversion error, rate limit) rather than a generic Failed label. Offer a retry action on failed files instead of requiring manual delete and re-upload. Reported by a customer evaluating Featurebase who is loading a Markdown documentation set into the AI agent.
Fibi should not respond to every Slack message
Fibi can reply to Slack messages even when they aren't questions and no assistance is needed. In one example, it replied to a message explicitly saying a response wasn't wanted, then replied again to a short “See” follow-up. Fibi should recognize when to stay quiet instead of engaging with every message. This would reduce unnecessary bot replies and let normal customer conversations continue naturally. When uncertain, it can lean toward answering, but it should skip messages that clearly don't need a response.
Slack Integration: Domain-level exclusion (allow/deny lists) for ingestion and replies
I want the ability to set a domain-level exclusion (allow/deny list) on the Slack integration (at both the workspace and per-channel level). When an event is processed, if the author's email domain matches our excluded list, Fibi should not ingest the post or trigger AI/automated replies. This is critical for teams with large volumes of internal users who aren't necessarily added as teammates in Featurebase but frequently post in Slack Connect channels, causing Fibi to treat them as end-customers and respond to internal banter or celebratory posts.
Featurebase notifications to Slack (advanced)
Introduce more advanced Slack notifications (e.g., like Linear). It would be huge QoL if existing Featurebase notifications were available as per-user Slack notifications, and each user should be able to choose which events they want pushed to Slack (vs. email or in-app only). Essentially, Slack should be another Notification destination once it’s connected. Two layers Personal notifications → Slack DM (from the Featurebase app) You connect Slack once on your account, then choose which events you want delivered to your Slack DMs. Quiet by default, opt in to what matters. Channel notifications → shared #channel Team-level (or filtered streams) for things like "new inbound support ticket" or "new feedback" - useful for triage rooms. Already exists for new feedback posts, but should be extended to the rest of the product. Notifications that should be available in Slack Feedback New post created (already supported) New comment on a post (already supported) Post status changes - for admins, and optionally for the upvoters/author of that post Post upvotes - when one of my posts (or a post I'm assigned to / subscribed to) gets upvoted Post assigned to me I'm @mentioned in a post or comment Reply to posts from Slack - Reply to comments inline, without leaving the thread, just like in Linear Support New conversations & tickets (channel notification for triage) Conversation assigned to me New customer reply on a conversation I'm assigned to / following I'm @mentioned in an internal note SLA breaches on the conversation assigned to me Reply to the customer directly from Slack Outbound: New survey response - real-time to a channel, matching what Pendo / PostHog / Sprig offer NPS detractor/promoter received Changelog entry published (channel) So essentially, a Featurebase teammate can live in Slack and trust that anything that actually needs them (a new ticket, an assignment, an SLA at risk, a status change on a post they own) will surface there, with everything else staying quiet.
Customize the Inbox details sidebar
Let teammates customize the right-hand details sidebar in the Inbox so they only see the sections and integrations relevant to their workflow. Teammates should be able to: Show or hide sections such as Discussions, integration links, attributes, and customer details Reorder sections Pin frequently used sections Save these preferences to their teammate profile so they persist across devices Currently, unused sections remain visible and add unnecessary clutter. This customization should work for both Conversations and Tickets.
Macros in mobile app
I would like to be able to use macros and tag conversations directly within the mobile app. I am currently unable to find the option to use macros, and it would be very beneficial to have the ability to tag conversations from the mobile app.