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

# Send history and deliverability

> Review past campaigns, delivered and failed counts, how bounces and unsubscribes are handled.

The **Send History** tab on [Program Dashboard → Contacts](https://firstrespondershub.com/program-dashboard/contacts?tab=sends) lists every contacts email campaign your organization has sent, newest first.

## What you see per send

| Field              | Meaning                                                                                                    |
| ------------------ | ---------------------------------------------------------------------------------------------------------- |
| **Subject**        | The subject line of the email.                                                                             |
| **Audience label** | Human-readable description of the audience — e.g. "EMT interested contacts" or "Custom list: Alumni 2024". |
| **Sent date**      | When the send was queued.                                                                                  |
| **Recipients**     | Number of eligible contacts at queue time (after unsubscribe/bounce exclusion).                            |
| **Delivered**      | Count of successful deliveries reported by the email provider.                                             |
| **Failed**         | Count of failures (provider error, invalid address, hard bounce). Shown only when > 0.                     |
| **Status**         | `Sending` while the background job is running; `Sent` when complete; `Failed` if the job errored.          |

## What "Delivered" actually means

A send is counted as **delivered** when the email provider accepts the message for delivery and reports `email.sent` or `email.delivered` on its webhook. It is **not** a confirmation that the recipient opened or read the email — open tracking is intentionally not included.

## What "Failed" covers

A recipient counts as failed if any of the following happens:

* The provider rejects the address (`email.failed`)
* The message hard-bounces (bad mailbox, closed domain)
* The provider rate-limits us and retry attempts exhaust

Hard bounces automatically set the contact's email status to `Bounced`, which excludes them from all future sends.

## Unsubscribes

Every email contains a per-recipient unsubscribe link. When a recipient clicks:

1. They land on the public [unsubscribe page](/contacts/unsubscribe-and-compliance).
2. Their contact's email status flips to `Unsubscribed`.
3. They are excluded from every future send from your organization.

Unsubscribe events are not shown in Send History line items (they happen after the send), but the contact's status updates in **All Contacts** and the status-filter counts.

## Resending to the same audience

You can re-send to the same custom list or audience — the send history is additive and does not block you. Be aware:

* Unsubscribed and bounced contacts from past sends will be automatically excluded from the new send's recipient count.
* The recipient count you see in the composer is the **current** eligible count, which may be lower than a previous send to the same audience.

## Troubleshooting a failed send

If an entire campaign shows status `Failed`, common causes are:

* **Missing organization address** — Organizations must have a street/city/state/zip set for the CAN-SPAM footer to render. Add it in organization settings and re-send.
* **Missing connected `from` email** — The platform sends from `team@firstrespondershub.com` by default. If this is failing repeatedly, contact support.
* **Quota exhausted mid-send** — If you hit the monthly quota while the job is running, remaining recipients are skipped. Upgrade and send to the remaining list.

For individual failed recipients within an otherwise successful send, no action is required — the platform automatically updates their status (bounced) if warranted.