Share product ideas and upvotes with our product team
1. The Problem:Currently, when an inbound email contains an attachment that Intercom rejects (due to size limits, unsupported file types, etc.), the system leaves a generic note in the conversation stream: "Attachments were dropped from this message." Because there is no context regarding what was dropped, support agents are forced to reply to the user and ask them to clarify what file they were trying to send. This creates unnecessary back-and-forth, delays resolution times, and creates a frustrating experience for both the agent and the customer.2. Proposed Solution:Update the "Attachments were dropped" event log to include the basic metadata of the dropped file.Example of current state:📎 Attachments were dropped from this messageExample of desired state:📎 Attachments were dropped from this message:Feature_Request_Bribe_v2.pdf (6.7 MB)Definitely_Not_A_Virus_Jared.zip (4.2 MB)Please_Build_This_Jared.png (2.2 MB)image001.png (45 KB)3. Why this matters (Business Impact):Context: Agents instantly know if the dropped file was a crucial document (like a PDF checklist) or just a harmless email signature image.Efficiency: Eliminates the need to ask the customer "What did you attach?"Customer Experience: Customers don't feel like their files disappeared into a black hole without explanation.4. Technical Feasibility:Since Intercom's backend already receives the Multipart MIME message and parses the headers (Content-Disposition, Content-Type, etc.) to evaluate whether to keep or drop the payload, this metadata is already being temporarily held in memory. Writing these specific header values to the conversation event log before purging the file data should be a highly feasible, low-lift addition that provides massive value to support teams.
For now it is not possible to change SLA settings once they have been created. If something needs to change, new SLA settings need to be created and used in the workflow. It would be much easier to be able to change those settings.
I’d love the option to be able to set Fin attribute reasoning to be hidden, or perhaps follow the “Show conversation events” flag, We have several attributes and it can be quite noisey.
When using an email code for data connectors I’d like to be able to configure two options: Choose the time out window myself Automatically communicate the time out window (regardless of whether it’s custom or not) to the customer whenever the security code is invokedA 10 minute window is very short and customers are often stuck in a loop requesting new codes over and over. This could be off-set with a longer window, and better communication about these timeouts. It seems like an industry norm to communicate time out windows by default and it’s strange that this isn’t done.
As of now, the Glossary only controls how terms are translated in outgoing messages. It does not apply to incoming customer messages. Fin guidance can’t rewrite or “correct” how inbound customer messages are translated in the Inbox either.Goal: to control how terms are translated in inbound messages.Use case: to ensure Fin connects with the correct internal knowledge or concept when translating phrases or messages from other languages, e.g. the same concept can be referred in a very specific phrase in a specific language that if translating literally will never get to the right reference.
In some cases, we need to proactively reach out to users via Intercom. For these situations, we use macros as templates for our messages. To better support our global user base, we also rely on real-time multilingual inbox translation.Currently, when using the multilingual inbox, it would be helpful to have the option to set the conversation language at the time of initiating the message. This way, the message could be automatically translated into the user's preferred language from the start, making the user experience even better.
It would be beneficial if agents could search for macros by their content in addition to their titles. This would allow them to quickly locate the specific macro they need without having to recall the exact title of the macro.
Hi, Whatsapp supports typing indicators, it would be amazing if this could be added into Intercom so customers can have more certainty that they will receive a response. See here: https://developers.facebook.com/documentation/business-messaging/whatsapp/typing-indicators/Thanks!
Allow reordering and renaming Messenger spaces in the mobile SDK
For any reporting in intercom it is essential for us to be able to download an image or pdf of a report like a bar graph or topics explorer report etc a csv is not helpful to share with our team. Zendesk already does this it will extremely beneficial.
We have dedicated livechat agents, and we want the way that livechats are allocated to be different from the way tickets are allocated. However, it appears to be all under the same thing and therefore we can’t have manual email conversation allocation but still have round robin livechat conversation allocation.It would be beneficial to have these operate separately, and even better as two entirely separate but linked views, so that it is clear what is from the chat widget and what is an email.
We would love to see CX Score available for phone conversations, not just chat and email. Current LimitationToday, CX Score is only available for chat and email conversations. Even when a full transcription exists, phone calls are excluded from CX Score, Insights, and Reporting. Why This MattersPhone conversations are a critical part of our customer experience and often involve the most complex or sensitive cases. Not being able to measure CX Score for voice creates a gap in our CX reporting and makes it harder to compare quality across channels. Proposed ImprovementEnable CX Score calculation for phone conversations when a full transcription is available. This would allow:Consistent CX measurement across chat, email, and phone Better use of existing transcriptions More complete Insights and Reporting for teams that rely heavily on phone supportValueThis feature would significantly improve cross-channel CX analysis, and help identify coaching opportunities for phone support.
Ability to choose which knowledge folders the content team can edit. We need to decrease risk by giving content editors access to edit ALL knowledge articles in a workspace.
Ability to make fin toggle disabled as default for newly published content.
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.