# Control which leads reach each destination

URL: https://useembers.com/help/integrations/delivery-rules/
Category: Integrations
Plan: Solo and above
Updated: 2026-10-31
Last verified: 2026-10-31

> Set a minimum score, ICP only, sources, and excluded titles and industries per destination, and route each agent's leads with configurations.

Every destination starts by receiving every lead that qualifies. Delivery rules narrow that down per destination, so a Slack channel, a CRM, or an outreach campaign only receives the people worth acting on.

> **Warning: Solo and above, administrators only**
>
> Delivery rules live on each integration's page, which requires Solo or above and a workspace admin. Members can still [push a lead by hand](/help/leads/send-to-destination/) once a destination is connected.

## What qualifies a lead in the first place

Before any rule runs, a lead has to qualify for delivery at all: a [score](/help/leads/how-scoring-works/) above zero, a match with your [ICP](/help/leads/icp-matching-and-feedback/) or a manual approval, and a company that is not on your [blocklist](/help/leads/company-blocklist/). Rules can only narrow that set, never widen it. Rules decide what leaves Embers, not what Embers collects: a lead a rule holds back still appears on your leads list and in the [Priority Queue](/help/leads/priority-queue/).

## Set the rules for a destination

### Open the integration's page

Open **Integrations** in the sidebar (`/integrations`) and choose the tool. Its page is `/integrations/<tool>`, for example `/integrations/slack`.

### Find Who gets delivered

On [Slack](/help/integrations/slack/), [HubSpot](/help/integrations/hubspot/), [Salesforce](/help/integrations/salesforce/), [Pipedrive](/help/integrations/pipedrive/), [Attio](/help/integrations/attio/), [Notion](/help/integrations/notion/), and [Google Sheets](/help/integrations/google-sheets/) it is its own card, **Who gets delivered**, in the setup at the bottom of the page; Notion and Google Sheets show it once the mapping is saved. On HeyReach, Instantly, Smartlead, and Emelia it is part of each configuration: choose its row on the **Configurations** card, or open the row's **...** menu and choose **Edit**. The row's **Who gets through** column sums it up, such as "Score 70 and up, ICP only".

### Set the rules and save

Choose **Save rules** on Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, and Google Sheets, or **Save changes** on a configuration. The line under the heading summarises what you set, such as "ICP only, score 70+, 2 excluded titles".

## The five rules

| Rule | What it does | Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, and Google Sheets start at | A new configuration starts at |
| --- | --- | --- | --- |
| Minimum lead score | A whole number from 0 to 100. A lead scoring below it is held back | 0 | 70 |
| ICP matches only | Deliver only leads that matched your ICP | On | On |
| Sources | Posts, Comments, Watchlist, Keyword, and [Qualified post](/help/signals/qualify-a-post/). None ticked means every source | Every source | Not shown |
| Excluded titles | Terms matched against the lead's title, or the headline when there is no title | None | None |
| Excluded industries | Terms matched against the lead's industry | None | None |

HeyReach, Instantly, Smartlead, and Emelia configurations start tighter because a sequence is a costlier mistake than a message in a channel. They have no **Sources** rule: the agents a configuration listens to do that job, as the next section explains.

Each exclusion list takes up to 50 terms of up to 80 characters. A term matches whole words and ignores case, so `intern` holds back "Marketing Intern" and leaves "International Sales Lead" alone.

Embers checks the rules in the order of the table and stops at the first one that fails. That rule becomes the recorded reason, for example `score 62 below 90`, `not an ICP match`, or `title matches excluded term 'intern'`.

## How configurations route leads

On HeyReach, Instantly, Smartlead, and Emelia, one connection holds any number of configurations. Each configuration is one route: the agents that feed it, the campaign or list it sends to, and its own rules. A workspace can also connect several accounts of one tool, such as an Emelia account per seat, and a lead goes to every configuration it matches across all of them, unless One sender per prospect (below) is on.

