Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3157 Ideas

    YoeriNew Participant

    Feature Request: Global Find and Replace for Articles (Help Center)Submitted

    Hi all,We are currently using Intercom Articles as our primary Help Center. However, we are running into a significant efficiency bottleneck whenever our software UI changes.Currently, if a UI label or feature name changes, we have to manually search for every single occurrence across all articles and update them one by one. For a modern documentation tool, this manual process is highly prone to error and very time-consuming.We would like to propose a "Find and Replace" functionality within the Articles product. Proposed Functionality:A dedicated tool that allows admins to search for a specific term and replace it:Scope: Option to apply changes to "All Articles" or "Current Article only".Search/Replace: e.g., Replace 'Brandkit' with 'Brand Identity'.Key Features/Checkboxes:Match Case: Ensure that capitalization is preserved (e.g., 'brandkit' becomes 'brand identity', while 'Brandkit' becomes 'Brand Identity').Preserve Formatting: Ensure the replacement term keeps the original styling (Bold, Hyperlinks, Italic, etc.) of the term it replaces.Why this matters:In a fast-growing software environment, UI terminology evolves. Manually updating hundreds of articles to match the current UI is a hurdle that prevents us from keeping our documentation up to date. A Global Find and Replace tool would significantly improve the developer and content creator experience within Intercom.Is this something currently on your roadmap, or can this be shared with the product team?Best regards,Yoeri from MailBlue

    YoeriNew Participant

    Feature Request: Global Find and Replace for Articles (Help Center)Submitted

    Hi all,We are currently using Intercom Articles as our primary Help Center. However, we are running into a significant efficiency bottleneck whenever our software UI changes.Currently, if a UI label or feature name changes, we have to manually search for every single occurrence across all articles and update them one by one. For a modern documentation tool, this manual process is highly prone to error and very time-consuming.We would like to propose a "Find and Replace" functionality within the Articles product. Proposed Functionality:A dedicated tool that allows admins to search for a specific term and replace it:Scope: Option to apply changes to "All Articles" or "Current Article only".Search/Replace: e.g., Replace 'Brandkit' with 'Brand Identity'.Key Features/Checkboxes:Match Case: Ensure that capitalization is preserved (e.g., 'brandkit' becomes 'brand identity', while 'Brandkit' becomes 'Brand Identity').Preserve Formatting: Ensure the replacement term keeps the original styling (Bold, Hyperlinks, Italic, etc.) of the term it replaces.Why this matters:In a fast-growing software environment, UI terminology evolves. Manually updating hundreds of articles to match the current UI is a hurdle that prevents us from keeping our documentation up to date. A Global Find and Replace tool would significantly improve the developer and content creator experience within Intercom.Is this something currently on your roadmap, or can this be shared with the product team?Best regards,Yoeri from MailBlue

    Limble EngineeringNew Participant

    Ability to Set Defaults for Article Fin Availability /OR set via APISubmitted

    Summary:Provide the ability to control Fin agent access to articles by default (either individually or a folder level default), and/or support for configuring this setting via API while creating/updating articles.Problem:Currently, all published articles default to having Fin access enabled. While we intentionally publish some articles as unlisted (accessible only via direct link), Fin can still surface these articles and information within to users.Our team frequently manages articles via API and is not always working directly in Intercom. As a result, we cannot reliably disable Fin access without manually logging in and updating each article.Why this matters:Unlisted articles are meant to be restricted to users with direct links Fin surfacing these articles can expose context-specific or limited-use information This can lead to: Customer confusion Incorrect guidance being shared Increased support friction Current limitations:No way to set Fin availability defaults for articles No API support to enable/disable Fin access No ability to control this at the folder level Fin audience settings exist at an individual article level, but are not configurable via APIProposed Solution Ideas:Allow setting a default Fin availability state (e.g., OFF by default) Add API support to control Fin access per article Enable folder-level settings to manage Fin access at scale Ensure unlisted articles can be excluded from Fin by defaultImpact:This would give teams better control over what Fin can surface, prevent unintended information exposure, and reduce manual workflows when managing content programmatically.

    Leandro WenzinNew Participant

    Allow routing “Continue on WhatsApp” to different numbers based on customer country or other attributesSubmitted

    Currently, the “Continue on WhatsApp” action always routes the customer to a single WhatsApp number configured in Settings → Channels → WhatsApp → Switch from Messenger to WhatsApp (one number per workspace).This creates a limitation for companies operating in multiple countries with different WhatsApp numbers per region. There is no way to direct customers to their corresponding local number, which negatively impacts both customer experience and operational efficiency.Problem:If a business uses different WhatsApp numbers per country, all customers are still redirected to the same number, regardless of their location or attributes. This can lead to:Customers contacting the wrong regional team Delays in response times Fragmented conversations and routing issuesSuggested improvement:Allow agents or automation rules to select which WhatsApp number is used when triggering “Continue on WhatsApp”.For example:Route based on customer attributes (e.g., country, language, region) Allow rules in workflows to define the destination number Allow agents to manually choose the WhatsApp number when using the “Use Continue on WhatsApp” action in conversationsThis last point would already be a significant improvement, as it would give support teams immediate control to route customers to the correct local number during live conversations.This would enable businesses to:Maintain local communication channels Improve response times and routing accuracy Preserve a better customer experience across regions