Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3474 Ideas

    AhuraNew Participant

    Restore Touchscreen Navigation and S Pen Support in Intercom InboxSubmitted

    I'd like to request that Intercom restore and improve touchscreen navigation and S Pen compatibility in the Inbox interface, specifically on my Samsung Galaxy S24 Ultra.What worked well before:Two or three years ago, using Intercom with the S Pen on Samsung Galaxy devices was an excellent experience. It was more precise and convenient than regular touch controls and significantly improved my productivity.Unfortunately, S Pen interactions deteriorated so badly last year that I eventually stopped using the pen entirely.What has changed recently:Over the past 10 days, recent UI updates have also significantly degraded regular touchscreen interactions on my Samsung Galaxy S24 Ultra.Scrolling to the top or bottom of certain menus and panels no longer works properly. I sometimes have to select text and drag it up or down just to reach menu options. Touch navigation feels less responsive, less accurate, and less reliable overall. The only noticeable improvement has been the ability to swipe certain notifications, such as connection and disconnection alerts, sideways.What I'm requesting:Please restore smooth, accurate touch scrolling across all menus and panels, fix the interaction issues introduced by recent updates, and bring back reliable S Pen support.Touchscreen and stylus compatibility should improve with new releases, not become less usable. These changes have had a direct negative impact on my daily workflow.I would genuinely appreciate it if the product team could review this feedback and share whether improvements or fixes are planned.Thank you for taking this seriously.

    Eric PluskotaNew Participant

    Make FIN always reference specific sections from articleSubmitted

    Product idea: "Always Surface" markers for AI-highlighted article sectionsThe problemWhen AI assistants answer questions from articles, they pick which parts of the content to use. Authors have no control over this. A critical section (a warning, a prerequisite, a pricing caveat, a key step) can get skipped or buried, even though the author knows it must always reach the reader.The ideaLet authors mark a specific section of an article as "always highlight." Whenever AI draws on that article, it must include or prominently surface the marked section in its answer, instead of treating it like any other text.How it could workIn the editor: the author selects a section and applies a flag, such as a "Highlight for AI" toggle, a callout block, or a tag. Behind the scenes: the marker is stored as metadata on that section, so retrieval and answer generation can see it. In the AI's answer: if the article is used as a source, the flagged section is always quoted, summarized, or linked, and visually distinguished (for example, "Important:"). Optional controls: a priority level (must include vs. should include), and a trigger scope (always, or only for certain topics or questions).Who benefitsAuthors and content teams get control over what's non-negotiable. End users get critical information instead of a partial answer. Support and compliance teams get fewer errors caused by missed warnings or caveats.ExampleA help article on connecting a data source includes the section "You must be an admin to complete this step." Flagged as always-highlight, the AI includes that line whenever it answers a question about connecting a data source, so users don't hit a dead end.

    David BloxhamNew Participant

    Help Centre content block - Target by audienceSubmitted

    The requestI'd like to show different Help Centre home-page content blocks to different people, using the same audience rules Intercom already offers on articles and Outbound messages. To make that work, I'd need:More than one content block on the home page. An audience setting on each block (Visitors, Leads, Users, or user attributes and segments), checked when the page loads. Per-language text for each block, as there is now.How we would use it"Can't log in?" block, for visitors only. People who aren't signed in are often stuck at login, MFA or an invitation. This block would send them to the access and support articles. Signed-in users don't need it. "Operational support" block, for a specific set of users. For example, customers on our operational support service, targeted by a company or user attribute. It would point them to the support routes and guides for their service. Other customers shouldn't see it. "Learn the Lavanda PMS at Lavanda University" block, for signed-in users only. The button opens a LearnUpon self-registration link.WhyOur Lavanda University block links to LearnUpon shareable group invite links. Anyone who opens one can register and is enrolled straight into our learning journeys. The Help Centre is public, so any visitor can see the block today. That includes people who aren't customers, which makes our training open to anyone who finds the page. Lavanda University is training for people who use our product, so the way in should only be offered to them. At the moment the content block is a single site-level setting. It's either on for everyone or off for everyone, so we can't make it safe without removing it altogether. The same limit stops us using the home page for visitor-only help, such as login problems, or for messages meant for one customer group.What we've triedOutbound Banners. They support audience targeting, but they appear as a strip across the page, not as part of the Help Centre layout. They're also built for announcements rather than permanent signposting. A home-page article list with audience-restricted articles. It hides articles from the wrong audience, but it's a list of links. It isn't a block with a heading, a description and a button.What it would give usA home page that fits whoever is looking at it: help getting in for visitors, the right support routes for each customer group, and training links only for customers. Today everyone sees the same thing.

    Doug AyersNew Participant

    [Bug] Updating article with API removes table stylingSubmitted

    SummaryWhen an article is created or updated through the REST API / MCP then the `style` attribute on table <td> tags are removed, undoing styling that was applied in the web editor to customize colors or widths. Steps to ReproduceUse the Knowledge web editor to create an article with a table, assign colors the to the column headers and adjust the column widths. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body contains the `style` attribute defining background-color and width on the <td> tags. Use the REST API / MCP to re-save the article as-is. In the web editor refresh the article and note that the table styling was removed. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body no longer contains the `style` attribute on the <td> tags. Expected ResultThe `style` attribute on the <td> tags defining the background-color and column width is preserved. Actual ResultThe `style` attribute on the <td> tags is removed. Example Step 1 Example Step 2<div class="intercom-interblocks-table-container"> <table role="presentation"> <tbody> <tr> <td style="background-color: #d7efdc; width: 320px;"> <p class="no-margin">Header 1</p> </td> <td> <p class="no-margin">Header 2</p> </td> </tr> <tr> <td style="background-color: #e8e8e8; width: 320px;"> <p class="no-margin">Lorem ipsum dolor sit amet</p> </td> <td> <p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p> </td> </tr> <tr> <td style="width: 320px;"> <p class="no-margin">Ut enim ad minima veniam</p> </td> <td> <p class="no-margin">Consectetur adipiscing elit</p> </td> </tr> </tbody> </table></div> Example Step 4 Example Step 5<div class="intercom-interblocks-table-container"> <table role="presentation"> <tbody> <tr> <td> <p class="no-margin">Header 1</p> </td> <td> <p class="no-margin">Header 2</p> </td> </tr> <tr> <td> <p class="no-margin">Lorem ipsum dolor sit amet</p> </td> <td> <p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p> </td> </tr> <tr> <td> <p class="no-margin">Ut enim ad minima veniam</p> </td> <td> <p class="no-margin">Consectetur adipiscing elit</p> </td> </tr> </tbody> </table></div>