Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3157 Ideas

    Diana OnepageNew Participant

    Customizing Fin’s "Did that help?" auto-reply for complex workflowsSubmitted

    The IssueFin automatically sends the "Did that help?" prompt after every response. When customers say "Yes," the conversation closes immediately. This breaks workflows where Fin provides an explanation but still needs to collect data or perform a handover.Example: Customer: "I want to change my email." Fin: Explains the requirements and asks: "Please provide your new email. Did that help?" Customer: Clicks "Yes" (out of politeness). Result: Fin closes the ticket before the customer can provide the email. This leads to negative CSAT and duplicate tickets. Requested Improvements Toggle Auto-Reply: Ability to disable the "Did that help?" prompt for specific Procedures or Intents. Logic-Aware Closing: Fin should recognize if he just asked the user for information; in these cases, the success prompt should be suppressed. Custom Follow-ups: Allow the "Yes" button to trigger a specific next step in some cases (not for all conversations) instead of an immediate close. Business ImpactReducing "premature closures" will significantly improve CSAT and prevent customers from feeling "shut out" by the bot, while maintaining the efficiency of Fin’s pre-qualifying explanations. Previous Workaround (Inefficient)To prevent this, we previously marked these intents as direct handovers. However, this meant agents had to handle the basic explanations themselves. We want to keep Fin’s efficiency in explaining the process (which works in 90% of cases) without him prematurely "killing" the conversation via the success prompt.

    Michael LeighNew Participant

    Sync Banner content to Fin AI knowledge baseSubmitted

    When a Banner is active in Intercom, teams should have the option to make its content available to Fin as a knowledge source. When the Banner is paused or deleted, that content should be automatically removed from Fin's knowledge base without any manual steps.The problemBanners are commonly used to communicate important product changes, outages, or announcements. In practice, many customers dismiss or skim banners without fully absorbing the information. This generates avoidable support volume — customers contact support asking questions the banner already answered.Fin has no visibility into active banner content today, so it cannot answer these questions accurately or consistently, even when the information is current and relevant.There are existing workarounds — such as creating a snippet or article with the same content — but these require manual cleanup after the banner is removed. Without that cleanup, outdated information remains in Fin's knowledge base, which creates a different problem.The proposed behaviourWhen creating or editing a Banner, an option is available to include the banner content in Fin's knowledge base. When that option is enabled and the banner is published, the content is automatically added as a contextual source for Fin. Fin can reference that content when responding to related customer questions while the banner is active. When the banner is paused or deleted, the content is automatically removed from Fin's knowledge base — no manual cleanup required.This closes a gap between what customers are told through banners and what Fin can actually answer. It reduces support volume during product change windows, improves the accuracy of Fin's responses, and removes a manual process that teams would otherwise need to manage themselves.