Backlog
132Under consideration
Product Tour - Primary button should link to custom URL
Primary button in a single-step Product Tour be able to link directly to a custom URL with customizable button text, instead of only closing the tour.
Reuse product tours across account-specific URLs
Allow one tour to work across paths such as /sites/{account}/walls/{id} without redirecting users to the account used during setup. Support configurable page patterns such as /sites/*/walls/*, or an option for startTour to start on the current page without navigation.
Allow dimming Product Tours overlay and not blocking the page
Product Tours should offer an option to disable background dimming and allow interaction with the rest of the page while a tooltip is visible. This would support single-tooltip feature announcements without interrupting use of the application.
Create and manage product tours via agent or API
Allow product tours to be created and managed programmatically (e.g. via an agent, MCP, or API) rather than only through the portal, with tours staying in sync automatically when the underlying site changes. The goal is to support bulk creation and continuous maintenance of many tours alongside the site's codebase, so agents can keep tours from breaking when significant UX updates ship. Related needs when scaling tours this way: A way to handle URLs containing customer-specific slugs as a tour's starting page (currently this forces a duplicate tour per customer, a better mechanism than a special redirect page is needed) A way to target pages that contain dynamic IDs, such as directing users to a specific customer record in the CRM and clicking a button on it.
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.
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.
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.
Planned
17Committed and queued
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.
Separate toggles for changelog comments and reactions
I want to be able to disable comments on the changelog while keeping reactions enabled. Currently, the "Disable Collaboration" toggle is binary and disables both, but I only want to moderate/disable the comments.
Filter Survey Statistics by Date Range
Allow users to filter all survey statistics by a custom date range (e.g., week-wise, month-wise) to enable historical comparison and trend analysis of survey results over time, regardless of the survey type.
Allow other display names for "Changelog" in widgets
Enable users to rename the "Changelog" tab within the Featurebase widget to a custom name, such as "News" or "Updates," to better align with their branding and communication strategy.
Option to add social links to your changelog page
Changelog is the perfect place to also link your socials to for cross-channel marketing and for people to be able to subscribe to you in the channels they are active on:
View bounced & unsubscribed email addresses from changelog
It would be great if we could see a list of all the email addresses where the changelog emails bounced, this way we can ensure that these emails are removed from the list of subscribers and we don’t repeat sending an email to a bounced email address in future posts. This would be beneficial to us (the end-user) and yourselves as this potentially could impact our email score and would save you (featurebase) in total emails sent.
Ability to rename "Latest changes" in changelog dropdown widget
Since changelogs are often used for other things than changes, people want to rename the “Latest changes” to something else:
Automatic AI Translation for Changelog
Translating the changelog is quite a manual work. We need to switch language by language and translate it manualy It would be nice to have a single button which would automatically translate to all languages
Optional steps for Surveys
When creating multiple steps/pages in a survey, it would be great to have the possibility to make a step/page optional for users. Give them the ability to skip the question and not be blocked from the rest of the questions
Survey response webhook
To automate getting the results of surveys into our Notion, this would be helpful.
Next up
3Committed and queued
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.
Auto-save surveys in draft
Its already happened a couple of times were i’m editing a survey and i reload the page or click on another menu item, without saving the survey and i lose all the progress 😭
Dismissing the Changelog Widget should persist for Users and not just Browser sessions
This statement is what the docs say: The state is stored in the browser's local storage, so it will persist across sessions. Which really means The state is stored in the browser's local storage, so it will persist across Browser sessions. I would like: The state is stored on the featurebase user, so it will persist User sessions. Please persist the user dismissing the changelog for no matter what device they are using.
In Progress
3Actively being built
Journeys - 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.
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.
Reorder surveys & answer options
would be extremely helpful if items you add to a survey options list can be reordered. Right now you have to delete options are enter them in the order you want them to be visible to users
Done
62Recently shipped
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
Outbound UI issues
As a product manager myself I see some minor discrepancy in the latest Outbound update. The Left panel should either be in plural like “Chats”, “Updates”, “Surveys” etc or the filter when filtering by “type” should say Update instead of Updates. Doesn’t impact any workflow but just a minor observation from end user standpoint.
Typo in CES Survey Template: "user" instead of "use"
The user reported a typo in the Customer Effort Score (CES) survey template. The text currently says "How easy was it to user our product?" and should be corrected to "How easy was it to use our product?". This was found in the survey card UI.
Users receiving old changelog updates
I am experiencing an issue where some users are receiving an old changelog popup, published last November, instead of the most recent updates.
Changelog callouts display wrong color in emails - shows red instead of brand green
Changelog callouts appear green in editor but render as red/pink when sent via email, despite brand color being set to green. Reproduction: Set brand color to green Create changelog with green callouts Send test email to inbox (i.e. Gmail) Callouts appear red instead of green This breaks brand consistency for customers using callouts in changelog emails.
Mention links in Changelog to Help Center not working
Mention link to Help Center article, which is publicly accessible isn’t working and directs to the same Changelog.
Contributor cannot see published changelog with segment targeting
A changelog post published by my team is visible to other team members and end-users, but I cannot see it anywhere in the Featurebase dashboard. My account has the Contributor role, and this seems to happen when the changelog uses segment targeting, even though the post is already published.
[Changelog API] Allow querying by startDate and endDate
Add startDate and endDate Query Parameters to Changelog API Extend the Changelog API to support filtering changelog entries by date using startDate and/or endDate query parameters, similar to the existing Posts API. This allows to fetch Changelogs based on timeframes. Post API startDate and endDate for reference:
Enhanced Changelog Email Analytics
I need more detailed analytics for my changelog emails. Currently, I only see limited information, and I would like to see metrics such as how many emails were delivered, opened, and clicked.
Small changelog card widget design
Linear example: cal example: