Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3160 Ideas

    Draft View or Preview View of Help ArticlesSubmitted

    The problem: There's no way to share a draft Help Center article with someone for review. Draft articles have no shareable preview link — the only way to see a draft is to log into Intercom and navigate to it in the Articles editor. Anyone without an Intercom seat simply can't review the content.Why this matters: The people who review and approve help content — subject-matter experts, product managers, legal/compliance — often aren't Intercom users. Today our options are: buy seats just so people can proofread, walk them through screenshots, or copy the draft into a Google Doc where formatting, images, and links break and feedback ends up disconnected from the real article.The request: Generate a shareable preview link for a draft article — a private URL that renders the article exactly as it will appear in the Help Center, viewable by anyone with the link, without requiring an Intercom login. (Optional niceties: links that expire or can be revoked, and a clear "DRAFT" banner on the preview so no one mistakes it for live content.)Related: It would also help to assign a draft article to its collection before publishing, so the preview reflects its real placement and publish day is just flipping a switch — not finishing setup.The payoff: a real review-and-approval workflow for Help Center content — faster sign-off, fewer errors reaching customers, and no premature publishing just to let a stakeholder read an article. Thanks for considering!

    Suggested articles based on URL Context Sensitive contentSubmitted

    The problem: The Suggested Articles widget in Messenger shows AI-generated suggestions, but they're often not relevant to the specific page the user is currently viewing. There's no way to target suggested articles by URL — we can't assign specific Help Center articles to specific pages of our app. Users on a specialized screen get generic suggestions, give up on self-service, and open a conversation instead.Example: A user is on our Special Orders dashboard (www.ourapp.com/specialorders). We have a Help Center article written specifically for that feature — but we can't make it appear there. Meanwhile the AI surfaces loosely related articles that don't answer the question the user almost certainly has on that page.The request: Let us assign Help Center articles to specific URLs and URL patterns, with wildcard support for dynamic segments — e.g., /account/*/settings should match every user's account settings page regardless of the ID in the URL.Intercom already supports current-page URL targeting for outbound messages, tours, and checklists — this request is essentially extending that same, proven targeting capability to Suggested Articles.Supporting details:1. Priority: Manually assigned articles should appear above AI-generated suggestions, so curated content always leads.2. Hygiene: If an assigned article is archived or deleted, it should automatically drop off the suggestion list — no broken or stale links.3. Reporting: Click/engagement data on assigned articles, so we can see which page-level suggestions actually deflect conversations and optimize accordingly.The payoff: more relevant self-service at the exact moment of need, fewer unnecessary conversations reaching the team, and better use of the Help Center content we've already written. This would also strengthen Fin — knowing which articles are most relevant to the page a user is on gives Fin better context to resolve questions on the spot, improving resolution rates for everyone. Thanks for considering!

    Madeline G.New Participant

    Add Key Metrics to Reporting; Average Wrap-up time, Total Missed Calls, Missed FCR ticketsSubmitted

    We would like to request the addition of several important metrics to the Intercom reporting feature that are currently unavailable but critical for coaching, performance monitoring, and operational transparency.Requested Metrics: Average Wrap-Up Time Definition: The average amount of time an agent spends in the “Call Wrap-Up” status after each call. Calculation: Total time in “Call Wrap-Up” status ÷ Total number of calls. Use Case: This helps managers identify trends in agent post-call behavior and coach toward more efficient after-call work practices. Total Missed Inbound Calls Definition: The number of inbound calls that were assigned to the agent but were not answered and needed to be reassigned to another agent. Use Case: This is vital for understanding availability and coverage issues, especially during peak hours or for specific teams. Tickets Not Closed on First Contact (FCR Details) Enhancement Request: The existing First Contact Resolution (FCR) metric currently shows a summary of which were closed successfully on the first contact (e.g., “13 out of 14 tickets closed on first contact”) but does not allow us to identify which specific tickets were not resolved on first contact. Request: Please allow drill-down or flagging of tickets that were not closed on first contact so we can review them individually. Use Case: These specific tickets are essential for targeted coaching and quality assurance, helping us understand what went wrong and improve future resolutions. Why These Matter:All three of these metrics are crucial for team performance management and quality control. Without them, we’re missing critical insights into agent efficiency, customer experience gaps, and improvement opportunities. These are common metrics across most support platforms, and their absence in Intercom limits our ability to coach effectively and maintain high service standards.