Emails and reminders (event page)

The panel on an event that lists what it sends and when.

• Every schedule is listed on every plan, with its kind (core or reminder), trigger, channel, status and next run in the event's timezone.
• Core schedules are the registration confirmation and delivering the ticket (email or printed). Every plan sends them; a missing entitlement never pauses them (PRICING §7, EVENT_TEMPLATE_FORMAT §1.5).
• Reminders are everything else and need reminders_configurable (Starter and above).
• The day-before reminder is included on every plan. An event published on a plan without reminders_configurable gets exactly one reminder — the system reminder email at 09:00 the day before the event starts, in the event's timezone — listed as Reminder — included. It is created once per event, a downgrade never pauses it, and an upgrade neither duplicates it nor takes it away: from Starter it is an ordinary reminder that can be renamed, retimed or cancelled. An event published after its own T-1 has passed does not get one, because it would go out immediately for an event that has already started.
• On Free the panel is read-only: core schedules and the day-before reminder send as set up, reminders imported from an event template wait switched off, and "Add reminders" opens the upgrade instead of a form. The service refuses the same things, with a message that names the plan.
• From Starter an organizer with communications.schedule can add schedules and edit them. Fixed-date schedules are not offered in this form yet (decisions-pending).
• A registration's own page has "Send ticket email now" for a one-off send outside any schedule.