Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3155 Ideas

    Briana M.New Participant

    Improve Email Follow-up Experience for Phone ConversationsSubmitted

    We would like to see improvements to the email follow-up workflow for conversations that originate from inbound phone calls.Our teams frequently need to send email follow-ups after a phone call when an issue cannot be resolved immediately. However, the current experience lacks transparency and control.When an agent selects Reply within a phone conversation, there is no indication of which Reply From email address is being used. Agents cannot change the Reply From email address if needed. The outbound email appears in the conversation more like a chat message than an email, making it unclear whether the customer received an actual email or simply another conversation message.What we’d like to see:The conversation be able to be changed to email when the conversation is initiated by phone call within the same thread. In additionDisplay the Reply From email address whenever an agent sends an email from a phone conversation. Allow agents to select or change the Reply From address (where applicable). Allow agents to add / change the Subject line Clearly distinguish outbound emails from chat messages within the conversation timeline. Provide clear visibility into how the customer will receive the message (email vs. in-app/chat).A more intuitive and transparent email workflow for phone conversations would significantly improve agent efficiency and reduce uncertainty when following up with customers

    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.