Automatic reminders
Four reminder emails go out for every event with no campaign to create; here's what each one sends, how org defaults and per-event overrides combine, and how to reword or turn one off.
Events sends four reminder and follow-up emails automatically, on an hourly sweep, with no campaign or announcement for you to create. An event with an empty reminders list is not an event where nobody gets reminded, these run regardless.
Each one has an organization-wide default (on/off, subject line, intro paragraph) and, for most, a per-event override. Open the event and go to Reminders, under Communication in the sidebar, to see the Automatic table for what's actually firing on this event. See Reminders for the reminders and claim nudges you create yourself, which run on a separate schedule from the four below.
The four automatic emails
- 24 hours before start: every confirmed attendee with an email gets their tickets and QR codes again.
- 2 hours before start: the same reminder, closer to the doors.
- Incomplete registration follow-up: chases ticket holders with outstanding action: unclaimed tickets, unsigned attestations, missing intake files, or open session RSVPs, all in one summary email per holder. Repeats on a cadence you set, up to a maximum number of follow-ups.
- Ticket transfer follow-up: reminds a recipient who hasn't accepted a transferred ticket, starting a fixed time after the invite. The default cadence is a first nudge at 24 hours and one follow-up at 72 hours total; that cadence isn't editable per event today, only whether the whole pipeline is on.
Org defaults vs. per-event overrides
Each pipeline's organization-wide default lives on the Reminders & nudges workspace settings page (linked from the Automatic table). From there you set whether each email is on, and override its subject line and intro paragraph. A Quiet hours window on the same page holds every automated send during a set stretch of hours, applied in each event's own timezone.
Per-event, the controls differ by pipeline:
- 24h and 2h reminders: a three-way choice right in the Automatic table: inherit the org default, force on for this event, or force off.
- Ticket transfer follow-up: a simple per-event on/off in the same table. It's ANDed with the org default: if the org default is off, nothing sends for this event no matter what you set here.
- Incomplete registration follow-up: no toggle in the table. Use its Configure link, which opens the event's Settings, under Attendee emails, then Nudges: an on/off switch, when the first nudge fires, and the follow-up cadence (days between sends, and a cap on how many).
Rewording one
On the Reminders & nudges settings page, each pipeline has its own subject line and intro paragraph field. Leave a field blank to keep the built-in default, shown as the placeholder text. Only the subject line and intro paragraph are yours to customize; the rest of the template, event details, ticket links, or the claim button, is fixed.
Quiet hours
Quiet hours is a single start and end hour, set once on the Reminders & nudges page and applied to every event in your workspace, in that event's own local timezone. When enabled, automated sends are held during the window and released once it ends.
Turning one off
For a single event, use the per-event control described above: the Automatic table's selects for the 24h, 2h, and transfer follow-up, or the Nudges settings toggle for the incomplete registration follow-up. To turn a pipeline off everywhere at once, flip its switch off on the Reminders & nudges page instead. Turning off the org default for the transfer follow-up blocks every event regardless of its per-event setting; the 24h and 2h reminders work the other way around, an event with an explicit "On for this event" override keeps sending even after you turn off the org default.
Updated