Share product ideas and upvotes with our product team
Hi there,I have been looking for an option to be able to add further content (more detailed text description, welcome message etc) to the start of a collection page. I am aware you can add a brief description of the collection, which gets displayed under the collection title, but this is limited in terms of how much you can include, and with no control over styling/formatting. Are there options to be able to do this that I am missing? Or if this is currently not possible, it would be a great feature to add! Thanks!
When you tag a conversation, you can not display the tags in the order of your choice.Some of them are used daily, some very seldom, they stick in their order of creation.It would be nice to be able to reorder them, either on the flight, either in the settings.
Make it possible to choose e.g., your own national holidays in a calendar format rather than having to manually choose holidays and reset manually every time.
Lots of our customers send emails from Outlook - the display in the Intercom console requires a lot of scroll. Small, but super annoying when dealing with a lot of tickets. It would be great if you could Auto resize to the drawer width Cut off annoyingly long signatures if possible
Problem to Solve:We have several teams that have individual phone numbers (Sales, Success and Onboarding), and right now there is no way to have inbound calls to their numbers automatically assigned to them. You can automatically assign voicemails to them, but not inbound numbers. The other workaround is that you can create individual inboxes for all of them, but this not ideal when you have a large number of people that will need inboxes across multiple teams working within one workspace.Request:Add the ability to assign a number to a person and a team, not solely a team in the phone setup: Add the ability to assign an inbound call to a teammate within workflows:
Hello team,I’m currently using ticket and API a lot for my customer and I’ve noticed that push wording is always the same saying: Push received when ticket is updated (from API here)APPLICATION NAMEINTERCOM_AGENT_NAME: ticket has been updated It would be really a great UX improvement to have the ticket name instead of “ticket” on the push title. Does not seem like a massive job to me so it could be a quick win. What do you think? 🙂
We’d love to request a new feature that would allow certain teammates to view workflows and their analytics without being able to edit them.Currently, it seems that access to workflows includes editing capabilities, which limits our ability to share visibility across the team without risking accidental changes. Our ideal scenario would be: Teammates can view workflows, including their steps, messages, and logic. They can also view analytics and performance data (e.g., number of completions, drop-off points, conversion rates). But they cannot edit, duplicate, or delete the workflows. This would be especially useful for: Content editors, who need to review workflows to ensure accurate and up-to-date information but shouldn't change workflow logic and review the analisys of the current created flow Cross-functional teams (e.g. Support, Sales, Ops) needing insight into automations Stakeholders reviewing campaign impact
Allow customers to delete messages in the chat bubble and also allow us to delete marketing chat messages that are no longer relevant.
I’d like to share some feedback regarding the current user experience of the Messenger widget – both from our customers and from my own experience when interacting with your support team.1. Lack of clear message titles in conversationsOne of the most frequent complaints we receive is the difficulty in identifying which conversation is related to a specific topic. The absence of descriptive titles or labels on messages makes it hard to navigate and manage multiple threads, especially when several support issues are being handled simultaneously. Adding clearer visual cues or customizable conversation titles would be a big step forward in terms of usability.2. Disruptive behavior when new messages arriveSome of our users have also expressed frustration with the widget automatically popping up every time we or FIN send a reply. Many of them work actively in their admin interface, and this behavior interrupts their workflow. We’d appreciate the ability to customize the widget so that only a non-intrusive notification is shown, rather than the full widget opening automatically with each new message. Or is it already something we can do?These improvements would really help create a smoother and less disruptive support experience for both our team and our end users.Thanks for considering this feedback – we’re looking forward to seeing what’s next.
When the “Participant is Teammate” option is selected for a conversation Topic, the text and content of Fin’s answers should be included when looking for keywords and assigning topics.We use Fin on a majority of our cases, and typically include teammate responses as part of topic identification. This means that at the moment, not including Fin as a teammate means topic identification does not work properly for a majority of cases.Users will often make spelling mistakes or use a very large variety of non-standard words and phrases, which do not get picked up by the Topic assignment ML algorithms. However, Fin can use context to understand the customer’s message, then identify and restate the topic in a way that is standard with our help center content, which would then be caught by topic tagging. This is currently a large gap that is pushing us to look for topic identification/AI categorization tools outside of Intercom, instead of being able to use the readily available tools we’re already paying for.
When adding individual webpages as knowledge sources (e.g. "About us", "Schedule a demo", etc.), each webpage is automatically placed in its own dedicated folder within the Knowledge base. Since we often add only a single page from each URL, these folders end up containing just one item each, creating unnecessary fragmentation in the content structure (see screenshot).It would be great if we had the ability to group multiple webpages from the same website into a single custom folder, such as “Website content”. If multiple pages are imported from the same site, allow those to be organized within subfolders inside the main folder. This change would improve content organization and clarity and allow for easier navigation and management in the Knowledge base.
Our tracker tickets use a field for attachments. Our team members can upload files, images or screen recordings that complement the tracker ticket. It is not possible to multi-select multiple files. Instead, you have to upload each file one by one. Since multi-select is possible in other areas of Intercom, we would like to see this feature be expanded on the attachment field of tracker tickets.
We are using tracker tickets to track feature requests. And BO tickets for all issues that need to be escalated. The issue is, if we were to want to search and read all conversations for each ticket type, we cant do so from the search function, so we have a harder time accessing our information from there. Additionally, intuitively one would expect to be able to search and sort inside of views: we are categorizing things by ticket type and sending them to views, but can’t search for specific things inside of these “folders”, lets say, again making our insights harder to access. And the same thing relates to tracker tickets: Tracker tickets have many conversations in them, which may have different tags or topics in them (in our case we use them for repeated issues/feature requests), so we need to search based on these differences inside of the tracker itself. To sum, every combination of conversations and tickets in a specific place should have the possibility of searching, sorting and filtering.
When you are using custom automation it would be really nice to allow attachments and screenshots to be allowed as right now my team has to leave Intercom and upload screenshots or attachments to jira and almost is a waste of time to even use the integration workflow.
Please provide the ability to Brand an Inbox with a phone number instead of soley branding with an email. My company needs this for reporting purposes. Currently the messenger app seems to be assigning the brand on phone calls and we have multiple brands, the phone is not on the same brand as the messenger and since theirs no email associated with the messenger I can not style it for our phone line.
It would be great to have the option to use tags for relevant articles.Intercom has a machine learning model that helps create relevancy for articles. For our company, we have multiple products which will have very similar titles. Unfortunately, this will create issues where the learning model may be recommending certain articles that aren’t exactly related. Tagging may be taken to account by the learning model, however, it would be great to have an option to determine article relevancy strictly with tags (e.g. surfacing only Product A-tagged articles when viewing a Product A-related article)
When viewing recent conversations it’s better to show the ticket numbers or ubject, status and ticket age. The current view requires the agent to open another window instead of the just the sneak peak of recent tickets submitted. Adding this feature could easily identify if customer submitted multiple tickets with the same inquiry
Please I am begging you to add group filters to reporting. Sometimes I want to look in one chart conversations where it’s assigned to a specific team and (fin AI agent is involved OR a team member replied). We have a lot of conversations that come into Intercom and I can’t broadly report on just all new conversations so I need a way to filter by conversations that Fin was involved (since this is only available to customers) and where a team member was involved. Right now I need to build two charts and than manually add these two together. Group filters are crucial!!!
It should be possible to create knowledge snippets using the API. AppetiteCurrently there is no knowledge type that can:Be used by Fin. Be made using the API. Not be read publicly.Problem with current solutionsInternal article: doesn't cover point 1Snippet: doesn't cover point 2Public article: doesn't cover point 3
We use the Zendesk integration to sync articles as this was advised by Intercom as a better solution than syncing from a webpage. By switching to this type of sync, we’ve experienced two undesirable outcomes:Articles open within the messenger. We’d prefer to have articles open in a separate tab. The formatting of the articles is modified in a way that makes the articles less reader-friendly and less aesthetically pleasing. Idea: It would be great if we could choose to have article open in a new tab instead of within the Messenger so that we can maintain our formatting and have more control over the customer experience.
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.