Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3162 Ideas

    Macall GardnerNew Participant

    Channel Routing: Add Email to Conversation and PhoneSubmitted

    Current Limitation:At the moment, technicians can only be logged into the following routing channels: Phone (Phone only) Conversations (Includes both Chat and Email) Suggestion for Improvement:I’d like to propose greater flexibility in how routing channels are configured and assigned. Specifically: Split Email from the Conversations Channel: Allow Email to be its own standalone routing channel, separate from Chat. This would enable technicians to be logged into Email without being required to handle Chat at the same time. Enable Multi-Channel Selection: Provide the option for technicians to select multiple channels—rather than being limited to just one or "All." For example, a tech could be logged into both Phone and Email, but not Chat. Alternative Approach:If separating Email from Conversations isn’t feasible, another solution would be to include Email as part of the Phone channel. This way, Phone agents could assist with email volume during slower phone periods.Why This Matters:In environments where email and chat volumes are particularly high, the current setup disproportionately burdens the “Conversation” techs while “Phone” techs remain limited in how they can help. This often requires manual intervention by team leads to balance workloads across the team. By allowing more flexible channel selection or smarter routing, teams could improve efficiency and reduce operational overhead. 

    Justin M12
    Justin M12Active User

    Tickets linkable in Help CentreSubmitted

    In our (intercom) help centre we reference customers to submit a ticket for certain problems that we know we will always require a ticket for.However we cannot link customers to submit a ticket within intercoms help centre. Either by using a link to open a ticket in the messenger or embedding a ticket form within the help centre article itself. There is no way to get a customer to the ticket we want from an article!I know this is possible using code to Trigger from HTML on your own webpageThere is also a nice way to add tickets to the messenger homeBut these do not solve the issue of customer on a help centre article have no next step to submit a ticket and must now start a live chat to get to a ticket!We have found a workaround (that is not easily scalable for many tickets) to this where by using workflows and “When customer clicks a website element” trigger we are able to link a specific button or text within the help centre to then open a ticket in the messenger.Ideally we would eitherbe able to use a set URL to create links to tickets in the help centre so we can link any elements we want  eg:https://www.yourhelpcentrecustomdomain/showticket/{ticket_ID) have a function built into the help centre button or another option to link a ticket.In both cases I think these would then open the messenger to the ticket id allowing the customer to complete and submit the ticket quickly from within the help centre

    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.