---
title: "Form and Event Communications Triggers & Groups"
slug: "form-and-event-communications-triggers-groups"
updated: 2026-05-04T17:35:42Z
published: 2026-05-04T17:35:42Z
---

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

# Form and Event Communications Triggers & Groups

Use triggers and groups to control when form and event communications are sent and which registrants receive them.

## Before you configure triggers and groups

- Form and event communications, including Scheduler communications, are sent only when the event status is **Confirmed**. If the event status is **Tentative**, you can administratively complete a registration form, but Slate does not send communications to the registrant.
- Confirmation pages do not appear when a registration form is submitted administratively through **New Registration**.
- If a registration is rescheduled, registration and update triggers do not fire.
- Submitting a pending or save-for-later form does not count as a registration for trigger purposes.

## Registration triggers

### Upon registration or update

Sends the communication when the registration form is submitted for the first time or updated.

| **Group** | **Communications are sent** |
| --- | --- |
| Direct Entry + Admin Entry | Regardless of registration method. |
| Direct Entry Only | Only if the registration is submitted or updated using a public link. |
| Admin Entry Only | Only if the registration is submitted or updated administratively. |

### Upon registration

Sends the communication when the registration is submitted for the first time.

| **Group** | **Communications are sent** |
| --- | --- |
| Direct Entry + Admin Entry | Regardless of registration method. |
| Direct Entry Only | Only if the registration is submitted using a public link. |
| Admin Entry Only | Only if the registration is submitted administratively. |

### Upon registration, including related event registration

Sends the communication when the registration is submitted for the first time, including registrations submitted through a related event widget. This trigger is rarely used.

Use this trigger when both the master event and related event communications should fire. For example, a multi-session event might need a confirmation email that includes times and locations for all related events selected during registration.

The main event must have an email notification for related event notifications to fire. A confirmation-page-only communication on the main form is not enough.

| **Group** | **Communications are sent** |
| --- | --- |
| Direct Entry + Admin Entry | Regardless of registration method. |
| Direct Entry Only | Only if the registration is submitted using a public link. |
| Admin Entry Only | Only if the registration is submitted administratively. |

### Upon update

Sends the communication when the registration is updated after the initial registration.

| **Group** | **Communications are sent** |
| --- | --- |
| Direct Entry + Admin Entry | Regardless of registration method. |
| Direct Entry Only | Only if the registration is updated using a public link. |
| Admin Entry Only | Only if the registration is updated administratively. |

### Upon waitlist registration

Sends the communication when the registrant is placed on the waitlist.

### Upon move from waitlist to registered

Sends the communication when the registrant is moved from the waitlist to registered.

### Upon cancellation

Sends the communication when the event registration is canceled by the registrant.

### Upon event cancellation

Sends the communication to all registrants and waitlisted registrants when the event is canceled.

## Time-based triggers

### Time before deadline

Sends the communication to all registrants in the **Registered** status a specified number of days, hours, and minutes before the registration deadline.

### Time before event

Sends the communication to the selected group of registrants a specified number of days, hours, and minutes before the event begins.

### Time after event

Sends the communication to the selected group of registrants a specified number of days, hours, and minutes after the event ends.

| **Group** | **Communications are sent** |
| --- | --- |
| All Registrants | All active registrants. |
| Attendees | Only registrants marked as **Attended**. |
| No Shows | Only registrants marked as **No Show**. |

## Post-deadline administrative registrations

If pre-registration is not required for an event and attendees will be administratively added after the event deadline, use the group that includes **Admin: Email Only (including post-deadline)**. This group sends communications to event attendees when they are registered administratively after the deadline.

Registrations added by Upload Dataset do not cause mailings using the **Include Post-Deadline** trigger type to fire.