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

> ## Agent Instructions
> Usertick runs surveys on websites, by link, by QR code and by email, and collects every response in one inbox with reports, dashboards and workflows. The REST API lives at https://app.usertick.com/api/public/v1 and uses Bearer API keys or OAuth access tokens; the JavaScript SDK is the @usertick/snippet package on npm.

# Follow sends

> See every survey email your organization sent or scheduled, check who received and answered each send, and cancel, retry or send again.

Every survey email your organization sent or scheduled appears in **Email → All sends**, and selecting a send opens its page with each recipient's result.

## Find a send

The menu on the left has three views:

* **All sends** lists scheduled sends under **Coming up**, followed by every send that went out under **Sent**.
* **Scheduled** shows the sends set to go out later.
* **Needs attention** → **Had failed emails** collects sends from the last 30 days that stopped or had failed messages.

Each row shows **When**, **Survey**, **To**, **Delivered**, **Answered** and **Status**. Search finds a send by its survey, subject or list, **Filters** → **Survey** narrows the list to one survey's sends, and **Sort** puts them in order by **When**, **Survey**, **Recipients** or **Answered**.

The search box also accepts `is:scheduled`, `is:failed` and `survey:"Q3 NPS"`. Put a survey name that contains spaces in quotes, and press <kbd>Enter</kbd> to apply the filters.

## Send statuses

| Status | Meaning |
| - | - |
| **Scheduled** | The send is waiting for its time. |
| **Sending** | Emails are going out, and the page updates while the send runs. |
| **Delivered** | The send finished with no failed messages. |
| **Some failed** | The send finished, but some messages failed. |
| **Stopped** | The send stopped after failed messages in a row, or stopped early for a reason the send's page names. |
| **Couldn't start** | Nothing was sent. Check that the sender is set up, then send again. |
| **Canceled** | The send was canceled before anyone received it. |

## Read a send's page

The top line gives the result, when the send went out, the survey, who it was for and the subject. Below it, the page shows the details of the send:

* The numbers row shows **Recipients**, **Delivered**, **Failed**, **Skipped** and, after something is delivered, **Answered** with its share of the delivered emails. **Delivered** notes how many bounced or were marked as spam, and **Skipped** notes why people were skipped.
* **Why it failed** groups the failed messages by cause, such as a mailbox that doesn't exist or rejected sender credentials, and says what to do about each one.
* **Recipients** lists every person with their result. You can search it by address, narrow it with **Filters** → **Status** to **Delivered**, **Failed** or **Skipped**, each with its count, and order it with **Sort** by **Time**, **Email** or **Status**. The search also accepts `is:delivered`, `is:failed` and `is:skipped`.

Selecting a recipient who is still in your contacts opens the contact beside the send. A deleted contact appears as **Deleted contact**, and the send keeps its counts.

Usertick skips a person when they unsubscribed or already received the survey, when their address is suppressed after a hard bounce or a spam report, when the month's Usertick emails ran out, when sending was paused, or when the survey closed during the send.

## When a send stops early

When a send stops early, a note on its page says why and links to the fix:

| Why it stopped | Links |
| - | - |
| The organization ran out of Usertick emails | **Buy extra emails** and **See plans** (with **Manage billing**), **Open Sender** |
| Usertick sending was paused | **Check sender settings** |
| A list it was for was deleted before it went out. Nobody received it. | **Open contacts** |
| The survey stopped taking responses: it was paused, archived or suspended, it reached a response limit, or the organization was deactivated | **Open survey** |

Nothing changes for people who were already emailed, and skipped people use none of your emails. Because a stopped send doesn't resume, fix the cause and create a new send to reach the rest.

## Act on a send

You can take these actions from a send's page, and **Cancel send** also appears on a scheduled send's row.

* **Cancel send** stops a scheduled send before it goes out, and the send stays in the history as **Canceled**. Before it cancels, the question shows the survey, the subject, the recipients and the scheduled time, and **Keep it scheduled** leaves the send as it is.
* **Retry failed** opens **Retry failed emails** with the people whose messages failed, up to 5,000 at a time. To reach the rest, retry again.
* **Send again** opens the window with the same recipients and with **Skip people who already received this survey** turned off.

## Responses from a send

Responses arrive in the [inbox](https://docs.usertick.com/results/inbox.md) together with those from every other channel, each linked to the contact the email went to. Each contact's panel lists the emails they received and their answers. See [Contacts and lists](https://docs.usertick.com/email/contacts.md#open-a-contact).

## Notices in the Email area

* When the Reply-To person for Usertick sending leaves the organization, Usertick stops sending survey emails and a notice appears on **All sends**. Scheduled sends fail until someone else is chosen, and for members with **Manage organization**, **Choose a Reply-To person** opens **Sender**.
* The sender line at the bottom of the menu shows how many Usertick emails are left this month. When the sender can't send, the line shows the reason instead: **Not set up**, **Paused**, **Waiting for a test email** or **Reply-To person left**.

## Who can do this

Seeing sends requires the **View surveys and results** permission, and **Cancel send**, **Retry failed**, **Send again** and **New send** require **Send email surveys**. To read sends from your own code, see the [Email sends API](https://docs.usertick.com/developers/api/email-sends.md).


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