← All posts

Event confirmation email template: paid, free and pending

Choose an event confirmation email template for paid tickets, a free place, pending payment or several tickets. Check fields, private access and phone previews.

Four open envelopes holding a checked ticket, a single ticket, a waiting card and three admission tickets

An event confirmation email template should tell the buyer what is confirmed, how many places the order covers and where to find their admission details. Choose the wording from the order's actual state. Someone waiting for a payment check needs a different next step from someone whose tickets have been issued.

Alongside the workshop ticket sales checklist, use the four versions below as wording to adapt or as a checklist for the messages your provider already sends. Replace every bracketed field and remove unused lines. The opening sentence must agree with the current order.

Choose the message from the order record

Open the order before choosing a subject line. Check payment, admission and quantity separately. A received registration form does not establish that payment succeeded, and an email delivery problem does not establish that the purchase failed.

Verified situation Version First message to the buyer
Payment accepted and admission issued Paid Your purchase is confirmed; here is ticket access
A free place has been issued Free Your place is confirmed; no payment is required
An active reservation awaits payment confirmation Pending Your reservation is awaiting confirmation; here is the next action
One buyer holds several issued admissions Multi-ticket Your order covers this many people; check how each person gets in

For pending orders, check what the chosen service permits at the door. The pending example below assumes admission is withheld until payment has been confirmed. Use it only where that matches the provider's behavior. The bank-transfer reservation guide covers hold deadlines, payment matching and expiry in detail.

Collect the fields before writing

Prepare an approved event record with the full date, start and finish, venue address, entrance and organizer contact. Label doors time separately if it differs from the event start. State the time zone when readers could interpret the time differently. Keep the same details on the event page and in the confirmation.

The order supplies the buyer's name, reference, ticket type, quantity and current status. A ticket-access destination must come from that order. Write down who maintains fixed event details and which fields the sending service fills automatically. A colleague should be able to trace a wrong date to its source rather than correct each email by hand.

Eventbrite's confirmation-email guide includes the event time, venue, ticket quantity and order information among the details organizers should supply. Use your actual event and purchase terms when filling those fields. Remove any receipt line unless you can explain where the buyer really receives that document.

1. Paid admission confirmation

Use this after checking that payment succeeded and the expected admissions exist. If the provider already sends a paid confirmation, inspect that message before adding another email that repeats it.

Subject: Your tickets for [event name] on [full date]

Hi [first name],

Your purchase for [event name] is confirmed.
Order reference: [reference]
Tickets: [quantity] x [ticket type], admitting [people covered] people.
Payment received: [amount and currency].

View your tickets: [private access destination from this order]
Event: [full date], [start] to [finish], [time zone].
Doors open: [doors time].
Venue: [venue name, full address and entrance].
Please bring [required item already stated before purchase].

For an order question, contact [monitored contact] and quote [reference].
[Organizer name]

Check whether the recorded amount includes all charges and use the wording that matches it. If the provider supplies a receipt separately, add its verified delivery location without describing this email as a receipt. Keep the ticket link private when asking someone else to review the wording.

2. Confirmation for a free place

A complimentary guest or a participant in a free session still needs a clear quantity and an admission route. “Free” should remove the payment task while preserving the practical arrival details.

Subject: Your place at [event name] on [full date] is confirmed

Hi [first name],

Your registration for [event name] is confirmed.
Confirmed places: [quantity].
No payment is required for these places.
Reference: [reference]
Admission details: [private access destination from this order]

When: [full date], [start] to [finish], [time zone].
Arrival: [doors or agreed arrival time].
Where: [venue name, full address and entrance].
Please bring [required item, if any].

If you cannot attend, contact [monitored contact] using [reference].
[Organizer name]

Match the subject to the quantity: “Your places” for more than one person. A provider may offer its own quantity formatting. Check that the free confirmation has no leftover instruction to pay, and that any ticket supplied is the one issued for this participant. The ticket-type worksheet explains how guest places count toward event capacity.

3. A reservation awaiting payment confirmation

Keep the pending state in both the subject and the opening sentence. This short message points to the reservation's existing payment instructions. It does not replace the full instructions or create a new deadline.

