Share product ideas and upvotes with our product team
Hi everyone! SummaryWe are building a structured segmentation system covering 8 countries × 6 license tiers × up to 7 roles per tier, plus driver, EMS, and product-specific sub-segments. This will result in 150–200+ audience segments in Intercom.At this scale, the flat list view of the Segments section becomes unmanageable. We are requesting a folder or collection structure for audience segments to enable organised navigation and team usability.Problem Intercom Segments currently exist in a single flat list with no grouping or hierarchy. With 150–200+ segments, finding the right audience requires scrolling or searching every time. There is no way to visually distinguish between segment types (e.g. country-based CPO segments vs. driver segments vs. product segments). This makes it difficult for support agents, Fin AI configuration owners, and CS managers to confidently navigate, audit, or update the correct segment. Onboarding new team members to the segmentation system becomes significantly harder without clear visual structure. Requested FeatureIntroduce folders or collections for the Segments section, allowing users to: Create named folders (e.g. 🇩🇪 Germany, 🇧🇪 Belgium, Business, Pro, Enterprise) Assign segments to folders — either at creation or via drag-and-drop / bulk assignment Expand / collapse folders in the sidebar or segment list view Nest segments logically without changing their underlying rules or behaviour Example StructureCopy📁 Germany (DEU) ├── DEU — Pro — Fleet Admin ├── DEU — Pro — Fleet Manager ├── DEU — Business — Finance Manager └── ...📁 Belgium (BEL) ├── BEL — Pro — Fleet Admin └── ...📁 Drivers ├── CC@home — Driver — Manual ├── CC@home — Driver — Automatic └── Reg. driver — no platform access📁 EMS ├── EMS — Dynamic (System Users) └── EMS — Static (Drivers)📁 Legacy (Wind-down) ├── All — Basic └── All — CompactImpact Area Current With Folders Segment navigation Scroll through 150+ flat entries Expand relevant folder, find segment instantly Fin AI configuration Error-prone — easy to select wrong segment Clear grouping reduces misconfiguration risk Team onboarding Requires tribal knowledge Self-explanatory structure Segment auditing Manual scan of full list Folder-level review Priority / Urgency We are actively building this segmentation system now and will reach 150+ segments within the next quarter. Without folder support, we may need to delay segment creation or work around the limitation with inconsistent naming conventions alone. This feature would benefit any Intercom customer operating at scale across multiple regions, products, or customer types. Workaround Currently UsedStrict naming conventions ({COUNTRY} — {Plan} — {Role}) allow alphabetical sorting to group segments loosely by country. However, this does not solve the navigation problem for cross-cutting segment types (drivers, EMS, product-specific) and is not intuitive for new team members.Additional Notes We would also welcome a search/filter bar within the Segments list as a lighter alternative or complement. A tagging system for segments (similar to Intercom tags on conversations) could achieve a similar result and may be simpler to implement.
I would love to be able to chose if and what Fin says once it's given an answer to a customer. It seems to default to 'was this helpful’ or ‘was this what you were looking for'. If you could ask your product team to make this a setting/personalised please.
The idea here is to allow Fin to “learn” from converstations that teammates have to take over on. The teammates answers should either automatically or perhaps with an option to “add to Fin’s knowledge” to allow Fin to learn from teammates answers. I know we can add snippets or add to existing knowledge articles, but this would really streamline the process. Maybe an option when you go to update the status of the ticket, you can “add to Fin’s knowledge.”
Today, temporary attributes in Intercom are limited to the lifecycle of a single procedure. This creates friction in conversations that involve multiple procedures or handoffs, since any intermediate state is lost when switching contexts. To work around this, we currently promote short-lived data to permanent attributes, which introduces latency, adds complexity, and clutters our data model.We’re requesting a way to make temporary attributes persist for the duration of a conversation (i.e., session-scoped), so they can be shared across procedures without needing to be written to permanent storage. This would allow us to pass state more efficiently between workflows, reduce unnecessary read/write cycles, and improve responsiveness.A conversation-scoped attribute layer—automatically cleared when the conversation ends—would make it much easier to build fast, reliable, multi-step conversational experiences without compromising performance or data hygiene.
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!
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 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.
I have another feature request. So far, we’ve been working primarily with email inquiries. When the review is sent, only the box with the 5 smileys is displayed (rating). It would be great if we could add some additional text here. Currently, the customer just sees the smileys without any reference to which ticket, etc.—that comes across as unprofessional. We did add some text in the workflow, but it isn’t being displayed.Thanks
We would like to give Fin the ability to embed playable video in chat and email responses similar to how Fin shares images. Or in some cases provide a direct link to the video. Currently if we request information from Fin that could include a video, Fin responds with “here is the video...”, but Fin can only share a link to the article where the video lives.
Hello Intercom team! I have a feature request that is probably somewhat unique. We have some external systems that our admin teams will forward emails to that do automated entry of things like purchase orders so that we can easily convert them to sales orders in our enterprise systems (Netsuite in this case). Right now, we have to do this manually for email conversations coming in that have purchase orders attached to them, but this process could be fully automated if we had a way to enable Fin to forward emails as part of a workflow or procedure. Currently there is no way to do this on the platform and as such we cannot automate those conversations. It would be awesome if email forwarding was added as an action that was available as part of those flows so that we could enable automation of this process! I am sure there are other use cases for this too that would be beneficial to other Intercom users.If you need any further context about our use case, let me know!
Today, it is possible to easily translate content within conversations. However, the translation of Help Center articles is still not automated.This limitation creates a significant workload, especially when managing multiple languages in the Help Center.In the age of AI and given the rapid evolution of your tools, it feels surprising that automatic translation of Help Center content is not yet available. Introducing this feature would provide major benefits in terms of time savings, consistency, and overall efficiency.
Hey team,Our support team have recently implemented Intercom Scorecards. I know this feature is in Beta, so I will preface this with hoping some of these features are coming soon. However, Customer Success wants to utilize the Scorecard they have implemented and found the following issues:When creating a new scorecard and adding existing scorecard criteria - if you make any edits to that existing criteria it changes any scorecard with that criteria - rather than allowing you to have a version of the same criteria. Some of the settings when using the same criteria do not automatically copy (rating reasons) meaning that you have to manually go in and set this up, when it should copy ALL existing settings. It would be great to be able to just duplicate and rename a scorecard rather than having to create a new one, and then copy the settings (that don’t all copy over). It’s very confusing. I would also like the ability to save view in the Scorecard so that I don’t have to filter each time. I would also like the ability to filter by Inbox rather than just reviewees.Thank you!
It would be great to have some of the formatting options for Snippets that are available for articles. Like the separator and headline cases. Being able to format the snippet will make it easier to read and follow the Snippet.
Hi Intercom community,We're running into a limitation with Fin that I'd love to get some input on.Fin currently only processes attachments shared as images (screenshots/photos) — it can't read the contents of document files like PDFs, DOCX or xlsx uploaded by customers via email or conversations.This is a significant blocker for our invoice workflow. Here's our setup:- We're training an AI Billing agent in Langdock, with Fin handling triage by extracting the relevant details from customer messages.- We've built out internal articles describing each document type, plus an index covering invoice formats, use cases, field structures, etc.- In most cases, customers simply mention their invoice number in the message — and that works fine.- However, when a customer uploads a PDF instead, Fin still asks for the invoice number, even though that information is right there in the attachment.Ideally, Fin would be able to read the PDF, extract the invoice number (and other relevant fields), and pass that context to the billing agent — without putting the burden back on the customer.Has anyone found a workaround for this? Whether it's a middleware solution, a Zap/webhook approach, or something else entirely — we're open to ideas. Any help is appreciated!Best regardsMatej
Add the ability to review and leave QA feedback on cases that were handled by more than one agent, in Monitors. Reviewers should be able to either leave one comment covering the case and all agents' work as a whole, or leave individual, agent-specific feedback for each agent involved in the conversation.When a reviewer opens a case in Monitors that involved multiple agents, give them two review options:Case-level comment: a single piece of feedback addressing the case and the agents' combined handling of it (e.g., evaluating handoffs, overall resolution quality, consistency across agents). Per-agent comment: individual feedback tied to a specific agent involved in the case, scoped to that agent's own contribution.These options shouldn't be mutually exclusive. A reviewer should be able to leave one overall comment on the case and separate feedback for one or more of the individual agents in the same review pass.
Hello! I really love the AI compose, rephrase and expand, but I often find the tone to be less than desirable, specifically around shortened words (I have/I’ve, We are/We’re). It would be great if AI compose could have some slight guidance on workplace specific requirements, such as the option to allow/restrict shortened words. Another adjustment that comes to mind is including/excluding the final sentence on the email (Many thanks, [YOUR NAME] [YOUR TITLE]). Its a relatively minor issue, but it definitely adds up over time! It would be great to someday use the AI compose feature without needing to make any adjustments manually!
Please add Hinglish as a separate language, it is very simple to add, most of the models know how to comunicate with help of it, and understands the contexr good.It will allow to support Indian market much better, since not all understands English good and also no one are using Hindi, since it is complicated to type.
For workflow that involve Fin, I have no choice on whether to let Fin engage with the customer or not. I need to use Fin to analyze new messages to determine intent and follow routing rules, but there’s no way for me to stop Fin from responding to the customer’s inbound message. Why?? Doesn’t make any sense. I should be able to leverage Fin for background back-office automations without exposing Fin to the customer.
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.