# Bulk Communications

Source: https://docs.astalty.com.au/guide/communications/bulk-communications

> Email every Participant with supports in a date range a PDF of their schedule, in one send.

Scheduling add-on - This feature requires the Scheduling add-on, which is available on Astalty Premium. See How to enable Scheduling.

> **Beta feature enabled by Astalty**
>
> Bulk Communications is in beta and is switched on per account. Email <support@astalty.com.au> to enable it.

Bulk Communications emails every Participant with supports in a date range a PDF of their schedule, in a single send. **Send Schedule** is the only type available today.

> **Sending one Participant's schedule instead?**
>
> To email a single Participant's schedule with control over cancelled supports and its own Email
> Log, use **Actions > Email Supports as PDF** on their Supports page. See
> [Viewing a Participant's Schedule](https://docs.astalty.com.au/guide/scheduling/viewing-a-participants-schedule#emailing-a-participants-support-schedule).

## Before You Start

- The **Admin** role, or the **Manager** role with **Can access Scheduling** turned on for you. It is off for Managers by default. See [Updating Roles and Permissions](https://docs.astalty.com.au/guide/roles-and-permissions).
- There is no approval step. Anyone who can open **Send Schedule** can send.

## Where to Find It

Select **Communications** from the left-hand menu (under **Manage** when your menu is grouped into sections). **Create a Bulk Communication** lists each type you can send; select **Send Schedule**. Past sends sit below under **Recent Bulk Communications**.

![The Communications page, with an arrow from Communications in the left-hand menu to Send Schedule, highlighted in the Create a Bulk Communication table, and three past sends listed under Recent Bulk Communications.](https://docs.astalty.com.au/assets/bulk-communications-landing.png)

## Choosing the Date Range

Set **Date** to the period the schedules should cover. It opens on the current week. Pick dates on the calendar, or use **Last**, **This** or **Next**, then **Week**, **Fortnight**, **Month**, **Quarter** or **Year**. A range cannot span more than 365 days.

**Include Unpublished Supports** is **No** by default, so only [published](https://docs.astalty.com.au/guide/scheduling/published-and-unpublished-shifts) supports count. Set it to **Yes** to include unpublished ones. A Participant whose only supports in the range are unpublished does not appear until you do.

Changing either setting clears your selection and rebuilds the list.

## Choosing Participants and Recipients

Every Participant with at least one support starting in the range is listed with a **Supports** count and their available **Recipients**. Astalty preselects rows that have a default recipient. Select any remaining rows and choose at least one recipient before sending. Use the search box to find someone, the header tick box to select or clear everyone, and the eye icon to **Preview schedule PDF** for one Participant.

![The Send Schedule page with a date range of 26 Oct to 1 Nov 2026, Include Unpublished Supports set to No, 45 email addresses, 32 participants selected, and an arrow pointing to the highlighted Send to 32 participants button.](https://docs.astalty.com.au/assets/bulk-communications-send-schedule-participants.png)

Recipients are the Participant and any of their Contacts with an email address recorded, each shown with their relationship. Archived Contacts aren't offered, and an email address shared by two people is listed once. Support Workers and other staff are never included.

Astalty preselects recipients per Participant:

1. The Participant's [support reminder recipients](https://docs.astalty.com.au/guide/settings/sms-reminders#nominating-contacts-to-receive-reminders), if reminders are set up for them.
2. Otherwise the Contact whose relationship is **Primary Contact**.
3. Otherwise the Participant.

Change any of these from the **Recipients** dropdown on that row.

> **A Participant with no email addresses can't be selected**
>
> If neither the Participant nor any of their Contacts has an email address, the row reads
> **No email addresses** and its tick box is disabled. Add an email address to the Participant or a
> Contact, then reload the page.

## Writing the Email

Select **Send to \[N] participants** to open the composer.

- **Subject** is prefilled as *"Support schedule for 7 Sep 2026 to 13 Sep 2026"* and can be edited. It holds 255 characters.
- **Message** is the body of the email. Each recipient also gets that Participant's schedule attached as a PDF.
- **Recipients** below recaps who is being emailed, per Participant.

### Placeholders

Use **Insert placeholder** above the Subject, or the **Participant**, **Business** and **Schedule** buttons under the Message toolbar, to drop in a value Astalty fills per Participant:

| Placeholder                    | Fills with                                                                                                                                                                                             |
| ------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `${Participant_FirstName}`     | The Participant's first name, or their preferred name when [Participant Name Display](https://docs.astalty.com.au/guide/settings/participants-settings#participant-name-display) shows preferred names |
| `${Participant_FullName}`      | The Participant's full name, or preferred and last name under the same setting                                                                                                                         |
| `${Participant_PreferredName}` | The Participant's preferred name, or their first name if none is recorded                                                                                                                              |
| `${Business_Name}`             | Your business name                                                                                                                                                                                     |
| `${Schedule_StartDate}`        | The first day of the range, as `8 Sep 2026`                                                                                                                                                            |
| `${Schedule_EndDate}`          | The last day of the range, as `8 Sep 2026`                                                                                                                                                             |

> **Placeholders always name the Participant, not the person reading the email**
>
> A Contact who receives the email sees the Participant's name in `${Participant_FirstName}`, not
> their own. Write *Please find attached the schedule for* `${Participant_FirstName}` rather than
> *Hi* `${Participant_FirstName}`, so it reads correctly for a parent or support coordinator.

## Sending

Select **Send**. Check the Participant and email address counts in the confirmation, then select **Send** again. Sending starts immediately.

Each email is sent from your business name, with **reply-to set to the email address of whoever pressed Send**, so replies come back to that person rather than a shared inbox.

> **A send cannot be scheduled, cancelled, retried or resent**
>
> Sending starts as soon as you confirm. There is no send-later option, no recurrence, and no way to
> stop a send once it is running. A recipient who fails or is skipped cannot be retried individually.
> Compose a new send for those Participants.

## Understanding the Results

**Send Schedule Results** opens as soon as the send starts, and lists every Participant with their recipients, status and a **PDF** link to the attachment they were sent. Expand a row to see each recipient's address and their own status.

![The Send Schedule Results page with an arrow pointing to the highlighted orange banner reading Sending finished. Not every recipient was emailed, 13 of 18 sent, 4 skipped, 1 failed, above a table of Participants with Failed and Successful statuses.](https://docs.astalty.com.au/assets/bulk-communications-send-schedule-results.png)

A banner at the top summarises the send and shows the sent, skipped, failed, cancelled, and delivery failed counts that apply.

| Status               | What it means                                                                                                         |
| -------------------- | --------------------------------------------------------------------------------------------------------------------- |
| **Sending**          | Queued or in progress.                                                                                                |
| **Sent**             | Handed to the mail provider. No delivery result yet.                                                                  |
| **Delivered**        | The mail provider confirmed it reached the inbox.                                                                     |
| **Delivery delayed** | Temporarily rejected and being retried.                                                                               |
| **Delivery failed**  | Permanently rejected, usually because the address is wrong or closed.                                                 |
| **Cancelled**        | Cancelled before it was sent.                                                                                         |
| **Skipped**          | The Participant was archived or deleted between composing and sending, so no email was sent and no PDF was generated. |
| **Failed**           | The email could not be sent.                                                                                          |

The chip on a Participant's row shows their worst recipient outcome, and reads **Successful** when every recipient is fine.

> **Sent does not mean delivered**
>
> **Sent** only means Astalty handed the email to the mail provider. A bounce arrives afterwards and
> changes that recipient to **Delivery failed**. The page keeps checking until every recipient has a
> final result. A **Delivery delayed** recipient is rechecked for 30 minutes after the send finishes.
> Reload the page later to confirm the final result.

## Things to Keep in Mind

- **A send covers at most 500 Participants.** Split a larger group across sends by narrowing the date range or clearing rows.
- **Cancelled supports are never listed on the PDF**, and cannot be included. This is the opposite of [Email Supports as PDF](https://docs.astalty.com.au/guide/scheduling/viewing-a-participants-schedule#choosing-what-goes-on-the-pdf) for a single Participant, which includes them unless you exclude them.
- **Participants with no supports in the range never appear**, so a send only reaches people who actually have something scheduled.
- **Archived Participants are excluded** when the list is built, and one archived after you compose is recorded as **Skipped** rather than **Failed**.
- **Support Worker names are abbreviated** on the PDF to a first name and surname initial, to protect your staff's privacy.
- **Every send is kept** under **Recent Bulk Communications**, with who sent it, the period it covered and its outcome. Select a row to reopen its results.
