> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getoneprofile.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Cooldown and exclusions

> One rule for the whole workspace: how long before anyone hears from you again, how many people at one account, and which accounts nobody touches.

Two sequences running at once can reach the same person in the same week without either one knowing. The cooldown is one workspace rule that stops that: nobody is contacted again inside the window you choose, by any sequence, from any sender.

## Set the two dials

<Steps>
  <Step title="Open Cooldown and exclusions">
    Go to [Cooldown & exclusions](https://app.getoneprofile.ai/settings/cooldown) in Settings.
  </Step>

  <Step title="Set the person cooldown">
    Turn it on and enter a number of days. Anyone contacted within that many days is not contacted again until it passes.
  </Step>

  <Step title="Set the account cooldown">
    Enter how many people at one account may be contacted, and over how many days. The count spans every sequence.

    A sequence needs a **Company domain** or **Company** column mapped on its Audience tab for this to apply. Where a domain is mapped, it is what identifies the account, so "Acme Corp" and "Acme, Inc." count as one company.
  </Step>
</Steps>

Either dial can be left off. Both start off for every workspace that existed before this shipped.

## Exclude accounts and audiences

An **exclusion list** is a named, reusable set of accounts no sequence should touch. There are two kinds:

* **Companies.** Names and domains you paste in. A value with no spaces and a dot is read as a domain, so `acme.com` matches everyone there.
* **An audience.** A live reference to a table. Rows added to that table later are excluded too.

<Steps>
  <Step title="Start a list">
    Click **New list**, give it a **Name**, and choose what it **Excludes**: **Companies I paste in** or **Everyone in a table**.
  </Step>

  <Step title="Fill a companies list">
    Click **Edit**, paste the names and domains one per line, then click **Add**. A table-backed list needs nothing pasted.
  </Step>

  <Step title="Decide who inherits it">
    Switch **On by default** on, and every sequence applies the list unless it switches the list off for itself.
  </Step>
</Steps>

A list marked **On by default** applies to every sequence that has not switched it off. A sequence's **Audience** tab shows the lists it inherited, and each can be switched off there. That never changes the workspace's list.

## What a held contact looks like

A contact caught by either dial is held, never dropped. The **Contacts** tab shows them as **In cooldown**, and **Next send** carries the date they become eligible again.

The **Why** column says how long ago they were contacted. Where the account dial caught them, it says how long ago a colleague was contacted, without naming who. A contact caught by an exclusion list shows as **Excluded**, and **Why** names the list.

Once the window passes, the next sweep enrols them automatically, as long as their row still matches the audience.

## Release someone by hand

Open the row menu and choose **Release into this sequence**. To release several, select them and click **Release**.

A release applies to that sequence only. The contact stays held everywhere else, and the clock is untouched.

## Good to know

<AccordionGroup>
  <Accordion title="What counts as contacting someone?">
    An email send, a LinkedIn message, an InMail and a connection request all start the clock. A profile view, a follow, a like and a withdrawn invitation do not.

    A sequence can also map a **Last contacted** column on its Audience tab. A date there counts exactly as one of your own sends would. Cells that will not read as a date are skipped, and the audience preview says how many.
  </Accordion>

  <Accordion title="How is this different from the do-not-contact list?">
    The [do-not-contact list](/outreach/do-not-contact) is compliance. Those people have asked never to hear from you, and only a person can take them off it. A cooldown is coordination between sequences that are all allowed to send, and it expires on its own.
  </Accordion>

  <Accordion title="Does a hold stop a sequence that is already running?">
    No. Someone already enrolled keeps receiving the sequence. The rules apply when a sequence decides whether to enrol somebody new, and again just before a send that would break the account limit.
  </Accordion>

  <Accordion title="Why is my account cooldown not applying?">
    The sequence's Audience tab maps neither **Company domain** nor **Company**, so there is no way to tell which people work at the same account. The audience preview says so where it applies.
  </Accordion>

  <Accordion title="Does the Last contacted column feed the account cooldown too?">
    No, only the person cooldown. An imported date says when one person was reached. The account rule needs to know how many distinct people at a company were reached, which an imported date cannot answer.
  </Accordion>

  <Accordion title="What happens to a sequence's holds when I delete a list?">
    Every sequence that inherited it stops excluding its accounts at the next sync, and the contacts it held are judged again then.
  </Accordion>
</AccordionGroup>

## Next steps

<CardGroup cols={2}>
  <Card title="Choose the audience" icon="users" href="/outreach/choose-the-audience">
    Map the columns these rules read, and see who a sequence will enrol.
  </Card>

  <Card title="Do not contact" icon="ban" href="/outreach/do-not-contact">
    The list Oneprofile will never email, however long ago you last wrote.
  </Card>
</CardGroup>
