Backlog
57Under consideration
Manage Fibi custom actions via API & MCP
Create and update Fibi custom actions through the API and MCP. This would let an AI agent configure and maintain actions without having to complete each setup through the dashboard.
Improve Fibi's resistance to completing unrelated tasks
Improve Fibi’s resistance to use as a general-purpose assistant. Fibi should decline unrelated tasks, such as translating personal messages, and redirect users to company support topics. Visitors can currently abuse Fibi as their GPT alternative in certain scenarios.
Toggle to allow or disallow images in Fibi responses
Add a setting to control whether Fibi can include images in responses. When disabled, Fibi must send text-only replies, including no separate image galleries or email image attachments.
Option for AI Agent to look for in a specified collection of articles for a workflow
If i have 3 Workflows for A, B, C, i would like Fibi AI agent to only look for in the corresponding collection of article. If the workflow A is running, Fibi AI agent should only look in the A collection articles, etc. Today he is mixing collection in this anwser leading to totally inconsitent answer. We’ve tried to be strict in his prompt but it still happen sometimes.
Configurable crawling interval and manual force recrawl for Fibi training data
Allow setting custom automatic recrawling intervals (e.g., daily or multiple times per day) for website training data sources like status pages, along with a direct button to force an immediate recrawl.
AI conversation attribute categorization without Fibi as a step
I want AI conversation attributes to categorize and route conversations based on their meaning, without requiring a 'Let Fibi answer' step or a reply to the customer first. Exact keyword matching is not reliable enough. For example, we route incoming emails to either our Questions or Bugs team. Questions should use our documentation to answer the customer. Bugs need diagnostic questions to collect the missing details, then a faster handoff to a human. The AI should first read the email silently, set the relevant conversation attributes, and let the Workflow route it to the correct team and instructions. Fibi can then reply if that branch requires it, or the conversation can go straight to a human.
Git repository integration for AI agent training data
Connect a Git repository (GitHub, GitLab) as a first-class knowledge source for the Fibi AI Agent, so that training content is maintained where the documentation already lives. Requested behaviour Connect one or more repositories and select file patterns (for example docs/**/*.md). Re-index on push, and show the diff between the previous and current version of each training file so reviewers can see exactly what changed. Preserve manual edits made in Featurebase across re-indexing, rather than overwriting them. Report per-file index status so a failed file is visible without opening every entry. A customer evaluating Featurebase raised this after comparing with Gleap's Code Repositories feature, where a connected repo generates knowledge entries automatically on each re-index and manual edits are kept. Today the Training Data API and MCP make this possible to build from the customer side using stable externalId values, but there is no native connector, no change detection and no diff view. Related: Source Markdown Files from Git Repositories (Help Center scoped) and APIv2 for Fibi Training Data Management.
Option to whitelist crawler IP addresses or User-Agent for website training data
Allow teams to whitelist the Fibi website crawler in their WAF/firewall by providing a published list of crawler IP addresses or a dedicated User-Agent string.
Fibi AI agent automatically create feature requests from conversations
I want an option or setting to let Fibi AI agent automatically create feature requests/posts in Featurebase directly from customer conversations. This is important because it would fully automate logging feedback.
Custom Actions for Support Agent Copilot
I would like the support agent Copilot to have access to the same custom actions that Fibi can use. This would allow me to run actions, such as checking user permissions, directly from the Copilot interface during a conversation. It makes sense for these actions to be available to both Fibi and the support agent Copilot, enabling me to provide full support within the chat without needing to switch to a different system.
Planned
4Committed and queued
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.
AI-detected conversation tags
Allow Fibi to automatically set conversation tags based on conversation context, similar to how conversation attributes can currently be detected and updated by AI. Today, tags can be applied through workflow rules such as keywords or explicit tag actions, which does not cover cases where the correct tag depends on understanding the full conversation.
Support Messenger User Context
The ability to provide the support messenger AI with additional contextual data about the user. This could be taken from their user attributes or passed to the support module at the time of sending a message. User Cases The user does/doesn’t have a subscription and therefore the AI can respond apprioty when a user asks about a paid feature (not saying they already have it when they don’t and vice versa). Knowing which page the user is currently on and maybe even more specific details. A user will often ask about something they are currently looking at and the AI should be aware of that. A user might be using an old version of your software, the AI should know this so that debugging can be aware that the problem has already been fixed in a newer version.
Automatic article gap detection for Fibi AI
Scenario Sometimes Fibi can’t answer a of question specific topic due to Help Center article not existing for that topic. If many similar un-answerable questions accrue, then Fibi should be able to create a Request for an Article for given topic, so it can be more helpful in the future. Solution Unanswered topics section in the Inbox with an option to Create an article for the topic Fibi will convert unanswered questions, that seem relevant to the product, into topics that will be collected into the Unanswered topics section
Next up
2Committed and queued
Fibi AI Table Parsing in Help Center
I want the AI agent (Fibi) to be able to read and extract information from tables in the help center. Currently, it seems to only process plain text, which means important data stored in tables is missed during AI searches and chat interactions. This is important because many of our technical specifications and pricing details are in tables.
Have Fibi index content from Help Center's FAQ elements
Currently, Fibi (and probably Help Center AI) doesn’t index and use info from the Help Center accordion elements used for FAQ. It’s super important to get this fixed, as we’re getting questions that are not answered but are documented.
In Progress
1Actively being built
Done
23Recently shipped
Reliable bulk upload of Fibi training files
Uploading more than two training files at once in Dashboard → Automations → Training Data is unreliable. Files fail very quickly and land in a Failed state, even for small files (for example a 1.8 KB Markdown file that reported 0 words). Failed files then have to be removed one by one and re-uploaded, which makes seeding an agent with a real documentation set slow and error prone. Requested behaviour Multi-file selection should upload reliably, with queueing or throttling instead of parallel failures. Show the actual reason a file failed (size, type, conversion error, rate limit) rather than a generic Failed label. Offer a retry action on failed files instead of requiring manual delete and re-upload. Reported by a customer evaluating Featurebase who is loading a Markdown documentation set into the AI agent.
Fibi should not respond to every Slack message
Fibi can reply to Slack messages even when they aren't questions and no assistance is needed. In one example, it replied to a message explicitly saying a response wasn't wanted, then replied again to a short “See” follow-up. Fibi should recognize when to stay quiet instead of engaging with every message. This would reduce unnecessary bot replies and let normal customer conversations continue naturally. When uncertain, it can lean toward answering, but it should skip messages that clearly don't need a response.
Improve Fibi accuracy, reliability & speed
Rework customer support AI Fibi to be more reliable and fast.
Exclude specific modules (Changelog/Feedback) from Fibi AI training
I want to be able to exclude specific modules (like the Changelog) from Fibi's training data. Currently, all changelogs are automatically indexed, which can lead to outdated information being used in AI responses. Having a toggle to disable certain modules or specific posts from training would help ensure more accurate and refined answers.
Reduce AI Agent Latency
I want the AI agent to respond much faster. Currently, the latency is too high, which creates a poor experience for users. This seems to be a general issue rather than account-specific.
Train/correct Fibi AI on its existing answers
Allow teams to select existing AI answers and use them as training signals for future responses by clicking “Improve answer” and inserting the ideal answer. This would let teams tell Fibi “this is the correct answer” and have it respond similarly next time, without needing to update help articles or add separate guidance.
Setting to Control Fibi's auto-solving (auto closing) and conversation resolution
I would like to turn off the auto-solving questions from Fibi AI. Specifically, I'd like for Fibi to leave questions open until a human manually closes the conversation, not marking anything as resolved automatically. Additional improvement would be to customize the timer before closing the conversation as well.
AI conversation attribute categorization
Use Fibi AI to automatically classify incoming conversations into defined attributes - so you can route faster and act smarter. Automatically fill in custom fields like product, priority, or issue type based on conversation content with AI to save time for human agents.
Internal AI reference codes are visible to end-users in support messages
As a user, I am seeing internal reference codes, like [REF-RESEARCH:XYZ], in the support messages from the AI bot. These codes should not be visible to end-users as they are confusing and serve no purpose for them. This seems to be a bug in how the AI agent's internal markers are processed and displayed.
Fibi isn't asking for email on hand-over & when anonymous users try to submit Posts
When anonymous posting is disabled Fibi AI should ask for email before allowing to submit a feature request / a feedback post - currently it isn’t asking for email and allows to directly submit Posts without identification It should be asking for an email on hand-over as well