- **Agents.** **All agents** sends every agent's leads, including agents you add later, and says what that covers today, for example "Leads from every agent, including agents you add later. Today that is your profile, 2 watched profiles and every keyword." **Choose agents** starts with nothing ticked, and saving asks you to "Choose at least one agent." until you tick one. Under **Profiles**, your own profile is one row, **Your profile**, for your posts and the comments you leave, and each [watched profile](/help/signals/watchlist/) is one row by name. Under **Other agents** are **Keywords** and **Qualified posts**. Ticking **Keywords** shows your [tracked keywords](/help/signals/keyword-tracking/) as chips under it, each with how many posts it has found, all switched on with **Every keyword, and new ones** ticked, so keywords you add later are sent too. Click a chip to switch it off and keep the rest, or use **Clear** and switch on only the ones you want; **Select all** switches on every keyword you have today. A line over the list says what is chosen, such as "2 of 15 keywords · 1 profile", and past eight profiles and keywords one search field finds either. A configuration saved before Your profile was one agent may show it half-ticked, with which half it still sends. Click it to choose both.
- **How an agent matches a lead.** Your profile, like a watched profile, matches people who engaged with that profile's posts or its comments. With keywords chosen, Keywords matches a person who wrote, or engaged with, a post that matched one of them. Only posts the relevance check kept count, the same posts the leads list counts. **Every keyword, and new ones** and Qualified posts match by the kind of signal the lead has.
- **The Agents column** on the **Configurations** card names what feeds each row: "All agents", "Your profile", "Jasmin Alić, all keywords", "Keyword “crm”", or a count such as "3 profiles, 2 keywords". A row with only half of Your profile reads "Your posts" or "Your comments", and one whose chosen keywords were all removed says "Keywords removed".
- **Two configurations, one lead.** A lead that matches two configurations with different targets goes to both, including configurations on two connections of the same tool. With the same target it goes once, and the second is logged as `already queued for` that target. To send each lead to one connection only, turn on One sender per prospect (below), or give their configurations different agents or rules.
- **A deleted agent** stops feeding the configuration. If every agent a configuration used is deleted, **Needs attention** at the top of the page warns `Every agent this configuration used was deleted. Choose agents again.` and it sends nothing until you edit it and choose agents again. If every chosen keyword was removed, it warns `Every keyword this configuration used was removed. Choose keywords again.` and Keywords matches nothing until you do.
- **The switch** on each row turns automatic sending on or off for that configuration alone. A configuration that is off can still receive a manual push.
- **Also send leads you already have**, offered when you add a configuration, sends the matching leads Embers already found, best score first, once. It passes the same rules, skips anyone already sent to that target (and, with One sender per prospect on, anyone another connection owns), and sends every matching lead, however many there are, in steps paced to what the tool accepts. The row shows "Sending existing leads · 40 of 120" while it runs.

## One sender per prospect

When each rep has their own outreach connection, such as an Emelia seat each, one prospect can match both and hear from two people at your company. **One sender per prospect** stops that across HeyReach, Instantly, Smartlead, and Emelia. It is off until a workspace admin turns it on in the **Outreach connections** card under your outreach tools on the **Integrations** page (`/integrations`), or on any outreach tool's own page. With it on:

- **The first connection keeps the prospect.** A prospect belongs to the first outreach connection Embers sends or queues them to. Every other outreach connection in the workspace skips them, whichever agent, configuration, or source the lead comes from, and logs the row as **Held back** with the owner, such as `already with Emelia: Sean`.
- **Ownership never expires.** It stays with that connection even after you disconnect it, because the person was already contacted.
- **One new lead, several matches.** Embers picks one connection: the rep whose own LinkedIn profile the prospect engaged with, when that connection's configuration chooses that profile under **Choose agents**. Otherwise, the matching connection with the fewest new prospects in the last 30 days, and on a tie the one connected first.
- **Inside the owning connection nothing changes.** Its other campaigns and lists can still get the prospect, each once.
- **Sending existing leads respects it.** **Also send leads you already have** passes over prospects another connection owns and sends the rest.
- **Send anyway is your call.** To put a prospect in a second connection on purpose, an administrator chooses **Send anyway** on its held-back row. It goes out once, and the prospect stays with its owner. Automatic delivery never overrides the owner, and **Retry** on a failed or blocked row for a prospect another connection now owns is refused with a pointer to **Send anyway**.

