Changelog
Support
Help Center

Share your product feedback!

Please tell us what we can do to make Featurebase the best product for you.

Planned

Featurebase notifications to Slack (advanced)

Introduce more advanced Slack notifications (e.g., like Linear). It would be huge QoL if existing Featurebase notifications were available as per-user Slack notifications, and each user should be able to choose which events they want pushed to Slack (vs. email or in-app only). Essentially, Slack should be another Notification destination once it’s connected. Two layers Personal notifications → Slack DM (from the Featurebase app) You connect Slack once on your account, then choose which events you want delivered to your Slack DMs. Quiet by default, opt in to what matters. Channel notifications → shared #channel Team-level (or filtered streams) for things like "new inbound support ticket" or "new feedback" - useful for triage rooms. Already exists for new feedback posts, but should be extended to the rest of the product. Notifications that should be available in Slack Feedback New post created (already supported) New comment on a post (already supported) Post status changes - for admins, and optionally for the upvoters/author of that post Post upvotes - when one of my posts (or a post I'm assigned to / subscribed to) gets upvoted Post assigned to me I'm @mentioned in a post or comment Reply to posts from Slack - Reply to comments inline, without leaving the thread, just like in Linear Support New conversations & tickets (channel notification for triage) Conversation assigned to me New customer reply on a conversation I'm assigned to / following I'm @mentioned in an internal note SLA breaches on the conversation assigned to me Reply to the customer directly from Slack Outbound: New survey response - real-time to a channel, matching what Pendo / PostHog / Sprig offer NPS detractor/promoter received Changelog entry published (channel) So essentially, a Featurebase teammate can live in Slack and trust that anything that actually needs them (a new ticket, an assignment, an SLA at risk, a status change on a post they own) will surface there, with everything else staying quiet.

Markus from Featurebase 12 days ago

8

General

Next

Native Enterprise SSO & SCIM Provisioning (SAML, Entra, Okta, Auth0)

Plug-and-play SSO and user provisioning for IT teams, without custom JWT setup. Covers: SAML 2.0 SSO with Microsoft Entra ID, Okta, Auth0, Google Workspace, and other major IdPs SCIM Directory Sync to auto-provision, update, and deactivate users when they join, change roles, or leave (full Joiner / Mover / Leaver lifecycle) IdP group to role mapping (e.g. Entra AD groups → Manager, Contributor, custom roles), so role changes flow in automatically Works with public portals, so internal team SSO doesn't require making your roadmap private

Markus from Featurebase about 2 months ago

4

General

Planned

Official Developer program for integrations

We’re considering launching an official integration partner program for Featurebase. The goal would be to make it easier for other software companies to build, review, and launch integrations with Featurebase and for our customers to discover trusted integrations. This could include: A public integrations directory Partner-built apps reviewed by Featurebase Clear API, webhook, and OAuth guidance for integration builders Sandbox or test workspace access for selected partners A launch/review process for new integrations Co-marketing opportunities for useful customer-facing integrations We’d love to understand what would make this most valuable.

Markus from Featurebase 2 days ago

General

Allow "Let Fibi answer" block to respond to previous messages in workflow

I want the "Let Fibi answer" workflow block to be able to process and respond to messages sent earlier in the conversation, specifically those sent before a "Collect data" or other pausing block. Currently, if a lead sends a message and then fills out a form, Fibi ignores the initial message once active. It should remember the initial input so leads don't have to re-ask their questions, making the experience more frictionless.

Josh Biller 15 days ago

Support platform

Add widget heading level setting to prevent duplicate H1 tags | widget H1 tag creates double H1 on website

Provide a configurable setting for embedded widgets to downgrade internal h1 elements, such as greeting text, to h2 or another SEO-friendly alternative. This would help avoid duplicate h1 tags on crawlable pages and reduce SEO issues reported by search engines. Currently this causes a website pages (using Messenger widget) to have two H1 tags, which they state confuses search engines and negatively impacts SEO. Similar issue has been encountered with Intercom. Double H1 issue will be noticed by search engines like Bing.

Tina Liu about 22 hours ago

Support platform

Default new admin/team posts to an internal board (per-user default board)

When a team member (admin) creates a new post in the dashboard, the board selector currently defaults to a public/customer-facing board (e.g. "Feature ideas"). This creates a real risk of accidentally publishing internal-only ideas to customers before they are ready. Ideally there should be a feature to remember the last board or set a default one.

Petra Mo 26 days ago

Feedback & Roadmaps

Toggle Modes for Copilot - Read & Write / Action-Specific Options

It would be great to have a toggle feature in Copilot that allows users to switch between different modes such as Read-only, Draft creation, Posting, and Ticket management. This would make Copilot more predictable and tailored to users' specific needs, improving workflow efficiency when using AI assistance for various inbox tasks.

Erik Kaljumäe 8 days ago

Support platform