Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3490 Ideas

    Duncan I.New Participant

    Feature Request: Ability to Require Agent-Only Fields in Intercom TicketsSubmitted

     SummaryWe propose adding the functionality to mark agent-only fields in Intercom tickets as "required" before a ticket can be closed. This enhancement would ensure consistent and accurate reporting and prevent incomplete data entries.Problem StatementIntercom’s ticketing system allows for custom fields that are visible only to agents, which is excellent for internal tracking and reporting. However, the inability to make these agent-only fields mandatory often results in incomplete data.For example:A field such as Resolution Type is critical for understanding the outcomes of cases. Agents sometimes forget to select the appropriate option from the dropdown, leading to gaps in reporting. This oversight impacts the accuracy of metrics and reduces the value of data-driven insights.Proposed SolutionIntroduce the ability to mark agent-only fields as "required" to ensure they are filled out before a ticket can be closed.Feature Details: Agent-Only Field Validation Allow administrators to configure agent-only fields as "required" in the ticket settings. Display a warning or notification to agents when attempting to close a ticket without completing these fields. Customizable Requirements Provide flexibility to specify when the field must be filled (e.g., upon ticket closure, status change, or assignment). Visual Indicators Highlight required fields that are missing in the ticket UI for easy identification. Integration with Workflows Ensure compatibility with existing workflows, such as automation or routing rules, without introducing errors or disruptions. Use Case ExampleAn agent resolves a ticket for a customer experiencing a "problem sending." Before closing the ticket, the system prompts the agent to fill out the Resolution Type field, ensuring data is captured for reporting. This eliminates the risk of the field being left blank, allowing the team to generate accurate metrics showing the outcomes of 500 "problem sending" tickets (e.g., resolved by re-sending, refunded, or escalated).Expected Benefits Improved Data Accuracy: Ensures critical fields like Resolution Type are always completed. Enhances the reliability of metrics and reporting. Operational Efficiency: Reduces the need for manual audits or follow-ups to complete missing fields. Helps managers better analyze and address recurring issues. Enhanced Accountability: Encourages agents to consistently follow internal processes. Technical ConsiderationsImplementation would involve:Modifying ticket field settings to include a "required for agents" toggle. Adding validation logic to check field completion before ticket closure. Updating UI/UX to visually indicate required fields and prompt agents when necessary.Priority and TimelineThis feature is critical for teams relying on Intercom for detailed reporting and operational metrics. We recommend including it in the next product update to address immediate user needs.

    Christian S12
    Christian S12Connector

    Exporting Additional Custom Attributes in Outbound CampaignsSubmitted

    Description: Currently, when exporting data from outbound message campaigns (e.g., specific post campaign), the export provides basic information such as user ID, email, and name. However, additional relevant details that would provide a more comprehensive view of the user are not available in the exported file. Requested Enhancement: I would like to request an enhancement to allow users to customize the columns in the exported data from outbound campaigns. Specifically, I would like the ability to add custom attributes to the export, similar to the functionality available in the Conversations and Reports sections. In these areas, users can drill into their data and add custom attributes to better understand and segment their audience. Use Case: In Conversations reports, custom attributes can be added, and those attributes appear in the exported file. The same functionality would be valuable for outbound message campaigns. For example, being able to export custom attributes (such as tags or additional user details) in the outbound message campaign data would allow for a deeper analysis of the campaign’s recipients. Currently, a workaround involves tagging users and filtering them based on the tag, but it would be more efficient and user-friendly to simply add the custom attributes to the export, similar to how contacts are handled in the contact list. Benefit: This feature would significantly improve the utility and effectiveness of the data exported from outbound campaigns, enabling users to analyze their campaigns more effectively and with greater detail.

    IW-technical-SupportNew Participant

    Auto-sanitize or anonymize public image filenames on uploadSubmitted

    Problem statement:When uploading images to articles in Intercom, the original filename is exposed directly in the public URL (e.g., /images/client-name_invoice.png). https://downloads.intercomcdn.eu/i/o/itah6lir/47298365/ba6a3a3434f9f289e5f0a483ee3f/[FILENAME].png This creates a privacy risk, especially if authors accidentally upload files with confidential or identifiable information in the filename.In fast-paced teams, it's unrealistic to expect every author to sanitize file names manually before uploading. Other platforms typically generate anonymized or UUID-based URLs to prevent this exposure. User Story:As a Help Center admin,I want Intercom to automatically anonymize image URLs and not expose the original uploaded file names,So that I can prevent leaking internal or customer-specific information through image links, even when authors forget to sanitize filenames. Feature RequestPlease automatically sanitize, anonymize, or hash uploaded filenames so that the public URL does not reflect the original file name. This could be a random string (e.g., image_abc123.png) or even a UUID. Why This Matters Avoids accidental exposure of confidential info (e.g., client names, internal systems) Reduces risk of data leakage through file URLs Prevents human error — filenames are often overlooked Follows standard practices from other platforms that generate anonymized or randomized URLs Reduces burden on authors to follow strict naming conventions Aligns with best practices in content platforms that randomize media URLs (e.g., /assets/xyz123.png instead of /uploads/john_smith_invoice.png)