Share product ideas and upvotes with our product team
Hey team, Some members of our team have cases un-snooze after their work day. People go in and snooze the cases again however, we just learned that when you snooze a case for a specific time, it snoozes it in your time zone and not the time zone of the person the case belongs to.Is it possible to change this so that it always defaults to the time zone of the case owner rather than the person snoozing it on their behalf?
Hey team,Our support team have recently implemented Intercom Scorecards. I know this feature is in Beta, so I will preface this with hoping some of these features are coming soon. However, Customer Success wants to utilize the Scorecard they have implemented and found the following issues:When creating a new scorecard and adding existing scorecard criteria - if you make any edits to that existing criteria it changes any scorecard with that criteria - rather than allowing you to have a version of the same criteria. Some of the settings when using the same criteria do not automatically copy (rating reasons) meaning that you have to manually go in and set this up, when it should copy ALL existing settings. It would be great to be able to just duplicate and rename a scorecard rather than having to create a new one, and then copy the settings (that don’t all copy over). It’s very confusing. I would also like the ability to save view in the Scorecard so that I don’t have to filter each time. I would also like the ability to filter by Inbox rather than just reviewees.Thank you!
The Macro schema does not currently expose folder information, which prevents macro folders from being used as programmatic identifiers.For example, we organize sales-related macros in a Sales folder. To build a dashboard for those macros today, we must hard-code every macro ID. Adding or removing a macro then requires a code change. Please add a folder_id to the Macro schema. This in turn will make it available in the Retrieve a Macro and List All Macros endpoint responses. With that, consumers could simply:Retrieve all macros Filter by folder_id (for example, 1234 for Sales)This would make macro integrations easier to maintain and enable more flexible filtering, especially if a Macro search endpoint is added in the future.
The @mention search functionality does not appear to continuously filter results as more characters are typed. For example, entering @Maria M still returns many unrelated names. The search should progressively narrow results and prioritize the closest matches based on the full text entered.
At this time it is not possible to add a table in an email reply or note.We are currently migrating from Zendesk to Intercom and our teammates used to add tables is about half of their communications. So this is a big gap in the Intercom functionality.
Hey there, I would really like to be able to merge conversations. is that on the roadmap yet?
I was hoping to be able to set up a workflow to better identify when we have a first time chatter reach out. Ideally it would be something like; previous chats = 0 if so apply a note to the chat stating that this is a new user chatting in for the first time.
Hi there, It would be a huge advantage to be able to edit sent messages to customers through Intercom Messenger. If a mistake is made, then you have to delete the message which is displayed that it has been deleted to the user, it’s not ideal at all. There are countless times it has been mentioned in our organization that we need the ability to edit the messages and we are surprised it’s not already a feature. Hopefully this is something that can be added. Thank you, Caitlyn
We would like more granular control over how individual teammates are presented to customers when sending emails from Intercom.Currently, teammates may need to communicate from different email addresses or inboxes depending on the type of request. For example, a VIP teammate may sometimes send from a dedicated VIP/Loyalty address, while at other times they may need to use a general Support address.At the moment, the customer-facing identity cannot be configured independently enough for each teammate or sending context. This can result in the same teammate being presented with an identity, role or signature that does not accurately reflect the context of the email being sent.Ideally, admins should be able to configure customer-facing email identity settings at one or more of the following levels: Individual teammate Team or Inbox Sender email address This could include: Display name or alias Team or role label Email signature Brand presentation Where possible, the correct identity and signature should be applied automatically based on the sender address or Inbox being used.This would allow teams such as VIP, Customer Relations and general Support to work within the same Intercom workspace while maintaining an accurate and professional customer-facing identity for each type of communication.
Problem:Our Help Center supports regional English variants (English (US) and English (Canadian)) and correctly serves the right version based on language override (we’d like to confirm as well that language override takes priority over browser language) when accessed directly. However, the Messenger only supports base language codes (e.g., en), not regional variants. This means a member with language_override set to en-US and one set to en-CA both see identical Messenger content (our default content set to en-CA ), there's no way to differentiate.Why this matters:Most of our members access the Help Center through the Messenger, not by visiting Help Center articles directly. So in practice, our regional Help Center translations only work for the small fraction of traffic that lands on articles directly — the primary access point (Messenger) can't route members to the correct regional version at all. This creates real accuracy problems: US members can end up seeing Canadian-specific content (pricing, policies, terminology) and vice versa, which actively misleads them.Requested feature:Allow Messenger language settings and language_override to support regional locale codes (e.g., en-US, en-CA, fr-CA, fr-FR), not just base language codes — so Messenger-served Help Center content matches the same regional targeting already available for direct Help Center visits.
We manage multiple Facebook pages as well as a large Facebook group through Intercom. One challenge our Support team runs into is that when someone comments on a Facebook post, the comment comes into Intercom without the context of the original post or thread.This can make it difficult for our team to understand what the user is responding to and provide an accurate response.It would be extremely helpful if Facebook conversations in Intercom included a direct link to the original Facebook post/thread the user commented on. This would allow our team to quickly view the context before responding and provide better, more accurate support.
Right now, Intercom's Telegram channel (Settings > Channels > Telegram) only supports connecting a standalone bot created via @BotFather. Customers have to find and message a separate bot username, which feels disconnected from the actual business.Telegram now offers "Business accounts" (available to Premium subscribers) that let a company keep its real, verified Telegram account — complete with opening hours, quick replies, greeting/away messages, and a business chat link — while automating replies through the Bot API's business_connection feature. A connected bot can send and receive messages on behalf of that real account instead of a separate bot identity.It would be great if Intercom supported connecting a Telegram Business account as a channel, the same way the current bot flow works today:- Conversations from the Business account land in the Inbox, with Fin and Workflows at full parity- Replies go out through the business_connection, so customers see the business's real name and photo — not a bot- Native Telegram Business settings (hours, quick replies, greeting messages) stay usable in Telegram itself, while Intercom handles the actual conversationThis matters most for teams whose customers are concentrated in markets where Telegram is the primary channel — a verified business account feels far more trustworthy and personal than a generic bot. Right now the only way to bridge this gap is third-party middleware, which adds cost and an extra hop. Native support would remove both.
Is there a way we can have this option back? i.e. we simply hide the decline button but without turning on auto-answer? We're wanting to discourage missing calls but not put customers in a situation where they're connected with an agent who is away from the desk without aux state update (human error/mistake).
Access Management for Team MailboxesCustomer service representatives should have access to all shared mailboxes at the team level. However, they should not have access to other employees' personal mailboxes.In the current setup, a customer service representative can access a colleague's personal mailbox and view detailed information about what that person has been working on throughout the day. This provides visibility into an individual's productivity and case handling activities, which is not necessary for performing day-to-day responsibilities.We would therefore like to restrict access so that:Customer service representatives have access to all team shared mailboxes. Customer service representatives do not have access to other employees' personal mailboxes. Only managers or other authorized roles have access to employee-specific information when required.Purpose: To ensure appropriate data access, protect employee privacy, and limit visibility to information that is necessary for job-related tasks.
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.
We use Fin in the Inbox, but we repeatedly run into the same problem: Fin sometimes sends very long messages and occasionally incorrect or irrelevant information.At the moment, Fin only reliably stops once an agent actively replies in the conversation.This is a real issue in day-to-day operations because when I’m on the go, I often can’t reply immediately — but I still need to stop Fin instantly as soon as I see that it’s going in the wrong direction.Feature request: “Stop Fin without replying”I’m requesting a way to immediately pause or stop Fin without requiring an agent to send a message.Clear trigger examplesFin should automatically stop when any of the following happens: The conversation is assigned to an agent An agent takes over / opens the conversation A manual toggle in the conversation header: “Pause Fin” / “Stop AI replies” (one click) Controllable on mobile (e.g. via the Intercom mobile app while on the go) Why this matters Prevents incorrect information from being sent to customers (quality & brand risk) Avoids unnecessary long AI messages in the chat (customer experience) Allows a safe handover to a human even when mobile, without having to send a “placeholder” reply just to stop Fin Acceptance criteria When a conversation is assigned to an agent, Fin stops immediately (no further messages or follow-ups). Agents can pause/stop Fin without sending a reply (UI control). The feature is available on mobile (at least stop/resume). Optional: audit log (e.g. “Fin paused by Gustav via assignment/manual toggle”).
Currently, when an outbound conversation is created, it is correctly assigned to the teammate addressing the ticket. However, if a team is later assigned—either manually or automatically—the assigned teammate is removed, even if they belong to the assigned team.This issue became more problematic with Balanced Assignment enabled. Once the team is assigned and the original teammate is unassigned, the system automatically reassigns the conversation to a different teammate. As a result, we have to manually reassign the conversation back to the original handler, adding unnecessary workload and potential confusion.We’d like to ensure that when a team is assigned, the original teammate remains assigned to the conversation.
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.