# Send notices and check delivery

Reach the intended people and distinguish delivery from reading.

Type: How-to guide

For: Authorised academy staff; all members as recipients

Before you start: Notices access. External channels require configuration, release enablement and recipient consent.

Reviewed: 2026-09-16

## Prepare a useful notice

Use a short title and put the action, date and relevant group first. Keep sensitive medical, safeguarding and payment details out of a general notice.

1. Open Inbox and its notices area.
2. Choose the audience by group, role or individual; review it before sending.
3. Write the notice and choose immediate or scheduled delivery.
4. Send or schedule it, then inspect recipient delivery/read state.

## Interpret the status

In-app delivery and read records are the product's primary communication record. Provider acceptance, a delivered message and an in-app read are different events. Do not assume every family read a notice because the send action succeeded.

SMS and WhatsApp apply to enabled operational notices only. They are launch-disabled until provider checks pass. A phone number alone is insufficient: verified contact, channel consent, recipient preference and suppression rules also apply. Automatic session, attendance and finance jobs are not blanket SMS/WhatsApp promises.

## When someone did not receive it

Check the audience, membership, schedule, delivery state and notification preferences. Ask the recipient to check the Inbox for the canonical notice. Escalate a persistent failed delivery with its reference; do not resend repeatedly when a provider outcome is uncertain.

## Related guides

- [Manage notifications and follow an update](https://kelab.app/docs/notification-preferences.md)
- [Launch and integration availability](https://kelab.app/docs/availability.md)
- [Roles, relationships and permissions](https://kelab.app/docs/roles-access.md)