Introducing: Featurebase MCP server

Hey there, Featurebase MCP is finally here! You can now connect to Featurebase directly in your favorite tools, like Claude, ChatGPT, and Cursor. Ask things like “What top paying customers are at risk of churning” or “Update all help center articles with the latest information about XYZ”. It uses all the available data in your Featurebase workspace to conduct deep research or take any action you need. The possibilities are endless - analyze feedback or latest conversations, edit your Help Center, automate reporting about a certain topic, and connect with other AI tools – in a simple conversation. The MCP server is built directly on top of our public API, so anything you can do through the API, an AI agent can now do for you. No custom integrations or code needed. Available on the Professional plan. Get started today →

Inbox Command-K, Keyboard shortcuts, and Settings rework

Hey there! Excited to bring you three quality-of-life improvements focused on making Featurebase faster to navigate day-to-day. It’s the start of stepping back and polishing the overall experience, and you can expect more like this in the near future as we keep tightening things up. Command-K action menu Hit ⌘+K (or Ctrl+K on Windows) from anywhere in a conversation to open the new action palette. It lets you run all the key actions in your inbox with just your keyboard. You can: Compose replies, notes, macros, or AI responses Assign to teammates, teams, or brands Update statuses, set priority, copy transcripts Convert conversations to customer or back-office tickets Link tracker tickets (internal or public) right from the palette It replaces the old basic ⌘+K with a single shortcut for almost anything you do inside a conversation. Keyboard shortcuts Featurebase now also has keyboard shortcuts throughout the support inbox. A few of the most useful ones: R - Compose a reply N - Compose a note M - Use macro Q - Draft an AI reply Z - Snooze A - Assign J / K - Move between conversations [ / ] - Toggle sidebars …and plenty more. Press ? anywhere in the inbox to open the full cheatsheet. Settings rework Lastly, we've improved the Settings to make them simpler, faster, and much less cluttered as Featurebase has grown. Four clear sections: Personal, Products, Workspace, and Data Settings for products you don't use stay collapsed, so you only see what's relevant Consistent layout, icons, and sub-navigation across every page Everything you'd expect to find is still there, just in the place you'd actually look for it! Other API for email notification management (opt in/out) Dropdown selectors for predefined values in Workflows

Introducing: Tickets in Featurebase

Not every customer issue is a quick chat. Some take time, need input from multiple teams, or affect many customers at once. That's where tickets come in. Tickets let you turn conversations into structured, trackable work items with statuses, assignees, and custom fields - so your team stays organized and your customers stay in the loop throughout the entire resolution process. Your Featurebase Inbox now handles both: Conversations - for simple queries that can be handled quickly (e.g. "How do I delete tags?") Tickets - for complex async queries that take time, require investigation, or need collaboration (e.g. "My bill is incorrect, please issue a refund.") Three ticket types for every workflow Complex queries come in different shapes and sizes. That's why Featurebase offers 3 ticket categories, each optimized for a different use case: Customer tickets - private conversations between your team and a customer for async requests where the customer can track progress and receive updates. Best for refund requests, account changes, and any other issues where users need visibility into progress. Back-office tickets - internal tickets for behind-the-scenes collaboration across teams, without involving the customer. Best for engineering escalations, billing investigations, etc. Tracker tickets - internal tickets for shared issues affecting multiple customers. When you update the status of a tracker ticket, it automatically updates all linked customer tickets at once. Best for tracking known bugs and service outages. Learn more about the three ticket types → Ticket Portal The Ticket Portal is a dedicated page where customers can submit new tickets, view existing ones, and track progress. It lives alongside your Feedback board, Changelog, and Help Center, so everything is in one place for your customers. Learn more about the Ticket Portal → Tickets in Messenger The Messenger widget now supports a dedicated Tickets tab where customers can view their tickets, see real-time status updates with a visual progress bar, and follow up on requests - all without leaving your product. Fully integrated with the Featurebase suite Tickets work with everything you already use in Featurebase: Workflows - automate ticket routing, auto-close stale tickets, send ticket forms in the Messenger, or convert conversations to tickets automatically Integrations - connect tickets with Linear, Jira, HubSpot, ClickUp, GitHub, and more to streamline collaboration across tools Feedback portal - Our AI automatically suggests users to post ticket topics (e.g. bug report/refund request) under the dedicated Ticket Portal, making sure your public Feedback forum doesn’t get cluttered with sensitive issues SLAs - set ticket SLAs to track your team's response and resolution times Multilingual support - Automatically translate customer tickets to provide in users native languages Lite seats - let back-office teams access Featurebase for free as collaborators to help resolve tickets User & Company profiles - all tickets appear as a dedicated tab in user and company profiles for full customer context Multi-brand - create and manage tickets across multiple brands from a single workspace Get tickets that keep the conversation going ✨ Get started with tickets today →

{Dynamic variables} across Featurebase

Hey there from earth! Dynamic variables are here. You can now personalize messages, changelogs, surveys, and more by automatically inserting customer data like {first_name} and {company_plan} details. Just type { in the editor to insert a variable. You can also set a fallback value so even if customer data is missing, your messages always read naturally. You can use dynamic variables in: Macros and message templates Workflows Changelogs and Surveys Messenger greetings Make every customer interaction feel personal, without the manual work! Learn more: @Dynamic variables in Featurebase Other releases "Select all" bulk select option for filtered post lists Admins can add follow-up questions when upvoting on customers behalf

Merge user profiles & more lead data

We've made it easier to keep your user data clean and give your team more context when helping customers. Merge user profiles You can now merge leads into existing user profiles so all conversations, attributes, and history are stored in one place. You can merge profiles in two ways: Manually update a lead’s email in their profile to match an existing user Merge potential duplicates directly from the Inbox when a duplicate warning appears during a conversation In many cases, profiles will also merge automatically thanks to browser cookies. Learn more here → More automatically captured lead data The Messenger now automatically collects metadata about your contacts, helping your team provide faster and more relevant support without asking extra questions. You'll now see: Recent page views - see exactly what pages someone was browsing before reaching out Browser info - name, version, and language settings System info - operating system and location details Language preferences - any language override settings if set This data is automatically captured when someone interacts with the Messenger on your website. Other Redirect old help article links to the new help center Change account email address without workarounds

Multi-board Linear & Jira syncing

You can now sync Featurebase with multiple Linear teams and Jira projects, with fully customizable sync rules per feedback board. This means each board can have its own sync behavior tailored to how your team actually works. You can now: Sync each feedback board with a different Linear team or Jira project Define unique status mappings per board, for example: 🐛 Bug Reports - Done → Fixed 💡 Feature Requests - Done → Shipped Set default Jira issue types (feature, epic, task) per board This finally gives your product and engineering teams full flexibility to tailor sync behavior to how they actually work. Learn more & get started: Linear / Jira integration

Multi-brand support for Messenger & Help Center

You can now support multiple brands, products, or companies from a single Featurebase workspace. Multi-brand support lets you create separate Messenger styles and Help Centers for each brand, while keeping your support operations centralized. With multi-brand support, you can: Create multiple brands with their own logos, colors, and sender emails Show a different Messenger style based on the website domain Run separate Help Centers with unique domains and customization Manage all of it from a single Featurebase workspace This is ideal if you manage multiple products under one company or operate different brands with shared support teams. Learn more & set it up: Multi-brand support → Multi-brand support is currently not available for the Feedback, Roadmap, and Changelog products, but it is on our roadmap! Feel free to upvote it, so we know to prioritize it.