Share product ideas and upvotes with our product team
Currently the Table of contents uses one font, one font size, and one color scheme.Please utilized multiple sizes and colors to differentiate the levels in the table of contents. For example H1 could be Bold 16 pt font and H2 could be Dark Gray 14 pt font. Similar to below:
The problem: The auto-generated table of contents in Help Center articles renders every entry identically — one font, one size, one color, no indentation. H1 and H2 headings appear as a flat list, so readers can't see the structure of the article at a glance. In long articles (exactly where a table of contents matters most), a flat list of a dozen identical entries is hard to scan and defeats the purpose of having a TOC.The request: Add visual hierarchy to the table of contents so heading levels are distinguishable. The standard treatment would be some combination of:1. Indentation — nest H2 entries under their parent H1, the way most documentation sites do.2. Size and weight — e.g., H1 entries in bold 16pt, H2 entries in regular 14pt.3. Color — e.g., H1 entries in the primary text color, H2 entries in a secondary gray.(Example attached showing the kind of differentiation we mean.)Even just automatic indentation by heading level — with no configuration options at all — would solve most of the problem. Configurable styles per level would be the ideal version.This applies wherever the TOC renders: both the Help Center on the web and in the Messenger. Since the TOC is already generated automatically from H1/H2 headings, the structural information exists — it just isn't reflected visually.The payoff: readers can see article structure instantly, jump to the right section faster, and self-serve more successfully on long articles. Thanks for considering!
It would be great to be able to add followers to a ticket instead of have to publicly cc internal teammates on tickets
Currently, it’s only possible to search by conversation attributes but it would be beneficial to add more filters based on the user’s data.
We assign agents to work, for example, on Emails, Calls, or Live chat; they should be able to select their availability to receive conversations from the inboxes assigned.
It would be beneficial if, based on escalation rules, Fin could create a back-office ticket to other teams.
At this time it is not possible to create tickets and select the From email address from which customer communication is done. The default workspace email address is then used.This does seem to be possible for conversations though. There you can select the email address from which you want to send the outgoing email to the customer.This should also be possible for tickets.At this time a conversation needs to be created with the outgoing email to the customer and after that the conversation can be turned into a ticket.In our environment our Operations teams monitor our systems, create a ticket when they see an issue and then the 1LS teams contact the customer.But this doesn’t work, because when 2LS creates the ticket, the communication 1LS sends is sent from the wrong From email address.
Right now, you can’t see total article views by bot vs human. Being able to see what type of viewer is viewing the articles is very beneficial into understanding more granular data about the article being viewed. If I was able to see the category/type of viewers, then I wouldn't even need to ask support why a spike in total views happened since I would be able to see it was the bot category that had the spike.
Right now, when I respond to a ticket and change the ticket state, the only thing I see when looking at the side panel for that ticket is “Moved to Submitted” or “Moved to ‘Waiting on Customer’ instead of the actual message I sent. We already have the option to filter for the different ticket states, so what I’m seeing when I glance at the ticket shouldn’t be the ticket state, rather it should be the start of what I’ve sent to the customer. Being able to glance at a ticket and see my last response helps be more efficient without having to open up the ticket to see my last response.
Problem to Solve:As of right now, there is no way for us to pull an audit log for users/leads/companies. There are times we need to investigate how something was created, who added in information on the account, etc.The answer seems to always be to use “API”, but that’s not realistic for Intercom to expect customers to have someone who knows API readily available to assist with CX tasks. Request:Create an “User/Lead/Company Audit Log” that allows us to easily view information about the accounts, such as:When it was created How it was created / by who When it was last updated What was last updated Who updated each item Additional Context:It is extremely difficult to investigate different things like the following examples:Why duplicate leads / users get created and why they’re not merging If integrations like Salesforce are working with syncing information Where information is being incorrectly synced from
When duplicating workflow duplicate everything. Currently when duplicating a workflow channels are not duplicated, i.e. email. When we duplicate a workflow that included Web, iOS, Android and Email the email channel is not included in the duplications.
Can Afrikaans please be worked into Intercom as a supported language? Being based in South Africa, 95% of our client base speaks Afrikaans. We are using AI tools as well to translate from English to Afrikaans where needed.
Allow ends users (our customers’ customers) to search the pervious conversation via keywords in messenger. So any conversations that contain such keywords would show up. One of the customers’ end user requested so that they can easily search and refer to previous conversation when talking to the support agent.
Present state - Selecting to edit an article forces all collapsible sections to expand Request - Instead keep collapsible sections collapsed once you select editThis helps the amount of scroll needed when I am editing, saving, and publishing.
It would be incredibly useful if Intercom Webhook topics included events for article creation and editing. This would allow my team to automatically trigger tasks in our project management system (e.g., via Zapier) instead of manually tracking every content update. Right now, the lack of these event types in Intercom prevents us from automating what could otherwise be a simple and efficient workflow.
We currently use outbound messaging to greet all new users and guide them to available support channels (Help Center, chat). However, the message can only be sent from a teammate, even though Fin can handle replies if the user responds, which they often do.For the sake of transparency and a better user experience, it would be great if we could set Fin as the sender. This way, users know they’re interacting with an AI from the start, rather than expecting a human response. At the moment, the only alternative is to explicitly state in the message that our bot will be responding, which can come across as a bit tacky.
The current ticket report is ok but has limitations related to tracker tickets. 1 tracker ticket is linked to multiple conversations. It would be great to see in the reports how many conversations have been linked to tracker tickets over a given period. This gives a more accurate impact of the issues related to tracker tickets. For example, if there were 5 tracker tickets last month, there can be a big difference in impact if only a handful of conversations were linked to the tracker, versus if 20 or 30 conversations were linked to each ticket. It would be good to be able to see this in the reports. Alternatively, having a way to automatically tag a conversation when it is linked to a ticket would help generating custom reports for this.
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.