Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3157 Ideas

    Support Iryna NNew Participant

    Add a Metric to Exclude Reassigned Conversations from First Response SLASubmitted

    Hello,We would like to suggest adding a reporting metric that would allow excluding conversations that were reassigned from one agent to another from SLA calculations — or introducing a new metric that measures the actual first response more accurately.Currently, we use the metric “Teammate assignment to first response.” However, there is a challenge:If Agent 1 communicates with a customer and then reassigns the conversation to Agent 2, the system calculates the first response time for both teammates. As a result, the same conversation (same ID) is effectively counted twice in SLA reporting. Additionally, the first response SLA is recalculated after reassignment, which distorts the reporting data.The metric “First response time” unfortunately does not meet our analytical needs.What we need is a metric that calculates the true first response after the initial teammate assignment — something like:“First Teammate Assignment to First Response (initial only)”This would ensure that the first response is counted only once per conversation and would prevent duplicated SLA calculations when chats are transferred between agents.A similar approach is implemented in Salesforce, where the first response is calculated as the actual first reply from an agent, regardless of further reassignments. Implementing something similar would significantly improve SLA accuracy and reporting transparency.Thank you for considering this idea!

    DblearonNew Participant

    Add performance metrics to conversation side panel for each conversationsSubmitted

    The reporting feature inside Intercom is great, and when you drill in for a specific chart/metric you can then sort by certain performance metrics. However, if I am in a conversation, reviewing the exchange between a customer and a rep; in order to calculate some of the most common metrics, which are already available in the reporting dashboard, I have to hover over each section of the conversation, note the date and time, then go to the next bubble and do the same thing, on and on for the whole conversation.This calculation has to be done because we all get the “I waited ten minutes for someone to reply!” or a leader reaches out and says “A customer told our sales rep it took 20 minutes to get a resolution.” 90% of the time, we find that isn’t even close to the reality….and we provide that response. But getting to that response is a lot of manual work:Pull up conversation (lets say messenger in this instance) Note the date and time for the first inbound message from customer Do mental math to make sure your timezones and office hours are taken into account Note the date and time for the reps first response (post bot in our case) We now have data point 1, we responded in 23 seconds, not “five minutes” Note the rest of our average response times back to the customer That could mean going one-by-one for 10+ messages or more to tabulate that on average we responded back to this customer in under 50 seconds. Note the time it took the customer to respond back to us, and calculate the average Again, 90% of the time their response back to us is 2 minutes, 5 minutes, etc. Go back to the customer and explain the realities (with the cheerful customer flair we always put on the message without basically telling them they are exaggerating their 20 minutes hold times) and back to leadership that we were actually under our goals times and this customer got awesome and quick service!It would be nice to have the ability to pull the following metrics into the right hand details panel for ever chat and email conversation. The data is already exists, just add the field as an option:Average first response time With options to define if it includes or excludes bot, office hours, etc, just like in the report builder Average total response time Time to close I understand I can get this data already by going to my reports, selecting drill down, finding the exact conversation among thousands and looking at the information (see screenshot example). Why not just have that data available right in the conversation on the right hand panel?   

    Jimmy HurffNew Participant

    Append Full Conversation History to Email Notications When Enabled / Add Deep Links to ConversationSubmitted

    This creates a frustrating user experience - the user gets an email that the conversation has been updated but they cannot see the entire thread within the email.  Here is a direct quote from an impacted customer:Good morning - This new chat system makes emails almost worthless because we often can’t tell which issue your answer is associated with. I would imagine you already know this but below is a good example if you do not.Proposed improvement #1: When a user is notified by email of an update to a conversation that they did not see in the messenger widget AND the company settings have conversation history enabled, send the entire history of the conversation.  See article below.https://www.intercom.com/help/en/articles/3527623-sending-email-notifications-without-conversation-content-or-historySpecifically, this callout:Important: If the email notification is sent because of user/lead inactivity from a conversation started from the Messenger, then it will only include the messages they haven't seen, not the full conversation history.I am not sure what the business rule / reason for this is.  If the config has been set to include the enable conversation history, all of the history should be sent. Proposed Improvement #2: An alternative option might be to include a deep link to the conversation.   If the user clicks the link, they are taken to a detailed view of the conversation directly.

    George.USNew Participant

    Cross-Workspace Ticket Sharing for Intra-Company CollaborationSubmitted

    I’d like to submit a feature request focused on improving intra-company collaboration across Intercom workspaces.As more companies adopt Intercom as their primary support platform, we’re increasingly seeing shared customers between two or more businesses that all use Intercom. In these scenarios, there is often a need for coordinated support across organizations when addressing complex or cross-functional customer issues.Zendesk currently offers the ability to share tickets between different Zendesk instances when companies have a common customer. This functionality enables seamless collaboration while maintaining clear ownership, visibility, and audit trails across organizations.A similar capability within Intercom — such as secure, permission-based conversation sharing between workspaces — would provide significant value. Key benefits would include: Improved cross-company collaboration on shared customer cases Reduced back-and-forth forwarding of screenshots and manual updates via side conversations Better customer experience through faster, aligned resolutions Clear accountability and visibility for all involved teams This feature could potentially include: Workspace-to-workspace conversation sharing (opt-in and permission-based) External collaborator access scoped to specific conversations Shared notes and internal comments across participating companies Audit logs and visibility controls to ensure data security and compliance As Intercom continues to expand into more complex B2B ecosystems, this kind of cross-workspace collaboration would be a strong differentiator and a natural evolution of the platform.