Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    2806 Ideas

    Arunkumar KumaresanNew Participant

    Incremental / URL-Level Sync for Website SourcesSubmitted

    ProblemFor website-based knowledge sources, the current Re-sync operation performs a full crawl of the entire website.In large deployments, this can involve thousands of pages. In our case, the source contains approximately 3,600 articles. When a single new article is published, there is currently no way to make only that article available to Fin immediately without triggering a full website crawl.Requested CapabilityProvide a way to selectively sync website content instead of requiring a full re-crawl.Possible options:Sync a single URL on demand. Sync a selected set of URLs. Incremental sync that discovers only new or modified pages since the previous crawl.BenefitsFaster Content AvailabilityNewly published articles can become available to Fin immediately without waiting for the next scheduled crawl.Reduced Processing TimeAvoid re-processing thousands of unchanged pages when only one or two pages have changed.Lower Resource ConsumptionReduces crawler workload, indexing time, and system resource usage for both customers and Intercom.Better Operational EfficiencyAllows support teams and knowledge managers to quickly publish urgent content updates and make them available to Fin.Example Use CaseA website source contains 3,600+ articles.A new troubleshooting article is published for an ongoing customer issue.The administrator wants Fin to learn only that newly published page immediately, rather than initiating a full crawl of all 3,600 articles.Current WorkaroundsWait for the weekly automatic website sync. Create a temporary Knowledge Hub Snippet. Trigger a full website re-sync.None of these provide true URL-level synchronization.Expected OutcomeAllow administrators to selectively re-index specific pages or run incremental website syncs so that newly published content can be made available to Fin quickly and efficiently.

    Gemma GWConnector

    Side Conversation Delivery Status and Failure NotificationsSubmitted

    Side Conversation Delivery Status and Failure NotificationsOur organization uses Side Conversations extensively to engage external teams, vendors, and partners. We have actively encouraged our users to stop emailing individuals directly from customer conversation threads and instead use Side Conversations as the standard workflow for involving external stakeholders. (Before teams were remove participants, deleting conversation thread, sending a message, then readding participants..)In customer conversations, Intercom provides visibility/error when an email cannot be delivered. However, Side Conversations do not provide any delivery feedback.Today, if a Side Conversation email fails to reach the recipient, there is no notification to the sender, no visible delivery status, and no indication that follow-up may be required (apart from checking whether a message is marked as "Seen" to confirm delivery.) While this can confirm that a recipient has opened a message, it does not solve the primary problem: There is no confirmation that an email was successfully delivered. There is no visibility into delivery failures. Users may assume an external team has received a request when they have not. Critical customer issues can be delayed because senders are unaware of delivery problems.  Requested EnhancementIntroduce delivery and failure visibility for Side Conversations similar to customer conversation emails, including: Delivered status Failed delivery status/Delivery error details where available Optional notifications to the Side Conversation creator or assignee when delivery fails  

    Apptrove MMPNew Participant

    Ability to Add No Index Tag to individual help centre ArticlesSubmitted

     Feature Request: Per-Article Search Engine Indexing Control for Help Center ArticlesI would like the ability to control search engine indexing at an individual article level within the Intercom Help Center.Current ProblemOur organization has knowledge base content published both on our main company website and in the Intercom Help Center. Some articles have similar or identical titles/content.Currently, Intercom only provides these options: Disable indexing for the entire Help Center. Make articles Unlisted, which removes them from Help Center navigation and search, remains only accessible through direct link. None of these meet our requirement.Desired FunctionalityWe need a per-article setting (for example, a toggle in the article editor or details panel) that allows:✅ Article remains: Publicly accessible via Help Center URL Visible in Help Center navigation Searchable within Help Center search for all visitors ✅ But: Not indexed by external search engines like Google/Bing Does not appear in public search results Search engines receive a noindex directive for that specific article Suggested ImplementationAdd an article-level SEO setting such as:Search Engine Visibility☑ Allow search engines to index this article☐ Prevent search engines from indexing this article (meta robots="noindex")This could be added in the article Details or SEO Settings section.Use CaseWe want our primary website content to rank on Google while still keeping duplicate/support content fully discoverable inside the Intercom Help Center for customers.This feature would help avoid duplicate content SEO conflicts without impacting the Help Center user experience.This version should work well for Intercom’s Product Wishlist submission.

    Product ManagementNew Participant

    Condition based content blocks within an Article to support Multiple Help Centres & Targeted audiencesSubmitted

    Problem Statement:As an enterprise organisation that supports multiple white label solutions, we have a large collection of articles in our legacy help centre that supports our direct and white label customers.  We are in the process of migrating this content over to Intercom and leveraging the Multi Help Center feature. However, we have found that we may have to have 10 or more articles on the same subject matter but may vary slightly due to various reasons so as to not only support our direct customers but our white label ones too. This potentially is a content management nightmare. 😫 Driving Motivation:Is to not have 10 or more duplicates of the same article that cater for a different White Label audience(s), especially in our case where we would roll out a new feature to our direct customers first and then onto our white labels at a later stage or not at all, this can vary.  Ongoing maintenance of said content would be time consuming and resource intensive. Idea/Feature Request:We think, it would be highly beneficial to have conditional content blocks as a new component within an article which when placed on the page could have a targeted audience by setting an audience rule.Once a conditional content block is placed on the page in edit mode we can then place any of the other article component within that conditional content block like Insert an Image, Embed a video, insert a div or call out etc.We then set the targeted audience on that block using the same audience filter rules as you would use when setting up any pro active outbound campaign. (i.e. be able to set the audience based on user or company attributes etc). Additionally, the article would still respect the targeted audience as set via article settings (Visitors, Leads, Users), then at the content level with the conditional block in-line and one ore more article components set in it (i.e. a picture or paragraph of text), we can then set and specify a target audience with audience rules filters / segment creation.Multiple audience rules can be set per conditional content block using AND/OR conditions along with all the operators (is, is not, contains, greater or less than etc) that are used with user or company attributes.Design:Proposed element that allows for conditional content blocks within an articleThanksRuairí

    Dariya KhanNew Participant

    Feature Request: Granular Channel Segmentation (Emails, Calls, Chats) within a Collapsible "Your Inbox"Submitted

    DescriptionObjective We are looking to optimize the agent workspace by transforming the top-level "Your inbox" section into a dynamic, collapsible category list that segments work by channel type: Emails, Calls, and Chats. As attached in our design concept (image_d56e80.jpg), this change will drastically improve workspace organization and help agents prioritize real-time vs. asynchronous conversations seamlessly.The Current Challenge Currently, the standard Intercom sidebar aggregates all assigned conversations under a single, flat "Your inbox" counter. Lack of Instant Visibility: Agents cannot tell at a glance whether their pending notifications are urgent live chats, inbound calls, or asynchronous emails. Sidebar Clutter & Extra Clicks: To differentiate work by channel, teams are forced to scroll down and rely heavily on heavily populated "Team inboxes" or custom "Views" (e.g., Backlog - Emails, Abandoned Chats). This forces agents to constantly shift contexts and navigate away from their primary personal inbox. The Proposed Solution We propose making "Your inbox" an expandable dropdown folder at the very top of the hierarchy. When expanded, it reveals distinct sub-categories with individual badge counts for: Emails Calls Chats This retains the clean layout of the Intercom sidebar while surfacing crucial channel information directly within the agent's personal workspace.This UI enhancement changes the personal inbox from a simple landing page into a strategic command center for frontline agents. We would love to see this implemented to help support teams scale their efficiency!

    Home Dashboard for Custom Reporting & Multi-Brand OperationsSubmitted

    Business NeedAs a multi-brand organization, our teams rely heavily on reporting to monitor conversation volume, performance, customer experience, and operational health across brands. Currently, users must navigate into reports to access key metrics, and in some cases reporting limitations around conversation data updates create visibility challenges.Proposed EnhancementProvide an option to configure a custom dashboard that appears immediately upon entering Intercom. This dashboard would serve as a reporting homepage and display user-selected metrics, reports, and widgets relevant to daily operations.Why This MattersFor organizations managing multiple brands, having instant visibility into operational metrics would: Reduce time spent navigating through reporting menus. Improve awareness of conversation trends and workload changes. Help managers identify issues requiring immediate attention. Increase adoption of Intercom reporting as a daily operational tool. Create a more executive-friendly experience for leadership teams. Additional Consideration: Data Accuracy Across Brand ChangesThe value of this dashboard depends on reporting reflecting the current conversation attributes. We have observed situations where conversations are reassigned or updated with a different company after creation, but reporting appears to continue reflecting only the original company value.For multi-brand organizations, this creates reporting gaps because conversations may be correctly categorized operationally but not represented accurately in reporting.A dashboard solution would be significantly more valuable if reporting consistently reflected the most current conversation/company attributes, allowing organizations to measure activity accurately across brands.Company Name is just one example. This happens with other attributes too. Expected OutcomeA configurable reporting dashboard combined with reporting based on current conversation metadata would provide a true operational command center for multi-brand teams and improve confidence in Intercom as a source of business reporting.