Share product ideas and upvotes with our product team
We want to be able to add an image or callout in between numbered steps without breaking the list. Right now when I do this in an article, it restarts the list at 1 after the image or callout. This is disappointing as it’s forcing us to to static lists and manually number each step, or take the helpful image/callout out of the steps and lose their value. It’s also important that we use numbered steps over bulleted lists so readers can tell if they’ve skipped a step or not.
Consolidate conversation tags. Ex. if there are 5 tags used by the same team, merging the 5 into 1 conversation tag. Currently method of deleting tags ensures all reporting data related to the conversation tag is gone, rather than stored under a new tag.
It would be really useful to have a button appear on articles that you can click to quickly return to the top of the page. It would allow users to get back to the search bar a lot faster than having to scroll up, especially when viewing a longer article.
It would be incredibly helpful for our readers to be able to use a table of contents (TOC) that shows more than H1 and H2 in public articles. Ideally it would show down to H4 but just adding H3 would be great. Some of our documents have a lot of content at the H3 level that readers have to keep sorted in their own heads. This would also be helpful in internal articles.
Hey all!I’m just wondering if there is any way to add custom author attributes in Intercom? I’d like to allow teammates to add in their preferred pronouns so that they can be added into email signatures as something like:{{ message.author.pronoun }}I haven’t been able to find anything yet, let me know if this is possible at all, or if there is a workaround!
Hi team! We use the Reports - Conversations to access the ‘new conversations’ drill-in, and export the list of new conversations weekly. The problem we face is that the Company Name and User Name columns do not update retroactively in the list, they always show the Company Name and User Name that originated the conversations instead of what we’ve updated afterwards.Since we have multiple conversations that are generated by emails sent from our colleagues (so the User Name must be replaced by the ‘real customer’), we need to have a lot of manual work after exporting the list, replacing these values individually. We think it would make a lot of sense to have the Company Name and User Name both updating in real-time, since it is normal that during the course of a conversation the Company Name and User Name might get changed. This would be extremely helpful for us and would avoid us doing a lot of manual work handling the CSV file after exporting the list. Thank you!Pedro Silva - Full Fabric
When setting up a new help center, language settings were not been properly set. After adding articles, we fixed the language settings, but articles already added are categorized to the bad language.We started to edit the articles in hope language setting can be changed for existing articles, but the field is read-only.It would be great to be able to change the language category of exisiting articles, or copy / move article text among language versions.
Hi team,As a Intercom user, I wanted to share a few suggestions to improve the flexibility of the pop-up menu that can be helpful for all the users: More positioning options Right now, the pop-up only appears at the bottom of the screen. It would be great to have more placement options (like top corners or other floating positions) to better fit different layouts. Primary CTA button behavior It would be helpful if the primary CTA button could stay visible but disabled until all required fields are filled. This would make the flow clearer for users. More transition effects Currently, the pop-up has a basic opening animation. Adding other transition styles, like slide-in, fade in, would make the experience feel more customisable and modern according with different needs. At the moment, these settings aren’t very customisable.Thanks
The ability to flag articles and add internal notes regarding feature nuances or scheduled updates would really help our team stay on the same page and maintain updated content more efficiently.
Hi all, this could be interesting for many of you:Current status:when we resolve a ticket the SLAs get stopped. And when a customer replys to the resolved ticket the ticket gets reopened and the existing SLAs apply again.Problem:As the exisiting SLAs will be applied and for example the first response time is already exisiting, we do not have enough time to answer those reopened tickets in a timely manner. Therefore the SLA performance gets down.Solution:For us it would be really helpful to apply a new first response time or completly new SLA's for reopened tickets. Hopefully this is relevant for more Intercom useres, so this will get checked and prioritized 😊
Right now when a customer messages in an unfamiliar language, the messenger sets the language to the main fallback language. That makes it hard to understand in which languages our users are reaching out to us in, which we do not support. If the messenger could take into consideration all languages, and mark the conversation in the appropriate one that would be best, but another option is setting the conversation to a clearer “English - fallback” value for example, allowing us to manually go through those conversations to detect them.Right now the language is just set to our main one and can’t be separated unless manually going through ALL of our conversations.
We had the idea to create a feature that enables help centers to easily offer support content in multiple languages without the need for manual translations. Currently, managing a multilingual knowledge base requires significant effort and resources. To simplify this process, you could implement AI-driven translations that automatically convert articles from a default language (e.g., Dutch) into other languages (e.g., English, French, German) based on user preferences.Admins would be able to set a default language for their entire help center and choose additional languages to offer. When a new article is published, or an existing article is updated, it would automatically be translated into the selected languages using AI. A small notice at the top of each translated article could inform readers that the content has been automatically translated, allowing for transparency around potential minor inaccuracies.This solution would significantly reduce the effort and cost associated with managing multilingual help centers, making it accessible even for smaller teams. It would also help companies provide a more inclusive experience to a global audience.
Allow Help Center article search to be pre-seeded with context when the UI Widget is launched to help a user.We are implementing Help Center as a means to provide guidance to our customers. We will have a browsable help center but our primary goal is to provide context specific guidance to users as they undertake various actions in the system. We plan to use the Intercom UI Widget to achieve this. We support thousands of different online forms that we potentially need to provide guidance on via a help center. Managing that amount of article / collection IDs in the system is not workable for us.We wish to be able to provide context to the widget such that it displays the correct content to the user without hard coding Intercom IDs within our application. We want to avoid that as it will be difficult to maintain. Instead, we would like to pass the context of what the user is doing to Intercom and for the UI widget to display the correct article or articles based on what they are attempting to achieve. For example, when the user is forming a legal entity in Delaware, rather than coding the ID of the article that covers that specific online form into our system, we would pass ‘formation’ and ‘delaware’ to the UI widget and it would find the article or articles that best match that context.
Problem to Solve:There’s not an efficient way to continuously do outreach to customers that leave negative reactions on posts, banners, etc. It’s cumbersome, and leaves room for human error, to have to rely on continuously checking the outbound metrics, tag, message, etc.a Request:Add the ability to create a trigger that can target specific reactions that are left, as well as allow the ability for it to be applicable to any post, banner, etc, not have to target reactions left on specific content. Screenshot example:
I need the ability to Customize Ticket Status Update Emails.
I wanted to add the idea to have a Loom app available in the App store. I use Loom a lot, so it would be great if we could integrate it to be used in the Inbox and maybe in the Messenger - to host our videos. I appreciate we have a lot of video software already, but more variety wouldn’t hurt. I know there’s an option to build an app, but I’m not a developer, so while I’ll have a go, I don’t know where there’s a process for requesting integrations.
Current Limitation:At the moment, technicians can only be logged into the following routing channels: Phone (Phone only) Conversations (Includes both Chat and Email) Suggestion for Improvement:I’d like to propose greater flexibility in how routing channels are configured and assigned. Specifically: Split Email from the Conversations Channel: Allow Email to be its own standalone routing channel, separate from Chat. This would enable technicians to be logged into Email without being required to handle Chat at the same time. Enable Multi-Channel Selection: Provide the option for technicians to select multiple channels—rather than being limited to just one or "All." For example, a tech could be logged into both Phone and Email, but not Chat. Alternative Approach:If separating Email from Conversations isn’t feasible, another solution would be to include Email as part of the Phone channel. This way, Phone agents could assist with email volume during slower phone periods.Why This Matters:In environments where email and chat volumes are particularly high, the current setup disproportionately burdens the “Conversation” techs while “Phone” techs remain limited in how they can help. This often requires manual intervention by team leads to balance workloads across the team. By allowing more flexible channel selection or smarter routing, teams could improve efficiency and reduce operational overhead.
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.