Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3443 Ideas

    Christopher DucoteNew Participant

    Feature Request: Auto-Collapse Quoted Email Trails in InboxSubmitted

    The ProblemWhen customers reply to email conversations, their email client includes the entire previous thread below their new message — as virtually every email client does by default. Intercom's Inbox renders this quoted trail fully expanded, inline, for every single message in the conversation. The result is that a 6-reply email thread becomes an endlessly scrolling wall of duplicated text, where the same content is repeated over and over, growing exponentially with each reply.This makes it genuinely painful to work through email-based tickets. Instead of quickly scanning the latest reply at the top and moving on, agents have to scroll past pages of repeated content just to orient themselves. Multiply that across dozens or hundreds of tickets a day and you're looking at a real productivity hit — not to mention the mental fatigue of parsing the same text blocks repeatedly.Why This Is FrustratingEvery major email client and nearly every competing helpdesk platform handles this gracefully. Gmail, Outlook, Zendesk, Freshdesk, Help Scout — they all detect the quoted text delimiter and collapse it behind a simple "show quoted text" toggle or ellipsis. It's a solved problem. It has been a solved problem for over a decade.The fact that Intercom still displays raw, fully expanded email trails in 2026 is baffling. This isn't a complex engineering challenge. Email clients universally use standard markers for quoted text (> prefixes, --- Original Message --- delimiters, etc.). Detecting and collapsing these behind an expandable toggle is straightforward — it's the kind of thing a single engineer could prototype and ship in a day.What We'd ExpectQuoted email trail text should be collapsed by default in the Inbox conversation view. A simple "Show quoted text" or expand toggle (like Gmail's ellipsis ...) should let agents reveal the full trail when they actually need context. This should apply to all inbound email messages where quoted/forwarded content is detected.The ImpactThis affects every single team that handles email-based conversations or tickets in Intercom. It's not an edge case — it's the core workflow. For teams processing high volumes of email tickets, the lack of this basic functionality adds up to hours of wasted scrolling and lost focus every week.This feels like the definition of a quick win: low complexity, high impact, long overdue. We'd love to see it prioritized.

    Amy TetchnerNew Participant

    richer article formatting and better support for long-form knowledge contentSubmitted

    It would be great to see the Intercom article editor evolve to better support longer, more structured knowledge content.At the moment, articles work well for relatively simple content, but once they become longer or contain larger tables, videos, reference information or multiple sections, the authoring and reading experience can become quite limited.A few improvements that would make a big difference:More formatting optionsSome additional formatting controls would help make longer articles easier to scan and understand, including:Underlining Font/text colour Highlighting More control over spacing Additional callout styles for notes, warnings, tips and important informationThese do not need to turn the editor into a full publishing tool, but some extra flexibility would make it much easier to create clear visual hierarchy.Collapsible / accordion sectionsAccordions would be extremely useful for longer articles.Rather than asking users to scroll through a very long page, content could be grouped into expandable sections so users only open the information relevant to them.Ideally, content inside accordions would remain searchable and fully accessible to Fin.Native video hostingIt would also be useful to have a way to upload and manage videos directly within Intercom Knowledge.Currently, videos generally need to be hosted on a third-party platform before they can be embedded into an article. This adds another platform to manage purely for hosting content.A simple media library could allow authors to:Upload videos directly Reuse the same video across multiple articles Replace or update a video without updating every article Add captions and subtitles Add transcripts Control access where requiredBetter tablesTables are particularly useful for technical, reference and comparison content, but larger tables quickly become difficult to use.It would be great to have options such as:Sticky/frozen header rows Alternating row shading Sort columns A–Z / Z–A Filter by column Search within a table Dropdown filters Freeze the first column Better control of column widths Cell alignment options Better responsive behaviour on mobileFor long lists or reference tables, being able to search and filter the data would be a significant improvement over manually scrolling through a static table.Search within an individual articleFor particularly long articles, an optional Search this article function would also be useful.This would be different from Help Center search. If someone already knows they are in the correct article, they should be able to search within that content without relying on their browser's Find function.This could be particularly useful for:Long reference lists Compatibility tables Error codes Product or feature matrices Glossaries Large FAQsBetter navigation for long articlesAdditional navigation options would also improve the experience, such as:Sticky table of contents Anchor links Back to top Previous/next section navigation Direct links to individual accordion sections Section headings that remain visible while scrollingReusable content blocksReusable content would also be very useful for knowledge bases with a lot of articles.For example, if the same warning, prerequisite, support information or standard explanation appears across multiple articles, it would be useful to maintain that content once and reuse it elsewhere.Updating the source block could then update every article where it is used, helping reduce duplication and improve content governance.OverallAs Intercom Knowledge becomes capable of supporting more substantial documentation alongside Fin, it would be great to see the article editor become more suitable for complex and long-form content.The biggest improvements for me would be:Accordions Native video hosting Better table functionality Search within an article Richer formatting Better long-page navigationThese would make larger articles much more usable for both authors and readers, while reducing the need to rely on third-party tools or workarounds.