Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3160 Ideas

    Daniel Rönnberg
    Daniel RönnbergActive User

    Show escalation guidance applied in conversation eventsSubmitted

    We’re really happy with the new escalation guidance functionality and have started using it to control which users can escalate to human support in chat. Current setup Paying users can always escalate to human support via chat Non-paying users are limited to AI support in chat and are guided to email if they need human support We’ve achieved this by creating a separate audience for non-paying users and configuring escalation guidance that encourages them to continue chatting with Fin or reach out via email when they ask to speak to a human This works very well functionally 👍 Feature requestWhat would be extremely helpful is the ability to see when escalation guidance has been applied directly in the conversation events, similar to how other guidance or automation events are shown today.For example: “Escalation guidance applied: Non-paying users – AI only” Timestamped and visible in the conversation timeline  Why this matters It would help us verify that escalation logic is working as intended Makes troubleshooting and QA much easier Improves internal visibility and confidence when reviewing conversations Especially useful when multiple escalation rules and audiences are in use Right now, there’s no clear way to confirm from the conversation view that the correct escalation guidance was triggered, which makes it harder to monitor and validate the setup over time.Thanks for building a great feature already — this would be a small addition with a big impact on usability and trust. 

    Nicola ReddyNew Participant

    Automatically remove email participants from an email thread when non-Intercom users update the email recipient listSubmitted

    Currently in Intercom, when an external customer/email recipient removes an email recipient from an email thread, Intercom automatically adds them back on to the thread. This means that it is very easy to press “reply” and send your email to recipients who should not have received that email. This poses a serious data protection risk. It places extra work on the Intercom user to double check again the email recipient list every time before sending a reply, which results in extra work and undue delay in replying to customer emails. This behavior creates a real risk that confidential information or data may accidentally be sent to the wrong recipient.It would be very useful if Intercom either (a) only allowed replies to the email recipients who were on the immediately previous email - even if that is from an external user or (b) clearly alerted the Intercom user that an email recipient has been automatically re-added back into the conversation by Intercom, to reduce the risk of my team replying and sending information to a recipient who should not have received it.This would then match how other inboxes operate e.g. gmail, hotmail when using a “reply all” function. Currently the Intercom “reply” default position is different to what the user expects and so increases the risk of the user getting it wrong.Expected benefits: Prevent accidental sharing of confidential information/data with unintended email recipients; Increase GDPR and data security; Reduces work for Intercom users and increases customer response time as no extra checks needed before pressing “reply”; Avoids the need to alert staff and train them to a different unexpected feature that does not match industry norm when replying to emails with multiple recipients.