Emails and confirmation expectations
POM Events does not send email. Not to attendees, not to organizers, not at any point. This page sets the expectation and covers what to do about it.
What is not sent
| Expected message | Sent by POM Events |
|---|---|
| Registration confirmation to the attendee | No |
| Notification to the organizer | No |
| Waiting-list notice | No |
| Promotion notice when a place is released | No |
| Event reminder | No |
| Cancellation notice | No |
| Post-event follow-up | No |
The visitor is told the result on screen, immediately, and that is the whole of the automatic communication.
What is sent, on a paid event
WooCommerce sends its own order emails. Those confirm a purchase, not a place at an event.
That distinction matters to the buyer: they receive an order confirmation and may reasonably wonder whether they are registered. Make the order email say so, and repeat the event's date, time and place in it.
Do not promise what does not happen
Check your public copy for promises the site cannot keep:
- You will receive a confirmation email — remove it, or implement it;
- We will email you when a place is released — the promotion is manual and silent;
- Check your inbox for details — there is no inbox message.
An attendee who waits for an email that never arrives assumes their registration failed, and registers again.
Say what actually happens
Put it where the visitor reads it — the event's introduction, or the form clause:
Your place is confirmed on screen when you register. We do not send a confirmation email; add the event to your calendar with the link on this page.
And for a capacity event:
If the event is full you will join the waiting list. We contact people individually as places are released.
The manual routine
Because nothing is automatic, someone must own the messaging:
| Moment | Action |
|---|---|
| A registration arrives | Nothing, unless you choose to acknowledge it |
| A place is released | Contact the person you promoted, by email or telephone |
| A week before | Send a reminder from the exported list, if you promised one |
| Something changes | Contact everyone, from the export |
| After the event | Send the follow-up you promised |
Every one of those uses the addresses and telephone numbers in the attendee list or the export.
Sending them automatically
If your site should send confirmations, they can be built on the plugin's public hooks:
- Registrations — the registration action fires after a registration is stored, with the user, the event and a flag so several integrations cooperate. Read the stored status so a wait-listed person is not told they have a place.
- Status changes — the status action fires after an organizer moves a registration, which is the hook for a promotion notice.
- Purchases — the paid path does not fire the registration action; implement it on a WooCommerce order hook as well, or half your attendees will hear nothing.
See Registration lifecycle hooks and Attendee status hooks.
Before launching a site that takes registrations
- [ ] No public copy promises an email that is not sent.
- [ ] The event page says what happens after registering.
- [ ] Capacity events explain the waiting list.
- [ ] Someone owns contacting attendees.
- [ ] Paid events' order emails carry the event details.
- [ ] If confirmations are required, both paths — form and purchase — are implemented.