---
title: Resend Event Tickets
description: "Eventixa Pro lets administrators resend an attendee's event ticket from the attendee details screen. This is useful when an attendee did not receive the original ticket email, entered the wrong email address, lost the message, or asks for another copy.…"
url: "https://eventixawp.com/docs/resend-event-tickets/"
updated: "2026-09-27"
category: Attendees
---

# Resend Event Tickets

Eventixa Pro lets administrators resend an attendee's event ticket from the attendee details screen.

This is useful when an attendee did not receive the original ticket email, entered the wrong email address, lost the message, or asks for another copy.

> **Available in:** Eventixa Pro
> **Location:** Eventixa → Attendees → Open Attendee
> **Related features:** Attendees, Ticket PDF, Email Delivery, QR Check-In

## Open the Attendee

Go to: `Eventixa → Attendees`

Find the attendee who needs another ticket.

Click the attendee name to open the **Edit Attendee** screen.

## Find Attendee Actions

On the Edit Attendee screen, locate the: **Attendee Actions** panel.

Depending on the active Eventixa features, this panel can include actions such as:

- View booking
- Download Ticket PDF
- Re-Send Ticket

Click: **Re-Send Ticket** to send the attendee's ticket again.

## When to Resend a Ticket

Use Re-Send Ticket when:

- The attendee did not receive the original email.
- The message was deleted.
- The attendee email address was corrected.
- Ticket delivery failed.
- The attendee asks for another copy.
- An administrator needs to reissue the same attendee ticket.

## Verify the Attendee First

Before resending, confirm:

- Attendee name
- Email address
- Event
- Event date
- Ticket
- Registration status

For recurring events, also verify the correct occurrence.

This helps prevent sending the wrong ticket to the wrong person.

## Check the Email Address

The ticket is sent using the attendee's saved email information.

Before clicking Re-Send Ticket, verify the email is correct.

If the email is wrong:

1. Edit the attendee email.
2. Click **Save Attendee Fields**.
3. Confirm the updated address.
4. Then click **Re-Send Ticket**.

## Do Not Resend Before Correcting the Email

If the attendee's existing email is incorrect, resending first will simply deliver the ticket to the same wrong address again.

Correct the attendee record before resending.

## Ticket Eligibility

Only resend a ticket when the attendee still has a valid registration.

Review:

- Attendee status
- Booking status
- Registration type

A cancelled attendee should not normally receive an active event ticket.

## Completed Attendee

A valid completed attendee is generally the normal case for ticket re-delivery.

For example:

**Attendee Status:** Completed with a valid standard ticket can use the Re-Send Ticket action.

## Cancelled Attendee

If the attendee status is: **Cancelled** review the related booking before resending.

Do not send an active ticket for a registration that is no longer valid.

## Failed or Expired Booking

If the associated booking failed or expired before registration completed, verify whether the attendee should have a valid ticket at all.

Open: **View booking** and review the booking and payment state first.

## Free Tickets

Free-ticket attendees can also have event tickets where ticket delivery is enabled.

No paid transaction is required for the ticket to be re-sent.

## Paid Tickets

For paid registrations, verify that the booking reached the appropriate valid state before resending the ticket.

If payment is uncertain, review the related booking first.

## RSVP Tickets

RSVP behavior differs from standard ticket registration.

Whether a ticket should be delivered depends on the supported RSVP workflow and response.

For example, a **Not Going** RSVP should not be treated as an active attending ticket holder.

## Ticket PDF

Where Ticket PDF functionality is available, the attendee actions can also include: **Download Ticket PDF**

This lets an administrator download the ticket instead of sending it by email.

## Download vs Re-Send

Use: **Download Ticket PDF**

when you need a local copy for printing or manual delivery.

Use: **Re-Send Ticket**

when the attendee should receive the ticket again by email.

## Ticket Content

A re-sent ticket should represent the attendee's current valid ticket information.

Depending on the configuration, the ticket can contain information such as:

