> For the complete documentation index, see [llms.txt](https://schedulink.io/help-center/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://schedulink.io/help-center/when-somethings-wrong/why-didnt-my-email-send.md).

# Why didn't my email send?

An account says they never got it. Five causes, in the order worth checking.

An account tells you they never received the confirmation, or you look at a job and an email that should have gone out hasn't.

Almost every cause here is silent. Nothing errors, nothing warns you, the email simply doesn't go. So work down the list rather than guessing.

## 1. The event is still in Planning

Check this first. It's the most common cause and the quickest to fix.

**No automated emails send while an event is in Planning.** That's deliberate, so a job you're still negotiating doesn't start emailing the school, but it catches people who booked a date weeks ago and never moved the status on.

Open the event and look at its status. Move it to **Scheduled** and the automation starts.

## 2. Nobody at the account holds the role

Emails go to contact **roles**, not to named people. When an email is due, Schedulink looks for everyone holding the role that email was set up for, and sends to them.

If nobody holds that role, there's nobody to send to. No error, no warning, no email.

Open the account, look at its contacts, and check somebody actually has the role in question. A contact can hold several, so adding one to an existing person is usually enough.

This is also why a school with only one contact often stops receiving some emails but not others.

## 3. The fallback is switched off

Schedulink can look at the event's own contacts and then fall back to the account's, but that behaviour is a studio-wide setting.

In **Setup > Organization**, look at how event email recipients are found:

**If no recipient in the event** checks the event first, then falls back to the account. This is what most studios want, and what we recommend.

**Always** pulls from both every time.

**Never** looks only at the event. If nobody was attached to that particular job, the email doesn't send. Set to Never, this is often the real cause when everything else looks correct.

## 4. It sent, but it didn't arrive

Open the event, go to its Emails section, and click the email. You'll see every contact it was addressed to, whether it was **sent**, and whether it was **delivered**.

Those are different. Sent means Schedulink handed it over. Delivered means their mail server accepted it.

**Delivered but not seen** is almost always a junk folder. Ask them to check, and to add your studio's sending address to their safe senders so it doesn't happen again.

**Sent but not delivered** means the address bounced. Check it for typos, and check the person still works there.

## 5. The email was never on the job

If the emails section doesn't list it at all, it was never scheduled.

That happens when the job was created from an event template that doesn't include that email, which is easy to do when you have several templates and picked the wrong one at booking.

You can add the email to that job by hand from the Emails section, and add it to the event template so future jobs get it.

## Sending it now

Whatever the cause, you don't have to wait for a fix to reach the account. Open the event, find the email, and send it. That works whether or not the original send failed.

## Still not going?

Get in touch with the account name, the event name and which email it is, and we'll look at the send log.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://schedulink.io/help-center/when-somethings-wrong/why-didnt-my-email-send.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
