Share product ideas and upvotes with our product team
It would be super nice to be able to remap the shortcut keys to my preferred values. For example, closing a conversation is a lot of clicks. Would be nice to have ctrl-x or ctrl-c or something similar like other keyboard commands in other editors. If I could map them myself that would be great.
It would be incredibly helpful for client reporting to add the option to include time in custom states to the data exports for tickets, similar to the existing “time in submitted” “time in progress” and “time in resolved” options: https://app.intercom.com/a/apps/n7bz1b4g/reports/customer-support/export
If there is a relevant product tour to answer a customer question, Fin should be able to automatically offer it to the customer within the chat to complete.
Let's say I have a bunch of tickets connected to conversations, lets say the ticket type is "bug" and it's for bugs. Now if I wanted to tag all "bug" conversations in bulk, I couldn't. Because if I select them all and edit in bulk to add these tags, the system won't tag the tickets, as tags only work in conversations. This messes with bulk actions enormously.So we should be able to either 1 - tag tickets too, or 2 - bulk editing tickets to add tags, the tags should get added to the conversation that is connected to it. Tagging tickets sounds like the best, though, because then reports can be made based on the tags for them too.
Hello,Currently, to my knowledge, our customers are only able to view their own conversations and track their own tickets meaning it would have to be tied to their name.We would like to request the capability to set level access to tickets and conversations so that some of our customers (for instance system administrators) be able to access all tickets and conversations for their entire company. For our Enterprise customers we host meetings with key system adminstrators on their end to discuss current outstanding tickets and it would be ideal for them to be able to have sightline on this and minimally to be able to recieve and view the updates on tickets as they progress through various statuses. Thank you for your consideration.
The API has an “upsert company” endpoint. This is beyond useful compared to the much more fragile process of creating a contact:The “create contact” endpoint 409’s if there is a conflict - it does return the id in the message, which is good, but it should do so in a more structured way. Having to rely on this is finnicky. Having to then call 3 endpoints is tedious and leaves the door open for race conditions (which I’ve definitely experienced), e.g. search contacts, not found, then conflict on create contact. search contacts if found update contact if not found create contact I’ve actually noticed it’s more reliable to call create contact, then handle the 409 conflict with the returned id. Anyway, I think there’s a huge opportunity for improvement and symmetry in the API by adding an “upsert contact” endpoint.This would mirror the well done “upsert company endpoint” It would eliminate the mentioned poor user experience.
Looking for a way to measure the amount of conversations closed in first 24 hours it was opened. This is different from Closed conversations on first contact rate or FCR measurements because that only measures cases that only 1 team member has been involved with or only measures the very first contact. First Day Resolution (FDR) over First Contact Resolution (FCR) can provide unique advantages, especially in cases where complex inquiries or multi-step solutions are common. Here’s why FDR can be beneficial:Supports Complex Issue ResolutionBalances Efficiency with QualityReduces Repeat Contacts and Follow-upsProvides a Better Indicator of Service Quality for Certain BusinessesFDR allows for a realistic timeframe to resolve more complex issues that can’t be immediately handled in a single interaction, focusing on achieving resolution within a day rather than in a single contact. This gives agents the time to investigate thoroughly, consult with other departments, or gather necessary information without rushing. FCR, by contrast, can push agents to resolve an issue quickly in one contact, which may not be feasible for more involved problems, potentially affecting resolution quality.In sum, FDR is particularly useful in environments requiring thoughtful resolutions within a reasonable timeframe. It balances responsiveness with the flexibility needed for quality service, while FCR remains beneficial in scenarios focused on efficiency and straightforward inquiries. I understand FCR may work from some service desks but for a more IT based Technical Service desk, FDR is more standard practices. Product ask: Please add a filter or report way that we can review Closed conversations in first X amount of hours. Some businesses may even want by Business Hours, we would be happy with just a rolling 24 hours.
Currently right now role permissions for REPORT settings are pretty much see them all or see none of them. Would like to be able to select what reports are visible for users. Business use case: Support Techs to have visibility to just their personal performance metrics not their peers to help with supporting more confidential performance issues someone on the team might be having that only a person in leadership role should be addressing.
Hey everyone,We are relying massively on the workflows and overall, they are great. However, there is one limitation that is a real pain. The inability to add mid-paths or change the path directions. And what I mean by that is the following example. I know it’s a simple one but imagine how this will look if you have to edit a complex workflow.Here is the example.I have a workflow that simply asks for Conversation rating and depending on the rating, it notifies a Slack channel; I want simply to add a check where if the conversation as already rated, we should not send a CSAT rating again. The configuration should be edited by simply adding this branch that will check if Conversation rating was already requested. However, if I want to do this change, I have to add the condition here Currently, this is not possible. So I have to delete all paths, and simply start everything from scratch. This won’t be a huge work for this particular example but if I want to rebuild some of our complex workflows, this will be a huuuge pain. Idea: Being able to edit path directions and adding mid-paths without the need of deleting all the steps that follows.
Don't scroll past! Give an upvote if you want to avoid the risk of losing attachments without even knowing it. The current 20 MB limit for incoming email attachments is absolutely ridiculous in 2024!Even worse - when email attachments exceed this limit, they are silently rejected with zero notification to either the sender or the organization. This is completely unacceptable for a paid business solution!AT MINIMUM, you should implement notifications when email attachments are rejected. Better yet, increase this laughably low limit to match modern standards.As a paying customer, I find this situation absurd. Please address this ASAP.
The large list of conversations is very difficult to scan because I can only read the (company) name of the person and the last message (which is often not descriptive enough). I would be useful if a conversation would be automatically titled by AI. Similarly to how ChatGPT chats are titled.
It would be great if there was a “last survey response date” user attribute that stored the last date a user responded to a survey. We can see this data under survey responses, however, since it’s not a stored attribute, we can’t sync the data back to a CRM - in my case, back to HubSpot.We also can’t use it as a filter to build audience list or segment customers. The data is literally there, but only way to use it is to export into a sheet, then manually import to HubSpot. It’s just not scalable as is but adding this function will save us so much time and effort.
Our team would benefit hugely from a feature that allows integration of personal WeChat accounts via API with Intercom. This functionality would enable seamless communication between our team and customers who primarily use WeChat for support and engagement, ensuring our ability to engage with China-based users on their preferred platforms.Key Benefits:Enhanced Customer Engagement - Majority of our users in our most saturated region favor WeChat for communication, and this integration would allow us to meet customers where they already are, improving response times and engagement quality. Centralized Communication - By connecting personal WeChat accounts, our team can manage all customer interactions directly within Intercom, helping to streamline support processes and ensure consistent customer experience across channels. Expanded Reach - Adding WeChat to Intercom would allow us to reach a broader user base, particularly in markets where WeChat is the dominant messaging platform.Current Limitations with Octopods App:While the Intercom app Octopods currently offers a WeChat integration, it only supports connections to official WeChat accounts. This setup restricts our ability to interact in group chats and limits the flexibility needed for real-time customer support and engagement, which are essential for building community, addressing multiple customer concerns, and managing high-touch engagement.Suggested Implementation Details:API Integration - Develop a secure API allowing users to link their personal WeChat accounts directly to Intercom. Message Syncing - Ensure two-way message synchronization so conversations are updated in real-time across both platforms. Security & Compliance - Include authentication and data security measures to meet both WeChat's and Intercom’s compliance standards.Potential Use Cases:Customer service teams managing high volumes of support requests from WeChat users. Sales and engagement teams interacting with leads and prospects on WeChat to build stronger customer relationships in China.Thank you for considering this feature request!
It would be great to have an option like 'Ask Another Question' to encourage users to keep engaging with FIN and explore more on their own.Right now, after FIN answers a question, users see 'That helped' or 'Wait for the team,' which either closes the conversation or puts them on hold for human support. This isn't ideal if we want to guide users toward self-serving. Adding an option that nudges them to keep asking could make a real difference."
In the Rules there was the option “When - A customer replies to outbound content”. This is not available in the workflows. It is only partially available where you select “Client- Has replied to post.”where you need to point out every post, by name.While in the rules it was for all posts, situation that helped a lot with the assignment of the responses to the posts.It would be much more useful to have the ability to assign the conversation if the client responded to a post is “true” instead of having to add multiple audience rules for every post.Below, I have added the example from the old automations, as you can see it is very simple, it handles all the Posts.And the workflow version where we need to point to every post that we want to include. So in the end it is not an idea, basically it is a request to import this option from rules to workflows, as it was very useful. Thank you.
Request:Add customer-facing titles to conversations.Reasoning:It’s very frustrating as a customer when you’re trying to go back and look at a past conversation to see an answer that was given by Support to reference again. There are times I can’t find the answer and have to open up a new conversation to ask the same question again. If this is frustrating for me as a customer of Intercom, I know this has to be frustrating for our customers as well. Example of Requested Change:
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.