Allow multi-page applications to persist Messenger widget navigation state (such as active articles or conversation views) across full page reloads, or expose SDK events and getters (e.g. active article ID or view change events) so host applications can restore deep widget state programmatically.

Chris 18 days ago

I installed the Featurebase Mobile app on my Mac from the App Store. When I then open the Featurebase web dashboard in my browser and choose Continue with Google, the sign-in process does not finish in the browser. Instead, Featurebase Mobile opens automatically. This means I cannot sign in to and use the web dashboard while the mobile app is installed on my Mac. To complete the browser sign-in, I currently need to remove the mobile app. The mobile app should be able to open relevant mobile links, but signing in to the Featurebase web dashboard on a Mac should remain in the browser.

Andrew about 12 hours ago

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.

Matthew Parratt about 1 month ago

2

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.

Danny Schaffer 5 days ago

Allow to hide certain ticket types from the list when support staff click the '+' (ticket) button in Inbox to create a new ticket. We have many ticket types that are automatically generated by our software based on various events. Our internal team should not manually create these tickets, but currently, they appear in the list, causing confusion and leading to manual creation attempts. A simple 'Hide From Ticket View' flag on a ticket type would prevent support staff from seeing these automated ticket types when creating new ones.

Jason (PT) 5 days ago

Allow admins to customize module labels in the interface, such as renaming "Tickets" to custom terms like "Processes", “Request“, etc. This helps teams align the platform's UI with their internal terminology and workflows.

Fresh (PT) 5 days ago

Forwarded and automated HTML emails currently have their formatting, headers, and inline styling stripped heavily, causing layout distortion (empty boxes/lines) in the conversation view.

Bryan ten Kate 20 days ago

When a customer starts submitting a ticket with too little information, have an AI agent step in during the submission flow (not just as a separate chat widget) to ask clarifying follow up questions, point to relevant documentation, and help structure the ticket before it reaches the support team. Today the AI chat widget and the ticketing flow are two disconnected paths, so a customer who opens a ticket directly skips any AI assistance, and the support team still has to go back and forth for missing details (server setup, browser info, etc). Raised on a demo call with BLUEEND AG (support/ticketing evaluation, second layer support for on-prem customers).

Stefan Pasel 6 days ago

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.

Kajsa 7 days ago

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.

An Anonymous User 7 days ago

Integrations

Add a configurable setting to auto-close automations that allows admins to choose whether abandoned conversations are closed when a user has an email attached or not.

Andrew 8 days ago

Allow the "Customer became unresponsive" workflow trigger (or a dedicated bot-unresponsive trigger) to fire when a customer stops responding during a bot workflow, enabling automated nudges or auto-closures for abandoned bot conversations.

Andrew 8 days ago

Allow the MCP server to filter tickets and conversations using custom workspace statuses (such as "In Review" or "Waiting on Customer Response"), expanding beyond the current 'open', 'closed', and 'snoozed' options to match UI filtering capabilities.

Alec 11 days ago

We use the Slack integration heavily, but today Slack only syncs conversations into Featurebase, it cannot create a ticket directly. Our channel partners live in Slack, and we would like a way for a Slack message or workflow to create a Featurebase ticket directly (not just a conversation), so partner requests get the same tracked, ticket level workflow as our other support channels.

Alla Awad 26 days ago

Integrations

Allow users to zoom out further on the workflow visual canvas to make linking distant top-to-bottom nodes easier without scrolling.

Andrew 12 days ago

Reduce excessive empty vertical/horizontal spacing between workflow blocks on large canvas layouts to keep connected nodes closer together.

Andrew 12 days ago

Allow export, import, or programmatic editing of workflow definitions using standard formats like YAML or JSON to simplify building complex flows.

Andrew 12 days ago

Allow inbound emails from organization members/admins to be treated as customer support tickets with full reply and commenting capabilities, rather than routing them as internal teammates without customer participants.

James Stevens 27 days ago

There’s no easy way to get to the full screen changelog or at least be able to see and post reactions and comments in the changelog tab of the FAB Widget.

Emi de Feast Fit 14 days ago

Support custom URI schemes (e.g., app-specific deep links like myapp://) in Messenger message bodies and workflows rather than sanitizing/stripping non-standard protocols.

Andrew 15 days ago