Control Help Center article visibility and audience access through the API and MCP, and unpublish live articles without deleting them. This would let teams manage access and take outdated content offline from their own tools or AI workflows.

Markus Palm 5 days ago

Knowledge is currently split between Help Center articles and Fibi AI Agent Training Data. They live in separate dashboards, use different content models, and cannot be searched, maintained, or automated as one source of truth. Create one Knowledge dashboard for all reusable support content, similar in concept to Intercom's Knowledge workspace. Common content types: public Help Center article, internal article, snippet, uploaded document, and external source. Choose where each item is used: Help Center, Fibi, and Copilot. An internal or Fibi-only article must never be publicly visible in the Help Center, but should be available to Fibi when answering. Unified management: search, filters, folders, bulk actions, and configurable columns for type, collection, audience, publication status, language, author, last updated date, and where the content is used. Consistent editing and lifecycle: one formatting model, drafts and publishing where relevant, source freshness, and clear ownership. Complete API and MCP coverage: list, search, create, update, delete, publish, and manage metadata for every supported content type. The goal is to stop treating public documentation and AI knowledge as separate systems. Teams should be able to create knowledge once, control who or what can use it, and maintain everything from one place.

Markus Palm about 1 month ago

Today, "disabling" the Help Center only removes the module from the portal menu (Settings → Branding → Portal menu → Delete). The content itself stays live, so after disabling it customers still see: Articles suggested during ticket and conversation creation. Articles reachable and indexable on the public Help Center URL. The expectation is that deactivating a module makes its content and all linked functionality inactive, in one action. Requested behaviour A single workspace-level switch that takes the Help Center fully offline: no article suggestions in the Messenger or ticket forms, no public article URLs, no search-engine indexing. Apply the same principle to the other modules, so turning one off never leaves a surface still serving its content. Make the current behaviour explicit in the interface, since the existing control is a navigation change rather than a content switch. Current workarounds are partial: the Messenger Help module and article search card can be turned off individually in Settings → Support → Messenger → Customization, and articles can be restricted to Team members one at a time, which removes them from suggestions and search indexing but cannot be applied in bulk. Raised by a customer evaluating Featurebase who deactivated the Help Center and found the articles still active.

Stefan Pasel 18 days ago

We’re trying to get our Help Center articles to appear in Google search and other external/third-party AI search results. They rely on JSON schemas that are usually inserted into the HTML of the page. Here’s some details: https://201creative.com/structured-data-ai-search/

Micah 26 days ago

Requested on a demo call: more color options, text sizing, and a highlight option for Help Center article text. This matters both for branding consistency and for ADA/accessibility compliance, since the current color options are limited.

Jarrod Biggins 15 days ago

We currently use helpscout and they have a nice option to open a specific knowledge base article using various display styles: modal, in the messenger, etc. Read more here: https://developer.helpscout.com/beacon-2/web/javascript-api/#beaconarticle This allows us to surface relevant help articles directly within our product, one-click away. It is a must have for us before we can migrate our help center to Featurebase.

Mathias Le Scaon 17 days ago

Migrations

Add the ability to set a specific text size (roughly 10pt to 48pt) on any text selection in the Help Center article editor, independent of the H1/H2/H3 heading levels. Today, text sizing is tied to heading levels only \u2014 there's no way to bump body text up or down a couple of sizes for emphasis or readability the way most text editors (including Zendesk's) allow. Related: there's also an existing request for full colour-wheel/hex selection in the same editor (https://feedback.featurebase.app/p/helpdocs-color-palette) \u2014 both come from the same underlying need for finer text formatting control when producing reader-friendly articles. Raised during an active enterprise trial migrating from Zendesk (iClassPro).

Robi Rohumaa about 1 month ago

Add session-level metrics to Help Center analytics \u2014 specifically number of sessions and average session duration, similar to what Zendesk's Self-service dashboard provides. Current Help Center analytics cover unique visitors, top pages, traffic sources, devices, and browsers, but there's no session-based reporting today. Teams migrating from Zendesk rely on these numbers for their existing self-serve support reporting and need parity to switch over confidently. Raised during an active enterprise trial migrating from Zendesk (iClassPro).

Jarrod Biggins about 1 month ago

Migrations

We need a way for staff or readers to flag an incorrect translation on a published Help Center article, plus a dashboard view where flagged items can be reviewed and actioned by the content team. Today, fixing a bad AI translation relies on someone noticing it and knowing to manually go correct that specific locale in the editor \u2014 there's no in-context flagging mechanism or a queue to triage reported issues. Raised during an active enterprise trial evaluating multilingual Help Center rollout (iClassPro).

Jarrod Biggins about 1 month ago

Translations

I need the ability to hide video controls, enable autostart, and loop native video files uploaded directly into Help Center articles. This would allow for more dynamic and seamless content presentation without requiring external embeds or GIFs for simple animations.

Andreia Silva | Customer Support Associate 28 days ago

Allow video players in Knowledge Base articles to adapt to 9:16 vertical videos without pillarboxing (black bars on the sides), making it easier to display mobile app guides and walkthroughs.

William Rozenek about 1 month ago

Currently, if I have an article that needs to be pulled from the public knowledge base, my only options are to leave it, delete it, or unpublish it. Unpublished articles clutter up my drafts—preferred solution would be that “drafts” are only for new articles or ones I’m actively updating, NOT for my archived material. I don’t want to delete because sometimes I need to refer back to specific language or analytics. Thank you for considering!

Edith Henry about 1 month ago

Provide a simple tool for readers to report translation errors in the help centre. These reports should then be visible in an actionable inbox.

Jarrod Biggins about 2 months ago

Translations

Feature: Visual Diff for Article Version History Problem The current Article History only shows previous versions and allows restoring them, but it doesn't show what changed between versions. Users have to manually compare articles, which is inefficient for larger documentation. Proposed Solution Introduce a visual diff view in the version history that highlights: 🟢 Added content 🔴 Removed content 🟡 Modified content Similar to GitHub, Google Docs Version History, or Notion, users should be able to quickly identify changes before restoring or reviewing a version.

Maruf Ansari about 2 months ago

The Help Center loading times should be improved - currently the Help Center feels less snappier than it should and sometimes loads for too long, which could make end-users bounce.

Markus Palm 3 months ago

Add published Help Center URLs for every enabled language to sitemap.xml, rather than only including URLs for the default language. This would improve discovery and indexing of localized Help Center content.

Umakhan Magomedov about 2 months ago

Translations

I love that we can add emojis to collections, but I would love the ability to add images to the collections to give users a bit more visibility to the section and to make the site feel a bit more customized. Example I Found

PB Vision Team 2 months ago

I want to be able to customize or change the verbiage/placeholder text of the "Ask AI about [X]" search helper in the Help Center AI Search bar to better match our branding and preferred language phrasing.

Filament Team 2 months ago

Our customers and we are very dissatisfied with the current quality of AI search results in the Help Center: - Answers are off-topic - Answers are suddenly in English instead of German (all help articles are in German) - Typos lead to completely incorrect answers Expected solution: - We expect significant improvements in AI processing in the Help Center! - We would like to be able to customize the system prompts for AI responses in the Help Center ourselves!

Daniel Heide_NEVARIS 3 months ago

I would love if you please make an inetgration with Trupeer so we could bring help articles and videos over in one click.

Laura 3 months ago

Integrations