Share product ideas and upvotes with our product team
Allow reordering and renaming Messenger spaces in the mobile SDK
For any reporting in intercom it is essential for us to be able to download an image or pdf of a report like a bar graph or topics explorer report etc a csv is not helpful to share with our team. Zendesk already does this it will extremely beneficial.
We have dedicated livechat agents, and we want the way that livechats are allocated to be different from the way tickets are allocated. However, it appears to be all under the same thing and therefore we can’t have manual email conversation allocation but still have round robin livechat conversation allocation.It would be beneficial to have these operate separately, and even better as two entirely separate but linked views, so that it is clear what is from the chat widget and what is an email.
We would love to see CX Score available for phone conversations, not just chat and email. Current LimitationToday, CX Score is only available for chat and email conversations. Even when a full transcription exists, phone calls are excluded from CX Score, Insights, and Reporting. Why This MattersPhone conversations are a critical part of our customer experience and often involve the most complex or sensitive cases. Not being able to measure CX Score for voice creates a gap in our CX reporting and makes it harder to compare quality across channels. Proposed ImprovementEnable CX Score calculation for phone conversations when a full transcription is available. This would allow:Consistent CX measurement across chat, email, and phone Better use of existing transcriptions More complete Insights and Reporting for teams that rely heavily on phone supportValueThis feature would significantly improve cross-channel CX analysis, and help identify coaching opportunities for phone support.
Ability to choose which knowledge folders the content team can edit. We need to decrease risk by giving content editors access to edit ALL knowledge articles in a workspace.
Ability to make fin toggle disabled as default for newly published content.
Currently, participation includes notes and replies. If an agent is involved in a phone call, that is not counted as participation, but should be.
The current teammate profiles (admin profiles) are fairly basic and do allow for an editable text field for a fun quote.The idea we are putting forward is to allow for custom attributes (fields) to be able to be created for teammate profiles, these could be use to list teammates professional certifications for instance.One or two extra fields that could be either lists or multi line text would be a great start.
ProblemFin handles chat well — short turns, fast iteration, low downside if a reply needs a follow-up. Email is a different beast. Threads are longer, context spans days or weeks, and the stakes are higher: customers expect a considered, accurate response, and a wrong reply is much harder to walk back than in a live chat.That makes full autonomy a poor fit for most email conversations. But it doesn't mean Fin can't help. Right now, the gap between "Fin resolves it autonomously" and "agent writes from scratch" is too wide for email — there's nothing in between.ProposalWhen a new email arrives, Fin generates a draft reply using:- The full thread context- Connected knowledge sources (help center, macros, past resolved threads)- Brand voice and tone settings already configured for FinThe draft sits in the conversation ready for an agent to review, edit, or send. A confidence indicator and visible source citations would let agents verify in seconds rather than re-researching the answer.Why this is valuable- Cuts response time without giving up the human-in-the-loop check that email genuinely needs.- Captures Fin's value on conversations that today are 100% manual.- Creates a feedback loop: agent edits become signal for improving future drafts, and eventually for moving simpler email categories toward autonomous resolution.Use caseWe run a marketplace where most supplier-side conversations happen over email. They're rarely fully automatable, but most of what we write is a variation of something we've written before. A Fin draft would save the majority of the writing time per reply while keeping us in control of what actually ships.
Right now, seat removal can only be done in the UI. I’d like an API endpoint (PUT /admins/{id} or similar) that lets us revoke a teammate’s seat programmatically.We want to manage those that do not login or use Intercom for more than 30 days programmatically. We found we can find those via the API, but we can’t remove the seat.We need the API updated.
When an email is forwarded from another department which isn’t using Intercom, their internal email needs to be removed so that clients can’t see it.At present it is possible to select the existing trail in the reply box and delete the entire trail, but this means that the trail is lost for the response being sent and therefore there is no context for the response.A workaround is to then copy and paste the part of the trail you do want, but these can often be very long, and it will also end up putting your email signature right at the end of what you have pasted instead of after the most recent response.We would simply like to be able to highlight and delete the last response like you can in Outlook or Freshdesk in case it is an internal email which we would not want to be included to the client.
As the Manager of the Customer Onboarding team, we heavily rely on sandbox environments for customer enablement. Ideally, I’d be able to have tooltips that I can set to be persistent beyond the initial interaction so users can go back and review them as they’re learning the software platform.
Currently we can use our phonenumber only on Intercom. But Intercom is limited in using this number and sending messages there. It is not even possible to use Intercoms API to send a transactional mail programmatically. It would be nice, if we could send transcactional mails with our own system through the WhatssApp Cloud API and then also connect Intercom to the same WhatsAPp Cloud API.
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.