> 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/run-your-studio/automated-emails.md).

# Automated emails

How emails reach your accounts, how to check they arrived, and what to do when they didn't.

Schedulink sends emails to your accounts on your behalf: booking confirmations, roster requests, reminders, follow-ups. You set them up once on an event template and they go out on schedule for every job of that type.

This page is about emails on live jobs. For writing them, see Email templates.

## Who an email goes to

Emails are aimed at **contact roles**, not at named people. When one is due, Schedulink looks for everyone holding that role and sends to all of them.

Two things about roles solve most questions about recipients.

### The roles are yours to create

There's no fixed list. Go to **Setup > Preferences**, find the **Contact Roles** section, and add whatever you need. The new role appears immediately on every contact, ready to assign.

So if you want a role that means something specific to your studio, make one. There's no limit.

### An email can target several roles at once

When you attach an email to an event template, you can aim it at more than one role rather than duplicating the template. Anyone holding any of those roles receives it.

## Where Schedulink looks for those people

Every contact belongs to an account. You can also add contacts to a **particular event**, choosing from the people on that account, and that's what lets one job go to a different person from another.

When an email is due, Schedulink checks the event first:

**If anyone added to the event holds the role, it goes to them and nobody else.** The account is ignored.

**If nobody added to the event holds the role**, what happens next depends on a studio-wide setting in **Setup > Organization**.

| Setting                      | What happens when the event has no matching contact                              |
| ---------------------------- | -------------------------------------------------------------------------------- |
| If no recipient in the event | Falls back to the account and sends to **everyone there** holding the role       |
| Always                       | Sends to everyone holding the role on both the event and the account, every time |
| Never                        | Sends nothing                                                                    |

Most studios want the first one.

{% hint style="warning" %}
**The fallback sends to everyone on the account with that role, not to one person.**

Say a school has three contacts holding Data: the office manager and two coaches, each added to their own team's event. A fourth team gets booked and nobody is added to it. That email doesn't reach just the office manager, it reaches all three, because all three hold Data at account level.

The fallback is a safety net for jobs where nobody was added, not a way to route mail. If you need a particular person on a particular job, add them to that event.
{% endhint %}

### Adding a contact to an event

Open the event and go to its Contacts section. You're choosing from the people already on the account, and adding them here tells Schedulink they're the ones for this job.

Worth doing whenever a client has several people who each look after a different job, like a school with a coach per team.

The reliable pattern is to add a contact to every event, including the ones handled by a general office contact. Then the fallback never fires and each email goes to exactly one person.

## The five most studios automate

If you're deciding what to set up, this is the sequence that covers a picture day end to end.

**Booking confirmation**, the day the job is confirmed. Date, time, contacts, what to expect. Without it you're answering "when is this happening again?" three weeks later.

**Roster request**, weeks before the shoot, with a form attached. Without it you're chasing the office the week of the shoot.

**Shoot day reminder**, a couple of days before. Time, location, anything specific. Without it you get "wait, you're coming today?" on the morning.

**Day-after follow-up**, asking how it went and what happens next. Catching a problem early means it doesn't repeat at the next school.

**Images ready**, the moment galleries are done, so nobody is left guessing and parents stop calling.

## Seeing what's scheduled

Open an event and go to its Emails section. Every email the template scheduled is listed with its send date.

Click **Preview** to see the message as the recipient will get it, with the account name, dates and custom fields already filled in. Worth doing on your first job of a new template, because a placeholder that didn't resolve is obvious here and invisible later.

You can also send yourself a test first.

## Sending one by hand

You don't have to wait for the schedule. Open the event, find the email, and send it. That's what you'll do when an account asks for the details again, or when something changed after the automatic send went out.

A manual send isn't limited to the contacts added to that job. The contact selection field lists **every contact on the account**, so you can include someone for a one-off without editing the event first.

That's the difference between manual and automatic sends worth holding on to. Automatic sends go to roles, and where Schedulink looks for them is the Organization setting above. A manual send is you choosing names.

Emails are still sent per event, though. There's no bulk send across several accounts at once.

## Checking whether it arrived

Click an email after it's gone and you'll see every contact it was addressed to, whether it was **sent**, and whether it was **delivered**.

Those mean different things. Sent means Schedulink handed it over. Delivered means their mail server accepted it. An email that shows delivered but hasn't been seen is usually in a junk folder, and the fix is asking them to add your address to their safe senders.

## When an email didn't go out

See Why didn't my email send? for the full list. The two most common are an event still sitting in Planning, and nobody at the account holding the role the email is looking for.

## Stopping an email that's already scheduled

There's no way to cancel a single scheduled email. If a job isn't going ahead, set the event to **Cancelled**, which stops everything still due to send.

So if you've booked a job speculatively, leaving it in Planning until it's confirmed is safer than scheduling it and hoping to intervene later.

## Turning off emails to your own team

The emails Schedulink sends *you* about tasks and events are separate from all of this, and everyone controls their own under **My Profile**. See Finding your way around.


---

# 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/run-your-studio/automated-emails.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.
