Please tell us what we can do to make Featurebase the best product for you.
Safer publishing controls for changelog updates
Enterprise teams need a safer way to publish changelog updates without slowing down drafting. They want “Show from website & widget” and “email notification” to start off by default, plus a draft-and-approval workflow where teammates can create and edit changelog updates but only designated approvers can publish them. Today, the changelog permission covers both drafting and publishing, while disabling update emails entirely is too broad. The goal is to prevent accidental public releases or customer emails while keeping the release process efficient.
Workflow to send changelog to all channels
Today we manually have events for sending changelogs to the channels
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.
In Progress
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.
Customize the slack message
When submitting a changelog, we would like the ability to customize the message so that it has richer context/ summary. Can be a default field that we manually update, but need to send that along with the title of the changelong
Draft/schedule AI changelogs from posts in "in testing" or custom pre-release statuses
Currently, AI-assisted changelog drafting from a linked post only works once that post is in a "Complete" state. Teams who sync Linear (or Jira) with custom pipeline statuses (e.g. "In testing", "Ready to release") want to draft and schedule the changelog/release note as soon as engineering marks an issue with one of those pre-release statuses, rather than waiting for a separate "Complete" status change. This would let the changelog go out the moment a feature is actually shipped without a manual second step.
Planned
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.
Microsoft Teams notification on changelog/release note publish
When a new changelog/Update is published in Featurebase, automatically post a notification into a designated Microsoft Teams channel, mirroring the existing Slack integration. Teams only customers (no Slack) currently have no built in way to alert their internal channel when release notes go live, forcing a manual workaround.
Triggering rule based on "if the user answered THIS survey already"
That would allow to create survey flows, for instance, asking someone to participate in a product interview after leaving a feedback on a specific survey regarding a feature to be developped.
Next
Recurring Survey should be displayed until responded
It would be useful to have option to display Survey to the user until it has been answered, even when it was dismissed. Dismissal should hide the survey until the next match only.
In Progress
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.
Allow Banner CTA actions to open a specific Update in the in-app Updates widget
I want to be able to configure an Outbound Banner CTA button with an action type like "Open Update" and select an existing Update. When clicked, this action should trigger the in-app Updates/Changelog popup widget to open that specific Update internally (using the SDK's existing `manually_open_changelog_popup` programmatic behavior), rather than navigating the user away to the public standalone Updates page. This keeps the user inside the in-app experience.
Native Salesforce integration for inbound events to trigger surveys and actions
As an administrator, I want Featurebase to support native inbound events from Salesforce. This would allow us to trigger automated actions—specifically sending surveys or modifying user attributes—without having to build custom developer pipelines or use third-party middleware like Zapier or Make, which violates our corporate security policies.
Embedding surveys in custom elements
Embedding surveys in custom elements would allow us to flexibly position them and show them where and whenever we want, ignoring existing built-in triggers.
In Progress
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
Feature Request: Streamlined Audience attribute filtering for massive send-out.
The customer is requesting a more efficient method for audience targeting when they filter users based on custom text attribute. Currently, they need to do separate condition for each of the unique value in the attribute and join them by OR instead of just passing in an array of items and ‘one of’ comparator or similar. Alternatively, customer suggested .csv import or similar bulk-addition mechanism.
More granularity for outbound scheduling frequency
In “Send based on a fixed schedule if the person matches the rules” we currently can do weekly, monthly and yearly. I would like to set a survey for every 2 months on the 5th for instance. Same goes for weeks, years…
Add customizable tags to Update (Changelog) cards
I would like to add tags to Changelog cards. These tags should appear at the bottom left under the title, for example, displaying 'feature update', to help users understand the nature of the popup and prevent it from being perceived as a random notification.
WhatsApp Broadcasts
Send outbound messages directly to WhatsApp chats and channels. We’d love to support WhatsApp as an Outbound channel, so teams can send proactive updates to WhatsApp communities or customer chats from Featurebase. This would help teams reach users who prefer WhatsApp for product updates, support, community announcements, and time-sensitive communication. Ideal support would include: Choosing connected WhatsApp chats/channels as the audience Sending announcements, surveys, updates, and support notices Previewing the message before sending Tracking replies, reactions, and engagement where available Letting replies create or link back to Featurebase conversations
Bookmark and share default Outbound views via URL
I want specific default views in Outbound (such as Updates, Surveys, Banners, etc.) to store their state in the URL so they can be bookmarked and shared directly, similar to how custom views currently behave. Currently, navigating to Outbound -> Updates doesn't store the state in the URL and only displays the default Outbound view.