Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    518 Ideas

    RichieNew Participant

    Allow CC and BCC recipients to be added to Fin's outbound email repliesSubmitted

    Currently, Fin AI Agent has no way to add CC or BCC recipients to its outbound email replies. Fin can only carry forward participants that were already on the inbound thread , there is no mechanism to inject a standing address into every reply Fin sends. When human teammates reply, they can manually add CC or BCC recipients. But when Fin handles the conversation autonomously, there is no equivalent option, meaning automated responses fall outside these oversight and compliance workflows entirely. What we're asking forThe ability to configure one or more standing CC and/or BCC addresses that are automatically included on every email reply Fin sends. Ideally this would be configurable at:Deployment level — a global setting under Fin AI Agent > Deploy > Email that applies to all Fin email replies Workflow level — an option within the "Let Fin handle" step for more granular control per workflowThis would bring Fin's email behaviour in line with what human teammates can already do manually, and ensure automated responses aren't excluded from compliance, audit, and oversight processes.The reason why we are asking for this?Audit and ComplianceProvides an easily accessible audit trail that can be used for internal investigations, compliance reviews, information requests, and quality assurance activities without relying solely on the Intercom platform.Operational VisibilityAllows authorised staff to search and review AI-generated outbound communications directly within Outlook, reducing the need for additional platform access when validating customer interactions.

    SmithDJ1985New Participant

    Allow Fin to present hyperlinks in conversationsSubmitted

    When Fin answers a question by drawing from a help article, it paraphrases and summarizes the article content well, but it strips out any hyperlinks that are embedded in that article. So if an article says something like "You can create one. Here's how" with "Here's how" linking to another resource, Fin reproduces the sentence in plain text with no link. The customer never sees it.We confirmed this is a documented limitation in Intercom's own support documentation. Specifically, the following two Intercom help articles both address it directly: Fin AI Agent FAQs (https://www.intercom.com/help/en/articles/7727118-fin-ai-agent-faqs), under "Customer Experience": "Currently, Fin AI Agent is not able to present links in consistently formatted hyperlinks. You can use Guidance to encourage Fin to hyperlink where possible, but this will still depend on which sources were initially retrieved by Fin when forming an AI answer." FAQs (https://fin.ai/help/en/articles/16257287-faqs), under "Fin Functionality": "Currently, Fin AI Agent is not able to consistently present links in formatted hyperlinks." We tried the Guidance approach referenced in the first article and tested it extensively. The result is that Fin does surface some URLs inline, but it does not carry through the actual hyperlinked text from the article body. The hyperlinks in our article content are simply dropped. Our customers never see them.The workaround we were pointed toward is writing out URLs as plain text in every article body rather than using formatted hyperlinks. For a help center of any meaningful size, that is not a realistic ask. Our articles are written the way any standard help center article would be, with descriptive anchor text linking to related resources, and the expectation that those links would carry through to Fin responses is a reasonable one.What we are hoping for is straightforward: when Fin references content from an article that contains a hyperlink, it should surface that link in its response rather than silently dropping it. This would make Fin significantly more useful for customers who need to take a next step or find related information, and it would eliminate the need to maintain two versions of article formatting.Thanks for considering this. Happy to share specific examples from our testing if that would be useful.

    Maria KontaNew Participant

    FIN able to detect loops/ count turns/ conversation durationSubmitted

    What has been tried: We attempted to address this by implementing and refining a configurable looping behavioural instruction rule, including expanding the frustration signal vocabulary and broadening the trigger criteria. Testing confirmed the rule fires reliably for verbatim-repetition loops. For progressive loops — where the customer advances the conversation rather than repeating it — the rule does not fire. This is a platform-level constraint, not a configuration gap: cross-turn state tracking is not available within the current behavioural instruction layer.We are requesting a conversation-state-aware loop detection mechanism built into Fin's core runtime, with the following properties:1. Turn counting with topic continuity tracking Fin should track, across turns, whether the customer's underlying issue has changed or whether they are persisting with the same root problem. A customer who addresses the same issue across 3+ turns — even from different angles — should be flagged as looping, not just customers who repeat the same sentence. Sometimes looping shows differently accross each conversation, it may appear as progressive instead of stagnant. 2. Frustration signal accumulation Rather than a single-turn evaluation ("does this message indicate frustration?"), Fin should accumulate frustration signals across the conversation. A neutral message following two rejected or corrected responses should be scored differently than the same message at the start of a conversation.3. Conversation re-open recognition If a customer re-opens a conversation (within, e.g., 24 hours) after it was closed as assumed resolved, Fin should treat this as a strong signal that the prior session did not resolve the issue and apply a lower escalation threshold in the re-opened session.4. Time awareness Fin should be able to tell how long a customer is involved in the conversation with FIN and make a call depending on the time spent chatting to offer human assistance or not All these should be confiurable on workspace level and useable in guidance to customise FIN messaging to customer.