Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3160 Ideas

    Sandra W.New Participant

    Feature Request: Ability to Archive Macros InsteadSubmitted

     Hi Intercom Team,I'd like to submit a feature request on behalf of our customer service team regarding macro management.Currently, the only option available when a macro is no longer needed is to permanently delete it. This creates a few challenges for our team:1. Loss of historical reference – Deleted macros cannot be reviewed or audited later, which makes it difficult to track what messaging was used in the past.2. No recovery option – If a macro is deleted by mistake or needs to be temporarily retired (e.g., seasonal campaigns, paused workflows), there's no way to retrieve it.3. No internal knowledge base – We'd benefit from having an internal archive that serves as a repository of past macros, allowing our team to reference, repurpose, or reinstate them when needed.4. Legal and compliance requirements – This is especially important for us from a legal standpoint. We need to maintain a traceable legacy of which macros were in use at any given time. In the event of a dispute, audit, or regulatory review, being able to demonstrate what standardized responses were being sent to customers is critical. Our request is to introduce an Archive feature for macros, similar to what many tools offer for other content types.Ideally, this would:- Allow admins to archive macros instead of permanently deleting them - Keep archived macros hidden from the active macros list so they don't clutter the workspace - Provide a dedicated "Archived Macros" section where admins can browse, search, restore, or permanently delete archived macros - Include metadata such as who created it, who archived it, and the dates of activation and archival — essential for audit trails - Ideally, log a history of edits made to a macro over timeThis would significantly improve macro lifecycle management for teams like ours, reduce the risk of losing valuable content, and help us meet our legal and compliance obligations.We'd love to hear if this is on your roadmap! Best, Vanessa A. 

    Vladislav DereticNew Participant

    Add support for "Regular Expressions" in Outbound message rulesSubmitted

    Dear Intercom team,We would like to request the ability to use regular expressions when creating outbound communication campaigns, targeting audience by Current Page URL in outbound messages.At the moment, Current Page URL targeting only supports filters such as is, contains, starts with etc..  This creates limitations when: URLs contain dynamic numeric IDs We need to target a specific range of IDs We want pattern-based targeting without creating multiple OR conditions We want to avoid engineering workarounds (e.g., custom attributes) For example, we want to target only a specific subset of courses on our Learning Management System (e.g., courses with ids between 123 and 153), but since Current Page URL is a string, without regex, or, the ability to treat IDs in URLs as Numbers allowing us to use comparison operators on URLs, this becomes difficult or requires engineering changes, especially if we are running tens of courses on our platform.The difficulty in this scenario is also that we cannot afford to just target all courses (e.g. contains /courses/), since many of them would have been concluded (students graduated) or many of them would have just started (i.e. we may not want to send communication to them just yet).We could see a benefit for having Regex functionality in: LMS and similar platforms with course IDs E-commerce and other platforms with product IDs SaaS apps with resource-specific URLs Adding Regex support would: Reduce dependency for segmentation and custom attributes. Custom attributes is one solution to this situation, but which would require some engineering work to ensure correct and efficient update custom attributes without creating too much overhead, especially if there are limits on how many times can a custom attribute be updated over a given period of time. Enable more precise targeting Reduce campaign setup complexity (e.g. in above scenario, we would need to manually set up tens of outbound rules to make it work for a specific range of IDs, which would soon become unsustainable if the number of products and product categories grows in the future. Prevent potential errors from large OR-based rule sets To reference our example from above, if we wanted to target course URLs with IDs ranging between 123 and 153 (inclusive), with regex we could e.g. implement a rule targeting /courses/(12[3-9]|1[3-4][0-9]|15[0-3])We believe adding regex support to Current Page URL filters would significantly improve targeting flexibility for dynamic web applications and reduce reliance on engineering workarounds as well as custom attributes. Thank you very much for consideration.