Share product ideas and upvotes with our product team
There is zero reason to gender callers in the voicemail summary, but beyond that, it’s also incorrect a lot of the time. Example: we had a customer named Aaron call in but the summary said Erin and referred to the call as “she” throughout the summary. It would be better to say “The caller… they.”
Our team does not provide omnichannel support—our agents are only available via phone during specific hours of the day. We would like to track the number of hours each agent's channel availability was set to "Phone" on any given day. This will help us measure whether an agent was available to take calls for the full duration of their scheduled phone shift.
Part of the rationale around the CX score is to replace the need of CSAT scoring. I don’t send CSAT requests out as often as I used to, but I still like to offer the option. However, when chatting with Intercom’s iteration of Fin, I’m asked to leave a CSAT score every time, which seems like overkill on its own, but it also makes the bot frustrating to use, which makes me use it less and less.
Currently, we have 2 distinct types of calls that come in. These calls are routed using a workflow to a specific inbox. If teammates had the ability to be available or unavailable for a specific inbox, it would be a huge benefit to ensure our team is working as efficiently as possible.
I have a SaaS app where each client can customize its domain. For instance, the base domain is app.myname.com, but a client has the domain app.customer_name.pt, When accessing the ticket portal through the base domain, everything works flawlessly. However, when a client with a customized domain tries to access the ticket portal, the cookies aren't transferred, due to the different domains. Is there any way the ticket portal link can accept the JWT that authenticates the user, allowing the ticket portal to create the necessary cookies?
When it comes to setting up the Details tab, we have to direct all team members to update each individual item the way we want it in terms of pinning attributes and apps. We know for each team what we want this to look like across the board and it would be nice if we could bake out a template and link it to the team so that if they are on the team or specific product we could assign them the Details sidebar format that has all the things we need ready to go.Currently we have to tell them every individual thing to pin and add and how to organize it.
When creating a new macro, you can select which team or teams the macro applies to. We often need to select a multitude of these. Every time you select one, it takes you back to the top of the list and you have to scroll back down to the select the next one and this continues for each one thereafter. Even if you type in the key word, that will take you there for the first selection and then it resets for your next selection. It would be nice if I could type in “Dash” which is a key word in all of my team inboxes and I could bulk select all the Dash ones without it resetting everytime.Thank you, this would save us so much time!
When Users/Leads reply to messages in WhatsApp, it would be great to see to which ones they do that. It is a crucial feature that is missing, and because of that miscommunication happens a lot.
The current red exclamation mark warning system triggers consistently on legitimate emails due to routing configurations, reducing its effectiveness as a security indicator. When warnings appear universally across all conversations from certain domains or forwarding setups, they lose their ability to highlight genuinely suspicious activity.The system currently applies blanket risk assessments without distinguishing between legitimate routing patterns and actual security concerns. This creates "warning fatigue" where users become desensitized to alerts, potentially missing real threats.Proposed improvement: Enhance the warning algorithm to better differentiate between legitimate email configurations and actual security risks, reducing false positives while maintaining protection against bad actors.
We offer a platform for collecting and reporting ESG data. Sometimes, we get questions from users reporting data that we need to check with users collecting data (i.e. our customers). Instead of forwarding the email and creating a separate conversation, it’d be very neat if one could forward an email and create a side conversation out of it. That way, we would have related threads in one single place.
Customers would like to completely hide chat bubble so it isn’t a distraction to their work. Additionally, they would like to be able to totally clear out/delete a announcement messages.
The ability to utilize the Automated Workflow features in Intercom for the Phone Channel. Using the “Convert to ticket” button in phone interaction does not allow that interaction to be recognized in ticket workflows. (Intercom internal team indicated this was a feature request - submitting here) Business case why this would help - keeping the transcript and recording with the ticket will improve the service experience and also not require the team to create duplicate tickets separate from a phone interaction.
Ahoy everyone!It’d be great to have the option to view CC’d addresses in an email thread instead of only having the “To” field visible. Our crew deals with time-sensitive conversations which require confirmation that a user’s response to our outreach includes all participants, but some major email platforms will automatically migrate participants other than the sender to the “CC” field regardless of initial positioning. As an example, a reply sent from Gmail will only allow one address in the “To” field, while a reply sent from Yahoo respects user input and allows multiple addresses in the “To” field. Our crew currently has to check the raw email data for every conversation and compare it against the participants listed in the right-hand sidebar of the threaded conversation due to these inconsistencies, which results in increased handling time and more potential for error. Adding the CC field into Intercom’s email display would be huge help!
We are having a hard time having Fin AI Agent being able to read and answer questions based on multi-column tables. It seems like this would be a pretty easy thing for an AI to manage understanding.
When searching a term within the Help Center, I would like the possibility for that word to stay in the search bar even when I access a suggested article. It gives me more context of what I’ve been looking for and would also be relevant for search history.
When using the search bar within the Help Center functionality, I would like to be able to see my search history below the search bar when entering a new query. That would make it possible for em to see what I searched before and go back to previous content.
Hello,With the introduction of the FIN support for webhooks (https://community.intercom.com/ideas/add-fin-replies-to-conversation-webhooks-7784), businesses can use workflows to speed up the work.When FIN/Workflow replies with a comment which includes quick reply buttons, the two “conversation.admin.replied” webhooks are sent. One with the conversation part with type `conversation_part` and the second with part_type: `quick_reply`. Here is how the message with quick reply buttons looks in Intercom:The FIN message with two quick reply buttons sent by reusable workflow Unfortunately, The webhook with part_type: `quick_reply` does not include information about the buttons:Webhook payload for part_type: `quick_reply` As many 3rd-party chat platforms have support for quick reply buttons (including Telegram), it’d be nice to include the information about buttons to the quick_reply webhooks.In the Intercom documentation, there is a parameter `reply_options`. Perhaps, there is an issue in the code that prevents having `reply_options` in the webhook:REST API docs https://developers.intercom.com/docs/references/rest-api/api.intercom.io/models/admin_reply_ticket_request Also, to have a complete set of tools to incorporate quick reply, it is essential to have an endpoint that allows “click” on a quick action. For example, an additional parameter in the reply endpoint:curl example
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.