Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    518 Ideas

    Roy
    Top Expert ✨
    RoyTop Expert ✨

    Dynamic UI Previews: Generating Ephemeral App Experiences from API Responses in Fin FlowsSubmitted

    ⚠️ Problem StatementCurrently, when a Procedure Builder configures a flow to fetch external data (e.g., retrieving a list of recent orders, linked accounts, or purchased products via an API), the experience often breaks continuity. After the data is fetched, Fin has to ask the user to manually type out the specific order number or product name into a blank text input. This manual transcription introduces friction, increases the margin for user error, and degrades the premium "app-like" messenger experience. ✅ Proposed Solution / Feature ConceptIntroduce an automated, temporary messenger app experience generated dynamically from API payloads. Instead of returning raw text or forcing a manual text reply, Fin should leverage an ephemeral UI component (a "Preview App") directly inside the messenger canvas.When an API response returns an array or an object collection, the Procedure Builder should be able to map those objects to interactive UI elements. The customer can then simply click/tap their selection from the visual response to advance the flow. 🛠️ Example Use Case / Flow Step 1: Fin initiates a backend check: "Display all orders for this customer." Current State: Fin lists the text or drops a blank input box: "Please type the order ID you are referring to." Proposed State: Fin renders an interactive list/carousel card component showing the last 3 orders (Order #, Date, Total). Step 2: The customer clicks the specific order card. Step 3: Fin instantly updates the context and moves to the next interactive picker: "Which product from this order are you referring to?" (Renders clickable Product Items).

    Ed MorrellNew Participant

    Preserve and restore conversation ownership after Fin AI Agent involvementSubmitted

    When a human agent takes ownership of a case, particularly for complex, multi-step issues like repair bookings or courier collections, and Fin subsequently handles part of that conversation (e.g. answering a status update, running a procedure), there is currently no native way to automatically return the conversation to the original owning agent once Fin's involvement ends or escalates. Our agents handle cases that span multiple touchpoints. An agent may book a scooter collection or repair, making them the case owner with full context. If the customer later contacts us again, Fin may handle the interaction but when Fin escalates or the conversation needs human attention again, it lands in an unassigned team queue. The original agent loses the case unless they find it or it gets manually reassigned to them. The only current workarounds I can think of:Agent name tags + a workflow branch per agent (brittle, requires maintenance as the team changes) Creating a new custom attribute (however, we've exhausted our attribute allowance on reporting-critical fields)None of these are clean solutions, they all require ongoing manual maintenance or sacrifice something else.The ask: A native "Case Owner" concept at the conversation level, separate from the current assignee, that: Can be set by an agent when they take ownership of a case Is preserved throughout Fin's involvement in the conversation Automatically reassigns the conversation back to the case owner when Fin escalates, hands off, or the conversation leaves the bot inbox Alternatively, a workflow trigger condition of "previous human assignee" that can be used to route conversations back to whoever held the conversation before Fin took over. As teams adopt Fin more deeply particularly on email channels where conversations reopen and span days or weeks, case continuity becomes critical. Fin is excellent at triaging and answering, but the handoff back to a human needs to be intelligent, not just "drop it in the team queue." This feature would allow teams to confidently expand Fin's scope without sacrificing the accountability and context that comes with named case ownership. This would affect any teams using Fin on email or async channels with multi-touchpoint cases, repairs, logistics, complaints, or anything requiring follow-up over time. ThanksEd

    Thales LopesNew Participant

    Improvement Suggestion — Adding Sector as a Criterion for Audience RulesSubmitted

    I’d like to report a potential improvement regarding the Audience configuration.Recently, we expanded the operation to other products. Given this scenario, managing the materials now requires more robust audience rules to prevent content related to other products from being incorrectly used in ERP support interactions, and vice versa.After reviewing the current Audience configuration, I noticed that it is not yet possible to use the Sector attributes we created for chat classification as a rule criterion. These attributes are currently essential for correctly routing each interaction to the appropriate Fin configuration and, consequently, to the support team responsible for the respective product.If we could use Sector as a condition in Audience rules, we would be able to segment customers and materials more precisely according to each product. In addition, this configuration would make future maintenance and adjustments much easier, as we could focus corrections and improvements on each sector's specific prompt, without having to revise broader audience rules.Given this need, we would like to request the addition of Sector as an available criterion when creating Audience rules. We believe this improvement would help ensure more accurate material segmentation, prevent inappropriate content from being used across different products, and make it easier to manage and continuously improve Fin.

    Judy CorreiaNew Participant

    Recommendation Audit or CategorisationSubmitted

    Currently Fin Recommendations (content gaps, data gaps and action gaps) only have two options - reject or mark as done/approve. Rejecting removes the recommentation and stops Fin from suggesting it again in the future. In our case this is limiting as a recommendation (in particular or data and action gaps) may not be technically possible today, but as technology changes the recommendation may make sense at some future time. It would be amazing if recommendations had a option for a “soft rejection” where it may be rejected now but we’d like Fin to make the recommendation again (if warranted) at some future time, someting like “remind me again in X months”It would also be great if: there were an audit trail, where we could see what recommendations were accepted and rejected. In addition to an audit, being able to specify reason for rejection, this would help with identifying the recommendations that may not make sense today but could in the future. Currently to overcome this limitation in auditability and tracking we need to keep a running list of recommendations in a spreadsheet, noting the recommendation, when it was suggested and the reason for rejection and review it regularly to see what might be feasbile today that perhpas wasn’t a few months ago. This adds extra overhead to our process and means having to bounce between applications vs having one source of truth within Fin.