Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    518 Ideas

    Daniel Rönnberg
    Daniel RönnbergActive User

    Hide unused Fin roles in content settingsSubmitted

    We only use Fin for Service, but when managing which roles content should be used for, Sales, Service, and Ecommerce are all shown as options. I can turn Sales off, but Service and Ecommerce appear to be linked, meaning Ecommerce cannot be turned off without also turning off Service. Likewise, turning Service on also turns Ecommerce on.From a user perspective, this is confusing because it looks like these roles can be managed independently, even though they cannot. Since we don’t use Fin for Sales or Ecommerce, I’d ideally like the option to hide or disable those roles entirely from our workspace, or at least have clearer UI messaging explaining that Service and Ecommerce are linked.The current setup creates unnecessary friction when managing content because I have to keep seeing and accounting for roles that are not relevant to our use case. It also makes the settings feel more complex than they need to be for teams that only use Fin for support/service.Suggested improvements: Allow admins to hide or disable unused Fin roles at workspace level. Allow Service and Ecommerce content settings to be managed independently. If they must remain linked, make this explicit in the UI before users try to toggle them. Consider simplifying the content management experience for teams that only use Fin for Service. This is not blocking us from using Fin, but it adds avoidable confusion and makes content governance harder than it needs to be.

    Arunkumar KumaresanNew Participant

    Incremental / URL-Level Sync for Website SourcesSubmitted

    ProblemFor website-based knowledge sources, the current Re-sync operation performs a full crawl of the entire website.In large deployments, this can involve thousands of pages. In our case, the source contains approximately 3,600 articles. When a single new article is published, there is currently no way to make only that article available to Fin immediately without triggering a full website crawl.Requested CapabilityProvide a way to selectively sync website content instead of requiring a full re-crawl.Possible options:Sync a single URL on demand. Sync a selected set of URLs. Incremental sync that discovers only new or modified pages since the previous crawl.BenefitsFaster Content AvailabilityNewly published articles can become available to Fin immediately without waiting for the next scheduled crawl.Reduced Processing TimeAvoid re-processing thousands of unchanged pages when only one or two pages have changed.Lower Resource ConsumptionReduces crawler workload, indexing time, and system resource usage for both customers and Intercom.Better Operational EfficiencyAllows support teams and knowledge managers to quickly publish urgent content updates and make them available to Fin.Example Use CaseA website source contains 3,600+ articles.A new troubleshooting article is published for an ongoing customer issue.The administrator wants Fin to learn only that newly published page immediately, rather than initiating a full crawl of all 3,600 articles.Current WorkaroundsWait for the weekly automatic website sync. Create a temporary Knowledge Hub Snippet. Trigger a full website re-sync.None of these provide true URL-level synchronization.Expected OutcomeAllow administrators to selectively re-index specific pages or run incremental website syncs so that newly published content can be made available to Fin quickly and efficiently.

    David Coen
    David CoenNew Participant

    Add Fin Guidance and Escalation Guidance to the Intercom REST APISubmitted

    The problemWe manage Fin with a large, frequently updated ruleset: Context & clarification Guidance plus Escalation Guidance (separate objects in Train → Guidance and Train → Escalation).Today this content is UI-only. There is no public REST API to list, read, create, update, enable/disable, or delete Guidance entries — unlike Help Center articles, which we already manage programmatically via the Articles API.This creates real operational pain:No single source of truth — teams maintain a parallel wiki/repo and manually copy-paste into Intercom after every change. No programmatic audit — conversation audit events expose fin_guidance_applied with guidance id and title, but we cannot fetch that object via API to verify live text, diff against git, or detect drift. “Ghost” guidance risk — we have seen guidance applied in production (visible in conversation audit) that does not appear in the editable Train list, making it impossible to fix or retire bad rules without Intercom support. High iteration cost — when routing logic changes (e.g. buy/ramp vs gift card vs swap), updating 15–20 guidance bodies by hand is slow and error-prone (character limits, audience, channels, paused vs live). Multi-workspace sync — other customers already ask for export; we need import + update, not just export.We already automate Fin training for Help Center and Data Connectors; Guidance is the missing piece.Proposed solutionAdd REST API resources for Fin Guidance and Escalation Guidance, modeled after Articles:Suggested endpoints (names illustrative): GET /fin/guidance — list all guidance entries (paginated) GET /fin/guidance/{id} — retrieve one entry by id (same id as fin_guidance_applied) POST /fin/guidance — create PUT /fin/guidance/{id} — update body/metadata DELETE /fin/guidance/{id} — delete or archive GET /fin/escalation_guidance (+ CRUD) — separate resource for Train → Escalation tab Fields to expose (minimum):id, title, body (plain text / markdown) type or category (e.g. context vs escalation) audience, channels state (enabled | paused | draft) created_at, updated_at Optional: usage stats (used, resolved, escalated) for observabilityNice-to-haves:Deep link from Inbox audit → specific guidance id in API response Webhook / event when guidance is created, updated, or deleted MCP server support (same pattern as articles) Preview vs production workspace targeting (if applicable)Why this mattersFaster, safer Fin iteration — git-reviewed changes deployed via CI, not manual paste. Drift detection — compare live Intercom state to repo; catch ghost or stale rules. Incident response — pause or patch one guidance entry in seconds when misrouting is detected (e.g. Phaze gift-card rule matching crypto buy conversations). Consistency with existing APIs — we already manage articles and snippets are requested separately; Guidance is the core Fin routing layer and should be first-class in the API too.Related requests (complementary, not duplicate)Ability to Export Guidance — export-only; we need full CRUD + escalation Add Snippets to the Intercom API Direct API Mapping for Fin Data Connectors — our team’s related Fin automation requestHappy to share our workflow (repo mirror, deploy checklist, conversation-driven QA) if useful for prioritization. 

    Matej Bosnjak
    Matej BosnjakConnector

    Product Request: Customizable Article Reaction Workflow TriggerSubmitted

     Hello Intercom community,  When a customer clicks 😞 or 😐 on a Help Center article, Intercom automatically opens a conversation and sends a built-in reply:German:"Schade, dass du die benötigte Antwort nicht finden konntest. Möchtest du das Team noch einmal um Hilfe bitten?"English:‘It's a shame you couldn't find the answer you were looking for. Would you like to ask the team for help again?’There is currently no way to: Edit or replace this default message Trigger a Workflow at the moment of the reaction The "customer sends first message" workflow trigger never fires in this context because the built-in reaction flow opens the conversation automatically and takes over before any workflow can run.Who is affected Any team that: Uses Fin AI Agent as their primary support agent Wants to collect structured feedback on why articles fail Cares about brand tone consistency across all customer touchpoints What we want Option A - Editable reaction reply text Allow admins to customize the default message that appears when a customer reacts negatively to an article - either globally or per Help Center.Option B - Dedicated Workflow trigger for article reactions Add a new Workflow trigger: "Customer reacts to article" (with filter options for 😞 / 😐 / 😃) that fires immediately when the reaction happens - before any conversation is opened.Ideal Workflow this would unlock Customer clicks 😞 or 😐 on an article A customizable message appears asking why the article didn't help Structured reply buttons are offered (e.g. "Too technical", "Missing information", "Didn't match my situation", "Something else") A short free-text follow-up is collected based on the button selected A closing message confirms the team will review the article The conversation is assigned to a teammate internally for action Why this matters Catches missing or unclear content early - before it turns into a support ticket Provides structured data on why articles fail, rather than just a reaction count with no context Enables teams to close the feedback loop and improve content proactively Ensures a consistent brand tone across all Fin and Messenger interactions Current workaroundNone available. The built-in reaction flow cannot be overridden or customized.Thank you for your cooperation. Best regardsMatej - reevSenior Customer Support Manager

    Add customization options for the "The team can also help" text when using "Set AI Agent expectations"Submitted

    When configuring Fin under Settings → Channels → Messenger → Conversations tab → "With Fin," selecting the recommended option "Set AI Agent expectations" automatically inserts the subtitle "The team can also help" beneath the workspace name in the Messenger conversation header.This string is currently hardcoded — there is no way to edit, replace, or remove it anywhere in the Messenger or Fin settings.We'd like to see several customization options for this text:1. Custom text — the most important one. Let us provide our own wording so it matches our brand voice and support model (e.g., "Our support team is here if you need a person" or "Ask to speak with our team anytime").2. Keep the default — workspaces that are happy with "The team can also help" should be able to leave it as-is with zero extra setup.3. Hide it entirely — a toggle to remove the subtitle for teams that don't want a second line in the header at all.4. Per-language customization — the custom text should support Intercom's multilingual settings so each supported language can have its own version, just like other Messenger strings.5. (Nice to have) Availability-aware text — the ability to vary the message based on office hours or team status, so we're not promising "the team can also help" at 2 AM when no one is online.Suggested implementation: an option set within the "Choose how Fin sets expectations" section — Default / Custom text / Hidden — with a multilingual text field when Custom is selected. This would mirror how "Start conversation button text" is already editable directly below this setting, so there's an existing pattern to follow.Thanks for considering!