Product Wishlist | Community
Skip to main content

    Idea Pipeline

    Filter by idea status

    Browse by category

    3160 Ideas

    Nurit
    Innovator ✨
    NuritInnovator ✨

    Workflows ImprovementsSubmitted

    Workflows are an excellent tool that we frequently use for our custom bot and back-office operations. I would like to suggest a few enhancements we find missing in our work and could improve them.Custom triggers - the ability to trigger a workflow based on different activities or attributes. for example, a change in a user data attribute , a back office ticket closed or reopened, or a teammate status change.Additional actions - one example is a code block, which would be very helpful for custom functions. Other examples are opening or closing a ticket, reopening a conversation, random split (for example, randomly assigning a conversation to several teammates and not teams), and setting people's data.Additional filters - some of the filters we searched for - customer has any open conversations/back office ticket, customer has contacted x times in the last x hours/days, “customer visits a page” filters to the customer visits a page trigger, is the conversation linked to a back-office/tracker ticket.Additional dynamic parameters - such as conversation ID and intercom's user ID.A link as a reply button.Loopback flow - the ability to go to a different flow and return to the same point in the original flow.Version management - the ability to restore older versions.   Duplicating a workflow from the test environment - We usually test workflows first in our test environment, having the option to duplicate it to our regular workspace will be very efficient.The ability to publish a flow with "floating" not connected boxes.Pause/publish workflows from the workflows home page.

    JHarlowe
    JHarloweConnector

    View Filters can use "and" as well as "or" in the same filter listSubmitted

    Currently you can only use the <and> logical operator instead of the <or> logical operator or vice versa in (query logic) Inbox view filters, chart filters and report filters. Essentially it has to be all <and> or all <or> in the list. You can not have different logical operators per query line. Current behavior shows that if you change one logical operator  <and> to an <or> it changes all the filter logical operators in your query to that same thing, even if you only want to have one <and> and a few <or> lines. Funny part is that in the Company and People filter you CAN mix up / combine the logical operators in the filter list as it does not force all logical operators to be <and> vs <or> or vice versa. The ask here is to simply extend the same multiple conditions in a query, such as <AND, OR> the Company and People filter operators have to the Inbox views, charts, reports filters and other data set areas of Intercom where they are more needed, as the Inbox views, charts and reports filters tend to be the more widely used areas of the system and multiple conditions in a query, such as AND, OR are critical to the flexibility of viewing. -------TL;DR---------Current World Example in same filter:Team Assigned is Team A <and> Teammate Assigned is B; Current channel is Phone <and> Current channel is email; State is not Resolved <and> State is not Workaround provided Proposed Idea in same filter:Team Assigned is Team A <and> Teammate Assigned is B; Current channel is Phone <or> Current channel is email; State is not Resolved <or> State is not Workaround provided. The current filter logical operator restriction limits the filters quite a bit and it results in impossible scenarios, i.e. a ticket can not be in two states at the same time or two channels at the same time, two Teammates assigned, two Teams assigned etc.. Thus preventing the ability to say:show me a list of conversations that are in Team Inbox A <and> are assigned to Teammate A <or> Teammate B <or> Teammate C in the same view.It has to beshow me a list of conversations that are in Team Inbox A <and> are assigned to Teammate A <and> Teammate B <and> Teammate C. which is not a possibility since tickets can only be assigned to one team mate at a time. Thus no results would populate¯\_(ツ)_/¯