Most notifications send the moment something happens. The rest are scheduled: they measure from a date, wait an offset, and may repeat. This page explains the controls in the Sends section of a template and how they combine.
Each scheduled notification measures from a date that belongs to its record. You cannot change the reference date, but knowing it tells you what "3 days before" means.
| Notification family | Measures from | Stops when |
|---|---|---|
| Session Reminder, Subject Group Session Reminder, Organization Session Reminder | The session start | The session starts |
| Session Complete, Subject Group Session Complete, Organization Session Complete | The session end | Single send |
| Subject Group Session Initial Booking, Booking Reminder Campaigns One to Five | The subject group's start date | The subject books, or the subject group's end date |
| Employee Job Reminder, Organization Contacts Upcoming Job | The job start | The job begins |
| Invoice Payment Reminder, Invoice Past Due (subject, organization, account manager) | The invoice sent date or due date | The invoice is paid |
| Employee Timesheet Clock In / Clock Out Reminder | The timesheet's scheduled start or end | The employee clocks in or out |
| Employee Equipment Item / Bag Past Due | The equipment due date | The equipment is checked in |
| E-Sign Request Reminder | The date the request was sent | All signers have signed |
| Task Due Date Reminder, Task Overdue Alert, Task Recurring Reminder, Employee Task Overdue | The task due date | The task is complete |
| Resource Allocation Warning / Exceeded / Digest | The allocation date | The allocation is resolved |
| Control | Meaning |
|---|---|
| Starts | How long before or after the reference date the first send happens. A count and a unit: minutes, hours, days, or weeks. Zero means "at the moment". |
| Before / After | The direction of the offset. Reminders run before; follow-ups and past-due notices run after. |
| Repeats | Whether the notification sends again after the first one. Untick it for a single send. |
| Every | The interval between repeats, again as a count and unit. |
| Until | Shown for information: the condition that ends the series, from the table above. |
| Max Repeats | A cap on how many times the series sends to one recipient. Leave blank to rely on the Until condition alone. |
| Repeats Indefinitely | Ignores Max Repeats and keeps sending on the interval until the Until condition is met. Used by the resource allocation notifications. |
| Reset Repeat Count | Clears the per-recipient counters so a capped series can start again. Useful after you fix a template that had been sending to the wrong audience. |
A sentence under the controls restates the rule in plain words, for example 3 weeks before a job starts, every 3 weeks until the job begins. Read it back before you save.
Subject group booking notifications add two things. Custom Start and End Dates let you run a campaign between two calendar dates rather than measuring from the group's start, and a time of day sets when the daily batch goes out. Five independent campaigns plus the Initial Booking notification give you a sequence such as: invitation on day one, a reminder a week later, a last call three days before booking closes.
A subject added part-way through a campaign is picked up on the next tick rather than waiting for the following interval, so late roster additions are not missed.
Out of the box, most reminders start one day before their reference date and repeat every 15 days, which in practice means a single send for anything scheduled less than two weeks out. Job reminders start three weeks ahead. Timesheet clock reminders start 15 minutes before the shift and repeat hourly. Adjust these to your own rhythm on the studio defaults first, then sync.