Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3497 Ideas

    Macall GardnerNew Participant

    Reporting: First Day Solved (FDR) metric. Closed conversations in first 24 hoursSubmitted

    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. 

    ericMBActive User

    Search non-text characters, pleaseSubmitted

    Currently, search for standalone non-text characters like hyphens and underscores fail.They return “no results found”. But it would be very helpful if they were found, when they exist.MOTIVATIONIt would be nice to know everything I need to know when writing a UI article.It really would!But there are often questions. I need to make note of them somehow, and make sure to get answers before the article goes out the door. The best way to do that, in my experience, has been to mark those areas with underscores. (Dashes would work, too, if they weren’t used in so many compound words.)I’ll often use sequences like this:“__TBD: The interface lets you do this...__”“Learn more in __Link:That article__”At times, I might also use underscores without a prefix, in a fill in the blanks manner:“Click __button__ to do something”“__VIs that how it works?__”In short, there are many times that I need to mark “information to be provided later” in such a way that:a. It stands out from the text, instead of blending in (to make it easy to spot)b. It lets me capture my thoughts & phrasing while I’m there, thinking about it.c. I can FIND it again later. I’m so used to that way of doing things that my final clean-up step is to search for double-underscores.The double-underscore search typically finds all of the idioms listed above, and any others I’ve forgotten to list.Intercom is the first publication system I’ve used (of many) in which that search fails.That’s not to say that I’m wedded to the idea of using underscores. Maybe I could mark such things with a double-asterix, or double exclamations points, or anything else that Intercom can find with a Content search.The KEY is that the mark-up mechanism stands out from the text, so it’s visible on a casual inspection.Most other systems let me color text, so I will often put such things in bold, red, so they fairly leap out from the page. I’m not asking for that --it adds work in the editor, which needs to be 100% solid and reliable.But surely search can be improved.thanks for listening!eric

    Eirine SchneiderNew Participant

    Enable Connection of Personal WeChat Accounts via APISubmitted

    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!