Updates
Support
Help Center

Share your product feedback!

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

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 from Featurebase about 6 hours ago

2

Outbound

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 about 1 month ago

8

General

Granular MCP Permissions (Read/Write)

I want dedicated permissions for MCP (Model Context Protocol) that are separate for 'read' and 'write' access. Currently, using MCP requires 'API Access' or 'Manage API' permissions, which might be too broad for certain roles like Product Managers. Having granular MCP permissions would allow us to grant AI tool access without giving full API management capabilities to every role.

ScalePad IT Administrator 11 days ago

1

General

Planned

Fibi follow-up setting customization

There should be a way to configure Fibi's follow-up behavior, including options like: Fibi will confirm whether the user still needs assistance - Fibi asks a short follow-up question after answering, such as “Did that answer your question?” Fibi will offer escalation - Fibi checks in and offers to connect the user with a teammate if they still need help. No follow-up - Fibi sends only the main answer and does not send follow-up prompts or idle nudges. Fibi, currently always sends follow-up prompts and idle nudges based on internal logic, but there is no surfaced setting to disable or customize that behavior.

Markus from Featurebase 20 days ago

Fibi AI Agent

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 29 days ago

2

General

Fibi Agent Tool & Reasoning Transparency

Problem The Fibi agent is currently a black box with no visibility into which tools are being called (especially custom actions) and behind the scenes reasoning. This makes it difficult to triage poor responsive, evaluate how effective custom action instructions are, and know if custom actions are being called or not. Vision Have an expandable section within the chat thread in the support dashboard that shows tool calls and reasoning text. Out of scope Tool call and reasoning visibility changes to the user in the chat window.

Alex Z 4 days ago

Fibi AI Agent

APIv2 Create or Update contact allow ignoring Last activity

When programmatically updating or creating a contact via the API (e.g. POST /v2/contacts), the "Last activity" timestamp of the contact gets automatically set to "now". This creates issues because updating background details (like plan names, custom fields, or tags) pollutes the actual user activity analytics. Option or parameter in the API to allow updating contact details without modifying the "Last activity" timestamp would alleviate this. This is important because it currently makes it impossible to know when the user was truly active last in the application when syncing data in the background.

Valentin from Filently 4 days ago

General

Conversation APIv2 Support for fetching RAW email contents as well

Allowing to fetch the RAW email allows to check and parse the contents externally when deemed necessary. While the API is designed to automatically truncate non-contextual content (footers, repeated thread history) - it would be still beneficial to have possibility to access the contents via programmatic way as well.

Amr from Lunch Flow 4 days ago

Help Desk

Bookmark and share default Outbound views via URL (Updates, Surveys, Banners)

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.

Luke Inderwick 6 days ago

Outbound