Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3161 Ideas

    MichelleNew Participant

    More Configuration and Style Capabilities for Help CenterSubmitted

    We’re currently working to make our support subfolder on web feel more visually aligned with our main domain, both to create a smoother user experience and to better support our acquisition and retention goals. As part of that effort, we’d love to see more flexibility and control over the layout, styling, and conversion elements. Below are a few feature requests that would make a huge difference:Fully Customizable Sticky HeaderHaving a landing page with a sticky header with fully customizable dimensions would be a game-changer for visual brand continuity.Fully Customizable FootersWe’d love more control over footer content. Whether that’s custom CTAs, more internal links, or embedding a widget or partner badge. Currently, we’re limited to default templates and can’t align it to our tone or brand. It is also a missed opportunity to delight users with features we offer.Device-Specific CTAsIt would be incredibly helpful to configure CTAs to appear on web only (or mobile only). This would let us surface relevant actions depending on user context—e.g. show conversion links on web, but not within the mobile app as users have already converted.Support for Schema MarkupAdding support for structured data (especially Article, FAQ, and Product schema) would allow us to boost visibility in search results. As we look to set our content up for success over the long run, schema markup is also key for better SEO and GEO and search tracking.Clickable Author Bios and Bio PagesWe’d like to create author bio pages, with the option to click through to them from the article byline and footer. This is something we already support on our main domain, and the lack of parity on the Intercom subdomain is currently a limiting factor in our ability to feature and optimize support content more broadly. It would help with credibility, trust, and content discoverability.Navigational FlexibilityAt the moment, there is no way for users to return to the primary domain from the Intercom support subdomain. This affects bounce, e.g. if the user does not find what they’re after in our support, and/or does not allow a journey for users to convert should they wish. We’d love to surface more of our Help Center content in a subfolder across our site, but the current limitations make it really tough to create a cohesive experience. More configuration and style settings would go a long way in helping us deliver better content visibility, stronger branding, and ultimately a more seamless experience for our users while supporting our acquisition and retention goals. Curious if others are feeling the same, and hoping some of this might already be on the roadmap behind the scenes!

    Macall GardnerNew Participant

    Channel Routing: Add Email to Conversation and PhoneSubmitted

    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.