In Progress
Requests filter rework
Rework Filtering in Requests and Roadmaps so teams can find and combine the information they need through one consistent filter menu: Filter options Status - select individual workflow statuses. Status type - select broad workflow types, covering all statuses within each type. Category - select one or more categories. Labels - select individual labels or a whole label group. Selecting a group matches any label within it. Support “No label,” including no label within a specific group. Form fields - filter by the request’s custom field values, with operators appropriate to each field type. Insights - filter by the number of linked insights, including zero, minimum, maximum, and ranges. Impact - Filter by the individual follow-up answers, including unanswered. Keep these separate from the combined Importance score used for ordering. Importance Urgency Usage frequency Requesters - match customers who requested the feature. Count - minimum, maximum, exact count, or range. MRR - the MRR of requesters Customer - select specific requesters. Company - select companies represented by requesters. Segment - requesters belonging to selected segments. Customer attributes - attributes of the requesters. Company attributes - attributes of the requesters’ companies. Author - match the request’s author. Customer - select the author. Company - the author’s company. Segment - segments the author belongs to. Customer attributes - the author’s attributes. Company attributes - attributes of the author’s company. Assignee - select teammates, including “Me” and “No assignee.” Dates - Provide relative presets and “Custom date or timeframe.” Support before, after, and between, plus “Not set” where relevant. Due dates also need future presets and “Overdue.” Treat time in status as a duration, with minimum, maximum, and range options. Due date Created date Updated date - latest change to the request’s content or properties. Status updated date - latest workflow status change. Completed date - latest transition into a completed status. Triaged date - when the latest required triage review was completed. Time in current status - elapsed time since entering the current status. Comments and other edits must not reset it. Visibility Visible on portal Author only Internal Source - multi-select the channels where feedback originated (e.g. Slack, Public portal, Support, and Feedback widget). A request can match multiple sources through its linked feedback. Include “No source” for missing origin data. Integrations - select an integration, such as Jira or Linear, then filter for linked or unlinked requests. Filter behavior Support AND / OR groups, incl
Markus Palm 7 days ago
Requests & Insights
In Progress
Requests filter rework
Rework Filtering in Requests and Roadmaps so teams can find and combine the information they need through one consistent filter menu: Filter options Status - select individual workflow statuses. Status type - select broad workflow types, covering all statuses within each type. Category - select one or more categories. Labels - select individual labels or a whole label group. Selecting a group matches any label within it. Support “No label,” including no label within a specific group. Form fields - filter by the request’s custom field values, with operators appropriate to each field type. Insights - filter by the number of linked insights, including zero, minimum, maximum, and ranges. Impact - Filter by the individual follow-up answers, including unanswered. Keep these separate from the combined Importance score used for ordering. Importance Urgency Usage frequency Requesters - match customers who requested the feature. Count - minimum, maximum, exact count, or range. MRR - the MRR of requesters Customer - select specific requesters. Company - select companies represented by requesters. Segment - requesters belonging to selected segments. Customer attributes - attributes of the requesters. Company attributes - attributes of the requesters’ companies. Author - match the request’s author. Customer - select the author. Company - the author’s company. Segment - segments the author belongs to. Customer attributes - the author’s attributes. Company attributes - attributes of the author’s company. Assignee - select teammates, including “Me” and “No assignee.” Dates - Provide relative presets and “Custom date or timeframe.” Support before, after, and between, plus “Not set” where relevant. Due dates also need future presets and “Overdue.” Treat time in status as a duration, with minimum, maximum, and range options. Due date Created date Updated date - latest change to the request’s content or properties. Status updated date - latest workflow status change. Completed date - latest transition into a completed status. Triaged date - when the latest required triage review was completed. Time in current status - elapsed time since entering the current status. Comments and other edits must not reset it. Visibility Visible on portal Author only Internal Source - multi-select the channels where feedback originated (e.g. Slack, Public portal, Support, and Feedback widget). A request can match multiple sources through its linked feedback. Include “No source” for missing origin data. Integrations - select an integration, such as Jira or Linear, then filter for linked or unlinked requests. Filter behavior Support AND / OR groups, incl
Markus Palm 7 days ago
Requests & Insights
GitHub integration: board-level sync rules and per-board repository routing
Bring the GitHub integration in line with Linear and Jira: let each Featurebase board (category) route to its own GitHub repository, and let sync rules be scoped per board. How it works today Automatic push uses one repository for the whole workspace. It can be limited to selected categories, but every pushed post lands in that single repository. GitHub sync rules map a GitHub issue state to a Featurebase status. A rule has no board field and no repository field, so rules cannot be scoped by board or by repo. The repository is only selectable at push time, on a manual push. A post can end up linked to issues in several repositories that way, one push at a time. One GitHub App installation per workspace. Requested behaviour A repository field and a board field on GitHub sync rules, so each board can drive its own repository and its own status mapping. Automatic push that resolves the target repository from the post's board instead of from one global setting. Same shape as Configure Linear integration Sync Rules per board and Jira integration sync rules with multiple projects, both already shipped. Why it matters Raised by a prospect running roughly 15 products, each with its own engineering team and its own repository. Without board-to-repository routing, only one team gets hands-off automatic sync and every other team has to push manually, or the company has to split into separate Featurebase workspaces purely to work around the integration. Related: Support for multiple GitHub organization integration, Advanced GitHub Integration Mapping (Title, Body, Board to Labels).
Anne-Flore Haviez 3 days ago
Requests & Insights
GitHub integration: board-level sync rules and per-board repository routing
Bring the GitHub integration in line with Linear and Jira: let each Featurebase board (category) route to its own GitHub repository, and let sync rules be scoped per board. How it works today Automatic push uses one repository for the whole workspace. It can be limited to selected categories, but every pushed post lands in that single repository. GitHub sync rules map a GitHub issue state to a Featurebase status. A rule has no board field and no repository field, so rules cannot be scoped by board or by repo. The repository is only selectable at push time, on a manual push. A post can end up linked to issues in several repositories that way, one push at a time. One GitHub App installation per workspace. Requested behaviour A repository field and a board field on GitHub sync rules, so each board can drive its own repository and its own status mapping. Automatic push that resolves the target repository from the post's board instead of from one global setting. Same shape as Configure Linear integration Sync Rules per board and Jira integration sync rules with multiple projects, both already shipped. Why it matters Raised by a prospect running roughly 15 products, each with its own engineering team and its own repository. Without board-to-repository routing, only one team gets hands-off automatic sync and every other team has to push manually, or the company has to split into separate Featurebase workspaces purely to work around the integration. Related: Support for multiple GitHub organization integration, Advanced GitHub Integration Mapping (Title, Body, Board to Labels).
Anne-Flore Haviez 3 days ago
Requests & Insights
Next
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.
Markus Palm about 9 hours ago
Help Center
Next
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.
Markus Palm about 9 hours ago
Help Center
Next
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.
Markus Palm about 9 hours ago
Requests & Insights
Next
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.
Markus Palm about 9 hours ago
Requests & Insights
In Progress
Unified knowledge management for Help Center and Fibi AI Agent
Knowledge is currently split between Help Center articles and Fibi AI Agent Training Data. They live in separate dashboards, use different content models, and cannot be searched, maintained, or automated as one source of truth. Create one Knowledge dashboard for all reusable support content, similar in concept to Intercom's Knowledge workspace. Common content types: public Help Center article, internal article, snippet, uploaded document, and external source. Choose where each item is used: Help Center, Fibi, and Copilot. An internal or Fibi-only article must never be publicly visible in the Help Center, but should be available to Fibi when answering. Unified management: search, filters, folders, bulk actions, and configurable columns for type, collection, audience, publication status, language, author, last updated date, and where the content is used. Consistent editing and lifecycle: one formatting model, drafts and publishing where relevant, source freshness, and clear ownership. Complete API and MCP coverage: list, search, create, update, delete, publish, and manage metadata for every supported content type. The goal is to stop treating public documentation and AI knowledge as separate systems. Teams should be able to create knowledge once, control who or what can use it, and maintain everything from one place.
Markus Palm about 1 month ago
Help Center
In Progress
Unified knowledge management for Help Center and Fibi AI Agent
Knowledge is currently split between Help Center articles and Fibi AI Agent Training Data. They live in separate dashboards, use different content models, and cannot be searched, maintained, or automated as one source of truth. Create one Knowledge dashboard for all reusable support content, similar in concept to Intercom's Knowledge workspace. Common content types: public Help Center article, internal article, snippet, uploaded document, and external source. Choose where each item is used: Help Center, Fibi, and Copilot. An internal or Fibi-only article must never be publicly visible in the Help Center, but should be available to Fibi when answering. Unified management: search, filters, folders, bulk actions, and configurable columns for type, collection, audience, publication status, language, author, last updated date, and where the content is used. Consistent editing and lifecycle: one formatting model, drafts and publishing where relevant, source freshness, and clear ownership. Complete API and MCP coverage: list, search, create, update, delete, publish, and manage metadata for every supported content type. The goal is to stop treating public documentation and AI knowledge as separate systems. Teams should be able to create knowledge once, control who or what can use it, and maintain everything from one place.
Markus Palm about 1 month ago
Help Center
In Progress
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.
Stefan Pasel 14 days ago
Help Center
In Progress
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.
Stefan Pasel 14 days ago
Help Center
Manage workspace settings through API and MCP
Create, edit, and delete Request labels, categories, statuses, and form-field definitions through the API and MCP, including field options and required-field settings. This would let teams and AI agents set up and maintain their workspace configuration without repeating the setup manually in the dashboard.
Markus Palm about 9 hours ago
Requests & Insights
Manage workspace settings through API and MCP
Create, edit, and delete Request labels, categories, statuses, and form-field definitions through the API and MCP, including field options and required-field settings. This would let teams and AI agents set up and maintain their workspace configuration without repeating the setup manually in the dashboard.
Markus Palm about 9 hours ago
Requests & Insights
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.
Kelly Szabo 3 days ago
Helpdesk
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.
Kelly Szabo 3 days ago
Helpdesk
Multiple customer SSO configurations per Workspace
Allow a Featurebase Workspace to configure and manage multiple customer-facing SSO setups instead of relying on one global SSO login URL and JWT configuration. This would support companies that have multiple products, brands, portals, or customer identity systems within one Workspace. Each SSO setup should be able to have: Its own login URL and JWT verification configuration Routing rules that associate it with specific brands, custom domains, Messengers, Help Centers, or public portals Support for returning the customer to the correct surface after authentication Featurebase should resolve the appropriate SSO setup from the active brand or domain while keeping the customer data and product configuration centrally managed in one Workspace. This request concerns customer-facing SSO and is separate from Enterprise SSO used by teammates to access the Featurebase dashboard.
Markus Palm about 1 month ago
General
Multiple customer SSO configurations per Workspace
Allow a Featurebase Workspace to configure and manage multiple customer-facing SSO setups instead of relying on one global SSO login URL and JWT configuration. This would support companies that have multiple products, brands, portals, or customer identity systems within one Workspace. Each SSO setup should be able to have: Its own login URL and JWT verification configuration Routing rules that associate it with specific brands, custom domains, Messengers, Help Centers, or public portals Support for returning the customer to the correct surface after authentication Featurebase should resolve the appropriate SSO setup from the active brand or domain while keeping the customer data and product configuration centrally managed in one Workspace. This request concerns customer-facing SSO and is separate from Enterprise SSO used by teammates to access the Featurebase dashboard.
Markus Palm about 1 month ago
General
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.
Danny Schaffer 14 days ago
Helpdesk
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.
Danny Schaffer 14 days ago
Helpdesk
Improve Fibi's resistance to completing unrelated tasks
Improve Fibi’s resistance to use as a general-purpose assistant. Fibi should decline unrelated tasks, such as translating personal messages, and redirect users to company support topics. Visitors can currently abuse Fibi as their GPT alternative in certain scenarios.
Kevin Gunst about 7 hours ago
Fibi AI Agent
Improve Fibi's resistance to completing unrelated tasks
Improve Fibi’s resistance to use as a general-purpose assistant. Fibi should decline unrelated tasks, such as translating personal messages, and redirect users to company support topics. Visitors can currently abuse Fibi as their GPT alternative in certain scenarios.
Kevin Gunst about 7 hours ago
Fibi AI Agent
Toggle to allow or disallow images in Fibi responses
Add a setting to control whether Fibi can include images in responses. When disabled, Fibi must send text-only replies, including no separate image galleries or email image attachments.
Kevin Gunst about 7 hours ago
Fibi AI Agent
Toggle to allow or disallow images in Fibi responses
Add a setting to control whether Fibi can include images in responses. When disabled, Fibi must send text-only replies, including no separate image galleries or email image attachments.
Kevin Gunst about 7 hours ago
Fibi AI Agent
Manage and create Roadmaps through API and MCP
Create and manage Roadmaps through the API and MCP, including their columns, filters, and visibility. This would let teams and AI agents configure Roadmaps and keep them up to date from their own tools without manually editing each Roadmap in the dashboard.
Markus Palm about 9 hours ago
Requests & Insights
Manage and create Roadmaps through API and MCP
Create and manage Roadmaps through the API and MCP, including their columns, filters, and visibility. This would let teams and AI agents configure Roadmaps and keep them up to date from their own tools without manually editing each Roadmap in the dashboard.
Markus Palm about 9 hours ago
Requests & Insights
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.
Markus Palm about 9 hours ago
Helpdesk
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.
Markus Palm about 9 hours ago
Helpdesk
Waiting on customer
Ability to pin primary data storage to a single hosting provider/region (e.g. Hetzner/Germany only)
We would like the option to restrict or pin where our primary workspace data is stored to a single hosting provider and region (specifically Hetzner in Germany), rather than the current multi-provider EU setup (AWS/other EU providers). This matters for organizations that need to avoid any exposure to US-jurisdiction infrastructure (e.g. CLOUD Act concerns via US-based subprocessors), even when the data itself stays physically hosted in the EU.
Claudia van Kruistum about 11 hours ago
Helpdesk
Waiting on customer
Ability to pin primary data storage to a single hosting provider/region (e.g. Hetzner/Germany only)
We would like the option to restrict or pin where our primary workspace data is stored to a single hosting provider and region (specifically Hetzner in Germany), rather than the current multi-provider EU setup (AWS/other EU providers). This matters for organizations that need to avoid any exposure to US-jurisdiction infrastructure (e.g. CLOUD Act concerns via US-based subprocessors), even when the data itself stays physically hosted in the EU.
Claudia van Kruistum about 11 hours ago
Helpdesk
Create macros via API and MCP
Create support macros through the API and MCP so teams can set up reusable replies programmatically.
AppgenixSoftware about 11 hours ago
Helpdesk
Create macros via API and MCP
Create support macros through the API and MCP so teams can set up reusable replies programmatically.
AppgenixSoftware about 11 hours ago
Helpdesk
Manage Fibi custom actions via API & MCP
Create and update Fibi custom actions through the API and MCP. This would let an AI agent configure and maintain actions without having to complete each setup through the dashboard.
Alex Z about 11 hours ago
Fibi AI Agent
Manage Fibi custom actions via API & MCP
Create and update Fibi custom actions through the API and MCP. This would let an AI agent configure and maintain actions without having to complete each setup through the dashboard.
Alex Z about 11 hours ago
Fibi AI Agent
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.
An Anonymous User about 12 hours ago
Helpdesk
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.
An Anonymous User about 12 hours ago
Helpdesk
Set conversation attributes when creating a ticket
Allow conversation attributes to be chosen at the moment a new ticket is created, rather than only after the ticket exists. Currently the ticket must be created first and then located again to fill in the attributes, which doubles the work when the information is already known at creation time. The creation dialog (see attached screenshot of the Create new ticket view) offers no place for these attributes even though there is room for them. The selection must expose the existing conversation attributes so the values link to the current attribute set; adding a separate new value that does not integrate with the existing attributes would not solve the problem.
Bryan ten Kate about 13 hours ago
Requests & Insights
Set conversation attributes when creating a ticket
Allow conversation attributes to be chosen at the moment a new ticket is created, rather than only after the ticket exists. Currently the ticket must be created first and then located again to fill in the attributes, which doubles the work when the information is already known at creation time. The creation dialog (see attached screenshot of the Create new ticket view) offers no place for these attributes even though there is room for them. The selection must expose the existing conversation attributes so the values link to the current attribute set; adding a separate new value that does not integrate with the existing attributes would not solve the problem.
Bryan ten Kate about 13 hours ago
Requests & Insights