- Attendee name
- Event
- Date
- Ticket type
- QR code
- Other ticket details

## QR Code

Where QR ticketing is active, the re-sent ticket can contain the attendee's QR information.

The attendee record remains the same; resending does not create a new registration.

## Resending Does Not Create Another Booking

Re-Send Ticket only sends the existing attendee ticket again.

It does not:

- Create another booking
- Add capacity
- Create a new attendee
- Charge the customer again

The original registration remains unchanged.

## Resending Does Not Reset Check-In

If the attendee has already been checked in, resending the ticket does not reset their check-in status.

Check-in remains associated with the attendee record.

## Recurring Events

For recurring events, verify the attendee is associated with the correct occurrence before resending.

For example:

**Conference — April 15** and **Conference — April 29** can use similar ticket information but represent different event occurrences.

## Recurring Virtual Events

If the attendee belongs to a recurring Virtual or Hybrid event, ticket delivery should remain connected to the correct occurrence and access rules.

Resending the ticket should not bypass virtual-event access timing.

## Virtual Event Access

A ticket email may contain or relate to virtual event information depending on Eventixa configuration.

However, access can still depend on:

- Booking validity
- Attendee status
- Reveal timing
- Occurrence

Re-Send Ticket does not override these rules.

## Guest Checkout Attendees

Tickets can be re-sent to attendees created through Guest Checkout as long as the attendee has a valid saved email and eligible registration.

A WordPress account is not required merely to receive a ticket email.

## Manual Booking Attendees

Attendees created through Manual Booking can also use the same attendee ticket workflow where ticket delivery is supported.

Make sure the administrator entered the correct attendee email when creating the booking.

## Correcting Name Before Resend

If the attendee's name is incorrect:

1. Edit the attendee record.
2. Correct the Name field.
3. Save the attendee fields.
4. Verify the change.
5. Re-send the ticket.

This helps ensure the replacement ticket contains the corrected attendee information where applicable.

## Correcting Custom Fields

If ticket content depends on custom attendee fields, update those fields before resending.

For example:

- Company
- Session
- Ticket-specific registration answer

Save the changes first.

## Email Delivery

A successful Re-Send Ticket action means Eventixa attempted to send the ticket using the site's WordPress email system.

Actual inbox delivery can also depend on:

- WordPress mail configuration
- SMTP provider
- Receiving mail server
- Spam filtering
- Email address validity

## Ticket Email Not Received

If the attendee still does not receive the ticket, check:

- Saved attendee email
- Spam folder
- WordPress email delivery
- SMTP configuration
- Mail logs if available

Do not repeatedly resend without first checking the likely delivery issue.

## Use an SMTP Provider

For production event sites, reliable transactional email delivery is recommended.

A properly configured SMTP or transactional email service can improve ticket email deliverability compared with an unreliable default mail environment.

## Ticket Delivery and Bulk Email Are Different

Re-Send Ticket is specifically for an attendee's ticket.

It is different from Eventixa Bulk Emails, which are intended for broader event communication.

Use the appropriate feature for the message you need to send.

## Add an Internal Note

After correcting an attendee or resending a ticket, you can add an internal attendee note.

For example:

**Email corrected and replacement ticket re-sent at attendee request.**

This helps other administrators understand what was done.

## Why Notes Help

A ticket delivery issue may involve several support interactions.

Internal notes can record:

- Original delivery problem
- Email correction
- Re-send attempt
- Attendee confirmation

This avoids repeating troubleshooting later.

## Privacy

Before resending a ticket, verify that the email belongs to the intended attendee.

Do not send attendee tickets to unverified third-party addresses.

Tickets can contain event-access information and should be treated as private registration material.

## Changing the Recipient

If an attendee asks to send the ticket to a different email address, update the attendee email through the supported editing workflow first.

Then resend to the updated address.

This keeps Eventixa data consistent with the actual ticket recipient.

## Example: Wrong Email Address

The attendee entered:

`john@old-example.com`

but the correct email is:

