Share product ideas and upvotes with our product team
I want to be able to autoatically upload images without hosting public URL. It seems like a workaround that should not be necessary. This would make it easier and more intuitive to automate. So what I want:- Have local image files that I can upload automatically as part of an article or integrate them with a seperatae step automatically- Either through API or MCP
When I export a conversation to PDF, it’s missing the images (which are replaced with a placeholder: [image])I feel that omitting these screenshots/etc is omitting valuable context from the ticket, so they should be part of the export.
We would love to see an option that allows callers to remain in the queue without having to make an active IVR selection.In our market, the most common expectation is simply to wait for an answer. Requiring callers to press a key to continue waiting can create unnecessary friction and may lead to confusion or abandoned calls.An option to let callers stay in the queue automatically, while still offering callback or other choices as optional alternatives, would create a more natural and user-friendly phone experience.Would anyone else find this useful?
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.
Like Fin if you adjust a scorecard answer and add reasoning, the AI bot will learn from this so future reviews will take that feedback in to account
I WANT TO WORK OUR SUPPORT CONVERSATIONS IN A KANBAN VIEW. WHEN WILL THIS BE AN OPTION?
Currently, the message list displays all of a user's past inquiry threads. I would like to request a feature that allows users to hide or archive them on their end.
Hi there!We use external tools to aid our articles visually, and we would love to be able to embed them in your articles.Additionally, allowing HTML, CSS or iFrames would let us customize the articles to match our company look.Looks like quite a few people are asking about this in the Help Center, so fingers crossed it’ll be added in a future update.
Today, the only way to create a new slack message to a customer is through an Outbound Broadcast. That is super cumbersome. There should be a way to create a new slack message from the Inbox (Channel or DM), just like you can create a new convo or ticket. This is such a basic requirement.
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.
The Teammates page only shows how many teams a user belongs to, not the actual team name(s). Should list the NAMES of the teams in the Teammates page, not the quantity. Today, I have to go to the Team Inboxes page and check every single team and search for the user. This is time consuming and very prone to oversight.
The ability to use email signatures when replying to a ticket.We have all email conversations converting to tickets to support some integrated functionalities, and need signatures to send out with those replies. Having the team have to use personal macros and remembering to use them every time is a pain and a weird lift.
We have several articles relevant to multiple collections. Duplicating articles is not preferred. Thank you!
I understand that we can set up regular reports, but for more one off exports, where we know most of the preselected columns won’t be used, it would be good if we can save column settings instead of manually selecting and unselecting each column.
We enabled the email channel within the Intercom platform but there is a default assignee group in Settings>Inbox>Assignments>General>Default Assignee.The problem: Whenever an email comes it, it defaults to one of our chat channels first then the workflow picks it up and assigns it to the Email Inbox as designed. You can see this within the event logger showing each waterfall flow where it marks as default assignee then workflow. Ultimately with automatic routing of chats to agents, the emails are automatically getting assigned to them before the email workflow kicks in. Because of this and the default assignment is in place, it won’t take it out of default once assigned to rep.Temporary Fix: We have to mark conversations as Unassigned by default which now requires users/supervisors to monitor an unassigned queue.The ask: Why not have a default assignee inbox by Channel rather than the entire workspace.Expected Behavior: Chat Default Assignee = Chat_Inbox; Email Default Assignee = Email_Inbox; SMS Default Assignee = SMS_Inbox
Hello team,One thing I often feel is missing when working with reports, is the ability to switch between absolute numbers and percentages. This is particularly useful when using more than one metric. For instance, how many support tickets did we receive in January, and (2nd metric) how many of these were from France? Great to have absolute numbers and we can do the math, but even more useful if you could toggle this to a percentage view. It becomes even more powerful when you have more variables obviously: How many support tickets did we get in France, and how were these distributed among all our customer countries? If you have customers in 30 countries this adds a lot of value. Different example: I want to see how our support volumes are distributed over the days of the week for an 18 month period. Also possible with absolute numbers, but percentages here would add more value. Thanks for reading this and for upvoting!Regards,Christian Osmundsen, Deliverect
Hi Intercom community! At the moment there's no way to stop a conversation closing for inactivity while a procedure is running. If a customer drops off halfway through, the conversation just closes. The procedure doesn't finish, nothing gets escalated, and we've got no reliable way of finding it again afterwards. That's fine for most topics but it becomes a problem for anything high-risk or high-priority, where we need the case seen through whether or not the customer comes back to us. The only workarounds are adding tags and creating extra workflows to reopen these conversations. It would be great to have functionality within the procedure itself to escalate if the user becomes inactive, or a global setting that always escalates to the default inbox if the conversation contains a certain tag & the user went inactive (this might be more future-proof, incase of new features or the same problem found in other existing features)
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.