Exclusion rules keep the campaign from reaching people who shouldn't get the message: contacts already talking to your team, active customers or leads already worked in another action.
You set up the rules in the campaign's audience step and, before activating, see how many people will receive it and how many were left out for each reason.
Available on: WhatsApp and LinkedIn campaigns.
Who can do it: any user with access to the Campaigns module.
When to use them
-
A reactivation campaign that shouldn't talk to anyone who replied in the last week
-
Prospecting that can't run over a conversation in progress
-
A send that needs to leave out active customers or leads in negotiation
Rule types
Already has an open conversation
Excludes anyone with an open conversation within the period you choose. You set the number and the unit (minutes, hours or days), up to 30 days. Example: with 7 days, anyone who talked to your team in the last week doesn't get the campaign.
Exclusion lists
Excludes anyone in one or more people lists in the workspace, such as “Active customers” or “Leads in negotiation”. The match uses the campaign channel's identifier:
| Campaign channel | What is compared |
| Phone number, exactly the same | |
| Profile URL, exactly the same |
How to set it up
-
In Campaigns, create a new campaign
-
In step 1, choose the channel (WhatsApp or LinkedIn) and the sender account
-
In step 2, choose the audience type: List, Funnel or External trigger
-
In the Exclusion rules section, turn on Already has an open conversation and set the period
-
Select one or more exclusion lists
-
Check the Campaign reach panel and move on to the next steps
How to read the campaign reach
The side panel shows the sequence below and is recalculated whenever you change the list, the stage, the period or the exclusion lists. Hover over each number to see the explanation.
| Number | What it means |
| In the list (or in the stage) | People selected in the audience |
| Eligible | People who passed the campaign's rules and filters |
| Will receive | Eligible people the campaign can act on in the channel (message or connection request) |
Under Excluded from sending, the panel shows how many people were left out by reason, in this order: Already has an open conversation, each exclusion list (in the order it was added) and No active [channel]. Each person shows up only under the first reason that applies to them.
Example: a list with 50 people, 2 with an open conversation, 2 in “Active customers”, 3 in “Leads in negotiation” and 1 without active WhatsApp. The panel shows 50 in the list, 43 eligible and 42 will receive, with 8 excluded from sending.
With an External trigger audience, the panel doesn't show numbers, because the audience is built as events happen.
Limits and rules
| Rule | How it works |
| Open conversation period | In minutes, hours or days, up to 30 days |
| Accepted lists | Any people list in the workspace. Company lists and the audience list itself don't show up |
| Audience types | The rules apply to List, Funnel and External trigger |
| When it's checked | Before each send, including later steps in the sequence, with the list's current content |
| After activating | You can't add or remove exclusion lists. The lists' content can change |
| Who was excluded | Doesn't come back to that campaign, even if they leave the exclusion list later |
| Empty list | It's valid and excludes nobody |
| List in use | A list used as an exclusion in an active campaign can't be deleted; Nuvia shows which campaigns it's in |
| Nobody to receive | With “will receive” at 0, the campaign can't be activated |
Common errors and solutions
| What happens | Why | What to do |
| A contact on the exclusion list got the message | The phone number or URL was written differently in the two lists | Standardize the identifier in both lists |
| I can't activate the campaign | Nobody is left in “will receive” | Review the period, the exclusion lists and the audience |
| I can't delete a list | It's in use as an exclusion in an active campaign | End the campaign or wait for it to finish before deleting |