Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3160 Ideas

    ericMBActive User

    Intercom KB needs article searchSubmitted

    I have a small number of articles, but to change “characteristics” to “attributes”, I am going to have to open each of them and do a browser search for that word. That situation becomes rapidly untenable as the number of article grows.As far as I can tell, the current KB search only examines the title and summary-descriptor. That’s fine for end users. Most of the time, that’s all they’ll need. But for the creators of the knowledge base, the KB must act more like a publication system--in this regard, at least.(It does a fine job with link management, which is no small feat. Bit this functionality is important, too. You don’t need it all the time, but when you need it, you really need it.)Perhaps there is an AI tool that can be employed to walk the article-tree and find relevant articles? For extra credit, I would recommend functionality I once implemented for a now-defunct documentation system:Allow replacement text to be specified Allow system-wide “replace all” but only after checking 27 times to be sure that’s what they really want to do Visit each article that contains the text, in edit mode Allow “replace all” within the article Allow a simple replace-and-go-to-next-instance (same article or next article)  Allow a revised-replacement Allow further revisions to the article, as long it’s already open for editing. - Sometimes, wording needs to be changed to accommodate the replacement text. - Sometimes, necessary revisions leap out at you while viewing the text. (It’s easier to do it in the moment, instead of having to take a note, remember to act on it later, find the article again, and then make the change.)CORRECTION:Intercom does have article search. (Thank God!). It wasn’t easy to find in the Help system, and I was oblivious to it in the KB pages, but it’s there. Right at the top of the folder listing, there is a “search for text” box. (Too cool! Searches within that folder, I think.) For a global search, go to the top-level container (Content), and do the search there. Yay! That at least makes it possible to find all occurrences. (You then visit each article in turn, click Edit, do a browser-search for the term in question, and type in a replacement. Not exactly convenient, but it is at least possible to get the job done.(BTW: Thanks for listening! :__)

    NynkeNew Participant

    Translate outgoing messages with AI inbox translationSubmitted

    Right now, when AI inbox translation is activated, incoming messages are naturally translated to English (our main language), and outgoing messages are translated from English to the language of the customer, as it should!However, in case an agent replies in the language of the customer (so not in English), their message isn’t translated to English in the backend, making it hard to have this case potentially picked up by another agent later on since they will have to manually translate the outgoing message if they don’t speak the customers’ language.Here is an example:A German customer contacts us Their message is automatically translated to English due to the AI Inbox translation The case is assigned to a German agent The agent replies in German since this is their native language and they can better express themselves this way, and most likely produce a better German reply than having it translated The customer comes back a few days later and the case now gets assigned to an English agent The English agent is only able to read the incoming messages (which have been translated with AI Inbox Translation to English), but the outgoing messages remain in German as they were originally written in German The agent now has to manually translate all outgoing messages to get a full picture of the case and workflows become inefficientThe suggestion here is to ensure that when AI Inbox translation is enabled, any outgoing messages that match the language of the customer are translated to English in the backend, and agents can switch between the original and translated view just like with the incoming messages.

    Sunita JakharNew Participant

    Feature Request: Translation Feature Improvement – Preview Before Send & Multilingual Reply Support for AgentsSubmitted

    Feature Request: Translation Feature Improvement – Preview Before Send & Multilingual Reply Support for Agents Description:We’d like to request enhancements to Intercom’s automatic translation feature to improve the agent experience and reduce translation-related issues when handling non-English conversations.Current Limitation: Agents cannot preview how their English response will be translated into the client’s language before sending it. Agents who are fluent in the client’s language (e.g., Dutch, French, Portuguese, Norwegian etc) are forced to reply in English, as direct replies in the client’s language are either discouraged or overwritten by the translation tool. This limits flexibility and increases the risk of tone or meaning being lost in translation. Proposed Enhancements: Translation Preview Before Sending: Allow agents to see a real-time preview of how their message will be translated before clicking “Send.” Multilingual Reply Option: Provide an option for agents to respond directly in the client’s language without triggering auto-translation — ideal for agents with the appropriate language skills. These improvements would give multilingual agents more control, reduce translation errors, and improve the overall quality and tone of client communication.Business Impact: Reduces risk of miscommunication in client interactions. Increases confidence among multilingual agents. Improves customer experience, especially in regulated or sensitive communication. Please let us know if this is feasible and whether it's already on the roadmap.