Share product ideas and upvotes with our product team
A lot of our conversations and tickets are run through email instead of the widget. It would be really helpful if we had rich formatting options(and a larger text input area) for these cases where we’re dealing with high complexity questions from our customers. This “community” tool supports a lot more formatting than your standard workflow.
We have gotten feedback from our customers that the toggle for FAQs can be frustrating, but we do not want to remove them because then the articles would be too long. An “expand all” option would be very helpful.
Description:During QA reviews in Monitors, reviewers often identify improvements needed after evaluating a conversation. Today there’s no structured way to capture follow‑up actions.Request: introduce a dedicated action / to‑do step at the end of the QA review where reviewers can define the next step (e.g., coaching, training, process update, content change). This would help teams track improvement tasks directly from the QA workflow instead of relying on notes or external tools.
When adding macros to a new folder, if you’ve got a lot of them for any given department (e.g. 100+) manually clicking the check box for each one in the list is a pain. Clicking ‘Select all’ from the results page you’re given, would be a great QOL option.
We would love the ability to disable call transfers to customer contacts, as this would significantly reduce the risk of accidentally transferring a customer to another customer.Teams need to transfer calls to internal departments, contacts that are not customers and do not use Intercom. A separate directory for internal contacts would help solve this.As an additional safeguard, a confirmation step could be displayed before completing a transfer, such as:"Are you sure you want to transfer [customer] to [contact]?"This would help prevent mistakes and improve call handling security.
The old knowledge hub had saved views for article management. Intercom lost this feature with the new knowledge hub, and I desperately need it. I can’t train my entire company how to use filters in knowledge hub, and expect them to re-input filters every time they need to see certain articles/statuses. It’s way too cumbersome. Please bring back saved views for Knowledge!!! PLEASE!
We only use Fin for Service, but when managing which roles content should be used for, Sales, Service, and Ecommerce are all shown as options. I can turn Sales off, but Service and Ecommerce appear to be linked, meaning Ecommerce cannot be turned off without also turning off Service. Likewise, turning Service on also turns Ecommerce on.From a user perspective, this is confusing because it looks like these roles can be managed independently, even though they cannot. Since we don’t use Fin for Sales or Ecommerce, I’d ideally like the option to hide or disable those roles entirely from our workspace, or at least have clearer UI messaging explaining that Service and Ecommerce are linked.The current setup creates unnecessary friction when managing content because I have to keep seeing and accounting for roles that are not relevant to our use case. It also makes the settings feel more complex than they need to be for teams that only use Fin for support/service.Suggested improvements: Allow admins to hide or disable unused Fin roles at workspace level. Allow Service and Ecommerce content settings to be managed independently. If they must remain linked, make this explicit in the UI before users try to toggle them. Consider simplifying the content management experience for teams that only use Fin for Service. This is not blocking us from using Fin, but it adds avoidable confusion and makes content governance harder than it needs to be.
We would highly appreciate it if the 'Before SLA breach' lead time could be increased or made customizable. The current 1-hour notification is simply too short for our workflow. Ideally, we would like the flexibility to set a lead time of up to 10 days, or a dynamic trigger at 70% of the initial SLA duration, which is standard functionality in many other support tools.Thank you for looking into this!
Description:Currently, when chat messages haven't been seen in the Messenger after 3 minutes, Intercom automatically sends email notifications to customers. These emails use the first line of the chat conversation as the subject line, which often results in:Random, unprofessional subject lines Truncated text that cuts off at awkward points Inconsistent branding that makes emails hard to identifyRequested Feature:Add the ability to customize the subject line for these automatic email notifications, either by:Setting a consistent default subject (e.g., "Commusoft Chat Summary" or "New Message from [Company Name]") Using the subject field that's already available when composing new chats Providing a template system for dynamic subject linesBusiness Impact:This would help customers easily identify and prioritize chat-related emails, reducing the risk of missed communications and improving overall customer experience.
Workspace members should be able to view and edit the shared memory that Operator uses (e.g. tone of voice, style guides). At the moment, this context isn't visible or editable by the team, which makes it harder to keep it accurate and up to date, and leads to duplicated effort when different team members try to recreate or adjust the same guidance.Giving teams visibility into this shared memory, and the ability to update it, would reduce repetitive work and give everyone clearer insight into how Operator's output is shaped, supporting better collaboration across team members who share responsibility for its performance.
Current behaviour: Monitors can only be archived. Once archived, the only available action is to restore them.Requested change: From the archive, allow users to either restore or permanently delete a Monitor.Why: Without a delete option, the archive accumulates Monitors indefinitely, including test items and other monitors that are no longer needed. Over time this creates clutter and makes the archive harder to manage.A delete option would let us clear out items we genuinely don't need, keeping the archive clean and relevant.
Currently merging of tickets (or conversations) with multiple participants isn’t allowed. This means that you have to link tickets via a note instead. It would be ideal to allow these to be merged as is the case for single-participant tickets to avoid unnecessary duplication.
Hello Fin team,It's easy to go a little blind on resolution rates, since what really matters is what the customer believes is the truth. Fin will calculate an assumed resolution if a customer stops replying to the thread and leaves. Although this is quite common in the SaaS industry, it is also not a very safe indicator that the issue was in fact resolved. Even for confirmed resolutions, it may be that the customer thought it was perfect and confirmed, but later found that this was actually not the resolution anyway. To get a better picture of this, please consider this feature request for reporting:Any lead or user who does not only reopen a previous conversation (this can already be done in reporting), but opens a new conversation within X time (a variable that we should be able to select), is considered a recontact. The combination of AI resolution together with low recontact rate is dynamite, and far stronger than just showing off with a high AI resolution alone. Thanks,Christian Osmundsen, Deliverect
Unpinning a report folder should not apply to all workspace users, it should only apply to the current user. Similar to how when a teammate unpins an inbox, it only applies to teammate.
At the moment, the GET Conversations endpoint supports returning translated text for outbound communications only via the “include_translations=true” query.It would be great if this could be expanded to include inbound communications as well.
We need a way to be able to tell who applies tags and when. Making that information visible in the event logs would be extremely helpful.Additionally, this and other conversation events should have the ability to be pulled via API. I will submit a second topic for the API feature request.
As an Essential customer, I completely understand that some advanced features should remain exclusive to higher-tier plans.However, Workflows feel less like an advanced feature and more like a core part of running a modern support team. Simple automations such as sending an inactivity reminder, automatically closing inactive conversations, assigning conversations, or triggering basic actions are fundamental support capabilities.Upgrading from Essential to Advanced just to access Workflows is a significant price jump, especially for startups and small businesses that don't need the additional Advanced features.A great compromise would be to offer Workflows as an optional paid add-on for Essential customers.This would:Give small businesses access to essential automation without forcing a full plan upgrade. Create an additional revenue stream for Intercom. Allow growing companies to adopt automation earlier while still leaving Advanced and Expert plans attractive for their additional capabilities.I believe this would make Intercom much more accessible to startups while benefiting both customers and Intercom.
It would be great to add the ability to indent paragraph text within the help article builder. It would be helpful to add this to the main article, collapsible links, etc.
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.