Subject: [Event name]: reservation [reference] awaits confirmation

Hi [first name],

Your reservation for [quantity] places is awaiting payment confirmation.
Event: [full date], [start time, time zone], [venue].
Reservation reference: [reference].
Current payment action: [the exact action required for this order].
Payment instructions: [private reservation destination].
Your places are held until [full date, time and time zone].
Admission details will follow after payment is checked and confirmed.

If you have already paid, send [required reference] to [private contact].
If the hold has expired, contact us before making a payment.
[Organizer name and monitored contact]

If the buyer has already supplied evidence and is waiting for the organizer, the current action might be “We are checking the transfer reference you sent.” Asking that buyer to pay again would misstate the next step. Recheck the active reservation and its deadline before resending a saved message.

4. One buyer, several tickets

The purchaser and the people entering may be different. Ticket Tailor's event-confirmation documentation says its event confirmation goes to the buyer rather than the attendee emails collected for individual tickets. Check your provider's delivery arrangement before assuming every guest received instructions.

Subject: Your [quantity] tickets for [event name] on [full date]

Hi [buyer first name],

Order [reference] is confirmed for [quantity] admissions.
Ticket type: [type and what each admission covers].
Private ticket access: [destination from this order].

The event runs from [start] to [finish] on [full date, time zone].
Arrive at [arrival time], [venue address and entrance].
For this order, [verified instructions for guests arriving separately].
Please check the admission details for every person before sharing them.

For a missing ticket or a guest change, contact [monitored contact]
and quote [reference].
[Organizer name]

Fill the separate-arrivals line with a process you have tested. If an order page exposes all tickets, forwarding its link gives the recipient access to the whole order. Where supported, use individual ticket sharing. Otherwise ask the organizer how to arrange separate arrivals. Avoid sending the same admission credential to several people and assuming each copy provides another place.

Replace placeholders with a checked example

Use a fictional order to check the wording before inserting real buyer information. For example, order DEMO-317 contains three issued admissions for a printmaking session on 18 November 2026, 18:00 to 20:00, Jerusalem time. Doors open at 17:45. The venue field is “Example Studio, 12 Sample Street, courtyard entrance.” These are test details, not a real advertised event.

The multi-ticket subject becomes “Your 3 tickets for Printmaking evening on 18 November 2026.” The first line names three admissions. The arrival instruction says 17:45, while the event line still says 18:00. A dummy label such as PRIVATE-ORDER-317 marks the access field during text review; replace it with the provider's real test-order destination only in the supported test process.

Create a separate pending example with its own reference and two places. Its subject must say it awaits confirmation. Its body must not inherit “payment received” or the first example's ticket access. Keep these examples separate so an edit to one template cannot quietly turn a reservation into a purchase confirmation.

Test the rendered message on a phone

Send through the provider's supported test or preview process and read the actual result. A draft in a document cannot show whether a field is unsupported, a link was omitted or a long venue name broke the layout. Review each of the four states with a long name and full address.

  1. Check the subject and first visible lines for the correct status and event.
  2. Compare date, start, arrival and quantity against the source records.
  3. Open private access from the intended buyer's test message and verify the right order.
  4. Confirm that a free place asks for no money and a pending message promises no issued admission.
  5. Test the actual route for a multi-ticket buyer's separately arriving guests.
  6. Open the help route and verify that someone monitors it during sales and on event day.

For a missing message, check the existing order and use the provider's supported recovery or resend route. Keep a delivery failure separate from the admission state. The door checklist covers what to investigate when a buyer reaches the entrance without usable ticket access.

If you plan to manage the event with Skedful, contact the team with the event date, country, quantity needs and payment method to confirm availability and the buyer messages provided. Check which fields and template changes are supported before adapting the messages. Save the approved wording beside each tested order state and name the person responsible for updating event details before sales open.

About this article

Skedful is responsible for this blog.

Worked examples and sample calculations describe hypothetical scenarios. When an article cites research or customer results, follow the source for its context and limits.

Found an error? Send us the article link and the passage that needs a correction.

Report an error to Skedful

Reminders come with every Skedful plan, on a schedule you set once. PricingSkedful vs Fresha vs Booksy