Wie CompleteEvent automatisierte E-Mails plant

The Four Automated Email Types

CompleteEvent schedules four emails per registration at the moment an attendee is confirmed:

• reminder_3day — 3 days before event start, at the configured send hour in the event's timezone
• reminder_1day — 1 day before event start, at the same send hour
• reminder_morning — morning of the event, 2 hours before the send hour (minimum 6 AM)
• post_event_survey — N hours after event end, where N is the configured survey delay (default 2)

All four rows are written to a scheduled_emails queue at registration time. A cron job checks this queue every 15 minutes and sends any emails whose scheduled time has passed.

Timezone-Aware Scheduling

The send hour is always interpreted in the event's local timezone — not UTC, not your browser timezone. If your event is in America/New_York and the send hour is 9, the reminder fires at 9:00 AM Eastern. Daylight saving transitions are handled correctly.

This means attendees in Tokyo and attendees in London both get the same email at the same local morning time relative to the event, not the same UTC timestamp.

Registration-Time Scheduling

Send times are computed when the attendee registers, not at send time. This means:

• Each attendee's scheduled times are stored individually in the queue.
• Emails in the past are never queued — if someone registers the day before, the 3-day reminder is silently skipped.
• If you change the send hour or survey delay on a future event, CompleteEvent deletes the existing pending rows and re-schedules them with the new times for all confirmed registrations.

What Happens to Late Registrations

If an attendee registers after a reminder's scheduled time has already passed, that reminder is skipped automatically. Only future-dated emails are inserted into the queue. An attendee who registers 12 hours before the event will still receive the morning-of reminder and the post-event survey, but not the 3-day or 1-day reminders.

The Notification Log

Every email sent (or failed) is recorded in the notification log. To view it, go toReports › Survey Results and look for the email history section, or open an individual registration and check the activity timeline.

The log records: email address, type (reminder_3day, reminder_1day,reminder_morning, survey), subject line, status (sent,failed, cancelled), and the Resend message ID for bounce tracking.

Troubleshooting Missing Emails

Check the notification log first. If the status is sent, the email left CompleteEvent successfully. Ask the attendee to check their spam folder or search for the sender address (events@completeevent.app or your custom domain).

Status is cancelled — the reminder type was disabled at the event or org level, or the send time was in the past when the attendee registered.

Status is failed — Resend returned an error. This usually means the email address bounced. Contact support if you see a pattern of failures.

No row exists — the attendee registered after the send time had passed, so no row was created for that reminder type. The remaining future-dated reminders will still send.