Share product ideas and upvotes with our product team
Hi Intercom Team,I wanted to share a couple of small but impactful usability issues I've encountered when editing articles that use expandable sections: Heading Format Reset: When pasting content into an expandable section, it automatically converts the pasted text into an H2 heading, regardless of the original format. This forces me to manually reset each section to the appropriate heading type every time, which slows down the editing process. Sections Auto-Expanding on Edit: After saving an article and then clicking "Edit" again, all expandable sections reopen by default. For articles with many sections, this makes it difficult to quickly pick up where I left off. It would be a huge time-saver if previously collapsed sections remained collapsed or if the editor could remember the scroll position and state of the sections. These are minor adjustments, but resolving them would really streamline the workflow and improve editing efficiency.
It would be great if we could edit or delete company and people attributes. In cases where you incorrectly used an attribute name on a people attribute you meant to use on a company attribute that would help a bunch! If you create one incorrectly in one place (people attributes) you cannot recreate it under company attributes.
We have a team that will rotate between phone calls and chats. Everyone is part of the phone inbox but they switch themselves to conversations only when they are not scheduled to be part of the phone calls. We have found that if all agents on the phones are not available, the VM will then route to anyone on the team even if they are not set to accept phone calls as it seems VMs are treated more like a conversation.We would like it, and it would seem to make sense, that a VM stays only with those agents that are on the phones and continues to deliver to those agents when they do become available rather than go to someone who should be dealing strictly with chats
Currently, “If you chose not to set expectations for human support, the button will say "Get more help" regardless of the options selected above.”However, we would like to be able to customize the copy here to instead say something of our choosing like, “Open a support ticket.”
When you have an article open, I would like the browser tab of the article to display the title of the article you’re editing. This would make editing multiple articles at the same time easier, so you can see what each tab’s article is about.
Can the "Ticket state" on the "Ticket portal" be widened to show the status fully?Currently users can only see the red "Waiting on..." without seeing the crucial information of who it's waiting on.Ideally it would fully show “Waiting on customer” or “Waiting on you”.
Hi team, The support team I work for handles a lot of tickets about various topics. It would be so handy if we could label tickets with either color or symbols. So everyone can see/ have an indication about what the ticket is about. This would save us a lot of time, because otherwise everyone has to read the tickets. With the labels we could also work with an urgency system. Thank you!
Hi Intercom Team,We’d like to request support for the following additional languages in the AI autotranslation flow within the Multilingual Workflows [Beta] feature: ak-GH (Akan) – Native language for over 43% of Ghana's population. bem-ZM (Bemba) – Spoken natively by approximately 33.4% of Zambia’s population. yo-NG and ha-NG (Yoruba and Hausa) – Together, these represent over 50% of native speakers in Nigeria. so-SO (Somali) – The native language of Somaliland (~98% speakers). ky-KGZ (Kyrgyz) – The official language of Kyrgyzstan, spoken by at least half of the population. zu-ZA (Zulu) – One of the most widely spoken languages in South Africa. Adding support for these languages would significantly enhance our ability to provide inclusive and effective customer support across key regions.Looking forward to your feedback!Best regards,Alex from Swoo
While I am setting workflows, I found there is no branch that can tell if a conversation is linked to a ticket. Since not only customer-tickets is used, I think it would be helpful too add such condition in the branch. So we could set more automation for different conversations. 🙏
I would it if you merge a conversation the tags that have been tagged on one conversation get tagged to all conversations
It would be nice if we could configure the Summarize Conversation option in the AI Compose feature.For example, what headings to include in the summary etc.Apologies if this is already a feature. Thank you!
Hi Intercom team 👋At the moment, date-type custom conversation attributes can be used when building workflows, but they are not available in the export section for conversation data. Only boolean versions of such attributes appear as options.This creates a limitation for reporting and analysis, especially when trying to filter by specific months or calculate time-based trends (e.g. “longer than 30 days”).Request: Please enable the export and filtering of date-type custom conversation attributes to support more flexible and insightful reporting.Thanks a lot! 🙏
Hi Intercom team 👋We’d love to request a feature that allows tracking of the original team inbox a conversation was assigned to, in addition to the final team inbox it was reassigned to or closed under.Currently, the "Conversations reassigned" metric only shows where the conversation ended up, but not the original team it was routed through. This makes it difficult to analyze routing paths, understand handovers between teams, and evaluate inbox assignment efficiency over time.Request: Please enable tracking of both the initial and final team assignments for each conversation. This would help us: Analyze team routing patterns Identify bottlenecks in assignment processes Improve workload distribution and capacity planning Thanks for considering this! We'd be happy to be notified if this gets picked up 🙌
I would love it if there was a way to export knowledge articles written in Intercom.As our knowledge base grows it becomes increasingly difficult to manage our articles in Intercom and we really need a way to manage these assets externally We are looking into how to use API to do this but it would be fantastic if this fundamental function was included in Intercom
I noticed when creating a product tour, if you choose a sender it automatically includes the senders name with a “from <brand name>”. For internal purposes we want to keep the brand name as it stands but I wish we could change the customer facing name of the brand. All of our brands are similar so internally it helps to give them specific names but for customer facing we would like to keep it short and simple.
Percentages are important as data format. While I know it’s possible to ask for users to limit their data as a number, decimal number or a list, it’s not the same as a percentage.I need to integrate with Intercom and connect with percentage values, I cannot risk a user error messing up the data transfer.There’s currently no way to limit the number ranges (1-10), realistically, the percentage is a 0 to 1 range.Please add the data the “percentage” to Attributes.
We’re a SaaS platform based in Sweden with a large Nordic user base. To support our users better, we’ve enabled multilingual support in Fin. However, I’ve noticed that Fin often confuses Norwegian and Danish. In most cases, when a user writes in Norwegian, the response is generated in Danish.While speakers of Scandinavian languages (Swedish, Norwegian, and Danish) can generally understand each other, this mix-up leads to poor user experience. It would be a significant improvement if Fin could better distinguish between Norwegian and Danish. For now, I will have to disable one of the languages, likely the one with fewer users, to prevent confusion.
When onboarding with Intercom, we ended up using the defautl zendesk import, which misassigned a lot of companies and users. Later on we used the API to reimport Zendesk tickets, companies and users, however it turns out that ‘deleted’ tickets still appear in reporting.We’ve also had an issue where a product bug in our product caused several thousands emails to our support inbox. We also deleted these tickets. However this now means that we have to jump through hoops to get accurate reporting.By default any deleted conversation should not have an effect on reporting.
We often receive sensitive documents from users via chat or email. Once we’ve reviewed the document, we send a confirmation to the user.We would love to have the ability to remove attachments from a message without deleting the entire message. This would allow us to protect sensitive data while keeping the context of the original user message intact. That way, users can still see what they wrote, and we can maintain a complete and transparent conversation history.Currently, the only option is to delete the full message, which is not always ideal — especially when we want to retain the user’s message for reference or follow-up.
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.