Reminders

Reminders sends timed email to your event's confirmed registrants and nudges people who received a ticket but haven't claimed it. Open the event, then go to Reminders, under Communication in the sidebar.

Two counts sit at the top of the tab: Reminder audience (confirmed registrations with an email on file) and Unclaimed audience (ticket holders who haven't confirmed attendance, plus pending invite recipients). Both are live counts, and they're the exact pools a reminder you create draws from.

Automatic reminders

Below the two counts, an Automatic table lists four reminders that Events sends with no operator action at all: a reminder 24 hours before the event starts, another 2 hours before, an incomplete-registration follow-up for ticket holders with outstanding steps, and a ticket-transfer follow-up for unclaimed transfers. Each row shows whether it's on for this event and how many emails it has sent so far. See Automatic reminders for what each one sends and how to reword or turn one off.

Creating a reminder

Select New reminder at the top of the page to open the composer. Two kinds are available, presented as radio cards:

Event reminder

Targets confirmed registrations with an email on file. The default subject is Reminder: {event title}. You can optionally narrow the audience to a single ticket type, useful when different ticket types represent different sessions, tiers, or days.

Claim nudge

Targets two groups:

• Ticket holders with an email address set but no confirmed attendance.
• Pending ticket invite recipients, people you sent an invite link who haven't claimed their ticket yet.

Both groups are combined and deduplicated by email address before sending. The default subject is You haven't claimed your ticket for {event title}.

Scheduling

Three schedule modes are available:

• Manual (Send now): schedules the reminder for the next cron pass. It becomes active within approximately 5 minutes.
• At a specific time: pick an exact date and time. You enter this in your browser's local time; it is stored and processed as UTC.
• Relative to event start: set a number of days before the event starts (0–60). The cron checks every 5 minutes, so the actual send time can drift by up to 5 minutes from the exact offset.

Customizing subject and body

Both fields are optional. When left blank, each kind uses its built-in default template.

• Subject override: up to 200 characters. The placeholder text shows the default for that kind.
• Body override: up to 4,000 characters. Plain text; line breaks are preserved in the sent email. Leaving this blank uses the default template body.

Your body override replaces only the intro paragraph. The email still shows the event date, venue or join link (for an Event reminder), and always ends with a button linking each recipient to their own tickets or claim page, you don't need to add that link yourself.

The reminder's name (up to 120 characters) is visible only to you, it does not appear in the email.

Check Activate immediately to create the reminder in scheduled status. Leave it unchecked to save it as draft and activate it later.

Statuses and actions

Each reminder moves through a predictable lifecycle. The status tells you where it is and which actions are available. There's no edit action, to change a reminder's content or schedule, cancel or delete it and create a replacement.

• draft: saved but not active. You can send it now or delete it.
• scheduled: queued for delivery. You can send now (which moves the send time to the next cron pass) or cancel.
• enqueuing: the cron is actively building the recipient list. You can cancel at this point, but cannot delete until sending completes.
• sending: emails are being dispatched in batches. You can cancel; the worker skips any remaining queued sends on its next pass.
• sent: delivery complete. You can delete the record.
• cancelled: stopped before or during delivery. You can re-activate with Send now, or delete.
• failed: an unrecoverable error stopped the reminder. Delete the record and create a replacement.

Delete is only available from draft, cancelled, failed, and sent. If a reminder is in enqueuing or sending state, cancel it first, then delete.

How sending works

Reminders are dispatched by a cron job that runs every 5 minutes. The worker batches outgoing emails in groups of ~100 using the Resend batch API, so a large audience (5,000+ recipients) completes in a few minutes without tripping rate limits.

The cron worker has a 4-minute budget per 5-minute window. Very large sends that can't complete in one pass resume on the next. Reminders in sending state are still in progress; check back in a few minutes if the count hasn't reached the total recipient number.

After a reminder is sent, the record shows sent_count and failed_count so you can see how many emails were delivered and how many bounced or errored.