Backlog
372Under consideration
Messenger File names invisible in light/dark mode
Attachment file names in the Featurebase messenger are invisible in light/dark mode, while dark mode displays them correctly. The text color appears to conflict with the white background and is not configurable via the messenger theme settings. The default text/background contrast for attachment cards in light mode needs fixing.
Inbox view editor closes during filter selection
In a narrow browser window, clicking Add rule in Views → New view closes the editor and sidebar drawer. Resizing across the mobile breakpoint can also discard the draft. The editor should stay open during filter selection, resizing, and background clicks. Saved views should also have a keyboard-accessible Edit action.
Automatically unsubscribe spam and blocked users
Automatically unsubscribe users who are marked as spam or blocked, so that manual user cleansing and manual unsubscribing are no longer needed to stop people who should not be receiving the information or posts anyway.
Allow “View raw email” on inbound teammate messages
I’d like to view the original email when a teammate forwards a customer email into the inbox, including when it starts a conversation. Currently “View raw email” is hidden for teammate-authored messages. Enabling it would make the forwarded customer context accessible without changing sender attribution or advanced email routing.
Complete conversation and ticket actions through API and MCP
Set Conversation priority and link or unlink existing Tickets and Conversations through the API and MCP. This would let support automations and AI agents prioritize Conversations and connect them to work already tracked in Tickets without manual dashboard steps.
Create macros via API and MCP
Create support macros through the API and MCP so teams can set up reusable replies programmatically.
Messenger SDK iframe sandbox triggers Chromium warning
The hosted Messenger SDK creates the "Featurebase live chat" iframe with src="about:blank" and a sandbox containing both allow-scripts and allow-same-origin, which makes Chromium log a sandbox-escape warning on every authenticated application page. Reproduced with featurebase-js@1.0.3 using the documented React provider; the Messenger works but the warning appears consistently, and the package exposes no supported sandbox override. Move the iframe document to a dedicated cross-origin URL or revise the sandbox configuration at the SDK level rather than requiring DOM mutation of the generated iframe.
Add an unread filter button into Messenger widget
Add an 'unread' button in the widget so users can jump to unread conversations instead of scrolling through all of them. This would improve the scenario, where the Messenger can consist of many conversations.
Automatically create feature branch in GH based on status of feedback
If a ticket is marked by a status, for example “Accepted” - We should try to decrease the developer load and automatically create a feature branch in GH. Linear does this perfectly, it creates the branch and maintains updates to it, if the branch is merged, the ticket/feedback item is updated too, and the status can be moved to based on the state: If the feature branch has a PR to another branch, Status is “code review” If the feature branch has its Pr merged, status is “Completed” for example. The GH integration can use some love in this regard to make FB the only place our devs work from.
AI escalation of critical support emails to PagerDuty address
Escalation workflow + 3rd-party e-mail Use AI to pick critical messages out of the high volume of support tickets (a lot of noise, with occasional needles like "server down") and escalate them to a different e-mail that is connected to the PagerDuty service, so it wakes up support staff at night.
Planned
16Committed 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.
Include images/videos in macros
Being able to include images or videos in macros would improve the workflow. Currently we need to first add the macro and then find and include the relevant attachment.
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.
Allow ticket state and category filters in OR groups for Inbox views
Ticket state and ticket category filters can currently only be used inside AND groups when creating Inbox views. This means they cannot be combined with other filter groups using OR, even though the view editor supports AND/OR grouping for other filters. For example, I want a Bug reports view that includes Inbox items where either: Ticket category is Bug Report conversation attribute Issue type is Bug The editor blocks this configuration and disables Save changes. This makes custom Inbox views much less flexible. Ticket state and ticket category filters should work with the same AND/OR grouping logic as other filters. Screenshot
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
Multi-language support for Workflows
I would like the workflow action to have multi-language support, so it's possible to enter text in multiple languages, such as Dutch and English, i.e. adding translations.
Customizable sender name for team inbox
Currently, outgoing support emails in Featurebase automatically use the individual team member’s name as the sender. For our use case and likely many others we prefer all support emails from the support inbox to show a generic sender name (e.g., “Support {Organization}”), rather than an employee’s name. Could you add an option to customize and set the sender name for support inboxes, so all outgoing messages display the desired team or company name instead of the personal user’s name? Thank you for considering this improvement!
Side conversations - collaborate with external partners inside tickets
Allow teammates to collaborate with external partners directly within a conversation or ticket with side conversations. This keeps all communication in one place and avoids tool switching. Why it’s needed No need to jump to email or other tools to loop in partners. Updates stay tied to the original ticket, so nothing gets lost. Easy to manage multiple partner threads under the same customer issue. Key capabilities Start side conversations with external partners. Have multiple threads linked to one ticket. Updates flow back into the main conversation. Reassignments also transfer linked side conversations. Example: Support can message a delivery provider about a missing package while keeping the customer updated in the main conversation.
Admin roles for Support platform
Settings to allow roles to: View conversations Participate in conversations Full access to Support module and its settings
Private macros
Option to control whether only me, everyone, or specific teams should be able to see and use that macro.
Next up
4Committed 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.
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
4Actively being built
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.
Reusable conditions / Segments in Workflows
I want to be able to reuse complex conditions (like a saved segment or a group of filters) across different workflows. For example, if I have a condition like 'email contains any of 6 definitions', I don't want to have to recreate that logic in every single workflow. It would be much easier to just select a 'Segment' or a 'Saved Condition' as a branch criteria.
Support merging conversations / tickets
A couple of use cases I have: End user reports an issue which requires opening a support thread with another provider, it’d be helpful to see both conversations in one place. Some providers (like Stripe) send a new email on every reply, rather than using the same email thread, which introduces a lot of clutter in the inbox with every reply.
WhatsApp Integration for Support
Integrate with WhatsApp Business to enable it as a support channel within Featurebase, allowing users to receive and manage support requests via WhatsApp.
Done
160Recently 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.
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.
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.
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.
Settings: opening an Enterprise locked tab introduces a blur on the page that makes navigating to another settings section impossible
Example: dashboard/settings/support/assignments?tab=limits. Not urgent, but would be a quality-of-life improvement. Keep up the good work, guys!
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.
Fibi AI CSAT
Have users rate Fibi AI's response quality to get more data on what to improve and how Fibi AI is working.
Setting to prevent replies to closed tickets
We already have a “prevent visitors from replying to closed conversations” setting for the Messenger, but there should also be a separate option for tickets.
Conversations should be unassigned when a CS/Admin is removed
When a Team member/CS/Admin is removed, their assigned conversations are not automatically unassigned. Instead, they remain assigned to the removed user and are only visible via the 'All messages' filter, effectively being assigned to a non-existent user. This behavior is problematic, as it leaves conversations in a 'stuck' state, requiring manual identification and reassignment.
Support rich formatting in the "Special notice"
Support rich formatting in the Messenger’s “Special notice” field.