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 4 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 4 days 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
ASAP
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.
Robi Rohumaa about 2 months ago
Requests & Insights
ASAP
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.
Robi Rohumaa about 2 months ago
Requests & Insights
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
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 11 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 11 days ago
Help Center
Add 'currently viewing' to feedback posts
I am requesting a feature to display who is currently viewing a feedback post within the feedback module. This functionality is currently available in the Support inbox but not for feedback posts. Our team experiences duplicate effort, with approximately 5 out of 400 weekly feedback posts last week receiving similar replies from multiple agents. This leads to wasted agent time and a suboptimal user experience. Implementing a 'currently viewing' indicator would allow agents to avoid posts being actively worked on.
Ashley Yau 13 days ago
Requests & Insights
Add 'currently viewing' to feedback posts
I am requesting a feature to display who is currently viewing a feedback post within the feedback module. This functionality is currently available in the Support inbox but not for feedback posts. Our team experiences duplicate effort, with approximately 5 out of 400 weekly feedback posts last week receiving similar replies from multiple agents. This leads to wasted agent time and a suboptimal user experience. Implementing a 'currently viewing' indicator would allow agents to avoid posts being actively worked on.
Ashley Yau 13 days ago
Requests & Insights
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.
An Anonymous User 14 days ago
Integrations
Helpdesk
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.
An Anonymous User 14 days ago
Integrations
Helpdesk
Unsubscribe all users in a company from outbound emails
When a client leaves or is on a bespoke product, we need to stop standard client-facing emails for everyone linked to their company. At the moment, this has to be done one person at a time. Add a company-level action that lets an admin unsubscribe all current members at once, either from all emails or selected subscriptions. Ideally, admins could also choose whether future members inherit the setting.
Kelly Szabo about 8 hours ago
Outbound
Unsubscribe all users in a company from outbound emails
When a client leaves or is on a bespoke product, we need to stop standard client-facing emails for everyone linked to their company. At the moment, this has to be done one person at a time. Add a company-level action that lets an admin unsubscribe all current members at once, either from all emails or selected subscriptions. Ideally, admins could also choose whether future members inherit the setting.
Kelly Szabo about 8 hours ago
Outbound
Example request
Make the Featurebase MCP publicly installable from the Claude Connectors Directory and OpenAI Plugins Directory, so customers no longer need to copy MCP URLs or follow manual setup. OpenAI uses one shared listing for ChatGPT and Codex.’ Before submitting: Prefer one public Featurebase listing and endpoint, while keeping Reader and Writer capabilities separated through server-enforced scopes. Read-only should remain the default - do not recreate the legacy all-access token. Expose a stable remote MCP URL with OAuth and PKCE, accurate annotations on every tool, and separate read/create/edit/delete tools. Anthropic can reject catch-all tools that mix safe reads and writes. Create a reviewer Workspace with populated synthetic data and credentials that do not require MFA. Test every tool and provide clear failures for invalid scopes and inputs. Prepare the listing copy, logo, documentation, privacy policy, terms, support contact and starter prompts. OpenAI additionally asks for five positive and three negative test cases. Add OpenAI's domain-verification challenge endpoint, verify Origin-header validation, and consider CIMD for OAuth at marketplace scale. Non-obvious review notes: Anthropic submissions require a Claude Team or Enterprise owner. Accepted connectors normally start as Community connectors; Verified status is a separate, higher-touch review. OpenAI requires verified Platform identity and Apps Management Write access. After approval, we must manually publish the listing. Neither marketplace provides a fixed review SLA. References: Current Featurebase MCP setup Anthropic submission guide Anthropic review criteria OpenAI submission guide OpenAI review requirements
Markus Palm about 8 hours ago
Integrations
Requests & Insights
Example request
Make the Featurebase MCP publicly installable from the Claude Connectors Directory and OpenAI Plugins Directory, so customers no longer need to copy MCP URLs or follow manual setup. OpenAI uses one shared listing for ChatGPT and Codex.’ Before submitting: Prefer one public Featurebase listing and endpoint, while keeping Reader and Writer capabilities separated through server-enforced scopes. Read-only should remain the default - do not recreate the legacy all-access token. Expose a stable remote MCP URL with OAuth and PKCE, accurate annotations on every tool, and separate read/create/edit/delete tools. Anthropic can reject catch-all tools that mix safe reads and writes. Create a reviewer Workspace with populated synthetic data and credentials that do not require MFA. Test every tool and provide clear failures for invalid scopes and inputs. Prepare the listing copy, logo, documentation, privacy policy, terms, support contact and starter prompts. OpenAI additionally asks for five positive and three negative test cases. Add OpenAI's domain-verification challenge endpoint, verify Origin-header validation, and consider CIMD for OAuth at marketplace scale. Non-obvious review notes: Anthropic submissions require a Claude Team or Enterprise owner. Accepted connectors normally start as Community connectors; Verified status is a separate, higher-touch review. OpenAI requires verified Platform identity and Apps Management Write access. After approval, we must manually publish the listing. Neither marketplace provides a fixed review SLA. References: Current Featurebase MCP setup Anthropic submission guide Anthropic review criteria OpenAI submission guide OpenAI review requirements
Markus Palm about 8 hours ago
Integrations
Requests & Insights
Waiting on customer
Assign a single Help Center article to multiple brands directly
In a multi-brand workspace, allow a single Help Center article to be tagged or assigned directly to more than one brand's Help Center, instead of the article living under one brand only and access being controlled indirectly through user segments. Today, each brand has its own separate Help Center, and an article can only be attached to one of them. To make an article show up under a second brand, you have to either duplicate the article into that brand's Help Center or grant access via a user segment, there's no direct "this article also belongs to Brand B" option. Requested by a prospect running a white label, multi-brand support setup on behalf of their own customers, where some articles are shared across brands and some are brand specific.
Anuj K about 10 hours ago
Requests & Insights
Waiting on customer
Assign a single Help Center article to multiple brands directly
In a multi-brand workspace, allow a single Help Center article to be tagged or assigned directly to more than one brand's Help Center, instead of the article living under one brand only and access being controlled indirectly through user segments. Today, each brand has its own separate Help Center, and an article can only be attached to one of them. To make an article show up under a second brand, you have to either duplicate the article into that brand's Help Center or grant access via a user segment, there's no direct "this article also belongs to Brand B" option. Requested by a prospect running a white label, multi-brand support setup on behalf of their own customers, where some articles are shared across brands and some are brand specific.
Anuj K about 10 hours ago
Requests & Insights
Waiting on customer
Native one click sync of Help Center articles across brands
In a multi-brand Enterprise workspace, allow admins to copy or sync a Help Center article from one brand's Help Center to another directly inside Featurebase, without duplicating content by hand. Today the only way to bring an article from one brand's Help Center into another is a manual workaround via the MCP integration (prompting Claude or ChatGPT to copy the article/collection across), there is no native one click "share to another brand" action in the product itself. Requested by a prospect running a white label, multi-brand support setup on behalf of their own customers, where some articles are common across brands and duplicating them by hand for every new brand is not practical.
Anuj K about 10 hours ago
Requests & Insights
Waiting on customer
Native one click sync of Help Center articles across brands
In a multi-brand Enterprise workspace, allow admins to copy or sync a Help Center article from one brand's Help Center to another directly inside Featurebase, without duplicating content by hand. Today the only way to bring an article from one brand's Help Center into another is a manual workaround via the MCP integration (prompting Claude or ChatGPT to copy the article/collection across), there is no native one click "share to another brand" action in the product itself. Requested by a prospect running a white label, multi-brand support setup on behalf of their own customers, where some articles are common across brands and duplicating them by hand for every new brand is not practical.
Anuj K about 10 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 about 11 hours 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 about 11 hours ago
Helpdesk
Auto suggest known fix for recurring issues before creating a new ticket
When a repetitive problem comes in that we have already seen and solved before, we would like the system to automatically suggest the known fix to the person reporting it, instead of a brand new ticket being created that our team has to triage from scratch again. Ideally this could even resolve or close the ticket automatically once the known fix is suggested, saving our team time on repeat issues. Raised during a demo call. We are a franchise network handling IT support and feedback for around 500 to 600 internal franchise users, and want automation that reduces repeat manual triage.
Nadia Ajana 15 days ago
Requests & Insights
Auto suggest known fix for recurring issues before creating a new ticket
When a repetitive problem comes in that we have already seen and solved before, we would like the system to automatically suggest the known fix to the person reporting it, instead of a brand new ticket being created that our team has to triage from scratch again. Ideally this could even resolve or close the ticket automatically once the known fix is suggested, saving our team time on repeat issues. Raised during a demo call. We are a franchise network handling IT support and feedback for around 500 to 600 internal franchise users, and want automation that reduces repeat manual triage.
Nadia Ajana 15 days ago
Requests & Insights
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.
Robert 1 day ago
Integrations
Helpdesk
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.
Robert 1 day ago
Integrations
Helpdesk
Messenger widget state persistence and view change events across page reloads
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 25 days ago
Helpdesk
Messenger widget state persistence and view change events across page reloads
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 25 days ago
Helpdesk
Option to add JSON Schema to help center articles for better AIO/AEO
We’re trying to get our Help Center articles to appear in Google search and other external/third-party AI search results. They rely on JSON schemas that are usually inserted into the HTML of the page. Here’s some details: https://201creative.com/structured-data-ai-search/
Micah 18 days ago
Help Center
Option to add JSON Schema to help center articles for better AIO/AEO
We’re trying to get our Help Center articles to appear in Google search and other external/third-party AI search results. They rely on JSON schemas that are usually inserted into the HTML of the page. Here’s some details: https://201creative.com/structured-data-ai-search/
Micah 18 days ago
Help Center
Heap integration
Support a native integration between Heap and Featurebase. Connect Heap's product analytics so usage and behavioral data can guide which feature requests get prioritized, and analyze Featurebase activity alongside Heap events.
Markus Palm 2 months ago
General
Heap integration
Support a native integration between Heap and Featurebase. Connect Heap's product analytics so usage and behavioral data can guide which feature requests get prioritized, and analyze Featurebase activity alongside Heap events.
Markus Palm 2 months ago
General
Planned
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.
Markus Palm 2 months ago
Outbound
Planned
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.
Markus Palm 2 months ago
Outbound
Option for AI Agent to look for in a specified collection of articles for a workflow
If i have 3 Workflows for A, B, C, i would like Fibi AI agent to only look for in the corresponding collection of article. If the workflow A is running, Fibi AI agent should only look in the A collection articles, etc. Today he is mixing collection in this anwser leading to totally inconsitent answer. We’ve tried to be strict in his prompt but it still happen sometimes.
Elodie JAFFRO 6 days ago
Fibi AI Agent
Option for AI Agent to look for in a specified collection of articles for a workflow
If i have 3 Workflows for A, B, C, i would like Fibi AI agent to only look for in the corresponding collection of article. If the workflow A is running, Fibi AI agent should only look in the A collection articles, etc. Today he is mixing collection in this anwser leading to totally inconsitent answer. We’ve tried to be strict in his prompt but it still happen sometimes.
Elodie JAFFRO 6 days ago
Fibi AI Agent