Please tell us what we can do to make Featurebase the best product for you.
Waiting on customer
Offline support for the feedback widget and mobile app feedback
Field teams using a mobile or iPad app often have low or no connectivity. We want the in-app feedback widget (and support help entry point) to work offline: capture the report, screenshot and context locally, then upload and sync automatically once the device is back online. Native or embeddable support for iPad and mobile apps would also help, instead of relying on an iframe workaround.
Configure how portal footer links open
Workspace admins should be able to choose whether external footer links open in the same tab or a new tab. Currently, regular footer links open in the same tab, and the help-center link settings do not control them. Add this option to the shared footer settings.
Keep conversations with Featurebase support private within a workspace
When a workspace member contacts Featurebase support, other teammates with access to the workspace can currently view that conversation. Please add a private conversation option for messages sent to Featurebase support. When selected, only the person who started the conversation and the Featurebase support team should be able to view it. The sender should be able to share the conversation with workspace teammates later if needed. This would let people safely contact Featurebase about sensitive topics such as billing, account access, commercial questions, or private product feedback.
Show unsubscribes count and rate per email send
Display an unsubscribe count or unsubscribe rate for each email send. Today this number has to be tallied manually, which is inefficient and error-prone. Beyond the per-send figure, provide unsubscribe analytics per email or unsubscribe action, as well as total subscribe and unsubscribe metrics tracked over time.
Multiple customer SSO configurations per Workspace
Allow a Featurebase Workspace to configure and manage multiple customer-facing SSO setups instead of relying on one global SSO login URL and JWT configuration. This would support companies that have multiple products, brands, portals, or customer identity systems within one Workspace. Each SSO setup should be able to have: Its own login URL and JWT verification configuration Routing rules that associate it with specific brands, custom domains, Messengers, Help Centers, or public portals Support for returning the customer to the correct surface after authentication Featurebase should resolve the appropriate SSO setup from the active brand or domain while keeping the customer data and product configuration centrally managed in one Workspace. This request concerns customer-facing SSO and is separate from Enterprise SSO used by teammates to access the Featurebase dashboard.
Support consistent `sortBy` / `updatedAt` sorting across all API v2 endpoints
Allow API v2 list and search endpoints (such as `POST /v2/conversations/search`) to support sorting by `updatedAt` / `recent` so developers can reliably fetch and poll for incrementally updated records.
Heap integration
Support a native integration between Heap and Featurebase. Connect Heap's product analytics so usage and behavioral data can guide which feature requests get prioritized, and analyze Featurebase activity alongside Heap events.
Support multilingual password reset screens and emails
Extend portal language support to the hosted password reset screens, confirmation messages, and password reset emails. These currently use English and do not follow Multilingual settings. They should use the portal user’s selected language.
Export and import organization settings and automations for full environment backup
Allow exporting and importing full organization configuration, automations, and settings (including workflows, SLA rules, conversation attributes, and related configs) via JSON / API to support external backups and configuration syncing.
Option to disable user creation via SDK (API-only user management)
Add a setting for the widget/SDK integration to disable automatic user profile creation during SDK identification. When enabled, the SDK would only identify existing user records created via the API or dashboard, preventing unintended profile creation or ID reassignments via the widget.
Allow userId to take priority over email when syncing contacts via API
Provide an option or update contact sync behavior so that userId acts as the primary identifier. If a synced user's email address matches an existing record with a different userId, the sync should update the record by userId rather than failing with "User ID already taken".
Add translation usage breakdown
Provide an itemized breakdown of translation character usage by source, including Inbox, Feedback Portal, and Help Center, to make unexpected usage spikes easier to investigate.
Umami integration
Support a native integration between Umami and Featurebase. Connect Umami's privacy-friendly web analytics so traffic and usage trends can inform how feedback and feature requests are prioritized.
Granular API key permissions (read/write & module-level access)
Allow admins to create API keys with customizable permissions, such as read-only access and module-specific scope (e.g., changelogs, feedback, permissions).
Planned
Install Featurebase once and enable widgets from the dashboard
Users should be able to install Featurebase once, then enable Messenger, Feedback, Update, Banner, and Survey widgets from the dashboard without needing another engineering deployment for each one. This would make it much easier for non-technical teams to adopt more of Featurebase over time, while keeping custom code optional for custom placements.
Metabase integration
Support a native integration between Metabase and Featurebase. Bring Featurebase feedback, voting, and roadmap data into Metabase to build custom dashboards and analyze feature demand next to other business metrics.
Firebase integration
Support a native integration between Firebase and Featurebase. Sync product usage and analytics from Firebase so feature requests can be prioritized by real app behavior, and attribute feedback to Firebase users.
Power BI integration
Support a native integration between Power BI and Featurebase. Bring Featurebase feedback, votes, and roadmap data into Power BI to build reports and analyze feature demand alongside other business metrics.
Bug: MCP used with custom fields
Just tested MCP with ChatGPT and had a problem with custom fields. ChatGPT ist stating: In the MCP tool POST /v2/posts, customFields is defined as Record . However, Featurebase’s API expects a single string for text custom fields. This makes text fields such as Topic ID and Parent ID impossible to set via MCP: arrays are rejected by the Featurebase API, while single strings are rejected by the MCP schema validation. Please update the MCP schema to support field-type-specific values, so text fields accept a string and select or multi-select fields use the appropriate value format.
Connect multiple Featurebase Workspaces to one Salesforce organization
We use three separate Featurebase Workspaces for different parts of our business, while all teams share one Salesforce organization. Currently, the Salesforce integration only allows one Featurebase Workspace to connect to that Salesforce organization. We would like to connect all three Workspaces to the same Salesforce organization. Desired outcome Connect multiple Featurebase Workspaces to one Salesforce organization. Keep customer data, feedback, Cases, and Opportunities associated with the correct Featurebase Workspace. Choose or clearly see the relevant Featurebase Workspace when using Featurebase inside Salesforce. Why this matters Our products are separated across Featurebase Workspaces, but Salesforce is our shared CRM. The current one-to-one limitation means only one of our teams can use the native Salesforce integration.