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

# Before you launch: a checklist

> Ten checks to run before a campaign sends its first email: the mailbox, the list, the message, and what to watch after launch.

A launch cannot be taken back: once an email is out, it is out. These checks take a few minutes, and each one catches a mistake that is common and costly. None of them is charged. The test email uses one of the mailbox's emails for the day.

## The mailbox

**1. It is connected, active and has a sender name**

List your mailboxes with `GET /v1/accounts?channel=email`. The one you send from needs `isConnected` and `isActive` both true. Give it a `name` too: it is the sender name your recipients see.

**2. A new mailbox sends less**

`dailyCapacity` is the most emails a mailbox sends a day, from 1 to 15. A new mailbox starts at 15. Start one under 3 months old at 5:

```bash theme={null}
curl -X PATCH https://api.outbound.dev/v1/accounts/email/maya@fernway.co \
  -H "Authorization: Bearer $OUTBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"dailyCapacity": 5}'
```

A mailbox sends 15 emails a day at most, so a campaign that sends more needs more mailboxes. See [Set its daily capacity and signature](https://docs.outbound.dev/guides/connect-sending-accounts.md#set-its-daily-capacity-and-signature).

**3. It is warming up**

Warmup exchanges emails between your mailbox and others, so that mail providers come to trust it. It is free. Start it with `POST /v1/accounts/email/{accountId}/warmup`, then read the mailbox's `warmup`: its `status`, where the last 7 days of warmup emails landed, and `dnsGrade`, a grade for the domain's mail setup. See [Warm a mailbox up](https://docs.outbound.dev/guides/connect-sending-accounts.md#warm-a-mailbox-up).

**4. It has a signature**

`{Sender Signature}` in a step is filled in with the mailbox's `signature`. Set it with the same `PATCH` call, as HTML.

## The list

**1. The people can be reached**

[Readiness](https://docs.outbound.dev/guides/run-campaigns.md#check-it-is-ready) counts the people on the campaign's lists, with and without a work email:

```bash theme={null}
curl https://api.outbound.dev/v1/campaigns/6a1f0c2b9d4e8a7f3c5b2e30/readiness \
  -H "Authorization: Bearer $OUTBOUND_API_KEY"
```

```json theme={null}
{ "ready": true, "people": { "total": 42, "withEmail": 30, "withoutEmail": 12, "withLinkedin": 40 } }
```

An email-only campaign skips the people without an email. If `withoutEmail` is high, [enrich the list](https://docs.outbound.dev/guides/enrich-people.md#enrich-a-list) first.

**2. The people you must not write to are left out**

Put your customers, your competitors and anyone else campaigns should never write to on a list, and exclude it from every campaign with `POST /v1/exclusions`. Do it before you launch: an exclusion works when people are enrolled, and does not stop anyone already in a campaign. See [Exclusions](https://docs.outbound.dev/guides/run-campaigns.md#exclusions).

A campaign can also skip people your campaigns already wrote to, with `excludeContacted`, and people who replied to one, with `excludeEngagedContacts`.

## The message

**1. Every variable is filled in**

Variable names are exact. `{Contact First Name}` is a variable. `{First Name}` is not, and goes out as written, braces and all. Preview each step, and read the result for anything still in braces:

```bash theme={null}
curl -X POST https://api.outbound.dev/v1/campaigns/6a1f0c2b9d4e8a7f3c5b2e30/steps/6a1f0c2b9d4e8a7f3c5b2e31/preview \
  -H "Authorization: Bearer $OUTBOUND_API_KEY"
```

A preview writes the step for the first person on the campaign's lists. Nothing is saved or sent. See [Template variables](https://docs.outbound.dev/guides/run-campaigns.md#template-variables).

**2. A test email looks right in a real inbox**

Send the first step to yourself:

```bash theme={null}
curl https://api.outbound.dev/v1/campaigns/6a1f0c2b9d4e8a7f3c5b2e30/steps/6a1f0c2b9d4e8a7f3c5b2e31/test-email \
  -H "Authorization: Bearer $OUTBOUND_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"toEmail": "maya@fernway.co"}'
```

It is a real email and goes at once, from your first active mailbox. Check the subject, the sender name, the signature and how it reads on a phone. A test email carries no unsubscribe link and no tracking.

**3. The unsubscribe link stays on**

Every campaign email ends with a one-click unsubscribe link unless the campaign has `"addUnsubscribeLink": false`. Leave it on. A send to someone who unsubscribed is refused. See [Unsubscribes](https://docs.outbound.dev/guides/run-campaigns.md#unsubscribes).

**4. Tracked links use your own domain**

With click tracking on, links in your emails go through a link address. A [tracking domain](https://docs.outbound.dev/guides/run-campaigns.md#tracking-domain) makes that address a hostname of your own, so people see your domain when they hover a link. Set it up before launch: it needs one DNS record, and usually becomes active within half an hour of the record being found.

## Start small

* **Cap the first days.** `dailyEmailLimit` is the most emails the campaign sends a day. Set it low for the first days, then raise it with `PATCH /v1/campaigns/{campaignId}`.
* **Send in working hours.** A campaign sends from 9:00 to 17:00 in its `timezone`, on its `emailDays`. Set `timezone` to where your recipients are. Left out, it is UTC.
* **Launch once.** Send the launch with an [`Idempotency-Key`](https://docs.outbound.dev/idempotency), so a retry cannot start it twice.

## After you launch

* **Read the queue.** `GET /v1/campaigns/{campaignId}/queue?status=scheduled` lists the messages waiting to go out, each with the text it will send. See [Work the send queue](https://docs.outbound.dev/guides/run-campaigns.md#work-the-send-queue).
* **Pause if something is wrong.** `POST /v1/campaigns/{campaignId}/pause` stops the campaign sending, and its queued messages wait. Launch it again to carry on.
* **Read the results.** `GET /v1/campaigns/{campaignId}/stats` counts the messages sent, the opens, the clicks and the replies. See [Read the results](https://docs.outbound.dev/guides/run-campaigns.md#read-the-results).


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