Please tell us what we can do to make Featurebase the best product for you.
Reset Product Tour and Outbound engagement for selected users
Allow admins to reset engagement for a selected Product Tour or Outbound message for individual users. This would let existing users receive it again during testing or after important updates, including when previous completion, dismissal or repeat limits prevent it.
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.
Check segment membership and get per-user Updates through the API
We show Featurebase Updates inside our own app through the API. Each Update returns allowedSegmentIds, but the API has no way to tell which users are in those segments, so we can't honor segment targeting outside the Featurebase widget. Any one of these would solve it: Return the Updates visible to a given user (by userId), with segment targeting applied by Featurebase. This would be ideal. Check whether a contact is in a segment (by userId). List a segment's members. Without this, the only option is to rebuild the segment rules on our side and keep them in sync, which is fragile. If our copy drifts, an Update meant for a pilot group reaches everyone.
Disable Schedule until a date and time are selected
The update scheduling picker shows an enabled Schedule button above the calendar before a date is selected, which encourages premature clicks. Disable or hide it until a valid date and time are selected. Optionally move it below the date picker for a clearer form flow.
Bulk manage custom email subscription memberships
Allow administrators to add imported or tagged contacts to a selected custom opt-in email subscription through CSV import, bulk user actions, and the public API, while preserving explicit opt-outs. Currently, administrators must enroll contacts individually or use a separate opt-out subscription with tag-based targeting.
Build product tours via MCP or API
Product Tour Creation MCP or API Enable building product tours programmatically through the MCP or the API. The vision is for users to ask the AI questions about how to do something, have it build a tour for them, and guide them through it.
Unsubscribe link stays in English in translated Outbound emails
When an Outbound email uses a non-English translation, its unsubscribe link remains “Unsubscribe from future emails” in the editor and shared email templates. The built-in label should automatically follow the email’s resolved language, as it already does for Updates emails.
Fallback language for outbound email campaigns
Allow setting a fallback language when sending an outbound email campaign. Currently it seems not possible, so if a user has no local preference the email is sent by default in english. As a french team they would like to send emails in french by default instead of manually setting all users' local preference to french.
Add a shared company name and postal address footer to Updates emails
Workspaces should be able to configure a company name and postal address once and include them automatically in every Updates email. This footer should appear only in emails, without adding the details to the portals post.
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.
Discord component embeds for update post links
Support Discord's component embeds so links to update posts can be customised when pasted into a Discord channel, using features like buttons and custom text formatting. Suggested approaches: An embed builder on the dashboard, or allowing code injection to achieve this. Documented here: https://docs.discord.com/developers/link-previews/component-embeds
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
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.
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.
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.