Share product ideas and upvotes with our product team
The ability to have a toggle in the Help Center settings to have the messenger default to open on the Support page. Java script like Intercom('showSpace', 'home') exists for other pages, but we cannot add it to the Intercom Support page.
At this time, all tickets are be shown in the tickets portal, by default all tickets states are selected.We would like to be able to configure that resolved tickets are not visible by default.The customers would still need to be allowed to select the Resolved state so that they can view those tickets, but by default the Resolved state should be unchecked.
At this time the columns that are visible in the tickets portal cannot be configured.It would be nice to be able to decide for ourselves which columns are usefull for our customers and which are not.
At this time merged tickets are visible in the tickets portal, but they cannot be filtered out.It would be nice for our customers to be able to filter out the merged tickets.
The new UI update on inbox may have affected the behavior of side conversations.Current behavior: When composing an email in a side-conversation, closing the sidebar discards the draft entirely. Reopening the sidebar shows an empty compose field.Expected behavior/previous behavior: Drafts should be preserved when the sidebar is closed and reopened, consistent with how regular conversation drafts already behave.It's common to need the main Intercom window for research, looking up customer details, or referencing other conversations while drafting an email reply. Having to keep the sidebar open the entire time (or risk losing the draft) makes this awkward, and aligning side-conversation behavior with regular conversation behavior would remove that friction.Thanks!
Hi Intercom team,I’d like to suggest a feature request : the ability to create custom channels / custom connectors that fully support two-way messaging, not just outbound notifications.The core idea is to give teams more flexibility in how messages are sent and received while still relying on Intercom as the single unified interface for all conversations. A custom connector with full bi-directional capabilities would unlock several use cases, such as: Enabling SMS messaging in regions where Intercom SMS isn’t available (e.g., France). Syncing conversations with CRMs or project-management tools that include their own messaging system, ensuring users can message from those platforms while our teams continue to reply directly in Intercom. Building tailored workflows for industry-specific channels without needing to leave the Intercom UI. This functionality would significantly increase interoperability and reduce operational fragmentation for teams managing conversations across diverse systems.Thanks for considering this request!
When using the main inbox search you are able to use keywords to filter data. When not in the main inbox search keywords are not supported (See screenshot) In this small search box you are unable to use the same keywords and only supports text only. On top of that the filters under Last activity does not include Assignee which the only work around to filter by who the case owner is to filter the entire view for one user which creates endless amounts of users based views which is not ideal to set up.
When creating workflows, it would be helpful to have the option to use both AND & OR. When trying to filter by something like Categories for tickets, I might want categorys is: Feature Requests OR bugs, but there is other logic that needs to be applied, such as AND ticket type:customer AND state:resolved. If I did Category: Feature Request AND Category: Bugs, this would break the logic and nothing would apply to the workflow. This flexibility would be a huge help!
Currently when I go to add a tag, if I misspell or click enter too soon it creates a new one automatically. It happens often enough that it’s wasting my time going through the steps to delete the tag. There has to be a more efficient way or some type of blocking or “are you sure you want to create a new tag”. Something...please.
ProblemSetting list-type custom attributes on tickets via the API is painful enough that our engineering team now recommends against using list attributes — even when they'd be the better UX for our agents. Specifically, the issues that lead us to this recommendation are:1. Read/write asymmetry. Intercom returns the display label on read, but rejects that same label on write and requires an internal UUID. Round-tripping a value we just received does not work.2. UUIDs aren't exposed in the UI. The only way to obtain them is to make a specific API query — there's no admin screen or export.3. UUIDs differ between sandbox and production. Every list option must be re-discovered and re-mapped per environment; no config promotion path exists.4. Downstream cost. We now maintain one ENV var per list option per environment, just to translate stable concepts onto volatile UUIDs. The maintenance burden is steering us away from the feature entirely.Suggested fixes (any one would help; together they'd align with API conventions):1. Accept the display label on write, rejecting with a clear error on ambiguity.2. Support customer-defined stable keys per option (e.g. Stripe's lookup_key, Salesforce API names) so the same identifier works across workspaces.3. Expose UUIDs in the attribute admin UI, copyable.Bottom line: we want to use list attributes — they're better for our agents than free text — but today's API ergonomics outweigh that benefit. Closing this gap would let us adopt them broadly.
Enable users to reorder default conditional attributes within the conversation attributes panel (e.g., Issue Type, Product Attribute). This would allow teams to prioritize and organize fields based on their workflow, making the interface more intuitive and efficient when handling conversations.
Most of the teams in our company are fully remote and don’t want to be sat their desk wearing a headset all day in case a phone call comes in.It would be great if there were options to set which output device is used for the ringer vs the call itself - for example setting the incoming call alert to come through the PC speaker and the call itself to come through the headset.
My team supports multiple products and so has multiple “inboxes” for incoming phone calls. While the primary and Secondary inboxes seem to work for conversations (they are assigned to primary people first and secondaries as a fallback) this logic does not work for phones. The result is that some people get phones calls for products they do not support (but need to be on the inbox just in case cover is required). Ideally if someone is listed in a Phone Inbox as a “Secondary” they should only be assigned a call if NO primary teammates for that box are available
There should be an easy way to merge users, leads, companies, etc. Sometimes duplicates happen and I should be able to easily merge them (think Hubspot or Apple contacts). This is a common feature in other apps. I know there is a workaround, but I shouldn’t have to put in all of that work to fix an error.
If you are working on a ticket or conversation the outbound call options are limited to the user only.As an IT team we often need to talk to other people at the users end or speak to their IT team.Being able to dial a different number and keep the call within the existing conversation would make audit logs and the process itself much smoother and save a lot of time.
We have recently moved to Intercom and are using it for incoming Chats, Tickets and phone calls.It would be a massive help if a user had granular control of their notifications - for example being able to set different sounds and volumes for new items being assigned, replies to existing items or incoming phone calls. As it stands there is a single sounds for all notifications, and the incoming call “ringer” appears to be hard-coded as I can’t find ay settings for it.
Goal: Display the specific type of SLA (First Response, Next Response, or Close Time) directly in the team inbox and custom views. The Problem: Currently, the conversation list only displays the time value and color (e.g., "5m" in a red oval). While this indicates when a breach occurs, it doesn't show which SLA is breaching. Agents cannot distinguish between a Next Response breach (high urgency) and a Time to Close breach (lower immediate urgency). This makes it impossible for agents to effectively prioritize their workflow at a glance without clicking into every ticket.Proposed Solution: Add a visual identifier or label (e.g., "FRT" for First Response, "NRT" for Next Response, etc.) next to the SLA timer in the conversation list. Allow the conversation list to be sorted or filtered by those specific SLA types so agents can tackle specific types of breaches first. Business Impact: Enables smarter triage, ensures faster customer responses, and prevents agents from wasting time on low-priority breaches while critical response windows are missed.
The ProblemCurrently, advanced routing features (specifically Priority Routing and Secondary Inboxes) are exclusive to the Balanced assignment method.While the Balanced method aims for equal workloads, it creates a "Efficiency Tax" for our team: Performance Penalty: High-performing agents who close tickets quickly are immediately served new ones, while slower agents "protect" themselves from new volume by holding onto open tickets. Lack of Flexibility: To access the critical logic of Priority Routing, we are forced to adopt a distribution model that we find suboptimal for team morale and throughput. Solution A: Decouple Advanced Logic from Assignment MethodsDecouple Priority Routing and Secondary Inboxes from Balanced and enable them as global features that can be toggled on, regardless of the distribution model. This would allow us to keep the objective fairness of Round Robin while still ensuring VIP tickets are surfaced first and overflow is managed via Secondary Inboxes.Solution B: Introduce a New "Advanced Round Robin" MethodIf the Balanced architecture is too distinct for decoupling, we propose a new assignment method: Advanced Round Robin (or "Round Robin+"). This method would function exactly like the current Round Robin (circular distribution) but would include the "perks" currently exclusive to Balanced: Priority-First Distribution: The Round Robin "wheel" spins only for the highest priority tickets first. Secondary Inbox Support: The ability to route to a backup inbox if no agents in the primary Round Robin pool are available. Use Case & Business Impact Fairness: Round Robin ensures an objective distribution of leads/tickets regardless of an agent's current backlog speed. Criticality: We need Priority Routing to ensure our VIP customers are seen first, regardless of the distribution method. Workflow Efficiency: Secondary Inboxes are vital for our tiered support structure. Being unable to use them with Round Robin forces us to choose between "fair distribution" and "organized workflows." Summary of Requested Changes UI Update: In the Team Inbox settings, allow the "Priority Routing" toggle to remain active when Round Robin is selected. Logic Update: Allow "Secondary Inbox" selection to be compatible with the circular assignment logic of Round Robin.
When the end user is viewing their conversation and ticket history, they should be able to easily filter out closed / resolved tickets so that they are only viewing open issues.
It would be nice if you could disable self assignment. This way that you’re able to ensure that the round robin function takes place. Right now we have to monitor the queue in order to prevent cherry picking during peak hours.
This would be especially helpful when snoozing conversations far in advance for specific type of follow-ups on a certain date. Being able to see the snooze duration or reopen date directly in the Snoozed view would make it easier to keep those conversations grouped and plan ahead.Right now, since that information isn’t visible, I have to track the date separately outside of the product. Having this visible would make scheduling and managing future outreach much more efficient.
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.