Share product ideas and upvotes with our product team
I would like to have this as separate options. I would love to give my team the ability to delete internal notes but not give them the ability to delete replies
Hi Intercom team! I wanted to pass along a suggestion that would really help with reporting and real‑time analysis. Right now, we’re only able to see agent statuses as Active, Away, Away and Reassigning, or On a Call. It would be incredibly helpful to also see when an agent is actively working on a chat, email, or social media interaction while in a blended environment. Something like “Active (Chat), Active (Email), Active (Social)” would be a great upgrade. I know we can see in conversations when an agent resumes working on an interaction, but having that reflected in their real‑time status—both in Intercom and in our WFM tool—would give us much better visibility. It would improve reporting accuracy and help the WFM team monitor workload and staffing needs more effectively.
Right now, you can set / manage conversation data / attributes through ticket workflows, but you cannot do the same for ticket date / attributes. It would be helpful to support the same functionality for ticket data. For example, if a teammate changes a ticket state or certain filters apply to a ticket, it would be helpful to be able to set a ticket attribute.
Hello Team,Having different ringtones for incoming phone calls would be great . The notifications sounds can be changed but not the ringtone for phone. Maybe providing a few softer or upbeat options would be great.
Similar to the existing functionality to require conversation attributes to be completed prior to closing a conversation, it would be helpful to require that certain ticket attributes be completed by teammates before a ticket is resolved or closed. We often utilize ticket attributes for reporting purposes and it would be helpful to be able to enforce certain attributes be completed by teammates prior to resolving/closing tickets rather than just at ticket creation. Conversation attribute:Ticket attributes:
Feature Request: In-Chat Screen Capture & Recording IntegrationWhat we need? We want to empower drivers to provide instant visual context during support sessions. The goal is to take the existing "Report an issue" logic currently found in the pre-login Help Center and embed it directly into the driver’s active chat interface. This creates a "show, don't tell" experience that saves time for both the driver and the support agent.How should it WorkPlease refer to the following step-by-step logic currently utilised in our login-screen Help Center: The Entry Point: Within the active chat window, a new "Screen Capture" icon is added to the input bar. The Modal Trigger: Tapping this icon opens a "Help Center" style overlay. This overlay should offer a clear "Report an issue (screen capture)" button, mirroring the current support UI. System Authorization: Once selected, the app triggers a system-level permission dialogue (e.g., "Start recording or casting with Bettermile?"). This ensures the driver is aware of the recording. Privacy Protection: The interface must display a clear disclaimer—as currently seen in the app—warning the driver that anything visible on their screen (passwords, messages, etc.) will be captured. Seamless Attachment: Upon clicking "Start" and completing the capture, the recording/screenshot should not just save to the device; it should automatically upload and send as a message directly into the current chat thread.
It would be beneficial for the article history to be able to be surfaced over the Intercom API.Specifically so that it is possible to report on when an article was updated and who updated the article.
At the moment, Copilot relies on the original attribute assigned to the ticket. Manually changing the attribute afterward does not have any effect.In Snippets, we assign a specific audience based on an attribute, and this attribute depends on where the customer contacts us from. When customers reach out through the in-app chat, everything works as expected. However, when they contact us via email or our company’s website chat, we’re unable to identify which brand they belong to. As a result, the correct audience is not applied, and the relevant Help Center articles are not used for their questions. I also tried manually updating the attribute after the ticket was created, but Copilot still does not recognize the change.
Would it be possible to add a permission that allows certain users to view live conversations without triggering the “NAME is looking” indicator at the top of the conversation window? This could be useful to perform covert monitoring of how a conversation is handled by another teammate.
Currently, when an agent manually creates a new chat or email, the conversation is automatically assigned to the agent who created it. Our team workflow requires these conversations to be assigned to the Inbox instead so they can be triaged and handled by the next available team member.Right now, agents must manually unassign themselves and reassign the conversation to the Inbox every time they create a new chat or email. This adds extra steps to the process and creates the risk of conversations remaining assigned to the wrong person if the reassignment step is missed. We have reviewed the setting under Settings → Inbox → Assignments → General → Default assignee, but this setting only applies to incoming conversations and does not apply to chats or emails manually created by an agent. We also confirmed that this cannot currently be achieved via workflows. Suggested Improvement:Add an option that allows manually created chats and emails to be automatically assigned to the Inbox instead of the agent who created them.This would reduce manual steps for agents, improve team workflows, and ensure conversations are properly triaged through the Inbox rather than being assigned to an individual by default.
Hi everyone 👋I’m currently transitioning into customer support / help desk roles and learning how tools like Intercom are used in SaaS support environments.I’d appreciate any advice on how beginners can break into this field or what skills I should focus on. Thank you.
We need a way to include only conversations that received a CSAT rating during the selected period, so we can evaluate only the conversations that were actually rated. Right now, Monitors can include conversations that have no CSAT in the period (because they’re being included based on the customer’s most recent rating), which makes the Monitor and any attached scorecard unreliable for period-based evaluation.Justification: Monitor reports are already sensitive to how metrics are aggregated, so adding conversations that weren’t actually rated in the period makes it harder to trust the totals you’re reviewing.
Great for Microsoft shops that don’t want to pay extra for Slack.Also, this needs to be direct to user, not limited to Teams/Channels.
At the moment i don’t think we can create dot-points like:This is the main bullet points This is the second tier dot point. It would just be a nice to have feature.
It would be very helpful to have a “click to copy link” to jump directly to a specific conversation. I figure I could just grab the URL from the URL bar but I use Intercom installed as a “web app” in Safari browser, therefore the URL bar is not available. I imagine a similar issue affects those that use Intercom as a “web app” in Chromium browsers.As a work around I have to use “copy link to selected part” if I want to a share a link to the conversation with someone internally via IM (MS Teams). A little silly that I have to do this. ClickUp has “copy link to task”. Should be an easy thing!
Description :We operate with multiple support tiers (Level 1, 2, and 3), where query complexity increases with each level. We'd like to deploy Fin on our email support channel, but only for queries where we're confident it can deliver accurate answers.For Level 1 and Level 2 requests, Fin handles responses reliably. However, for Level 3 requests, the answers are significantly less accurate, and we need a human agent to respond instead.What we'd like:The ability to configure a workflow where, upon receiving an inbound email, Fin first detects the support level via a custom attribute, and then routes accordingly: Fin answers Level 1–2 queries automatically, while Level 3 queries are routed directly to a human agent — without Fin attempting a response.Today, Fin either answers or doesn't, but there's no way to conditionally gate its response based on a pre-classified attribute before it decides to engage. This would give us much more control over where Fin adds value versus where it could hurt the customer experience.
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.