Share product ideas and upvotes with our product team
When an internal user (commonly know as a ”teammate”) replies to a Side Conversation from Slack, their user is not correctly matched to their Intercom user despite having the same email address. This issue has been fixed for conversations triggered from Slack channels, as per this community feature request: The fix is to adjust the contact matching path to check against the account email for internal users instead of the profile email (which will never match, eg: “name@team-HASH_VALUE.intercom-mail.com”). Can we please have this fix rolled out for Side Conversations 🙏
Hi Intercom team!We would like to request the addition of Telugu to Intercom’s supported languages, similarly to the existing support for Tamil.We serve a significant number of Telugu-speaking customers, and having Telugu available would help us provide localized support, configure the relevant language settings, and create a more accessible customer experience.Thank you for considering it!
The current styling options for Intercom elements are very limited and do not allow consumers to effectively apply UI design systems and/or branding. In addition, the Intercom elements render within and `iframe` element and thus cannot be targeted directly by application styles. This, as in our case, means a dark-themed website cannot adjust the Intercom elements to match their existing UI styles - the elements always render with a white background, for example.This can be quite jarring for users as any given element from Intercom will likely be the brightest thing rendered anywhere on a given dark-themed site. We, for example, are trying to use product tours as new features are launched, but the mismatch between our UI and that of Intercom means we lose any level of design alignment between our platform and Intercom.This idea is meant to be a request to expand the number of styling options available for all Intercom elements embedded within a given project - particularly the messenger and product tours. Even just component background/divider/text/etc. colors would add a level of customization that would allow companies the ability to align Intercom with the UI/design of their own products much more effectively.This could be implemented as additional options in the “Styling” sections of the relevant components, or additional fields in the Javascript API attributes - the latter already provides some styling options such as `vertical_padding` and `action_color`.
The Problem Intercom’s 48-hour forced session timeout currently logs agents out without warning. If this happens while a teammate is actively on a live phone call, the connection abruptly drops mid-conversation, forcing customers to start over and creating a negative client experience.The Solution Implement a preemptive UI warning banner. 30 minutes before the 48-hour session limit is reached, the system should display a persistent, highly visible notification to the agent (e.g., "Your session will expire in 30 minutes. Please wrap up active calls and re-authenticate.").The Impact Proactive Session Management: Gives teammates a heads-up so they can either wrap up their current interaction or quickly refresh their session before taking a new, lengthy call. Protects the Customer Experience: Eliminates the risk of unexpected dropped calls and mid-troubleshooting disconnects. Simple Implementation: Maintains the strict 48-hour security limit without requiring complex background logic to detect active calls.
I hate how the tab text changes if anyone messages in to a shared inbox when I have my Intercom tab open and am not on it. I basically have to never have intercom open so that I’m not getting constantly pulled away when just an email comes in to the general support inbox, not even my own! Then if Fin wants me to rate a conversation, I’m getting non-stop flashing that Fin is saying something. Genuinely this is my least favorite product I’ve used in tech and I’m mind blown at how the team allocates their resources. We should not use this tool and I hope my leadership agrees with me soon to move away. Absolutely horrible setting customization in addition to a practically unusable UI.
Hello team,We were using the Operator to improve some FAQ articles, and it was able to identify some unique English-language articles that contained the word “participant.” Each of these articles has a Spanish-language equivalent, and all of them will need to be updated, but for some reason, updating this with the Operator takes way too long compared to doing it manually, so speeding up some processes would be required to save us some time and be more competitive.Thanks!
Currently, only slack messages sent by individual slack users are sent to Intercom via the Intercom + Slack app. We have some automated alerts in various slack channels that require attention from our support agents. These alerts are sent as message in the slack channels, but from a slack app/bot. We would also like these messages to flow into Intercom as well so that the slack + Intercom integration is a full 2-way integration. The more time our agents can spend in Intercom vs slack, the better!
Hi Intercom team What we'd likeAn admin-level setting that makes the CSAT comment field mandatory when a customer selects a rating at or below a configurable threshold. Today the comment box is always optional, so a large share of our low scores arrive with no explanation at all.Two settings would cover it:Require a comment for ratings below X — where X is set by the admin. We'd set it at 3, but other teams may only want it for 1–2. Minimum comment length — a configurable character minimum (e.g. 10), so a single dot or a space doesn't count as feedback.Expected behaviour on the customer sideThe customer taps a low rating, the comment field appears, and the submit button is disabled. The button stays disabled — with clear helper text such as "Please tell us what went wrong (at least 10 characters)" — until the minimum is met. Nothing is recorded until the comment is submitted, so the customer immediately understands why they can't proceed. Whitespace-only input and a single repeated character shouldn't satisfy the minimum. Helper/validation text should be editable and translatable, like other Messenger copy.Ideally this applies everywhere CSAT is collected: the Messenger conversation rating, workflow- and email-based CSAT surveys, and Fin resolution ratings. Consistency across channels matters — otherwise customers simply rate through whichever surface has no requirement.Why this matters to usUnexplained low scores are unactionable. We can't coach a teammate, fix a process, or follow up with a customer on "2 out of 5" and nothing else. CSAT feeds teammate performance metrics. An unexplained low rating directly affects someone's numbers, and we have no way to review whether it was fair. It skews reporting. A meaningful share of our satisfaction data carries no information at all, which makes the trend harder to trust when we present it internally. It discourages low-effort rating. Some customers click the lowest score reflexively, or repeatedly across conversations. A small amount of friction — you gave a 2, tell us why — filters out that noise, while genuinely dissatisfied customers are usually happy to explain.What wouldn't solve itWe're not asking for a way to exclude ratings from reports after the fact. Filtering a report doesn't change the score that was already recorded, and it still leaves us without the explanation we actually need. The value is entirely in the friction at the moment of rating: a rating that can't be submitted without a real comment is either explained, or not given at all.Functionally this looks like a contained change — a toggle plus a numeric field in the CSAT settings, and validation on the submit button — but it would significantly change how much we can do with our CSAT data.Thanks for considering it!
I’ve integrated Slack<>Intercom together so that clients can start conversations directly in Slack channels and Support can monitor said conversations via Intercom so nobody leaves their desired platforms.Issue is, it does not seem possible to trigger a CSAT score rating upon closing a conversation. This is ultra valuable and since these are our highest priority clients we really want to hear how they like communicating with Support and if this is an effective process. This seems to be available on a lot of channels but not Slack for some reason :(
I was excited to see that we could have Side Conversations in Slack! Until, that is, I saw that you could only notify channels. What?!As we can send Side Conversations to individuals via email, why can’t we send Side Conversations directly to Slack contacts? It makes the most sense.
Hi team 🤖When an Intercom conversation is triggered from a Slack thread, a private note is injected into the Intercom conversation which is useful. However it can easily get buried under previous and subsequent replies, which makes it difficult to find. Can we please have this link surfaced in the “Details” tab? It could easily sit as another item in the “Links” section. Or even in its own section that could contain other data about the Slack thread. Thanks, Campbell
Currently we have no way of seeing a “last updated on” and “last updated by” or a historical change log on any custom answers and that is reporting we need access into.
Currently the teammate presence setting in help desk shows everyone who is looking at a conversation. However, as a manager I’d like to sometimes be able to hide my presence. This would be found in the popup menu on the bottom left, which shows after hovering over my profile image. There would also need to be an additional permission found in Help Desk to allow the ability to hide someone’s presence. For example, all people in the “Admin” role should have the ability to hide their presence,
Add a native ‘Create Back-office ticket’ action to Fin Procedures, so Fin can create a linked internal ticket automatically when a procedure reaches a defined condition or step—without requiring a teammate handoff or custom API implementation
At this time column settings in views are saved in a browser cache. Leading to 2 issues for our use : when clearing browser cache, the column settings are gone teamleads are not able to create views for their team, as the teammates individually still need to set column settingsThis is very timeconsuming for us and leads to a lot of frustration.Would it be possible to save column settings in the view itself and not in the browser cache ?
When clicking create new conversation, it is defaulting to ‘chat’ - we never start new outbound chat, only email. This means that for every new email we want to send out of Intercom, we must manually change chat to email. It’s only a small thing, but adding up 100’s of email per week…Seems reasonable to allow workspaces to select a default new conversation type, I hope.
Are there plans to customise how the CX score is calculated? For example, I’ve noticed that the CX score can be negatively impacted when customers are unresponsive and our flows automatically close tickets after a few days following a chaser.It would be useful if the scoring could distinguish between negative customer feedback and cases that are simply closed due to customer inactivity, so that agents aren’t marked down for something outside their control.
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.