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

# Keep your contacts, deals, and pipelines

> See what's next with the people your squad works with, follow each deal step by step, run pipelines, clean up the list, and mark who must not be contacted.

**Contacts** is where your squad keeps the people and companies it works with, the deals with them, and the pipelines that carry many people through stages. Your teammates keep it while they work. They add the people that the work brings in, keep a deal for each client, and log what happened. Every email that a Squad inbox sends or receives is logged by itself. You read it, correct it, and do the steps that are yours.

* A **contact** is a person or a company. A person can belong to a company.
* A **deal** is one goal with someone: a new client to onboard, a quote, a renewal, or something you buy. It keeps the money, the steps owed both ways, the documents with their dates, and why each choice was made.
* A **step** is something owed on a deal. It belongs to you, to a teammate or another person in your squad, or to the other side, and it can have a day.
* A **pipeline** carries many people through your own stages, for example New, Contacted, Replied, and Won. A person can be in more than one pipeline. A pipeline with a goal and dates works as a campaign.
* A **follow-up** is the day to get in touch again with a person in a pipeline.

For the limits on deals, names, fields, stages, and pipelines, see [Limits and defaults](/docs/limits-and-defaults#contacts-and-pipelines).

## Open Contacts

**Contacts** is a place in the sidebar, pinned under **Today** until you unpin it. Open it in one of these ways:

* Select **Contacts** in the sidebar. If you unpinned it, it is under **More**. On Squad for Mac (private beta), you can also press ⌘4.
* Select **Email** in the sidebar. Select the title at the top of the list, for example **All inboxes**. In the menu, select **Contacts**.
* Press ⌘K (Ctrl+K on Windows) and select **Contacts**. To open one contact, type a few letters of a name. The matches show under **Contacts**.

Contacts opens on **Home**. The tabs at the top are **Home**, **Deals**, **Pipelines**, and **People**. **Deals** shows how many deals are open, **Pipelines** how many pipelines you have, and **People** how many contacts you keep.

A deal or a person opens over the tab that you came from. The line at the top names that tab, then the contact, for example "Deals › Rivera Practice". Select the tab's name to go back.

To find a person or a company from any tab, type in the search box ("Search name, email, domain or tag"). The results take the place of the tab. The search also finds people by their company, title, or city, and contacts by their tags and handles. Archived contacts do not show in search. When nothing matches, Contacts says "Nobody matches" and what you typed.

## Home: what's next

**Home** tells you, the way a chief of staff would in the morning, what's next and whose move it is.

At the top, one sentence sums it up, for example "You have 7 deals open. 2 things need you today. Juno is on 3 steps and 18 follow-ups. 3 things wait on the other side. Service agreement for Harlow renews in 5 days." What needs you is in bold.

Under the sentence, tiles show the numbers worth knowing:

* **Money**, for the owner and Administrators only, once your squad has a currency: "Paying you each month", then "Signed this month" and the deals waiting in quotes, for example "In 3 quotes, waiting for a yes". When yearly deals are among them, these say "A year, signed this month" and "A year in 3 quotes, waiting for a yes". A tile with nothing in it does not show, except the monthly one. Selling deals in another currency than your squad's are not added up, and a line under the tiles says how many, for example "1 deal in other currencies isn't counted here."
* **A pipeline's goal**: for the pipeline with a goal that ends first, for example "14 of 40" and "At Shared in Spring launch, by Nov 30", with a bar.

On the left, by whose move:

1. **Your move**: a card for each of your steps and follow-ups that is due today or late. A dot shows before the heading when something is due. See [Work a step](#work-a-step). When more are due than Home shows, the heading says how many in all, and **See them all in Needs you** opens **Needs you**. When nothing is due, it says "Nothing needs you today." and your next step, for example "Next for you: Send the contract, tomorrow." Your later steps that **This week** does not show come under the cards, with their day or "No date yet".
2. **Your squad is on it**: for each teammate, its steps due today, for example "**Juno**: Send the contract, Rivera Practice", and its follow-ups in each pipeline, for example "**Spring launch**: Juno follows up with 18 people (Send a first email)." The words in brackets are the next step that most of those people have. The teammates with the most work come first. Select a line to open the deal or the pipeline.
3. **Waiting on them**: the steps that the other side owes you, for example "**Alex Rivera**: Send the signed contract. Promised it, in writing.", with how many are late at the top. Then the deals that nobody has heard from in a while, with where the deal stands and how long it has been quiet, for example "quiet 16 days". When more wait than Home shows, a line says how many more are on the deals board, with a link to it, or to **Selling** and **Buying**. More quiet deals are only counted, for example "And 4 more deals have gone quiet."

On the right:

1. **Pipelines**: each pipeline, with how many people are at each stage that has someone in it, lost and closed stages left out, for example "Good fit 42, Messaged 49, Shared 14", and its goal so far, for example "14 of 40", or how many people it holds. Select a pipeline to open it.
2. **This week**: the next days, with everyone's steps, renewals, and follow-ups, by day. For example "Tomorrow **You**: Send the contract.", "Wed **Harlow**: Service agreement renews.", or "Thu **Juno** follows up with 12 people in Spring launch."
3. **Since you last looked**: what changed since your last visit to **Home** in this browser, newest first, each with a blue dot. It covers new deals, decisions, documents, steps done, kept, missed, or broken, new promises, and shares and quotes, with who did it. What you did yourself is left out. Select a line to open its deal or contact.
4. Questions to ask your chief of staff, for example "Who owes us something?", "Who in Spring launch reached Shared?", and "Who hasn't heard from us in a month?". Select one to open a chat with your chief of staff, with the question filled in.

A part with nothing in it does not show. When Home holds more than it can list, it says so, for example "And more this week." For how many each part lists, and how long a deal waits before it counts as quiet, see [Limits and defaults](/docs/limits-and-defaults#contacts-and-pipelines).

A Viewer sees **Home** without the actions and the questions. A person who sees only some teammates does not see the deals gone quiet, and a teammate hidden from them shows as "A teammate".

When Contacts is still empty, **Home** says "Nothing is here yet." and what your teammates do here, with **Ask** and your chief of staff's name (not for a Viewer). It opens a chat with your chief of staff, with a request to start a list of the people you work with filled in.

## Work a step

A step or a follow-up shows as a card on **Home** under **Your move**, and as a row in **Needs you** and on **Today**.

* The first line says the step, for example "Send the contract". A follow-up says its next step, or "Follow up" and the stage.
* If the person is marked do not contact, "Do not contact" and their name come first.
* On a card, the next line says who it's with, the money (the owner and Administrators see the amount, everyone else how sure it is), when it is due, and how it was promised. For example "Rivera Practice, \$2,400 a month, signed. 2 days late. Promised it, in writing."
* On a row, the next line says when it is due, how it was promised, where a teammate's task for it stands ("on it", "waiting for review"), and the deal or the pipeline. For example "a day late · promised it, in writing · Onboard the Rivera practice by November 1, with Rivera Practice".

When it is due reads in words: "today", "tomorrow", "in 3 days", "on 30 Oct", "a day late", or "4 days late". A late step is in bold. See [Statuses](/docs/statuses).

A card shows its actions. On a row, point at it, or move to it with Tab, to show them:

* **Done** marks the step done. A step that was promised is marked kept. On a follow-up, **Done** clears the follow-up and its next step.
* **Move the date** asks for the new day in **To**. It starts on tomorrow, and you cannot pick a day before today. For a deal's step, you can type why in one line. The why goes in the deal's history. Select **Move**, or **Cancel**. The step is then due in the morning of that day. A teammate's task for the step is set aside, and the teammate gets a new task on the new day. A follow-up keeps its next step.
* **Ask** and your chief of staff's name (on a card, **Ask** and the name **to do it**) opens a chat with your chief of staff. The step, who it's with, and the deal or pipeline are filled in, so a teammate takes it on. Nothing is sent until you send it.

Select the card or the row itself to open its deal, or the person for a follow-up. A step changes only after Squad saved the change. While it saves, **Done** says **Saving…**. If Squad refuses the change, the reason shows under it.

A Viewer sees the steps without **Done**, **Move the date**, or **Ask**. A step of a teammate who is hidden from you has no actions.

## Deals

### Find a deal

Select **Deals**. Pick which deals to show. Each choice says how many deals it holds.

* **Selling**: deals where money comes to you, such as clients.
* **Buying**: deals where money goes out, such as suppliers and partners.
* **Closed**: deals that ended won, lost, or dropped, from selling and buying together, the most recently changed first.

For **Selling** and **Buying**, pick **Whose move** or **List**.

**Whose move** shows the open deals in columns side by side. Each deal sits in the column of its next step. The next step is the earliest one that is not waiting on another step.

| Column | The next step |
| - | - |
| **Late** | Belongs to you, a teammate, or another person in your squad, and the time it was due has passed. A step dated on the dashboard is due at 9:00 on its day, so it can be in **Late** while it still says "today". |
| **Yours** | Belongs to you. |
| **Your squad's** | Belongs to a teammate or another person in your squad. |
| **Theirs** | Belongs to the other side. |
| **Nothing next** | Does not exist. The deal needs a step, or to be closed. |

Each column says how many deals it holds. An empty column says so, for example "Nothing waits on you." The deals in a column come in the order their next step is due, with undated steps last. When a column holds more deals than it shows, a button with how many more opens **List**. For the owner and Administrators, a column also shows its money: a sum over a year when a deal in it pays by the month or the year, for example "\$13,800 a year", else a plain sum. It counts only money in your squad's currency, and only when every deal of the column is on screen.

A deal on **Whose move** shows:

* **Do not contact**, when the person or their company is marked.
* Who it's with. For the owner and Administrators, the amount, how often, and how sure, for example "\$900" and "a month, on trial". Everyone else sees how sure, for example "On trial".
* Where the deal stands now, as your teammate last wrote it, or the deal's goal until a teammate writes it.
* A bar with one mark for each step: done, missed, ours to do now, waiting on them, or not yet.
* The next step, for example "Next: Send the contract.", how it was promised, and whose it is and when. A late step is in bold.

**List** shows the open deals, the most recently changed first. Each row shows the goal, the money (the amount only for the owner and Administrators), who it's with, how many steps are done, the teammate who looks after it, and the next step with whose it is and when. **Show more** at the end loads more.

When there are no deals yet, **Deals** says what a deal is, with **Ask** and your chief of staff's name **to open one**.

### Open a deal

Your teammates open deals as they work. To open one yourself:

<Steps>
  <Step title="Start">
    On **Selling**, select **New deal**. On **Buying**, select **New supplier deal**. A Viewer does not see these buttons.
  </Step>

  <Step title="Say the goal">
    In **The goal, in one sentence**, type what the deal is for, for example "Onboard the Rivera practice by November 1".
  </Step>

  <Step title="Say who it's with">
    Type their name in **With**, their address in **Their email**, or both.
  </Step>

  <Step title="Pick who looks after it">
    In **Looked after by**, pick a teammate, or leave **Nobody yet**. If your squad has playbooks, pick one in **Steps from** to start the deal with its steps, or leave **No playbook**.
  </Step>

  <Step title="Add the money">
    Only the owner and Administrators see this part. Type the amount in **Money (optional)** and the code of the **Currency**, for example USD. Pick **How often**: **Once**, **A month**, or **A year**. Pick **How sure**: **A target**, **Quoted**, **On trial**, **Approved**, **Signed**, or **Paid**.
  </Step>

  <Step title="Open it">
    Select **Open the deal**. The deal opens.
  </Step>
</Steps>

Squad finds who the deal is with:

* A contact with that email is the one.
* With a name and no email, a contact with exactly that name is the one. If more than one contact has that name, Squad refuses and asks for their email.
* Otherwise Squad adds a new contact with the name and the email.

The first currency that a deal's money is given in becomes your squad's currency. Totals add up only money in that currency.

### Read a deal

A deal reads from top to bottom:

| Part | What it shows |
| - | - |
| Top line | **Deals** (or the tab you came from) and the contact's name. Select the tab's name to go back. |
| Do not contact | "Do not contact \[name]. Your squad's email won't reach them.", when the person or their company is marked. |
| Title | The name of who the deal is with. Select it to open their page. Beside it, **Ask** and the teammate's name **about it**, and **⋯**. A Viewer sees neither. |
| Goal | "Goal:" and the deal's goal. |
| Where it stands | Your teammate's latest word on where the deal stands, in a sentence or two. It shows only when a teammate wrote one. |
| Details | The money and its way, for example "\$2,400 a month, signed, money in". Everyone but the owner and Administrators sees "Signed, money in". Then the playbook it started from with its version, the teammate who looks after it, and its project. Select the project to open it. |
| Closed | On a closed deal, "Closed." with the outcome and why, for example "Closed. Won: Signed for a year." |
| Rules | One line for each rule, for example "Rule: always copy their assistant." |
| Whose move | On an open deal, **Our move** with your squad's next step and when, and **Their move** with the other side's. "Nothing next. Give it a step, or close it." when there is neither. |
| **The plan** | Every step, grouped by phase, with how many are done. The next step is in bold. A step that ended is struck through. |
| **History** | The deal's history, newest first, with the day, where it came from, and who wrote each line. A long entry shows **Read it all**. |
| **Promises** | The steps that someone promised, **Ours** or **Theirs**, with when they are due or "Kept." or "Broken.", and how it was promised. |
| **Decided** | Each decision, who decided it and when, "Why:" and what was "Turned down:". |
| **Documents** | Each document with its dates, for example "signed 2 Mar 2026 · renews 2 Mar 2027". Select one to open the doc or the link. |
| **People** | The people on the deal with their roles. Select one to open their page. |

**Promises**, **Decided**, and **Documents** show their first few, with **All** and the number to show the rest. A part with nothing in it does not show.

Each step shows:

* What's owed.
* Under it: `after “[step]”` while it waits for another step, how it was promised ("promised it", "promised it, in writing", or "promised it, signed"), where a teammate's task for it stands ("working on it", "finished its task", or "waiting for review"), how it ended ("kept", "missed", "broken", or "dropped"), and the note given when it ended or moved.
* On the right: whose it is and when it is due, or the day it ended.

A step that ends stays on the deal, so a kept promise and a broken one both show. Nothing is deleted.

When a deal holds more history than the page can show, the page says "Some of this deal's documents and history are too large to show here."

### Change a step

On an open deal, point at a step that is still open, or move to it with Tab, to show its actions:

* **Done** (or **Kept** for a promise): the step is done. Its task is done too.
* **Missed** (or **Broken** for a promise): the step did not happen. Its task is set aside.
* **Move the date**: pick the new day. Optionally, type why in "Why, in one line (it goes in the deal's history)". Select **Move**.
* **Drop it**: the step is no longer needed. Its task is set aside.

A step owed by a teammate that you cannot see shows without these actions.

To add a step:

<Steps>
  <Step title="Start">
    Under **The plan**, select **Add a step**.
  </Step>

  <Step title="Say what's owed">
    In "What's owed, in one sentence", type the step, for example "Send the signed contract".
  </Step>

  <Step title="Pick whose it is">
    In **Whose**, pick **Yours**, a teammate, or the contact's name for the other side.
  </Step>

  <Step title="Pick the day">
    Keep **Due** and pick the day (tomorrow at first), or clear **Due** for a step with no day.
  </Step>

  <Step title="Add it">
    Select **Add the step**.
  </Step>
</Steps>

If Squad refuses a change, the reason shows on the deal, for example "Couldn't change that step." and why.

### Close, open again, or delete a deal

Select **⋯** ("More for this deal") at the top of the deal:

* **Close as won…**, **Close as lost…**, or **Close as dropped…** opens "Close “\[goal]” as won" (or lost, or dropped). Optionally, type why in "Why, in a sentence (it stays in the deal's history)". Select **Close it**. The tasks for its open steps are set aside, and the deal moves to **Closed**.
* **Open it again** shows on a closed deal. Its open steps wake again, and each renewal date makes its step again. It does not show when an open step belongs to a teammate that you cannot see.
* **Delete…** asks "Delete “\[goal]”?". Its steps, people, and documents go. Its history stays on the contact's page. Select **Delete the deal** to confirm. To end a deal, close it instead.

### Ask about a deal

When a teammate looks after the deal, select **Ask** and the teammate's name **about it**. A chat with that teammate opens with "About the deal “\[goal]”: " filled in.

Some changes are only your teammates' to make. Ask them to change the goal, the money, who looks after the deal, its people or rules, to add or remove a document, to record a decision, or to write where the deal stands now.

### What your squad does with deals by itself

* A teammate's step becomes that teammate's task on its day, or at once when it has no day. A step that comes after another waits until that one is done. If that one is missed or dropped, it keeps waiting. When the teammate finishes the task, the step is done. See [Tasks](/docs/missions).
* When a step of the other side is a day late and a teammate looks after the deal, that teammate gets one task to draft one friendly nudge. The email goes out under your squad's email approval, like all outreach. A step moved to a new day can get a new nudge. It is never written to someone marked do not contact, by their own mark, their company's, or their domain's.
* When a document has a renewal date, the deal gets a step ahead of it, for example "Get ahead of the renewal of Service agreement on 2027-03-02". It goes to the deal's teammate, else the person in your squad who looks after the deal, else the owner. Removing the date or the document drops the step.
* A pipeline can start a deal when someone reaches a stage, for example Won. The deal is named after the playbook (or the pipeline) and the person, for example "New client: Alex Rivera". The pipeline's teammate looks after it, and it starts with the playbook's steps. If the playbook gives a step to a teammate that the person who set up the pipeline, or the person who moved them, cannot use, the deal opens without its steps, and its history says why. A person in a pipeline gets one deal from it, however often they reach the stage. See [Work a pipeline](#work-a-pipeline).
* Your teammates are asked to write where each deal stands, in a sentence or two, each time it moves.

For how long these wait and how often Squad checks, see [Limits and defaults](/docs/limits-and-defaults#contacts-and-pipelines).

## Work a pipeline

### See your pipelines

Select **Pipelines**. Each pipeline shows on one line, with its name and how it stands:

* Against its goal, for example "14 of 40 at Shared, 31 days left, Juno". When the goal is met, the line starts "Goal reached:".
* Without a goal, how many people it holds, for example "120 people".

The line ends with the days left ("1 day left", "ends today", or "ended") when the pipeline has an end date, and with the name of the teammate who works it. Select a line to open the pipeline. Archived pipelines do not show.

A pipeline page shows, from top to bottom:

* **Pipelines** › the pipeline's name. Select **Pipelines** to go back.
* What the pipeline is for, then its goal, for example "Goal: 40 at Shared by November 30.", and the teammate who works it, for example "Juno works it."
* **The funnel**: every stage with a bar and its exact number of people, and how many are in the pipeline in all, for example "212 in it". With a goal, the line under it says, for example, "14 of 40 at Shared, 31 days left."
* **What moves people along**: the pipeline's rules, in sentences. For example "Outreach moves people to Contacted.", "A reply on any channel moves them to Replied.", "A quote from them moves people to Shared.", "Likes and follows count as touches but move nobody.", "Contacted waits 3 days, then gets a follow-up.", "An unsubscribe marks them do not contact.", and "Reaching Won starts a deal from its playbook."
* The people, in one column for each stage that is not lost or closed. A column shows the stage, its number, and what the stage means, for example "First message sent. Waiting for an answer." Each card shows the face of the teammate who has the person, the name, **Do not contact** when it applies, their title or company, and the follow-up, for example "Send the contract, today" or "Follow up in 3 days". A due follow-up is in bold.
* Under the columns, the stages that end a lead, for example "Lost: 3." with **See who**.

A column shows its first few people. When it holds more, select the number, for example **34 more**, to see all of them on **People**, filtered to that stage. To see everyone in the pipeline as a table, select **People** at the top of the page. **By stage** is the page itself.

**Ask** and the name of the pipeline's teammate (or your chief of staff when it has none) **about it** opens a chat about the pipeline.

### Create a pipeline

<Steps>
  <Step title="Start">
    On **Pipelines**, select **New pipeline**.
  </Step>

  <Step title="Name it">
    Type the **Name**, for example "Brand outreach". In **What it is for**, say what the pipeline tracks. Your teammates read this when they work the pipeline.
  </Step>

  <Step title="Add fields">
    Under **Fields**, select **Add a field** for each value that you want to track for each lead. Type its name and pick the type: **Text**, **Number**, **Choice**, **Link**, **Date**, or **Yes or no**. For **Choice**, type the choices, separated by commas.
  </Step>

  <Step title="Create">
    Select **Create pipeline**. The pipeline opens.
  </Step>
</Steps>

A new pipeline starts with the outreach stages: New, Qualified, Contacted, Engaged, Replied, Won, Lost, and Disqualified. To change them, open the pipeline and select **Settings**.

A goal, dates, the teammate who works the pipeline, rules by kind of touch, and a stage that starts a deal are set by your teammates. Ask for them:

```text Ask your chief of staff theme={null}
Set up a pipeline called Spring launch for the creators we pitch the launch to. The goal is 40 people at Shared by the end of November. Juno works it. A quote from them moves them to Shared, and Won starts a deal from the New client playbook.
```

### Change the stages and fields

<Steps>
  <Step title="Open the settings">
    Open the pipeline, then select **Settings**.
  </Step>

  <Step title="Edit the stages">
    Under **Stages**, change a name, pick what the stage means, and type the days in **Follow up after**. Leave it empty for no follow-up. **Up** and **Down** change the order. **×** removes a stage. **Add a stage** adds one.
  </Step>

  <Step title="Edit the fields">
    Under **Fields**, change, add, or remove fields.
  </Step>

  <Step title="Save">
    Select **Save**.
  </Step>
</Steps>

Each stage has one meaning:

| Meaning | What it does |
| - | - |
| **Open** | Work in progress. Only an open stage has follow-ups. |
| **Won** | The lead ends with a yes. It keeps a column on the pipeline page. |
| **Lost** | The lead ends with a no. It shows in the line under the columns. |
| **Closed** | The lead ends for another reason. It shows in the line under the columns. |

A lead in a won, lost, or closed stage never moves by itself again, and it has no follow-up. When you change an open stage to Won, Lost, or Closed, its leads lose their follow-ups.

Squad refuses to remove a stage that still holds leads. Move the leads to another stage first. A pipeline needs at least one open stage.

To archive a pipeline, select **Archive this pipeline** in its settings. It archives at once, without a question, and saves any other change in the dialog too. The pipeline leaves every list, and its teammates' follow-up tasks for it are set aside. The dashboard has no button to bring it back. Ask a teammate to restore it.

### Move someone to another stage

* On the pipeline's page, point at the person's card, or move to it with Tab. Pick the stage in the menu that shows under the card.
* On **People**, filtered to the pipeline, check the people, select **Move to**, and pick the stage.
* On a person's page, select **Change** on the pipeline's card, and pick the stage.

If Squad refuses a move on the pipeline's page, "Couldn't move" and the person's name show above the columns, with the reason.

A lead that moves to an open stage keeps its follow-up. A lead without one gets the stage's **Follow up after** days.

### Set a follow-up

A person's page lists their pipelines under "Where" and their first name ("Where they are" for a company). Each card says the pipeline and the stage, for example "Brand outreach: Contacted", and the follow-up, for example "Next: Send the contract, tomorrow." or "Follow-up in 3 days." A due follow-up is in bold.

<Steps>
  <Step title="Open the card">
    On the pipeline's card, select **Change**.
  </Step>

  <Step title="Pick the day">
    Select **In 2 days**, **4 days**, or **A week**. **Clear** removes the follow-up. The line says the follow-up, for example "Follow-up due today", or "Follow-up not set".
  </Step>

  <Step title="Say the next step">
    In **Next step**, type what happens at the follow-up, for example "Send the contract". It saves when you click away or press Enter. The box shows only when a follow-up is set.
  </Step>

  <Step title="Close the card">
    Select **Done**.
  </Step>
</Steps>

Only a person in an open stage has a follow-up. If the follow-up belongs to a teammate that you cannot use, the card shows it without these buttons.

Squad also sets follow-ups by itself:

* A lead without a follow-up that enters an open stage with **Follow up after** days gets one.
* When your squad reaches them, for example by email, a message, or a call, the stage's delay starts again.
* When they reach your squad, for example with a reply on any channel, the follow-up clears.
* A like, a follow, a comment, a mention, a share, or a quote leaves the follow-up as it is.
* When a follow-up moves or clears this way, the next step clears too.

A due follow-up shows on **Home** under **Your move** when it is yours, or under **Your squad is on it** with the teammate who has it. A follow-up belongs to the person or teammate it was given to. Otherwise it belongs to the pipeline's teammate, then to the teammate who added the person, then to the squad's owner. Each teammate with follow-ups due in a pipeline gets one task for them about once a day, and no new one while the last is open. A pipeline makes no follow-up task before its start date or after its end date.

## People

### Find someone

Select **People**. Pick **Everyone**, **People**, **Companies**, or **Archived**. The line above the table says how many, for example "1,204 people and 88 companies.", or "22 match." with a filter. When Squad does not keep the count for a filter, select **Count them** for the exact number.

To narrow the list, select **Filter by tag, address, pipeline or how quiet** (**Filter further** when a filter is on) and pick one:

| Filter | Choices |
| - | - |
| **Tag** | Your most used tags, each with how many contacts have it. With many tags, type in **Find a tag**. |
| **Address** | **Checked**, **Might bounce**, **Bounced**, **Nobody reads**, **Unsubscribed**, or **Not checked yet**. |
| **Quiet for** | **14 days**, **30 days**, or **90 days** with no touch. |
| **In a pipeline** | Each pipeline. |
| **More** | **No name yet** or **Do not contact**. |

Each filter shows as a token, for example "Tag: landlord" or "In: Brand outreach", and filters of different kinds combine. A second tag replaces the first. Select **×** on a token to remove it. Your filters stay in this browser until you remove them. If your access covers only some teammates, **Quiet for** is not offered.

The table shows **Name**, **Who they are** (their title and company, else their address, or a company's domain), and **Last in touch**. Filtered to a pipeline, it adds **Stage** and **Next**, the follow-up. **Do not contact** shows under the name when it applies. A record without a name shows its address in gray. **Show more** at the end loads more rows.

### Change the people you pick

Check the box on each row, or the box at the top to pick everyone listed. A bar under the table says how many are selected:

* **Add to a pipeline** and a pipeline's name adds them. Filtered to a pipeline, it says **Move to**, and you pick a stage.
* **Tag**, then type the tag and select **Tag them**.
* **Ask** and your chief of staff's name **to…** opens a chat with their names filled in.
* **Clear** unpicks them.

If some do not change, the bar says how many, with the reason. A Viewer has no boxes to check, and **Archived** has none either.

### Change everyone a filter matches

With at least one filter, select **⋯** ("Do something with everyone listed"):

<Steps>
  <Step title="Pick the change">
    Select **Tag all of them…**, **Add all of them to a pipeline…**, or **Archive all of them…**. On **Archived**, the last one is **Restore all of them…**.
  </Step>

  <Step title="Read how many">
    Squad counts first and says, for example, "This changes 42 records. Among them: Maya Chen, Sam Ortiz, and more. Each one's history says what changed." Nothing changes yet.
  </Step>

  <Step title="Fill it in">
    For a tag, type the **Tag**. For a pipeline, pick the **Pipeline**.
  </Step>

  <Step title="Run it">
    Select the button that says the change and the number, for example **Tag 42 records**.
  </Step>
</Steps>

The change runs in the background. The line at the top of **People** says "Changing 42 records.", then how many are done so far, then "Changed 42 records." with **OK**. If some records did not change, it says how many and why. A Viewer does not see these choices.

If a filter matches too many records to count, Squad does not run the change. Narrow the filter.

### Export a spreadsheet

Select **⋯**, then **Export as a spreadsheet**. The spreadsheet holds everyone that the tab and the filters match. Squad says how many rows it holds, with **Download it**. The link works for a day. Everyone in your squad can export, a Viewer too.

The spreadsheet has these columns: Name, Kind, Emails, Company, Title, Tags, Pipelines, Handles, Do not contact, Last touch, Added, and Source.

### Review the list

When something needs cleaning up, a card at the top of **People** says "Your contacts could use some care." and what, for example "12 possible duplicates, 40 without a name and 203 addresses nobody can reach." Select **Review**. Pick a list:

* **Possible duplicates.** Two records that may be one, likeliest first, each with who they are and why: "the same LinkedIn account", "same name, same company", "same name, one at a personal address", "same name", "the address looks like their name", or handles a letter apart. **Same person** merges them into the one your squad has been in touch with more, and says "Merged \[name] into \[name]. You can undo this for 30 days." with **Undo**. **Not the same** keeps both, and Squad does not offer the pair again.
* **No name yet.** Records known only by an address. **Ask** and your chief of staff's name asks a teammate to find their names from their emails and signatures.
* **Nobody can reach.** Each address that bounced, that nobody reads, or that unsubscribed, with **Archive** for its contact.

Each list's name says how many it holds. **‹ People** goes back.

### Add a contact

Your teammates add contacts as they work, so you rarely need to. To add one yourself:

<Steps>
  <Step title="Start">
    On **People**, select **Add someone** next to the search box.
  </Step>

  <Step title="Pick the kind">
    In **Add a contact**, select **Person** or **Company**.
  </Step>

  <Step title="Fill in the details">
    Type the **Name**. Add an **Email** if you have one. For a person, you can add the **Company** and the **Title**. For a company, you can add the **Website or domain**.
  </Step>

  <Step title="Pick a pipeline">
    If you have pipelines, pick one in **Pipeline**, or leave **None**. A new lead starts in the pipeline's first stage.
  </Step>

  <Step title="Save">
    Select **Add contact**. The new contact opens.
  </Step>
</Steps>

If Squad already has a contact with that email, or a company with that domain, Squad updates that contact instead of adding a second one, and opens it.

When you type a company for a person, Squad finds that company or adds it. A person with a work email joins the company that owns the email's domain. Squad never uses an address or a domain as a name: a contact without a name shows its address in gray until someone adds the name.

## Read a person

Select a person or a company to open their page. Above the name, the tab you came from shows with the name, for example "People › Maya Reyes". Select the tab's name to go back.

The top of the page shows:

| Part | What it shows |
| - | - |
| Name and title | The name, then the title and the company. Select the company to open it. Point at the name or the title to see who set it, when, and where the fact came from, for example "Set by Juno 2 days ago, from Maya's email of 3 October." When a person in your squad set it, the text ends "A teammate won't change it." |
| **Ask** and your chief of staff's name **about** and their first name | Opens a chat with your chief of staff about them. A Viewer does not see it. |
| Who they are | The paragraph a teammate wrote about them, then how your squad has been in touch, for example "In touch 3 times, last 2 days ago. They haven't written back yet." or "Nobody has been in touch yet." A person who can see only some teammates does not see this line. |
| **Do not contact.** | Shows only when a mark covers them. See [Mark a contact do not contact](#mark-a-contact-do-not-contact). |
| Possible duplicates | "This may be the same person as" (or "the same company as") another contact, with why, and **Merge into this one** and **Not the same**. See [Merge two contacts](#merge-two-contacts). |
| A merge | After a merge, for example "You merged Dana R. into this record on 3 Oct. You can undo this until 2 Nov." with **Undo**. |
| Rules | What always or never applies to them, one line each, for example "Rule: always copy their assistant". Your teammates save a rule when you tell them one. |

Under it, the left side shows:

| Part | What it shows |
| - | - |
| **Where** and their first name **is** (**Where they are** for a company) | One card for each pipeline they are in: the pipeline and the stage, what's next with its follow-up, a **Score** once a teammate sets one, and the pipeline's fields that have a value. **Change** opens the stage, the follow-up, the **Next step**, the fields, and **Remove from pipeline**. **Done** closes it. See [Set a follow-up](#set-a-follow-up). Under the pipelines, each deal they are on: an open one says what's next, and a closed one says how it ended. Select a deal to open it. **Add to a pipeline** puts them in another pipeline. |
| **History** | The timeline, newest first. Each entry says what happened, where, which way, and who logged it, for example "Email received" or "Call, from them". A like or a follow says "a weak signal: moves nothing". Select an email entry to open the email. **Show older** loads more. |

The right side shows:

| Part | What it shows |
| - | - |
| **Before your call**, with the day and time | The next meeting ahead that has a brief: what it is, who it is with, the brief, its notes, and **Open the email** or **Open the link**. |
| **Reach** and their first name (**Reach them** for a company) | Their addresses, each with **primary** when they have more than one, and a status word: **checked**, **not checked yet**, **Nobody reads it**, **Might bounce**, **Bounced**, or **Unsubscribed**. Then their handles on other networks, for example LinkedIn or WhatsApp, with the number of followers. **Add an email** adds one. Point at an address for **Make primary** and **Remove**. See [Statuses](/docs/statuses). |
| **What we know** | What your teammates found about them: a short brief of what matters now. Each finding they add after it is a dated entry in **History**, in full. |
| **People** | For a company: the people at the company. |
| **Notes** | Your own notes. They save when you click away. See [Notes](#notes). |
| **Projects** | The projects they belong to. **Add to a project** adds one. |
| **Tags** | Words that group contacts, for example `landlord`. **Add a tag** adds them. Separate several tags with commas. |
| **Where this record came from** | Who added them, from where, and when, for example "You added Maya from LinkedIn 3 days ago." |

At the bottom are **Mark do not contact**, **Merge with another contact**, **Archive**, and **Delete forever**. A Viewer does not see them.

A touch with a person at a company shows on the company's timeline too, with the person's name.

What a person in your squad sets stays as they set it: the name, the title, the company, the domain, the website, the location, the industry, what a teammate wrote about who they are, and do not contact. A teammate's later save does not replace it.

### Notes

Type in **Notes** ("What matters about this contact. Saves when you click away."). Under the box, "Not saved yet" changes to "Saved".

Notes hold one paragraph. For the length, see [Limits and defaults](/docs/limits-and-defaults#contacts-and-pipelines). When you type more, the box says "Notes hold up to 2,000 characters." with **Add it to their history** "as today's note instead". Select it to keep the whole text as a dated note in **History**. The box then says "Added to their history". A text too long for one history entry says "Notes hold up to 2,000 characters, and one entry in their history 8,000. Split it, or save it as a doc and link it."

## How email updates contacts

Squad logs these emails on the contacts by itself:

* Every email that a teammate sends from its Squad inbox, including scheduled sends when they go out.
* Every draft that a person approves and sends.
* Every email that a Squad inbox receives, except spam.

Squad matches each address to the contact that has it. If no contact has the address, Squad uses the company that owns the address's domain. An address on a free email service, such as gmail.com, never matches a company. Squad does not log email on an archived contact.

Squad also adds people:

* A sent email adds each recipient who is not a contact yet, with their company for a work address.
* A received email adds its sender only when your squad wrote first in that conversation. A first email from someone new adds nobody. The teammate who reads it decides.
* Squad never adds you, the people in your squad, or your teammates' own addresses.

Squad checks addresses too:

* When Squad adds an address that no person reads, such as a no-reply address, it marks it **Nobody reads it**. An address at a throwaway email service is marked **Might bounce**.
* When an email from your squad bounces for good, its address is marked **Bounced**, and **History** says that mail to the address bounced.
* When someone marks your squad's email as spam, their address is marked **Unsubscribed** and they are marked do not contact.

Email also moves leads in the outreach stages:

* A sent email moves an early lead, for example in New or Qualified, to Contacted.
* A reply moves an open lead forward to Replied. It never moves a lead back.
* A lead in a won, lost, or closed stage never moves.

These rules belong to each pipeline, and a pipeline's page lists them under **What moves people along**. Your teammates can change them for a pipeline that you set up with them.

Only email through a Squad inbox is logged by itself. Your teammates log calls, meetings, messages on other networks, and what else happened: a quote, a form, a purchase, an intro, an unsubscribe, or a decision. A like or a follow counts as a touch but never moves anyone, whatever the pipeline's rules say. A comment, a mention, a share, or a quote moves a lead only when the pipeline has a rule for it.

## Log a call, meeting, or note

<Steps>
  <Step title="Open the contact">
    Open the contact. **History** is on the left.
  </Step>

  <Step title="Start the entry">
    Select **Log a call, meeting or note**.
  </Step>

  <Step title="Pick the kind">
    Select **Note**, **Call**, **Meeting**, **Message**, **Intro**, **Purchase**, or **Research**. For a call, a meeting, or a message, select **We reached them** or **They reached us**. For an intro, select **We introduced them** or **They introduced us**. For a purchase, select **We bought from them** or **They bought from us**.
  </Step>

  <Step title="Write one line">
    In "What happened, in one line", type the summary. For a company, you can pick the person, or keep **Whole company**.
  </Step>

  <Step title="Save">
    Select **Log**.
  </Step>
</Steps>

The entry shows at the top of **History**. A logged call, meeting, message, intro, or purchase moves the lead like an email does: one from your side as a sent email, one from them as a reply. A note or research moves nothing.

## Mark a contact do not contact

<Steps>
  <Step title="Open the contact">
    Open the contact.
  </Step>

  <Step title="Start the mark">
    At the bottom of the page, select **Mark do not contact**.
  </Step>

  <Step title="Add the reason">
    Optionally, type what they said, for example "asked to stop".
  </Step>

  <Step title="Confirm">
    Select **Mark do not contact**.
  </Step>
</Steps>

The page then says "**Do not contact.** Your teammates won't email them." with "They said:" and the reason, and when it was marked, for example "Marked 2 days ago."

What the mark does:

* Squad refuses every email to the contact from a Squad inbox: a teammate's email, an email that you send with **New email**, an approved draft, and a scheduled send.
* Squad cancels the scheduled sends to the contact at once.
* Squad also refuses a teammate's email to the contact through a connected Gmail or Outlook. A Gmail draft or an Outlook draft sent as it stands, a reply to whoever wrote, or a recipient that is not a plain address is refused whenever anyone in your squad is marked, because Squad cannot see who it would reach.
* A mark on a company covers its people and every address on the company's domain.
* Email from the contact is still logged.
* Their deals and steps say **Do not contact** first, and a teammate never drafts a nudge to them.

Squad also marks a contact do not contact by itself when a teammate logs that they unsubscribed, when a teammate saves one of their addresses as unsubscribed, or when they mark your squad's email as spam.

When a teammate tries to email a marked contact, Squad refuses the send and tells the teammate: "This contact asked not to be contacted:" followed by the address, the name, and the reason, then "Remove the address. Do not reach them another way." When you send or approve an email to a marked contact yourself, the send fails. Open the contact to check for the mark.

Your teammates are told not to reach a marked contact on any other channel either, such as a direct message on a network. This is an instruction. Squad enforces the mark only for email.

To remove the mark, select **Allow contact again**. A teammate cannot remove a mark that a person in your squad set. If the mark comes from a company (theirs, or the one that owns their email domain), the page says that the company "is marked do not contact" and shows **Open** with the company's name. Remove the mark there.

## Merge two contacts

Squad shows "This may be the same person as" (or "the same company as") another contact when two records may be one, and says why: the same account on a network, the same name and the same company, the same name with one at a personal address, the same name with nothing that tells them apart, an address that looks like the other's name, or handles a letter apart. **People** > **Review** lists every such pair. See [Review the list](#review-the-list).

<Steps>
  <Step title="Start the merge">
    On the contact that you want to keep, select **Merge into this one** next to the duplicate. Or select **Merge with another contact** at the bottom of the page, type a name, email, or handle, select **Find**, and pick the other contact.
  </Step>

  <Step title="Confirm">
    Read the question, then select **Merge**.
  </Step>
</Steps>

The other contact's emails, handles, tags, notes, research, projects, pipelines, deals, rules, and history move to the contact that you keep. So do its places on other deals and the steps it owes. What the kept contact lacks, such as a title or a website, comes from the other one. What a person in your squad set stays. Notes and research join the kept contact's when together they fit in one paragraph. Otherwise they go in the kept contact's history, in full. In a pipeline that both are in, the lead that is further along stays. A do-not-contact mark on either contact stays. A link to the merged contact opens the contact that you kept.

Right after the merge, the kept contact's page says who merged whom and when, with "You can undo this until" a date, and **Undo**. While Squad still moves the history, the page says so, and **Undo** waits. After the undo period, Squad deletes the merged record for good. The line about the merge stays in **History**. For the undo period, see [Limits and defaults](/docs/limits-and-defaults#contacts-and-pipelines).

The question before a merge says "This can’t be undone." Today a merge can be undone with **Undo** until the date that the page shows.

If two records are different people, select **Not the same** next to the duplicate. Squad does not offer the pair again.

You cannot merge a person with a company.

## Archive or delete a contact

At the bottom of the page:

* **Archive** takes the contact out of the lists, search, its projects, and its pipelines. Its history stays. Squad does not log new email on it. Archived contacts are under **People** > **Archived**. Open one and select **Restore from the archive**. With a filter on, **⋯** and **Restore all of them…** restores everyone it matches. A teammate can restore one too, and a teammate that saves an archived contact restores it.
* **Delete forever** asks first. For a person, it says "This deletes the contact, their emails, leads and timeline for good. Their company keeps its own history." For a company, it says "This deletes the company, its emails, leads and timeline for good. Its people keep what happened with them." When they have deals, it adds "The deal with them goes too." or how many deals go. Select **Delete forever** again to confirm, or **Keep it**. Their open steps on other deals are dropped, and a done step stays without their name. You cannot undo a delete.

## Your steps in Needs you and Today

Your own steps and follow-ups that are due today or late wait for you outside Contacts too. "Today" is your day on your computer's clock, so the list changes at midnight where you are. A step with no day is not due.

* **Needs you** lists them, earliest first, after the questions and the emails, as rows with **Done**, **Move the date**, and **Ask**. When more are due than it shows, select **Show all** and the number **steps of yours** to list them. When one more is due, the link says **Show 1 more step of yours**. See [Needs you](/docs/tickets).
* **Today** shows the first few at the end of its **Needs you** section, after the purchases. Its sentence says them apart, for example "and 2 of your steps in Contacts are due". When more are due than it shows, **See all** and the count opens **Needs you**. See [Today](/docs/today).
* The number on **Today** in the sidebar, and in the browser tab's title, counts each of them.

For how many each place lists, see [Limits and defaults](/docs/limits-and-defaults#contacts-and-pipelines). Everyone in your squad sees their own due steps. A Viewer cannot mark them done, move them, or ask for help with them.

## Who can do what

| Role | What they can do in Contacts |
| - | - |
| Owner, Administrator | See, add, change, merge, archive, and delete contacts, deals, steps, and pipelines, and export a spreadsheet. See and set a deal's money, and see the money tiles and the totals. |
| Collaborator | See, add, change, merge, archive, and delete contacts, deals, steps, and pipelines, and export a spreadsheet. Deals show how sure the money is, for example "Signed", without the amount. |
| Viewer | See contacts, deals, and pipelines, without amounts, and export a spreadsheet. Change nothing. |

Everyone in your squad sees every contact, deal, and pipeline. A person who can see only some teammates does not see the in-touch line, "Last in touch", the **Quiet for** filter, the deals gone quiet, or the timeline entries of teammates hidden from them. They cannot give a step or a deal to those teammates. See [Invite people to your squad](/docs/teammates).

A teammate that works for a Viewer can read, count, and export contacts and read deals, but it cannot save or change them. A teammate sees a deal's amount only when it works for the owner or an Administrator.

## What your teammates do with contacts

Your teammates find contacts with filters that combine and count them exactly, read a contact or a deal in full, add and update contacts, log what happened on any channel, import a list with past events, change many contacts at once after a dry run, export a spreadsheet, merge duplicates and undo a merge, and set up pipelines with goals, dates, and rules. They keep a deal for each client: its steps, documents, decisions with what was turned down, and where it stands. They add the people that the work brings in without being asked. They do not keep passwords, card numbers, or health details on a contact. See [What teammates can do](/docs/agent-capabilities#contacts-and-pipelines).

```text Ask your chief of staff theme={null}
Open a deal for the Rivera practice: onboard them by November 1, from the New client playbook. Juno looks after it.
```

```text Ask your chief of staff theme={null}
Find 20 new leads for Brand outreach: food creators in Austin with 10k to 100k followers. Add them to the pipeline and draft a first email for my review.
```

```text Ask your chief of staff theme={null}
Which deals have gone quiet? Draft a short check-in for each one for my review.
```

The **Contacts** file on the **Memory** screen is a different thing. It holds standing facts that every teammate should know. The Contacts screen holds the records of the people and companies your squad works with. See [Memory](/docs/memory).

## On Squad for Mac (private beta)

**Contacts** in Squad for Mac (private beta) has the same tabs, deals, steps, pipelines, people, **Review**, and roles as the web, with these differences. For the numbers, see [Limits and defaults](/docs/limits-and-defaults#squad-for-mac).

* **Open it.** **Contacts** is also in the **Go** menu.
* **Search.** Type in **Search people and companies**, or press ⌘F to go there. The search starts after a few characters.
* **Add someone** is next to the search on every tab. Pick **A person** or **A company**, and type the **Name**. For a person, you can add the **Email**, **Works at**, and **Title**. For a company, you can add the **Website**. There is no pipeline menu. On a pipeline's page, **Add to** and the pipeline's name puts them in that pipeline. It starts checked, and you can clear it. Select **Add**. A Viewer does not see **Add someone**.
* **Home.** **Since you last looked** counts from your last visit to **Home** on this Mac. In a narrow window, **Pipelines**, **This week**, and **Since you last looked** go under the rest.
* **A step's menu.** On **Today**, in **Needs you**, and on the cards of **Home**, right-click a step, or press its letter while you point at it or Tab is on it: **Done** (D), **Move the date…** (M), **Ask** and your chief of staff's name **to do it** (A), and **Open the deal** or **Open** and the person's name (O). Pointing at a row shows **Done** and **Move the date**. A Viewer has only **Open**. In **Move the date…**, you can pick any day, also one that has passed.
* **Deals.** The choice is **By whose move** or **List**. The columns sit side by side when there is room, and one under another when there is not.
* **A deal.** A step has a **⋯** menu ("More for this step") instead of buttons that show when you point at it. Its letters work while you point at it or Tab is on it: **Done** or **Kept** (D), **Missed** or **Broken** (M), **Move the date…** (L), and **Drop it** (X). In a narrow window, **Promises**, **Decided**, **Documents**, and **People** go under the history. When you close a deal, the sheet says "Its open steps stop, and their tasks are set aside. You can open it again." Type **Why, in a sentence**, and select **Close as won**, **Close as lost**, or **Close as dropped** instead of **Close it**.
* **A pipeline.** To move someone, use the **⋯** on their card or right-click it, and choose a stage under **Move to**. You cannot create a pipeline, or change its stages and fields, on the Mac. Use the web dashboard, or ask a teammate.
* **People.** The button to narrow the list is **Filter**. To tag the people that you picked, select **Tag**, type it, and select **Add the tag**. After **Count them**, **Count again** counts once more. **Export as a spreadsheet** opens the file in your browser, which downloads it. In **Review**, press S for **Same person** and N for **Not the same** on the pair that you point at.
* **A person's page.** **Projects and tags** is one card. A company lists **People at** and its name. **What your teammates found** sits with **Notes**. The main address says **Emails go here**, and an address's **⋯** menu has **Send emails here** and **Remove**.
* **Follow-ups.** On a pipeline's card, select **Set a follow-up** or **Change**. Pick the day in **Follow up on**, type the next step in "What's next, in one line", and select **Save**. **Clear the follow-up** removes it. The stage on the card is a menu that moves them, with **Remove from** and the pipeline's name at the end.
* **Log something.** Under **History**, select **Log something**. Pick the kind and which way it went, type what happened in one line, and select **Log it**. On a company, you cannot pick one of its people. A long entry shows its first lines with **Read it all**, which opens the whole entry with **Copy**. **Show earlier** shows older entries.
* **The ⋯ menu on a person's page.** **Edit details…** changes the name, the website or the workplace and title, and **Who they are** (**What they do** for a company). **Do not contact…** asks "Don't contact" and the name, with **Why (optional)**, then **Don't contact**. **Allow contact again** shows when the contact carries its own mark. **Archive** or **Restore**. **Delete…** asks "Delete" and the name, and you confirm with **Delete** and the name **and their history**. On the web, these are buttons at the bottom of the page, and the web has no **Edit details…**.
* **Merge.** A possible duplicate shows **Open**, **Same**, and **Not the same**. **Same** asks "Merge" and the name "into this record?". Select **Merge**. The Mac has no search to merge with any other contact.
* **Your steps elsewhere on the Mac.** Your due steps count in the sidebar, the Dock icon, the menu bar, and the notch, as everything in **Needs you** does, and Siri says them. The menu bar adds a link, for example **Look at your 2 steps that are due**. While **Show all** loads the rest in **Needs you**, it says "Loading the rest of your steps." See [Answer what needs you](/docs/tickets) and [The notch and the menu bar](/docs/mac/notch-and-menu-bar).

## Troubleshooting

**A contact that you added opened as an older contact.** Cause: Squad already had a contact with that email, or a company with that domain. Squad updated it instead of adding a second one. Fix: nothing. Check the details on the contact that opened.

**A teammate says that a contact asked not to be contacted, or an email to someone does not send.** Cause: the person, their company, or the company that owns their email's domain is marked do not contact. Fix: remove the address. Only select **Allow contact again** if the person asked to hear from you again.

**An email did not show on a contact.** Cause: the email went through another app, for example Gmail, not through a Squad inbox. Or it was spam, or the contact is archived. Fix: restore the contact, or ask a teammate to log it.

**A deal shows no amount.** Cause: only the owner and Administrators see a deal's money. Fix: ask the owner or an Administrator.

**A column on Deals shows no total.** Cause: totals show only to the owner and Administrators, only when every deal of the column is on screen, and only for money in your squad's currency. Fix: open **List**, or ask a teammate for the total.

**A teammate's step has no task yet.** Cause: its day has not come, it waits for the step before it (a missed or dropped step keeps it waiting), your subscription is paused or canceled, or the person the work is for cannot use that teammate. Fix: move the date, finish the step it waits on, or give the step to another owner.

**No nudge was drafted for their late step.** Cause: no teammate looks after the deal, the step has no day, the person is marked do not contact, your subscription is paused or canceled, or the person the work is for cannot use that teammate. Fix: ask a teammate to look after the deal, or give the step a day.

**Open it again is missing on a closed deal.** Cause: an open step belongs to a teammate that you cannot see. Fix: ask the owner or an Administrator.

**Two contacts were merged by mistake.** Cause: a merge joins two records. Fix: select **Undo** on the kept contact's page, or ask a teammate to undo it, before the date that the page shows.

**The download link of an export does not show.** Cause: the line of a finished change to many records still shows at the top of **People**, and it hides the export's line. Fix: select **OK** on that line, then export again.

| Message | Cause | Fix |
| - | - | - |
| "A contact needs a name." | **Name** is empty in **Add a contact**. | Type a name. |
| "\[domain] already belongs to the company \[name]." | Another company has this domain. | Open that company, or merge the two companies. |
| "A pipeline named "\[name]" already exists." | Pipeline names must be different, archived pipelines included. | Pick another name. |
| "A workspace can have at most 50 pipelines." | Your squad has as many pipelines as it can hold, archived ones included. | Reuse a pipeline that you no longer need: rename it and change its stages in **Settings**. |
| "\[n] leads are in the stage "\[stage]". Move them to another stage before you remove it." | The stage still has leads. | Move the leads, then remove the stage. |
| "A pipeline needs at least one open stage." | Every stage means Won, Lost, or Closed. | Set one stage to **Open**. |
| "Two stages use the key "\[key]"." | Two stages have the same name, for example two **New stage** rows from **Add a stage**. Fields say "Two fields use the key". | Give each stage, or field, its own name. |
| "The select field "\[name]" needs its options." | A **Choice** field has no choices. | Type the choices, separated by commas. |
| "The pipeline "\[name]" is archived." | Someone archived the pipeline while you worked in it. | Ask a teammate to restore the pipeline. |
| "A person and a company can't be merged." | The two contacts are of different kinds. | Merge only two people or two companies. |
| "Each company has its own domain (\[a], \[b]), and a company keeps one. Clear one of them first." | Both companies have a domain. | Remove one domain, then merge. |
| "Together they have more than \[n] emails. Remove some first." (or tags, or channels), "Together they are in more than \[n] projects.", or "Together they have more than \[n] rules. Take some off one of them first." | The two contacts together hold more than one contact can. | Remove some from one of them, then merge. |
| "This merge is still moving its history. Try again in a minute." | Squad is still moving the merged contact's history. | Wait a minute, then select **Undo** again. |
| "A merge can be undone for 30 days, and this one is older." | The undo period has passed. | Fix the records by hand. |
| "More than one contact is named \[name]. Add their email to say which one." | **With** matches several contacts and **Their email** is empty. | Type their email. |
| "Money needs its currency as three letters (USD, EUR, GBP)." | **Currency** is not three letters. | Type a three-letter code. |
| "Only the owner and Administrators set a deal's money." | A teammate tried to set money while it works for someone who is not the owner or an Administrator. | Ask the owner or an Administrator. |
| "That teammate is not in this squad." | You picked a teammate that your access does not include, or the playbook gives a step to one. | Pick another teammate or playbook. |
| "A deal can have at most 200 steps." | The deal has the most steps it can hold. | Close the deal and open a new one for the next stretch of work. |
| "More than \[n] records match, too many to count before changing them. Narrow the filter to change them." | The filter matches too many records. | Add a tag or a pipeline to the filter. |
| "Couldn't make the spreadsheet. This filter reads more records than one spreadsheet can. Narrow it, by a tag or a pipeline, and try again." | The filter matches too many records. | Narrow the filter. |
| "This pipeline no longer exists." | Someone archived the pipeline, or the link is wrong. | Select **See the pipelines**. |
| "This deal isn't here anymore." | Someone deleted the deal, or the link is wrong. | Select **Back to** and the tab's name. |
| "This contact isn't here anymore." | Someone deleted the contact, or merged it and the undo period has passed, or the link is wrong. | Select **Back to** and the tab's name. |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.