Share product ideas and upvotes with our product team
My team and I would love the ability to react to an internal note. Even if it’s in the context of tickets only, but could be useful on all conversations. Teammate Benefit: Teammates can react and interact more in Intercom, without sending more notes and clogging up conversations with full note entries. It’d encourage more camaraderie as a team.Leader/Manager Benefit: When tagging entire teams or teammates on notes, (that doesn’t necessarily need a response) I’d ask them to give the note a thumbs up once they saw it, so I know when my whole team has seen an important communication on a tracker ticket, or conversation.
If you allow customers to submit tickets using the built-in “Ticket links” app, users can always set the value of any ticket attribute marked as “visible to customer”. It would be useful to make such attributes visible to customers, without allowing them to set the value — so they can see the value when viewing the ticket in the messenger or ticket portal.For our specific use case, we have an external ticketing system that allows us to log actions taken on a ticket. I’d like to be able to share these actions with customers. The current workaround would be to serialize the action log to the “Description” field. But, I’d like to instead write this to a separate field, if possible, without showing that field when users submit a ticket.
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.
Right now you a banner can open a new url, launch a product tour and even ask for reactions. But its missing launching surveys? An example of this“Do you have 2 minutes to answer a quick survey?” CTA: Answer*Opens the long survey*
Our team members are trained to always send a follow up email after their phone calls. We prefer that these are sent in the same conversation as the phone call, so that the our conversation statistics aren’t doubled for every phone call.Currently, Intercom only allows an in-app message to be sent after a phone call, with no option to send an email instead. While this will still send an email to the customer if they don’t see it in-app within 3 minutes, this creates three major issues for us:Even though we set a ‘Subject’ on the conversation, the email just has “Re: “ due to Intercom’s behaviour of never using the Subject for conversation notifications and instead using the user’s first line of text (which is its own whole thing, really). This looks incredibly sloppy, and means users can’t tell our follow-up emails apart in their inbox. Often the customer is in-app immediately following a call with us, so there’s a strong chance of them seeing and dismissing the notification by accident. This is usually important information that we would prefer they have in their inbox for future reference. The formatting of the “email” presents as a chat message rather than an email, which doesn’t look as polished.
hi all, when copilot suggests answers, there is currently no mechanism for the agent to provide feedback (good or bad) about the suggestion itself. The only options are either to provide feedback on the source, or tag the conversation/ticket for review (through tag or back office ticket0.Ideally, Copilot would have a 👍/👎 option that would flag the specific answer that needs reviewing, rather than the whole conversation.Thanks
Managing a wide library of content to support users/Fin can get tedious, especially as the product changes and docs need to be frequently updated/sunsetted/etc.As part of the Suggestions feature, I would love if Intercom would highlight articles that have broken internal links where past help docs have been unpublished/deleted.
A recent UI update has moved the conversation events from the right hand side to the left hand side of the screen.It doesn't make sense to have these events showing on the left where the customer responses are.When you're looking at the information, you're looking on the right hand side where our responses are and where our events should be. It doesn’t create a single, consistent vertical timeline –it makes it more time consuming to find the event and it doesn't flow. Having it on the customers side of the conversation interrupts the flow of the conversation and it’s just not an intuitive place for it to be.
Agregar funcionalidad de búsqueda dentro del historial de conversaciones del Messenger para que los usuarios puedan buscar mensajes anteriores y verificar si ya hicieron una pregunta específica o enviaron comentarios/solicitudes de funciones previas. Esto evitaría preguntas duplicadas y mejoraría la experiencia del usuario
We would love to select Intercom as our provider. But currently a very important for us functionality is not available:(Evaluating between HubSpot and Intercom and it comes down to one tiny thing, Parent-Child relationships for companies. I think majority of tools provide this OOB, I really hope Intercom makes it available! Thankfully we transitioning December 2025 and maybe by then the feature will at least be on the roadmap.
Proposed feature changeAllow the subject line of the conversation email notification for Fin Chat Simple Deploy conversations to reflect the topic of the conversation, ideally based on the first message the customer sends.ProblemWhen Fin is enabled using Chat Simple Deploy, and a welcome message is set e.g. “Hi! I’m Fin”, the first line of the conversation email is always Fin’s welcome message.As a result, the subject line of the conversation email notification is always Fin’s welcome message, rather than the customer’s question. This causes all conversation email notifications to have the same subject line, making it difficult for customers to quickly scan their inbox and identify the correct support conversation.ScopeThis change is only applicable for user initiated conversations when Fin is enabled using Chat Simple Deploy.
It would be useful to surface the Conversation ID directly in the preview panel when viewing a conversation in Fin.At the moment, if I need the Conversation ID, I have to navigate away from Content and open Conversations → Analyse to find it. This adds unnecessary friction, especially when debugging, sharing references with colleagues, or cross-checking data.Having the Conversation ID visible in the preview panel would:Save time and reduce context switchingMake troubleshooting and internal referencing easier Thanks for considering.
In Settings 👉 Data 👉 People 👉 Attributes, you can organise the Attributes which appear on the right hand side panel of the chat. Every company has their own preference for what Attributes show, and in what order.Whenever we create a new profile, they have to organise their right hand side panel in the way our company organises it - takes approx 30 mins.It would be great if you could pre-set these bookmarks, so that every user has the same bookmarked attributes already set up by the company.
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.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.