Administrator Emails
Eventixa can send administrator-facing email notifications when important registration activity happens on your website.
These notifications help site owners, event managers, and administrators stay informed without constantly checking the Eventixa dashboard.
Available in: Eventixa Core + Eventixa Pro
Location: Eventixa → Settings → Emails → Email Template
Related features: Bookings, Waitlist, Email Templates, Senders, Bulk Emails
What Are Administrator Emails?
Administrator emails are notifications intended for site or event-management recipients rather than customers.
They can alert your team when important activity occurs, such as:
- A new booking being created
- A visitor joining a waitlist
- Other supported administrative notification events
The exact templates available depend on the active Eventixa features.
Open Administrator Email Templates
From the WordPress dashboard, go to: Eventixa → Settings → Emails
Open: Email Template
This page lists all available Eventixa email templates.
Customer and administrator templates appear together in the template list.
Administrator-oriented templates can be identified by their name and description.
Admin New Booking
The main administrator booking notification is:
Admin New Booking
This template is sent to the configured site or administrator recipient when a new Eventixa booking is created.
It helps administrators monitor new registrations as they happen.
What the Admin New Booking Email Can Include
Depending on your template configuration, the message can include details such as:
- Booking reference
- Event
- Event date
- Purchaser
- Ticket
- Quantity
- Booking total
- Payment method
- Booking status
Use the email as an operational notification, then open the booking in Eventixa when more detail is required.
When Admin New Booking Is Useful
This notification is especially useful when:
- Events receive relatively few high-value bookings
- Staff manually review registrations
- Offline payments require follow-up
- Events have limited capacity
- Administrators need immediate awareness of new bookings
Booking Email vs Customer Email
The administrator email and customer booking email have different audiences.
Customer Booking Email
Tells the purchaser or attendee that their registration was received or confirmed.
Administrator Booking Email
Tells your internal team that a new booking was created.
Both can be active for the same booking.
Administrator Recipient
The admin notification is sent to the configured administrative recipient.
The actual address depends on your Eventixa sender/recipient configuration.
Review your email settings before going live to make sure notifications go to the correct inbox.
Use a Monitored Email Address
Administrator notifications should go to an inbox your team actually monitors.
Good examples include:
Avoid sending important booking alerts to an abandoned administrative address.
Multiple Administrators
If your workflow requires several people to receive notifications, configure the recipient setup supported by your Eventixa installation.
Keep the recipient list limited to people who genuinely need booking information.
Privacy
Administrator emails can contain customer and booking information.
Only send them to trusted internal recipients.
Avoid forwarding booking notifications to unrelated people.
Waitlist Admin New Signup
Requires Eventixa Pro
When Waitlist is active, Eventixa can provide: Waitlist Admin New Signup
This template notifies the site or administrator recipient when a visitor joins an event ticket waitlist and admin notifications are enabled.
Why Waitlist Admin Notifications Matter
A waitlist signup can be useful operational information when:
- An event is sold out
- Demand is high
- Staff are monitoring capacity
- Additional ticket capacity may be released
It helps administrators understand demand without manually opening the Waitlist screen.
Waitlist Admin Email Can Identify
The notification can provide context such as:
- Event
- Ticket
- Waitlisted visitor
- Signup information
The exact content depends on the configured template.
Customer Waitlist vs Admin Waitlist Email
These are different templates.
Waitlist Confirmation
Sent to the visitor who joins the waitlist.
Waitlist Admin New Signup
Sent to the administrative recipient.
One confirms the visitor’s action; the other alerts your team.
Active Template Status
On the Email Templates screen, an enabled notification displays:
ACTIVE
If an administrator email is not being sent, first confirm the corresponding template is active.
Manage an Administrator Template
To edit an admin email:
- Go to Eventixa → Settings → Emails → Email Template.
- Locate the administrator template.
- Click Manage.
- Review the subject.
- Review the heading.
- Edit the message content.
- Save the template.
- Test the associated workflow.
Subject Line
Use a subject that immediately tells the administrator what happened.
For example: New Event Booking Received or New Waitlist Signup
Avoid vague subjects such as: Eventixa Notification
Email Heading
The heading should reinforce the action.
For example: New Booking or New Waitlist Registration
Keep it short and operational.
Email Body
The email body should provide enough information for the administrator to understand the event without making the message unnecessarily long.
Useful details can include:
- Event name
- Booking reference
- Purchaser
- Ticket
- Amount
- Booking status
Booking Reference
Including the booking reference is especially useful.
For example:
Booking: EC26001572
An administrator can then quickly locate the record under: Eventixa → Bookings
Dynamic Placeholders
Administrator templates can use supported Eventixa placeholders to insert dynamic booking information.
For example:
- Booking reference
- Event title
- Customer name
- Amount
- Ticket information
The available placeholders are documented separately under: Email Placeholders
Do Not Hard-Code Booking Data
Use placeholders for changing values.
Do not manually write a particular:
- Customer name
- Event title
- Booking number
into a reusable template.
The same template should work across many bookings.
New Booking and Payment State
A new booking notification tells the administrator that a booking was created.
It should not necessarily be interpreted as proof that payment succeeded.
Always inspect the actual:
- Booking status
- Payment status
when financial confirmation matters.
Example: Pending Online Payment
An administrator might receive a new-booking notification while a payment is still being processed.
Do not assume the booking is fully paid based on the email alone.
Open: Eventixa → Bookings and verify the financial state.
Example: Offline Payment
For Local / Offline Payment, the admin notification can alert your team that a booking exists.
The payment may still need to be collected manually.
Review:
- Booking total
- Payment method
- Payment status
before confirming payment.
WooCommerce Bookings
When WooCommerce handles payment, WooCommerce can also send its own administrator order emails.
This means your team may receive:
- WooCommerce new order email
- Eventixa Admin New Booking email
These emails serve related but different purposes.
Avoid Administrative Email Duplication
If WooCommerce and Eventixa both send notifications, decide whether your team needs both.
For example:
WooCommerce Email
Useful for:
- Order
- Billing
- Payment gateway
Eventixa Email
Useful for:
- Event
- Ticket
- Registration
- Attendee context
Keep both when the distinction is useful.
Recurring Event Admin Emails
For recurring events, administrator emails should identify the correct occurrence.
For example: Community Science Festival — August 16, 2028
This prevents staff from confusing one occurrence with another.
Virtual Event Admin Emails
Virtual and Hybrid event booking notifications should still identify the event and registration clearly.
Internal notifications should not expose unnecessary private meeting credentials.
Free Bookings
Free event registrations can still generate an administrator new-booking notification.
The absence of payment does not make the booking operationally unimportant.
RSVP Notifications
RSVP customer emails have their own templates.
If your current Eventixa version does not provide a separate RSVP administrator email template, do not assume that one exists.
Use the Bookings or Attendees screens to monitor RSVP activity as needed.
Attendee-Level Information
Admin booking notifications are typically booking-oriented.
For detailed attendee-level information, use: Eventixa → Attendees
This is especially important when one booking contains several participants.
Internal Notes Are Not Customer Content
Booking notes and attendee notes are private administrative records.
They should not be exposed to customers.
Similarly, avoid inserting unnecessary internal notes into administrator emails if the notification can remain concise.
Email Senders
The Senders section under Eventixa email settings controls sender-related configuration where available.
Review sender settings to make sure administrator emails come from a recognizable and valid source.
Recognizable Sender
Use a sender identity your team can recognize.
For example: Eventixa Notifications or your organization name.
This helps internal messages stand out from unrelated mail.
Reply-To Behavior
Where supported, configure reply behavior according to your operational needs.
Do not assume replying to an automated admin notification will always contact the purchaser.
Check your sender configuration.
Deliverability
Administrator emails use the site’s WordPress email environment.
Delivery can be affected by:
- Server mail configuration
- SMTP
- Sending-domain authentication
- Spam filtering
- Invalid recipient address
Use SMTP
A reliable SMTP or transactional email provider is strongly recommended for production.
Missing administrator booking alerts can create operational problems even when customer emails are working.
Test Administrator Emails
Before launch, create a test booking.
Verify:
- Admin New Booking email arrives
- Correct recipient receives it
- Subject is clear
- Event is correct
- Booking reference is correct
- Links or details work
Test Waitlist Admin Notifications
Requires Eventixa Pro
For a sold-out ticket:
- Join the waitlist using a test address.
- Confirm the customer receives the Waitlist Confirmation.
- Confirm the administrator receives Waitlist Admin New Signup.
- Verify event and ticket information.
Test Paid Booking
Complete a paid booking and verify that the admin notification does not create confusion between:
- Booking creation
- Payment confirmation
Use Eventixa Booking Details for the final financial state.
Test Free Booking
Create a free registration and verify the administrator notification remains clear even though no payment is required.
Test Recurring Event
Register for one occurrence.
Make sure the administrator email identifies the correct date.
Common Problems
Admin New Booking Email Is Not Sent
Check:
- Template is Active
- Admin recipient is configured
- Booking was actually created
- WordPress email is working
- SMTP logs
Email Goes to Wrong Administrator
Review the configured recipient.
Admin Receives Email but Customer Does Not
Administrator and customer templates are separate.
Check the applicable customer template.
Customer Receives Email but Admin Does Not
Check:
- Admin New Booking template
- Recipient configuration
- Email deliverability
Admin Email Goes to Spam
Review:
- SMTP configuration
- Sender domain
- From address
- Mail authentication
Admin Thinks Booking Is Paid Because Email Arrived
The email indicates booking activity, not necessarily financial success.
Check Booking Details.
Wrong Recurring Date Appears
Verify the booking’s occurrence.
Waitlist Admin Notification Is Missing
Confirm:
- Eventixa Pro is active
- Waitlist is active
- Waitlist Admin New Signup template is Active
- Admin notifications are enabled where applicable
WooCommerce Generates Too Many Admin Emails
Review both WooCommerce and Eventixa notification settings and disable unnecessary duplication according to your workflow.
Recommended Administrator Email Setup Workflow
- Go to Eventixa → Settings → Emails → Email Template.
- Find Admin New Booking.
- Confirm it is Active.
- Click Manage.
- Configure subject and heading.
- Review message body.
- Add useful placeholders.
- Save.
- Review sender/recipient settings.
- Complete a test booking.
- Verify delivery.
- Test a paid booking.
- Test a free booking.
- Test recurring-event registration.
- Test waitlist admin notification if using Eventixa Pro.
Recommended Admin Email Content
A useful new-booking email should make it easy to answer:
- What happened?
- Which event?
- Which booking?
- Who registered?
- Which ticket?
- What amount?
- What should the administrator check next?
Avoid turning the email into a complete replacement for the Eventixa Booking Details screen.
Example Administrator Notification
A concise admin email might communicate:
New booking received
Event: Community Science Festival
Booking: EC26001572
Ticket: Standard Event Pass
Total: $19.00
Review the booking in Eventixa for complete status and payment details.
Recommended Production Checklist
Before accepting registrations, confirm:
- Admin New Booking is Active.
- Correct recipient is configured.
- Sender information is valid.
- Booking reference is included.
- Event information is clear.
- Recurring occurrence displays correctly.
- SMTP works.
- Waitlist Admin New Signup is configured if using Waitlist.
- WooCommerce duplication is intentional if WooCommerce is enabled.
Important Notes
- Administrator emails are separate from customer emails.
- Admin New Booking notifies the configured administrator when a booking is created.
- A new booking email does not by itself prove that payment succeeded.
- Verify Booking Status and Payment Status inside Eventixa.
- Waitlist Admin New Signup requires Eventixa Pro and the Waitlist workflow.
- WooCommerce can also send administrator order emails.
- Use supported placeholders instead of hard-coding booking data.
- Recurring-event emails should identify the correct occurrence.
- Administrator notifications can contain private booking information and should go only to trusted recipients.
- Use reliable SMTP for production email delivery.
