Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3486 Ideas

    NickBxNew Participant

    Fin Tagging in Conversation Notes for AI Re-engagementSubmitted

    Problem Statement: Currently, when Fin (Intercom's AI agent) hands over a conversation to human team members, it cannot be re-engaged to assist further in that conversation. This limits our ability to leverage Fin's capabilities for follow-up tasks, information gathering, or customer communication during ongoing support cases.Proposed Solution: Enable @fin tagging functionality within the internal notes section of conversations, similar to how team members can be tagged with @mentions. This would allow human agents to give Fin specific directions and tasks after handover has occurred.How It Would Work: Team members could type @fin followed by instructions in the conversation notes, and Fin would receive and act on these directions immediately.Use Cases & Examples:Information Gathering: @fin - please can you find out more about how the customer has their caching setup? Customer Communication: @fin - please can you respond to the customer and thank them for their patience while we investigate. Technical Follow-up: @fin - I've found a problem with the WP Rocket plugin, ask the customer if we can change the Cache life-span value to one week. Documentation Requests: @fin - can you send the customer our guide on SSL certificate installation?Benefits:Seamless collaboration between AI and human agents Faster response times for routine tasks Reduces human agent workload for standard communications Maintains conversation context and continuity Leverages Fin's knowledge base access during complex casesExpected Outcome: This feature would create a hybrid support model where human expertise and AI efficiency work together throughout the entire customer journey, rather than being limited to initial contact only.

    Nurit
    Innovator ✨
    NuritInnovator ✨

    Workflows ImprovementsSubmitted

    Workflows are an excellent tool that we frequently use for our custom bot and back-office operations. I would like to suggest a few enhancements we find missing in our work and could improve them.Custom triggers - the ability to trigger a workflow based on different activities or attributes. for example, a change in a user data attribute , a back office ticket closed or reopened, or a teammate status change.Additional actions - one example is a code block, which would be very helpful for custom functions. Other examples are opening or closing a ticket, reopening a conversation, random split (for example, randomly assigning a conversation to several teammates and not teams), and setting people's data.Additional filters - some of the filters we searched for - customer has any open conversations/back office ticket, customer has contacted x times in the last x hours/days, “customer visits a page” filters to the customer visits a page trigger, is the conversation linked to a back-office/tracker ticket.Additional dynamic parameters - such as conversation ID and intercom's user ID.A link as a reply button.Loopback flow - the ability to go to a different flow and return to the same point in the original flow.Version management - the ability to restore older versions.   Duplicating a workflow from the test environment - We usually test workflows first in our test environment, having the option to duplicate it to our regular workspace will be very efficient.The ability to publish a flow with "floating" not connected boxes.Pause/publish workflows from the workflows home page.