Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3475 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!

    Emma Mifsud TommasiNew Participant

    Automated Reminder Email Should Include the Original Subject LineSubmitted

    Currently, Intercom’s automated reminder emails don’t provide any indication of which conversation or enquiry the reminder relates to.This can be confusing for customers, particularly those who have multiple active conversations with us or who send several emails in a single day. When they receive a reminder, there is currently no subject, conversation reference, previous message excerpt, or other context to help them identify what they are being asked to respond to.The problemFor customers with multiple open threads, an email saying something along the lines of “We're just following up on your support request. Could you please review our response and update us by replying to this email?” isn’t actionable on its own. They may not know:Which enquiry requires their response Which member of our team they were speaking with What the outstanding question was Whether they have already replied to a different conversationThis creates unnecessary confusion and results in customers ignoring the reminder, replying to the wrong thread, or contacting us again to ask what the reminder relates to.Suggested improvementIt would be really helpful if automated reminder emails could include some context from the relevant conversation, for example:The conversation/email subject A short excerpt from the most recent messageEven something as simple as “We’re waiting for your reply regarding: [conversation subject]” would make these reminders significantly clearer.Why this would be valuableAutomated reminders are intended to prompt customers to take action, but without knowing what the reminder relates to, the customer may not be able to do that.Adding conversation context would make reminder emails much clearer and more useful, particularly for businesses whose customers regularly have multiple conversations open at the same time.

    Ed MorrellNew Participant

    Preserve and restore conversation ownership after Fin AI Agent involvementSubmitted

    When a human agent takes ownership of a case, particularly for complex, multi-step issues like repair bookings or courier collections, and Fin subsequently handles part of that conversation (e.g. answering a status update, running a procedure), there is currently no native way to automatically return the conversation to the original owning agent once Fin's involvement ends or escalates. Our agents handle cases that span multiple touchpoints. An agent may book a scooter collection or repair, making them the case owner with full context. If the customer later contacts us again, Fin may handle the interaction but when Fin escalates or the conversation needs human attention again, it lands in an unassigned team queue. The original agent loses the case unless they find it or it gets manually reassigned to them. The only current workarounds I can think of:Agent name tags + a workflow branch per agent (brittle, requires maintenance as the team changes) Creating a new custom attribute (however, we've exhausted our attribute allowance on reporting-critical fields)None of these are clean solutions, they all require ongoing manual maintenance or sacrifice something else.The ask: A native "Case Owner" concept at the conversation level, separate from the current assignee, that: Can be set by an agent when they take ownership of a case Is preserved throughout Fin's involvement in the conversation Automatically reassigns the conversation back to the case owner when Fin escalates, hands off, or the conversation leaves the bot inbox Alternatively, a workflow trigger condition of "previous human assignee" that can be used to route conversations back to whoever held the conversation before Fin took over. As teams adopt Fin more deeply particularly on email channels where conversations reopen and span days or weeks, case continuity becomes critical. Fin is excellent at triaging and answering, but the handoff back to a human needs to be intelligent, not just "drop it in the team queue." This feature would allow teams to confidently expand Fin's scope without sacrificing the accountability and context that comes with named case ownership. This would affect any teams using Fin on email or async channels with multi-touchpoint cases, repairs, logistics, complaints, or anything requiring follow-up over time. ThanksEd