Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3157 Ideas

    YoeriNew Participant

    Critical Bug/Functional Flaw: Dynamic Table of Contents is broken by Intercom’s own SEO guidelinesSubmitted

    Intercom’s Help Center Table of Contents (ToC) is intended to provide a two-tier navigation structure. However, Intercom officially recommends avoiding <h1> tags in the article body for SEO reasons (to avoid multiple H1s on a page; the <header> tag is also read as <h1>). This recommendation creates a fundamental conflict: following your SEO advice effectively breaks the ToC, reducing it to a single, flat layer because it ignores <h3> and <h4>. This is not a "new feature" request; it is a functional misalignment that renders the "dynamic" ToC obsolete for any company following modern web standards. The Problem• The Conflict: The ToC only supports <h1> and <h2>. Since using <h1> in the body is discouraged, we are forced to use <h2> as the top level and <h3> for sub-sections. • The Result: Sub-sections (<h3>) are invisible in the ToC. The promised two-layer navigation is currently impossible to achieve without sabotaging our SEO. • Collapsible Sections: The title of a collapsible section is also ignored by the ToC, making long-form, organized content difficult to navigate. Proposed Solution: User-Configurable ToC LevelsTo resolve this, Intercom must allow users to define the hierarchy of their Table of Contents. This can be easily implemented in the Help Center settings with a simple toggle/checkbox system: Settings: Table of Contents HierarchySelect which header tags should be included in the dynamic Table of Contents:☐ H1 (Not recommended for SEO)☑︎ H2☑︎ H3☐ H4☑︎ Include Collapsible Section Titles (When assigned an included header tag)This solution allows customers to align their navigation with their specific SEO strategy and content structure. Why this is EssentialWe are currently forced to choose between search engine visibility and user experience (readability). As a premium platform, Intercom should not force its users into this trade-off. The current logic is outdated and contradicts your own technical advice. Conclusion & Required ActionThis issue should not be relegated to a "Product Wishlist" where it relies on popularity votes. It is a structural flaw in the Help Center’s architecture that prevents the software from functioning as intended.We expect this issue to be moved to the Product Roadmap as a priority fix to align the Help Center functionality with Intercom’s own SEO best practices.

    Ashrith NanjappaNew Participant

    In-Chat Screen Capture & Recording IntegrationSubmitted

    Feature Request: In-Chat Screen Capture & Recording IntegrationWhat we need? We want to empower drivers to provide instant visual context during support sessions. The goal is to take the existing "Report an issue" logic currently found in the pre-login Help Center and embed it directly into the driver’s active chat interface. This creates a "show, don't tell" experience that saves time for both the driver and the support agent.How should it WorkPlease refer to the following step-by-step logic currently utilised in our login-screen Help Center: The Entry Point: Within the active chat window, a new "Screen Capture" icon is added to the input bar. The Modal Trigger: Tapping this icon opens a "Help Center" style overlay. This overlay should offer a clear "Report an issue (screen capture)" button, mirroring the current support UI. System Authorization: Once selected, the app triggers a system-level permission dialogue (e.g., "Start recording or casting with Bettermile?"). This ensures the driver is aware of the recording. Privacy Protection: The interface must display a clear disclaimer—as currently seen in the app—warning the driver that anything visible on their screen (passwords, messages, etc.) will be captured. Seamless Attachment: Upon clicking "Start" and completing the capture, the recording/screenshot should not just save to the device; it should automatically upload and send as a message directly into the current chat thread.