Use this article to understand how Series works, build your first Series, and set it live. Series lets you create automated, multi-step messaging campaigns using Intercom's Outbound channels — combining emails, in-app messages, Product Tours, and more into a single, targeted journey based on your customer data. Series is available on all Intercom plans that include Proactive Support. To create and manage Series, you'll need teammate access to Outbound in your workspace.
What is a Series?
A Series is made up of ‘blocks’.
There are four kinds of block:
A rule block is where you define the filters that a customer must meet to enter a series, or proceed down a specific path.
You can filter based on customer/company data attributes, or interactions with previous parts of a series. | |
A content block is where you create the content that your customers should receive. You can send: Chats & Posts, Product Tours, Mobile Carousels, Emails, Mobile Push messages, Custom Bots, or Banners. Each content block can have a goal, and specific scheduling. | |
A wait block lets you define a specific time period, or date that must pass before customers will proceed any further through a series. | |
A tag block lets you automatically apply tags to customers as they complete their journey through a series. You can tag customers when they match the filters for a rule block, or based on interactions with series content. Tags can then be used to enter or exit customers from other series, filter your reports, define segments or build custom Help Desk views. |
Blocks are connected in paths.
You can have a simple linear path like: Entry rule for Non-premium users - Intro Post message - Has clicked a link in the 'Intro Post' rule - Feature Tour
Multiple separate paths like: Entry rule for Non-premium users - Intro Post message - Wait for 3 days - Feature Tour or Entry rule for Premium users - Intro Chat message - Has replied to the 'Intro Chat' message - Tag Replied to intro
Or, paths that diverge and converge as needed:
This means it’s easy for customers to enter the series for different reasons, get relevant and contextual messages, and exit at the right time. 👌
How to build a Series
To create a Series, go to Outbound > Series and click + New Series in the top right corner. Then:
Choose to start from scratch or select a pre-made template.
Add an Entry Rules block and configure the filters a customer must match to enter the Series.
Add content, wait, rule, and tag blocks to build your messaging paths.
Set a goal and exit rules under Show settings.
Click Set series live to publish.
You can choose to start from scratch, or get started quickly with a pre-made template.
For this example, we’ll start from scratch. The first step to take is adding the entry rules. This is the set of filters a customer must match to enter the series and start receiving messages. Just drag and drop a rule block from the sidebar on the right:
If you’d like certain types of customers to enter the same Series at different paths, just create multiple rule blocks. 👌
Then click on the rule block to open its settings. Here you can choose the filters a customer must match to enter the Series:
Note: Customers can re-enter the same Series multiple times if you enable "Re-enter Series" on the starting rules block. This is useful when you’ve got a set of messages you want to send to customers when a recurring event happens such as a subscription expiring, or a purchase being made.
In this example, we’re targeting all users who don’t yet have the ‘Premium’ plan, so we can encourage them to upgrade.
As you add blocks, it’s a good idea to give them a clear title, which will be visible in the Series overview, so you can see at a glance what’s going on like Non-premium users for Entry Rules:
Next, let’s add our first piece of content; a post message sent in your app. You can drag and drop a message block from the right hand menu, or just hover over the previous block and add it like this:
Then, open the message to create its content:
Tip: You can also set an individual goal for this message, and schedule it to send at exactly the right time:
Setting send windows and fallback paths
For each message block, you can define how long a message should try to send for, as your customers might not be online to receive it right away. By allowing them a little more time to log in and receive it, your messages can be sent in exactly the right order.
Click this section to set the time period you’d like to attempt to send the message for. After this period, anyone who hasn’t come online to receive the message will be disengaged with this path in the Series:
Or, you can create a path for anyone who doesn’t receive it in the specified time period:
Try a different channel if sending additional messages to customers who haven’t logged in. For this example, we’ll add an email message as a fallback:
For all the users who do receive the message, you can add specific rules based on how they interacted with it. E.g. you could target everyone who clicks the upgrade link in the message. Just hover over “When delivered” for all the options:
Select the behavior you want to target (in this example ‘Clicked link’) and it’ll automatically add a rule block:
This allows you to direct customers down separate paths based on whether or not they match the rule. You can also define exactly how long they have to interact with the previous message by editing the Try to match rule.
Setting match windows on rule blocks
When it comes to matching times on Rule blocks within a Series:
"Try to match for x time" means it will wait up to that amount of time for the person to match the rule. If they match sooner, they'll move on sooner. If they don't match in that time, they will either progress down an "if not matched" path (if you have one set up) or disengage from the path (if none are set up).
"Try to match once" means that if the person does not match the rules as soon as they reach that block they will leave the path or progress down an "if not matched" path.
This rule doesn't allow any buffer time for customers to take action and is typically better for scenarios where you won't need to wait for the customer to do something (open or click on a message, take an action in your product, wait for an attribute to update, etc.). This rule is designed to immediately move them onto another message or part of the path.
In this example, the rule block is set to Try to match for 3d, giving customers three days to click the link after receiving the Intro post message:
To capture everyone who engages with the offer — whether through the Post or the fallback Email — add the same interaction rule to the Email block and connect both to the same next step:
In this case the next step will be a product tour, to demonstrate all the value the customer can get out of the ‘Premium’ plan. To connect one block to another, just drag and drop the connecting arrow:
Series lets you automate more than just messaging, so let’s automatically tag everyone who upgrades their plan after progressing through this Series. To do so, we need one more rule block which targets any customer who received the Product Tour, and is now on the ‘Premium’ plan:
To automatically tag customers who complete this journey step, add a tag block. Click the + connector after the rule block and select Tag from the sidebar:
And, for those that haven’t yet upgraded, we’ll add one more email as a fallback, and link that to the same tag block if it causes an upgrade:
Now, let’s take a step back and look at this Series in its entirety.
To encourage customers to upgrade their plan, there’s a Post message sent in your app, followed up with an email, both of which direct to a Product Tour. After customers take the tour, if they upgrade their plan they’re tagged automatically. If not, they’ll receive one last email to try again.
This example is based on the “Encourage Customer Upgrades” template. If you’d like to explore a ready made version, just open that template and dive in. 👇
How to use events as triggers in rule blocks
It’s important to note that when you create a rule block, the try to match rules only apply to the customer matching the audience rules and not the triggers you have set.
If for example, you have a rule block with an event and 'try to match once', the customer matches the audience rules but they’ll have to wait at this block until they trigger the event:
If the customer doesn’t trigger the event within 30 days of reaching the block, they’ll go down the “did not match” pathway or disengage.
If you want the customer to progress in the Series if they’ve already triggered the event in the past, you should add the event as an audience rule instead:
If you only wish them to progress if they triggered the event very recently, you can use the rule "event last occurred less than X days ago".
How to add timing between messages with wait blocks
The “Wait’ block enables you to add spacing between 2 messages.
Example: Send an email → Wait for 3 days → Send a follow up chat message
You can set two conditions to trigger the next message:
“Wait until a period of time”
“Wait until specific date”
Note: Series checks every 30 minutes whether a customer matches each rule, message, wait, or tag block.
How message and rule block wait times work
For each message block, you can define how long a message should try to send for, as your customers might not be online to receive it right away. Or, you can create a path for anyone who doesn’t receive it in the specified time period.
For customers who have interacted with your message, you can add specific rules based on how they interacted with it (e.g. completed the bot flow) and then target the customers who match that rule with a new message.
For these rule blocks you can define a time period the Series will check to see if a customer matches the rule. Or you set it to try and match once (without setting a time period):
If there’s a fallback path in place for customers who don’t match a rule block, or receive a message, they’ll proceed down this path instead, and not be marked as disengaged.
Important: Difference between implicit/explicit waiting: The wait times on a rules block allow you to define how long you want to try match the rules for. This is useful for cases where the user may not immediately take an action (e.g. If the user opens the last email). You want to allow time for the action to occur, and progress immediately when it does occur. This would not be possible with a simple wait block. Similarly, for in-app type messages, a wait block wouldn’t allow you to say “wait for the user to come online”. This is what the wait on the message block is for.
How to tag customers automatically with tag blocks
Teammates can use the tag block to tag or untag (remove tags) any customers in a Series, based on the actions they take:
Multiple tags are allowed in the tag block.
You won’t be able to create a new tag here, but can use any existing tag from the workspace.
Tag blocks can be used for example for:
Automatically include/excluding users in other Series
To update how customers are routed to your teams' inboxes
To flag to your team what messages customers have received / actions they’ve taken
To remove tags from users based on what path they took in the Series
Note: Any tag can be removed with the untag option on the customer’s profile, not just tags applied during the Series.
Tags can then also be used to enter or exit customers from other Series, filter your reports, define segments or build custom Help Desk views.
Note: Series checks every 30 minutes whether a customer matches each rule, message, wait, or tag block.
How to set a goal for your Series
To measure how effectively your Series is driving customer action, add a goal. Click Show settings in the top right of the Series editor, then select the Goal tab:
Then choose the right filters and how long a customer has to meet the goal:
If a customer matches the filters for your goal after the set time period, they won’t be counted towards the goal stats for this Series.
Tip: Find more information about Series goals.
Set up your exit rules
In the Show settings panel, select the Exit rules tab to define which customers should leave your Series early:
If a customer’s data is updated to match the filters in this exit rule they will exit the series completely, and cannot re-enter.
They can only re-enter if they no longer match these exit rules and 'Allow re-entry' is enabled.
For a simple way to manually remove specific customers from a series, just add an exit filter for all customers with a certain tag, then you can apply it as needed to anyone who should exit the series.
Important: Add the exit rule to your Series before tagging customers with the exclusion tag. If customers are tagged first and the exit rule doesn’t yet exist, they may receive messages in the window between when the tag is applied and when the exit rule is saved. Setting up the exit rule first ensures customers are immediately removed from the Series as soon as the tag is applied.
Customers can also exit a Series if they reach the end of a path, hit the series goal or don’t engage with messages for a set time.
Set your Series live
With your messages, entry rules, exit rules, and a goal in place it’s time to set your Series live 🚀
If there are any missing connections, or issues with your Series, you’ll be warned before setting it live 👌
After you set your Series live
Intercom first validates your Series. Once validation passes, activation runs in the background. You'll see live progress as it activates and a confirmation when it's fully live. Customers then start entering as they match your entry rules.
This background activation removes the previous request-timeout limitation, so large Series—especially email-heavy ones—can activate reliably.
Once your Series is live, customers will start to enter if they match your entry rules, and you can easily measure how they're progressing:
Each block in the canvas shows how many customers matched, received, or are still waiting at that step. Customers who leave the Series without completing it are shown as Disengaged — meaning they left without triggering your goal or reaching the end of the path. Customers who matched your exit rules before finishing are shown as Exited.
Note: “Scheduling” is available for Series rather than “Frequency and scheduling” because a customer will only enter a Series based on entry or exit rules, so having a frequency is not applicable.
A customer can enter multiple Series at the same time.
To learn all about measuring the performance of your Series, read this article.
Good to know
Keep these in mind when working with Series:
Customers are checked for Series entry approximately every 30 minutes, so there may be a short delay between a customer matching your entry rules and entering the Series.
By default, each customer can only enter a Series once. Enable Allow re-entry on the entry rules block if you want customers to re-enter when a recurring event happens (such as a subscription renewing or a purchase being made).
Activation runs in the background for complex Series. Deactivating or pausing a Series is still immediate.
Series is not available in Fin Standalone workspaces.
Need more help? Get support from our Community Forum
Find answers and get help from Intercom Support and Community Experts






