Share product ideas and upvotes with our product team
It would be great to be able to use the SLAs for team inboxes with response times the same way as we can automatically enter attributes in the messages or notes. Right now the idea I have is for the reusable workflow to be triggered by the agent, which would post current response time for each team that we have, and they would be used to write custom message for the user after the request is passed to relevant team. It is possible to post the ETA with the automation, but this way the agent reply loses points in its individuality and care, so hope you add such an option too :)
It would be very helpful if teammates could draw or annotate directly on a customer's screenshare during calls.When customers are sharing their screen, teammates often need to point out a specific button, field, setting, or area of the page. Today, we have to describe it verbally, which can slow down troubleshooting and make the experience more confusing for customers.Ideally, teammates could temporarily draw, highlight, or point on the shared screen during a call. This would make it easier to guide customers through setup, debugging, onboarding, and support workflows without needing a separate screen annotation tool.
Wanting the ability to react to customer messages not only on internal notes. This is good for channels like slack where an emoji could be seen on the inital message to signify action is being taken without having to go into the thread.
Action notifications should be a personal preference that users can toggle on or off. We can disable them workspace-wide through the API, but preferences vary: some people find them useful, while others strongly dislike them. This should be a user-level setting, not a workspace-wide default.
Customers would like more granular control over AI Inbox Translation by allowing incoming and outgoing translations to be managed independently.Currently, AI Translation functions as a single feature that both:Translates incoming customer messages for teammates. Automatically translates teammate replies back into the customer's language.This all-or-nothing approach creates challenges for teams that work with domain-specific, technical, or industry terminology, where automatic translation of outgoing messages can reduce accuracy, alter intended meaning, or negatively impact customer communications.Requested improvements include:Separate toggles for incoming and outgoing translations. The ability to enable incoming translations while keeping outgoing messages in their original language. Making outgoing translations opt-in rather than automatically applied. Improved handling of technical, product-specific, and domain-specific language to preserve accuracy and context.This would give teams greater control over customer-facing communications while still benefiting from translated incoming messages.
Currently, when an agent holds an Intercom seat, they cannot be CC'd on outbound emails sent through Intercom by another agent. The only available workarounds are tagging the agent in the notes section or reassigning the ticket entirely, neither of which is ideal when the need is simply to keep someone in the loop or copied on a back-and-forth email thread.This creates a challenge for teams where not all seat holders are full-time Intercom users. We do not believe this would introduce any risk of an email loop, as the intent is simply to copy an internal agent on an outgoing email, no different than a standard CC in any email client. Adding this functionality would bring Intercom more in line with how email naturally works and would greatly improve our visibility across the team when needed.
We would like to request a better way to organize linked websites for Help Center content (linked websites cannot be managed or organized, even into simple folders.) They currently sit stacked on the left menu bar and it’s a mess.
We would like to request a better way to organize linked websites for Help Center content (linked websites cannot be managed or organized, even into simple folders.)!--scriptorendfragment-->
I want to track anonymous end users searching for articles. This is a feature Zendesk has built into their platform and should really be a standard in Intercom. Right now, the only way to get this specific is to use the Google Analytics integration (according to FIN, but FIN is often inaccurate). Not having this feature is a big setback and doesn’t provide for accurate analytics.
Hi Intercom team,I’d like to submit a feature request regarding forwarded emails and quoted content handling in Intercom. Feature requestIt would be very helpful if Intercom could preserve and expose the full forwarded email content, including quoted messages and attachments, regardless of which email client was used to forward the email. Current behaviorWhen an email is forwarded from the web interface of the email provider, the forwarded content and attachments are visible in Intercom as expected.Example conversation:https://app.intercom.com/a/inbox/iln7babw/inbox/shared/all/conversation/215474365038458?view=ListHowever, when the same email is forwarded from Apple Mail on macOS, the quoted forwarded content and/or attachment is not visible in Intercom.Example conversation:https://app.intercom.com/a/inbox/iln7babw/inbox/shared/all/conversation/215474364926343?view=List Why this mattersOur workflow depends on reading forwarded customer emails inside Intercom and also accessing this conversation data through exports and the API.At the moment, if the email is forwarded from Apple Mail, the quoted forwarded content is not available in the Intercom conversation export as text or PDF, and the same incomplete data is returned through the API.This makes it difficult to reliably process forwarded emails, because the available conversation content depends on the email client used by the sender. Expected improvementPlease consider adding support for preserving and exposing the full forwarded/quoted email content and related attachments in Intercom, including cases where the email was forwarded from Apple Mail or other desktop email clients.This would make forwarded email handling more consistent across email clients and more reliable for API-based workflows.Thanks!
We need the ability to merge related emails/phone calls/chat tickets regardless of the original DNA of the channel type.
Hi Intercom Product Team,We are currently facing a limitation when retrieving conversation data through the Intercom API. For conversations with a large number of parts, the API response does not include all conversation parts, while the missing parts are still visible in the Intercom UI.This creates a data gap on our side, especially for analytics, reporting, auditing, and operational use cases. Since we rely on the API to ingest conversation data into our data warehouse, any missing parts can lead to incomplete or inaccurate reports.The main challenge is the current hard limit of 500 conversation parts. We would like to request one of the following improvements:Add pagination support for conversation parts. Provide a dedicated endpoint to retrieve all parts for a conversation. Include a cursor or next page token when a conversation has more than 500 parts. Provide an export option that includes the full conversation history.This would help ensure API data matches what is available in the Intercom UI and allow teams to build more reliable reporting and analytics.Thank you.
Why It Matters:Customer Experience: When customers receive replies in their native language, it significantly improves satisfaction, trust, and perceived support quality. Not replying in the customer’s language can lead to frustration, misunderstandings, and reduced resolution rates. Agent Efficiency: Manual translation of converted chats is time-consuming and error-prone. Agents spend extra effort translating messages, which slows response times and reduces the number of tickets they can handle. Scalability: As your business grows globally, manual translation doesn’t scale. Auto-translation enables seamless multilingual support without hiring additional translators or expanding language-specific teams.Risks to Consider:Accuracy & Nuance: Machine translation may not always capture context, tone, or industry-specific terminology, potentially leading to miscommunication. Data Privacy: Translating customer data through third-party services may raise compliance concerns (e.g., GDPR, data residency). Customer Expectations: If translation quality is inconsistent, customers may become frustrated when messages are unclear or inaccurate. Implementation Complexity: Integrating translation into ticket workflows requires changes to existing systems and may impact performance or user experience.Impact of Not Translating:For Customers: Receiving messages in a language they don’t understand can lead to confusion, repeated follow-ups, and a perception of poor support. For Agents: Manually translating adds cognitive load, increases response times, and may lead to burnout or errors. For the Business: Poor multilingual support can result in lower CSAT scores, higher churn, and missed opportunities in non-English-speaking markets.
Having an out of office for a particular inbox, rather than workspace. We have teams who aren’t customer facing working on back office tickets/have chats in their name while tickets are being dealt with in Jira. It would eb good to have an out of office for their inbox so customers know to create a new chat for a response from our customer services team as the escalations team wouldn’t deal with this.
Hi,I'd like to log a feature request and get your read on it.We rely heavily on automation and an AI agent in our support setup, and one of our biggest time sinks is duplicate tickets — the same user opening two or more conversations about the same request. We'd love to deduplicate these programmatically.The Merge into action already exists in the Inbox UI and is exactly what we need. The gap is that it's UI-only — there's no REST API endpoint or Workflows action to trigger it, so our automation and AI agent can't use it. I've confirmed this in your developer community (the "Conversation Merge via API" thread), where your team confirmed merging is currently manual-only.My ask: could you log a request for the existing merge action to be exposed via the API? Since the feature already exists in-product, this should be surfacing it rather than building something new.And to double-check before we plan around it — is there genuinely no current API or Workflows path to merge two conversations? If there's anything on the roadmap here, even rough timing would help us decide whether to build a workaround in the meantime.Thanks,DanielPraktika
Would it be possible to add tags to macros or something similar? Being able to only search macros with the exact title is limiting. For instance, say I have a macro titled “As you get going” since those are the first words of the macro, but it would be helpful to also be able to search “Getting Started” as a tag or alternate title. Something more intuitive for new learners!
I would like the ability to search for articles by their ID, not just by their title or keywords. This makes it easier for me to navigate to a specific article to review/edit when several might match by their title or keywords otherwise.
As a company we are using Macros significantly more as a time saving mechanism. However, we are finding the monitoring of their usage really challenging. It would be really useful to have a reporting dash which allows us to monitor Macros. How many times they’re being used, which are the most popular etc
We are desperate to have folder for our macros. This is functionality Zendesk has. Please Please bring in folders for macros!
Currently it is only possible to send videos from Trainn through FIN in a conversation. To make sure our customers get the full picture and all possible information, we would need to be able to embed the videos in our help articles as well.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
OKSorry, our virus scanner detected that this file isn't safe to download.
OK