Turning it on does not undo earlier sends. The switch shows how many prospects were already sent to more than one connection. It cannot see contacts your team adds to an outreach tool directly, messages a rep sends by hand on LinkedIn, or other Embers workspaces.

Without it, a lead goes to each campaign once per connection, and to every connection whose configurations match it.

## Read the delivery log

Slack, HubSpot, Salesforce, Pipedrive, Attio, [Notion](/help/integrations/notion/), Google Sheets, HeyReach, Instantly, Smartlead, and Emelia each list their deliveries on the **Activity** card of their page, newest first, with **All**, **Failed**, and **Held back** filters. Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, and Google Sheets keep 30 days of them. Each row is in one of these states:

| State | Meaning | What you can do |
| --- | --- | --- |
| Delivered | The destination accepted it | Nothing |
| Held back | A rule, a missing email or profile, or another connection that owns the prospect held it back. Nothing was sent | **Send anyway** |
| Failed | The destination refused it, or retries ran out | **Retry** after fixing the cause |
| Blocked | It could not be attempted, for example because the destination or its configuration is paused | **Retry** once resumed |

A held-back row is not an error and is not retried on its own. **Send anyway** sends it regardless of the rules. To push a lead that is not in the log, use **Send to** and tick **ignore rules**.

A failed delivery is retried automatically on a fixed schedule: the first attempt plus seven retries, spread from 30 seconds out to about 6.3 days. Some failures, such as a revoked key or a deleted channel, pause the destination instead; each integration's article lists them. Nothing is sent to a paused destination until you fix the cause and choose **Resume**.

## Signed webhooks are not filtered

[Signed HTTPS webhooks](/help/integrations/webhooks/#which-leads-trigger-an-event) carry every qualifying lead so your own code sees the full stream and decides for itself. If you want a filtered feed on an endpoint, filter it on your side or in the automation tool that receives it.

## Related

- [Send a lead to a destination](/help/leads/send-to-destination/): Push the leads you pick, with or without the rules.

- [Push leads into HeyReach](/help/integrations/heyreach/): Configurations in practice, one campaign per agent.

- [Send qualified leads to Slack](/help/integrations/slack/): One channel, two event toggles, and the card.

- [Choose where Embers sends your leads](/help/integrations/overview/): Every destination and the plan each one needs.

## Frequently asked questions

**Do delivery rules apply to signed webhooks?**

No. Signed HTTPS webhooks carry every qualifying lead and are not filtered by delivery rules. Filter them in your own code, or in the automation tool that receives them.

**Are the rules shared between destinations?**

No. Slack, HubSpot, Salesforce, Pipedrive, Attio, Notion, and Google Sheets each keep one set, and every HeyReach, Instantly, Smartlead, and Emelia configuration keeps its own. Slack can stay wide while a campaign only receives the people you would work today.

**Does tightening a rule remove leads already delivered?**

No. Rules are checked once, when a lead is about to be delivered. Anything already in the channel, the CRM, or the campaign stays there.

**Can one lead go to two HeyReach campaigns?**

Yes, when two configurations with different campaigns both match it. Two configurations pointing at the same campaign send the lead once. With One sender per prospect on, both campaigns must belong to the same connection.

**How do I stop two reps contacting the same prospect?**

Give each rep their own outreach connection, such as an Emelia seat each, and have an admin turn on One sender per prospect in the Outreach connections card on the Integrations page. The first connection a prospect is sent to keeps them, and every other outreach connection skips them.
