Create inbound Workflows over a broader range of channels, increasing the coverage of your automations in order to deflect, triage and route inbound conversations more efficiently, while providing your customers with support on the channels they use day-to-day.
Get started
You can create your Workflow using any trigger, except:
Customer visits a page
Customer clicks a website element
Customer opens a new conversation in the Messenger
Reusable workflow
Channel selection
From the trigger settings, you’ll be able to select the channels you would like this Workflow to apply to. When your customers send you a message on these channels, this Workflow will trigger if they meet the criteria you specify in the Audience section.
Note:
You’ll need to be integrated to the channels you want to use.
Learn more about channel compatibility.
Creating Workflows over Email
Selecting Email as a channel will allow you to send an auto reply if a customer sends their first message over Email. You can also tag, assign and route these messages, as well as showing reply time expectations.
To get the most out of this trigger, we recommend creating a separate Workflow solely for Email, as functionality is limited on this channel. By selecting Email alongside other channels, the paths and follow up actions available to you will be limited to those available over Email.
For greater flexibility, use the “Email to” predicate if you would like to create different auto-reply messages (and other steps and actions) depending on the Email address a user sends their message to.
If you have set up an email auto reply in Settings > Email > Auto reply for the same target audience as your new omnichannel Workflow, the message and actions created on the canvas will override the message in your Settings.
If a customer has replied to the same email within 2 minutes, Workflows are designed not to trigger. This is to prevent potential loops with auto-replies or similar automated email responses.
So if a workflow triggered on a customer's email and the customer sends another email within a 2-minute window, the workflow will not run again.
Channel compatibility
The table below highlights which actions are compatible with each available channel.
Key
🟢 = fully supported
🟡 = functionality supported, but there may be visual differences between channels
🟠 = partially supported (functionality is partially affected)
🔴 = not supported
Content
| Web | iOS | Andr | WA | FB | IG | TW | SMS | |
Write a message | 🟢 | 🟢 | 🟢 | 🟠 | 🟠 | 🟠 | 🟠 | 🟠 | 🟠 |
↳ Rich text | 🟢 | 🟢 | 🟢 | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 | 🟢 |
↳ Add emoji | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
↳ GIF | 🟢 | 🟢 | 🟢 | 🟠 | 🟢 | 🟢 | 🟢 | 🟠 | 🟢 |
↳ Articles | 🟢 | 🟢 | 🟢 | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 |
↳ Image | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟠 | 🟢 |
↳ Attachment | 🟢 | 🟢 | 🟢 | 🟢 | 🟠 | 🟠 | 🟠 | 🟠 | 🟢 |
↳ Product tours | 🟢 | 🔴 | 🔴 | 🔴 | 🔴 | 🔴 | 🔴 | 🔴 | 🔴 |
Collect customer data | 🟢 | 🟢 | 🟢 | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 | 🔴 |
↳ Allow customer to update data | 🟢 | 🟢 | 🟢 | 🟡 | 🟡 | 🟡 | 🟡 | 🟡 | 🔴 |
Expected reply time | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Pass to reusable Workflow | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Custom Action (using API) | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Send an app | 🟢 | 🟢 | 🟢 | 🟠 | 🟠 | 🟠 | 🟠 | 🟠 | 🟠 |
Pause for customer to reply | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Reply buttons | 🟢 | 🟢 | 🟢 | 🟡 | 🟠 | 🟠 | 🟠 | 🟠 | 🔴 |
↳Start over button | 🟢 | 🟢 | 🟢 | 🟡 | 🟠 | 🟠 | 🟠 | 🟠 | 🔴 |
↳ Save reply to attribute | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🔴 |
Condition | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Data selection buttons | 🟢 | 🟢 | 🟢 | 🟡 | 🟠 | 🟠 | 🟠 | 🟠 | 🔴 |
Note:
Send an app opens a URL in a new tab (webpage) on WhatsApp, Facebook, Instagram, email, and SMS.
For WhatsApp, interactive buttons and menus are available for up to 10 reply buttons.
We send buttons for up to 3 options.
Lists/menus for up 4-10 options.
Numbered lists fallbacks for 11+ options.
Actions
| Web | iOS | Andr | WA | FB | IG | TW | SMS | |
Tag conversation | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Tag person | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Assign conversation | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Send Ticket | 🟢 | 🟢 | 🟢 | 🟠 | 🟠 | 🟠 | 🟠 | 🟠 | 🔴 |
Disable customer reply | 🟢 | 🟢 | 🟢 | 🔴 | 🔴 | 🔴 | 🔴 | 🔴 | 🔴 |
Close conversation | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Conversation Data
| Web | iOS | Andr | WA | FB | IG | TW | SMS | |
Set OrderID | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Set CurrentOrder | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Set Issue Type | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Set Product Area | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Set Urgency | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Integration actions
| Web | iOS | Andr | WA | FB | IG | TW | SMS | |
Create lead in Salesforce | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Create case in Salesforce | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Create contact in Hubspot | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 | 🟢 |
Current known limitations
We currently do not support "channel-branching" - ie. having different paths depending on the user channel.
We currently do not support channel specific preview of your Workflow.
💡Tip
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts