Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    518 Ideas

    Roy
    Top Expert ✨
    RoyTop Expert ✨

    Why Fin Needs a "Persona-Based" Architecture 🎭Submitted

    Hey everyone! 👋 I’ve been diving deep into the new multi-role capabilities for Fin, and while the "one agent for everything" approach is a great start, I believe the next evolution of Fin should be Persona-Based. Right now, we have one "Fin" with one name and one tone across the whole journey. But in the real world, a customer's needs change as they move from the storefront to the support queue. Here’s why I think Intercom should develop the ability to define distinct Personas (e.g., "Mike" for Sales vs. "Thomas" for Support): 1. Trust is Built on Context 🤝A "Sales" persona needs to be proactive, persuasive, and high-energy 🚀. A "Support" persona needs to be empathetic, cautious, and technical 🛠️. Using a single "Humorous" or "Professional" tone for both feels like a compromise. 2. Visual Continuity & Human-Centric Design 🖼️By allowing us to set different Names and Avatars for different services: For Sales: A friendly face (Mike) that feels like an account executive. For Support: A specialist identity (Thomas) that signals expert assistance. This helps customers mentally "switch gears" and sets the right expectation for the conversation.  3. Specialized "Tool-Belts" for Agentic AI 🧰If we treat these as separate personas, we can define specific Permissions and Data Connectors for each: Mike (Sales) could have access to HubSpot or Salesforce to check lead status 📈. Thomas (Support) could have access to internal dev docs or API logs to troubleshoot bugs 🐛.  4. Cleaner Analytics & Handoffs 📊Separating personas allows for role-specific KPIs. We could measure "Mike" on Conversion/Booking Rate and "Thomas" on Resolution/Deflection Rate. It also makes the "AI-to-AI" handoff possible—imagine Thomas realizing a query is actually a sales lead and "transferring" the user to Mike! The Vision: Moving from a "Generalist Bot" to a "Specialized AI Team." 🏛️🇬🇧 I’d love to hear from the product team and the rest of the community—would you prefer one consistent Fin, or do you see the value in a squad of specialized AI personas? #FinAI #ProductFeedback #AgenticAI #CustomerEngagementCheers, Roy 🇬🇧

    Katee SafferActive User

    Route “Resolved” Fin Conversations to a Team (via Workflow Trigger)Submitted

    We’re looking for a way to route conversations to a human team after Fin AI Agent has resolved the user’s questions — specifically through Workflows, not Procedures.Important context:We need this workflow to be triggered based on conditions like specific URLs (e.g. contact buttons or pop-up proactive messaging on a specific page)And at this time, that requires Workflow-level control. This cannot be handled in a Procedure currently, as far as I understand. Use case:There are certain topics where Fin can fully answer questions, but a manual action is still required afterward.Example:A user lands on a migrations page and clicks “Contact us” Fin answers all their migration-related questions The conversation is resolved But we still need it routed to our team to process the migration requestCurrent limitation:If we force routing early, we lose the benefit of Fin answering questions first If we let Fin resolve, the conversation never reaches the team Procedures don’t solve this because they can’t control post-resolution routing based on entry conditions like URLWhat we need:A Workflow-based solution that can:Trigger from specific entry points (e.g. URL, button click, referral source) Allow Fin to fully handle and resolve the conversation Then automatically route the conversation to a specific team Optionally mark it for internal follow-up without reopening it to the userWithout this, we’re forced to choose between automation or operational workflows, instead of combining both.Ideal behavior:Workflow triggers → Fin handles conversation → Fin resolves → Workflow routes to team for internal processing

    Grace Ndabananiye
    Grace NdabananiyeNew Participant

    Retroactive Attribute Application for Updated Scorecards in MonitorsSubmitted

    Summary:When a scorecard's attributes are updated, unreviewed conversations already captured by a Monitor should reflect the new attributes, either as incomplete/pending fields, or via a manual "re-apply scorecard" option.The problem:Scorecards evolve. When you refine attributes to better capture quality signals, only future conversations benefit from those changes. Existing conversations in the Monitor, especially unreviewed ones, are locked to the old scorecard structure, making it impossible to apply your improved rubric retroactively without manual workarounds.This is particularly frustrating when a Monitor has been running for weeks and you haven't yet reviewed the backlog. Updating the scorecard mid-cycle effectively creates two incompatible datasets within the same Monitor.What I'd expect instead:At minimum, unreviewed conversations in a Monitor should have the new or updated attributes added as empty/pending fields when a scorecard is changed, preserving any existing scores while surfacing the new ones for review. Reviewed conversations could reasonably remain unchanged.Ideally, there would also be a "Re-apply scorecard to unreviewed conversations" option, a reset or refresh button scoped to conversations that haven't been manually evaluated yet.Impact:Without this, teams have to either (a) accept inconsistent data across a Monitor's history, or (b) or manually re-process old conversations. All of these options undermine the value of Monitors as a continuous QA tool.