Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3157 Ideas

    Duncan I.New Participant

    Feature Request: Auto-Populate Case/Ticket Numbers in Macros and Automated VerbiageSubmitted

     We propose adding the ability to auto-populate case or ticket numbers in macros and automated verbiage within Intercom. This feature would streamline communication with customers, improve case tracking, and enhance the overall support experience.Problem StatementIntercom currently allows for auto-population of customer profile data (e.g., "Dear [FirstName]"), which is a valuable feature for personalized communication. However, there is no option to auto-fill case or ticket numbers in messages.This creates the following challenges: Inefficient Workflow: Agents must manually copy and paste ticket numbers into messages, adding time to each interaction. Customer Confusion: Customers are not consistently provided with ticket numbers, making it harder for them to reference their cases. Tracking Issues: Without ticket numbers in customer communications, it is harder to trace cases when customers follow up or escalate issues. Proposed SolutionIntroduce a placeholder variable for case or ticket numbers (e.g., [ticketNumber]) that can be used in macros, templates, and automated responses.Feature Details: Dynamic Placeholder for Ticket Numbers Allow macros to include a new variable, [ticketNumber], which automatically inserts the associated ticket ID. Example: “If you need anything else, please reach out to support and reference case number [ticketNumber].” Customizable Format Allow administrators to customize the display format of the ticket number (e.g., "Case #12345" or "Reference ID: ABCD1234"). Integration with Automation Ensure ticket numbers can also be used in automated workflows, such as follow-up messages or escalation responses. Consistency Across Channels Include this feature for all communication channels supported by Intercom, such as email, chat, and in-app messaging. Use Case ExampleAn agent resolves a customer issue and applies a macro that says:“Thank you for reaching out. If you need further assistance, please contact us and reference case number [ticketNumber].”Instead of manually entering the ticket number, the macro dynamically fills in the unique case number associated with the conversation, ensuring accuracy and saving time. When the customer follows up, referencing the ticket number allows the agent to quickly locate the case.Expected Benefits Improved Efficiency: Reduces manual effort by auto-filling ticket numbers. Speeds up response times for agents. Enhanced Customer Experience: Provides customers with clear reference information for their cases. Reduces frustration during follow-ups or escalations. Better Case Tracking: Simplifies case identification for both agents and customers. Improves consistency and accuracy in support communications. This feature would deliver immediate value by addressing a widespread operational challenge.

    Doug AyersNew Participant

    [Bug] Updating article with API removes table stylingSubmitted

    SummaryWhen an article is created or updated through the REST API / MCP then the `style` attribute on table <td> tags are removed, undoing styling that was applied in the web editor to customize colors or widths. Steps to ReproduceUse the Knowledge web editor to create an article with a table, assign colors the to the column headers and adjust the column widths. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body contains the `style` attribute defining background-color and width on the <td> tags. Use the REST API / MCP to re-save the article as-is. In the web editor refresh the article and note that the table styling was removed. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body no longer contains the `style` attribute on the <td> tags. Expected ResultThe `style` attribute on the <td> tags defining the background-color and column width is preserved. Actual ResultThe `style` attribute on the <td> tags is removed. Example Step 1 Example Step 2<div class="intercom-interblocks-table-container"> <table role="presentation"> <tbody> <tr> <td style="background-color: #d7efdc; width: 320px;"> <p class="no-margin">Header 1</p> </td> <td> <p class="no-margin">Header 2</p> </td> </tr> <tr> <td style="background-color: #e8e8e8; width: 320px;"> <p class="no-margin">Lorem ipsum dolor sit amet</p> </td> <td> <p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p> </td> </tr> <tr> <td style="width: 320px;"> <p class="no-margin">Ut enim ad minima veniam</p> </td> <td> <p class="no-margin">Consectetur adipiscing elit</p> </td> </tr> </tbody> </table></div> Example Step 4 Example Step 5<div class="intercom-interblocks-table-container"> <table role="presentation"> <tbody> <tr> <td> <p class="no-margin">Header 1</p> </td> <td> <p class="no-margin">Header 2</p> </td> </tr> <tr> <td> <p class="no-margin">Lorem ipsum dolor sit amet</p> </td> <td> <p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p> </td> </tr> <tr> <td> <p class="no-margin">Ut enim ad minima veniam</p> </td> <td> <p class="no-margin">Consectetur adipiscing elit</p> </td> </tr> </tbody> </table></div> 

    Grace Ndabananiye
    Grace NdabananiyeNew Participant

    Keep conversations visible when archiving users/leadsSubmitted

    Right now, when a User or Lead is archived in Intercom, all their conversations are archived too. This causes problems because teams often still need access to past conversations for context, audits, support continuity, product investigations, and customer history - even if the user is no longer active.What we’re asking forPlease separate the act of archiving a user/lead from archiving their conversations. Conversations should stay visible and searchable unless an admin chooses otherwise.Why this mattersTeams rely on historical conversations to understand past issues and avoid asking customers to repeat themselves. Product, Engineering, and Compliance often need older conversations for investigations and audits. Archiving conversations affects reporting, SLAs, tagging trends, and Fin AI analytics. Re‑engaging customers becomes harder without visibility of previous interactions.Suggested improvementsAdd a workspace setting that lets admins choose what happens to conversations when a user/lead is archived (e.g., keep them visible, archive only closed chats, or apply a retention period). Provide a simple checkbox option when archiving a user/lead so the teammate can decide what to do with the conversations. Keep conversations discoverable in Search, Reporting, QA/Monitors, and Fin/Copilot analytics even if the user profile is archived. Show a small banner like “This user is archived” without hiding any history.What success looks likeArchiving a user/lead no longer hides or auto‑archives their conversations. Teams can still view, search, and report on those conversations. Open conversations remain open unless a teammate or rule closes them. The workflow is clearer and reduces accidental loss of useful history.