By Featurebase

Featurebase

What it does

Featurebase combines a shared customer-support inbox with a help center, feedback collection, public roadmaps and product updates. A team can respond to a question, record the related request, and later show customers what changed. The support workflow is the reason it fits Help Desk, while the product tools extend that conversation into planning and announcements.

Category
Help Desk
Last updated
Oct 20, 2026
Featurebase · Editorial illustration
Conceptual paper-and-clay illustration of customer messages moving through a shared support inbox to feedback and a product update.

Work at Featurebase?

Help customers find accurate information about your software.

Manage this listing →

Find your fit

Who it is for

It is aimed at SaaS support and product teams that want one place for conversations and requests. A small team can start with chat and an inbox; a larger team should map who answers conversations, who triages feedback and who publishes roadmap or update information.

Teams replacing a support mailbox should check the exact channels they rely on. Featurebase documents email and an in-app Messenger, but its current support page still calls the Slack inbox channel coming soon. Test actual channel availability before promising one queue for every source.

Back to sections

The work it supports

Core capabilities

The inbox brings customer conversations into a team workspace. Support email can feed it, and the embeddable Messenger can expose live chat, articles and updates inside a product. Internal notes and mentions help teammates coordinate a reply without turning the internal discussion into a customer message.

A Help Center can publish branded articles on a public page, while the widget surfaces those articles beside chat. Set up a few common questions first, then check whether customers can find an article and still reach a human for an unresolved issue.

Feedback can arrive through a customer portal, in-app widgets or integrations. Product teams can organize requests and show a customer-facing roadmap; updates can then be published in the app, on the website or by email. Agree on who changes request status and what a public roadmap promises before exposing it broadly.

The support page also presents internal notes, mentions and service-level tools. The current pricing grid places SLAs and workflow automation with Professional, so a pilot should use the intended plan when checking assignment, priority and reporting rules.

Back to sections

Understand the offer

Pricing and getting started

The current pricing page lists a one-seat Free plan with live chat, a unified inbox and unlimited conversations. Growth, Professional and Enterprise are paid per-seat plans, and the captured pricing view shows yearly billing. Count teammates who need access and confirm the billing selector, currency and exact rights before choosing a tier.

The paid-plan grid shows a separate $0.49 per AI resolution charge, while Free says AI is not supported. Professional lists workflows, round-robin assignment and SLAs. Treat AI use and richer routing as plan-and-usage decisions, and ask the vendor how resolutions are counted before enabling automated replies.

Back to sections

Look a little closer

Before you choose

Run a small end-to-end trial: send a support email, open a Messenger conversation, add an internal note, turn a recurring question into a Help Center article, and log a related product request. Check which steps your chosen tier supports and what customers can see in the portal.

If Slack is a required intake channel, get a current availability confirmation: the support page labels it coming soon. Review seat, AI-resolution and Professional feature costs together so the pilot reflects the way your team would actually operate.

Back to sections

7 distinct sources behind this profile. Research observed Oct 20, 2026. Features and offers can change.
View sources and research →

Help keep this profile useful

Spotted an outdated detail? Send the correction with a supporting source. A verified account is needed to submit.

Suggest a correction ↗