`john@new-example.com`

Recommended workflow:

1. Open attendee.
2. Update Email.
3. Save Attendee Fields.
4. Confirm the new email.
5. Click Re-Send Ticket.
6. Add an internal note if useful.

## Example: Lost Ticket Email

The attendee's email is correct but they deleted the original ticket.

Workflow:

1. Open attendee.
2. Verify email.
3. Verify attendee status.
4. Click Re-Send Ticket.

No attendee edit is necessary.

## Example: Ticket Email Failed

If the attendee reports never receiving the ticket:

1. Verify email.
2. Check mail delivery.
3. Review SMTP or mail logs.
4. Resolve the email issue if possible.
5. Re-Send Ticket.

## Example: Cancelled Registration

If the attendee is cancelled:

1. Do not immediately resend.
2. Open the booking.
3. Verify why the registration was cancelled.
4. Restore or correct the registration only through a valid supported workflow.
5. Resend only after the attendee is again eligible.

## Common Problems

### Re-Send Ticket Button Is Missing

Confirm:

- Eventixa Pro is active.
- The attendee has a supported ticket.
- The attendee is eligible for ticket delivery.
- The applicable ticket functionality is enabled.

### Ticket Goes to the Wrong Email

Update the attendee email first and save the change.

Then resend.

### Attendee Still Does Not Receive the Ticket

Check:

- Email address
- Spam folder
- WordPress email delivery
- SMTP configuration
- Mail logs

### Ticket Shows Old Attendee Information

Make sure you saved the attendee changes before resending.

### Attendee Is Cancelled

Do not resend an active ticket until the registration is valid again.

### Ticket PDF Can Be Downloaded but Email Is Not Received

This suggests the ticket itself exists but email delivery may be failing.

Check the site's mail configuration.

### QR Code Does Not Work After Resend

Resending should use the same valid attendee registration.

Check:

- Attendee status
- Booking status
- Correct event
- Correct occurrence
- Existing check-in state

### Attendee Already Checked In

Resending does not reset check-in.

This is expected.

## Recommended Re-Send Workflow

1. Go to **Eventixa → Attendees**.
2. Search for the attendee.
3. Open the attendee record.
4. Verify event and occurrence.
5. Confirm attendee status.
6. Verify attendee email.
7. Correct and save the email if necessary.
8. Find **Attendee Actions**.
9. Click **Re-Send Ticket**.
10. Confirm delivery where possible.
11. Add an internal note if useful.

## Troubleshooting Workflow

If ticket delivery fails:

1. Verify the attendee email.
2. Confirm registration eligibility.
3. Download the Ticket PDF to confirm the ticket exists.
4. Review WordPress mail configuration.
5. Review SMTP/mail logs.
6. Fix the mail issue.
7. Re-send the ticket.
8. Record important support actions in attendee notes.

## Important Notes

- Re-Send Ticket requires Eventixa Pro.
- The action is available from the attendee details screen.
- Verify attendee status before resending.
- Correct the attendee email before sending another ticket.
- Resending does not create another booking or attendee.
- Resending does not consume additional ticket capacity.
- Resending does not reset check-in.
- Recurring attendees must use the correct event occurrence.
- A valid Eventixa action does not guarantee inbox delivery if WordPress email is misconfigured.
- Use internal notes to document important ticket-delivery support actions.

## Related Documentation

- [Managing Attendees in Eventixa](https://eventixawp.com/docs/managing-attendees/)
- [Add and Edit Attendees in Eventixa](https://eventixawp.com/docs/add-edit-attendees/)
- [Managing Bookings in Eventixa](https://eventixawp.com/docs/managing-bookings/)
- [Booking Details in Eventixa](https://eventixawp.com/docs/booking-details/)
- [QR & PDF Tickets](https://eventixawp.com/docs/qr-tickets/)
- [QR Check-In](https://eventixawp.com/docs/event-check-in/)
- [Email Settings](https://eventixawp.com/docs/email-notifications-overview/)