Event confirmation email template: what to send after a ticket purchase

An event confirmation email should tell a paid-ticket buyer that their purchase succeeded, what they bought, where to find their tickets and when and where to use them. Put the ticket link and essential event details first, then give them a clear way to get help. Your ticketing platform should handle the purchase confirmation automatically; your job is to check that the buyer gets a complete, accurate message.

So someone has just paid for your event. They're probably checking their inbox, wondering whether the tickets are there and whether their friend needs a separate one. This is the first experience they have of you after handing over their money. Make it easy.

Below you'll find a reusable event confirmation email template, versions for different paid events and a practical test you can run before opening sales. These are examples of what a buyer should receive. Use them to review your platform's confirmation or, where editing is supported, write the message. They are not instructions to manually email every buyer.

Start with this event confirmation email template

Use the fields that apply to your event and remove the rest. The ticket destination must come from the actual order. Never paste another buyer's ticket link into a reusable message.

Subject: Your tickets for [Event name] are confirmed

Hi [First name],

Your purchase for [Event name] is confirmed.

Your order: [Quantity] x [Ticket type]

Order reference: [Order reference]

[View your tickets]

When: [Full date], [event start time], [time zone]

Doors open: [Doors time], [time zone]

Where: [Venue name], [full address]

Entry: [Verified instructions for showing the ticket at the correct entrance]

Your receipt: [Verified location of receipt or payment summary]

Need help with your order? Contact [support destination] and include your order reference.

See you there,

[Organizer name]

The words in square brackets are instructions for the person setting up the message, not text to send to buyers. Replace them with supported order fields or verified event information. If you can't provide a receipt link, explain where the receipt actually arrives. If your venue has no separate doors time, leave that line out.

Notice how little promotional copy this needs. Someone who has already paid wants their tickets and the details that make them usable. A short greeting gives you room to sound human without pushing the purchase information down the page.

For Loopyah events, the ticket confirmation links straight to the buyer's QR tickets. We also send tickets and receipts on your behalf. Check that experience before building an extra email that repeats it. Use these templates to check what the buyer receives. Change only the fields your platform lets you edit, and keep the automatic ticket delivery doing its job.

Write the message around the buyer's next questions

The first question is whether the order went through. Answer it in the opening sentence using the actual purchase status. A successful payment deserves a clear confirmation. A pending payment needs a pending message, with an explanation of what happens next. Don't use the same wording for both.

Next comes the purchase itself. State the event name, ticket type and quantity. If the buyer chose a particular date, session or seat, show that selection where the system supports it. Someone booking a Saturday session needs to see Saturday, not just the name of a weekend event.

Then make tickets easy to find. The main link should open the buyer's tickets or the verified route to them. Test it as a buyer. An attractive button that opens your home page creates another job for someone who has already completed checkout.

After that, give the event details in a form people can scan. Use a full date rather than a numerical date that readers could interpret differently. Write the venue name and address together. If two entrances serve different parts of the event, explain which one this buyer should use.

Finally, tell them how to resolve a problem. A buyer should not have to search your social accounts to ask why their order shows one ticket when they expected two. Give them the support route your team actually monitors, and explain which order reference helps you find the purchase.

You can still sound excited. "See you there" belongs at the end. A paragraph about an unforgettable night belongs on the event page, where someone is deciding whether to buy. In a purchase confirmation, enthusiasm works best when it accompanies useful information.

Choose a subject people can find again

Use the event name and a plain description of the message. "Your tickets for River Room Sessions are confirmed" tells the buyer what arrived and gives them useful words to search later. The sender should be recognizable too. If your organizer name differs from the event brand, check whether the combination will make sense to someone who has just bought.

Avoid a subject that sounds like another promotion. "You're in for something special" makes people open the message to discover what it concerns. That is unnecessary uncertainty immediately after a payment.

Keep the preview text useful if you can edit it. It can introduce the ticket link or the event date. Don't let a long logo description, empty greeting or browser-view instruction occupy the space where purchase information could appear.

Keep confirmation, receipt and ticket information clear

An order confirmation says the purchase succeeded and identifies the order. A receipt records the payment. A ticket provides the information used for entry. Your platform may put these together or deliver them through connected messages and pages. What matters is that the buyer knows where each one is.

Don't tell people "your tickets are attached" unless they really are. If the email links to a ticket page, say "View your tickets." If a separate receipt follows, say that only after checking the actual behavior. People take these instructions literally, especially when they are trying to enter the venue.

A payment summary also needs to reflect what the buyer paid. If you include ticket prices, fees, discounts or taxes, use the actual order data. Copying a single sample price into a general template is an easy way to make discounted orders look wrong. The total on the email should agree with the receipt and purchase record.

Treat the order reference as a way to find the purchase, not as an assumed substitute for the entry ticket. If your door staff scan a QR ticket, explain that route. If another process applies, write the verified process. Don't leave staff and buyers to decide on the day whether a payment email is enough.

For Loopyah buyers who need the payment record again, the ticket receipt guide explains the signed-in route through My Tickets, ticket details and the receipt option. If someone needs their receipt again, send them that guide and explain that they'll need to sign in. Tell them where to find the payment record rather than making them search the confirmation for an attachment.

There is also a privacy reason to keep these destinations clear. A receipt can contain purchasing information that a buyer doesn't need to share with everyone in their group. Before telling people to forward an entire confirmation, find out whether your system offers a supported way to distribute individual tickets and what that action exposes.

An add-to-calendar link, when available, is a convenience. It should describe the right event time and place. It does not replace ticket access or prove payment. Buyers should still know which link opens the item they need at the entrance.

Use a complete general admission example

Here's a filled example for a fictional indoor music event. The event, buyer, location and order are invented to show the structure. The example assumes the venue accepts the QR tickets reached through the order's ticket link. It does not describe a real Loopyah order or a universal entry policy.

Subject: Your tickets for River Room Sessions are confirmed

Hi Maya,

Your purchase for River Room Sessions is confirmed.

Your order: 2 x General admission

Order reference: RR-1048

[View your tickets]

When: Saturday 14 November 2026, 7:00 PM, Sydney local time

Doors open: 6:30 PM, Sydney local time

Where: River Room, 18 Example Street, Sydney

Entry: Open your ticket link and have both QR tickets ready at the main entrance. This order contains two general admission tickets; seats are not assigned.

Your receipt: You'll find the payment details in the receipt sent with your order.

Need help? Use the organizer support contact shown on your order and include RR-1048.

See you there,

The River Room Sessions team

The ticket button here is a label for the actual order link, not a public link you should reuse. The receipt wording assumes a receipt accompanies the order. Change it if your platform delivers the payment record elsewhere.

Why include the difference between doors and start time? Because "7:00 PM" alone can leave a buyer wondering whether that's when they should arrive or when the performance begins. You don't need a long explanation. Two accurate lines do the job.

Why state general admission? Because a buyer may otherwise read the venue name and assume they have a reserved seat. The confirmation should match what they purchased, including any important limitations already stated during booking.

Keep entry restrictions visible where they matter. If the event has a confirmed age rule or required identification, state it accurately and consistently with the event page. Don't introduce a new restriction for the first time after payment. If you discover a mismatch, correct the underlying event information and decide how affected buyers should be told.

Adapt the details for reserved seats, workshops and group orders

Keep the main structure. Change the information a buyer needs for this particular purchase. You don't need an entirely different welcome speech for every event type.

Reserved seating

For reserved seating, include the actual seat details where the system supports them. A section name alone may be insufficient if the ticket also specifies a row and seat. Use the same names shown on the tickets and in the venue's signage.

A fictional seat summary might read:

Your order: 2 x Reserved seating

Seats: Circle, Row B, Seats 12 and 13

Entry: Use the entrance printed on your tickets. Your ticket details show the section, row and seat for each attendee.

Don't write "sit anywhere in the circle" if the seats are assigned. Don't tell people to choose seats when they arrive if they already selected them at checkout. These are small copy mistakes with a very visible consequence at the door.

If the venue has special instructions for an accessible entrance, communicate the verified route clearly. Keep personal information out of a generic email. Where a buyer needs individual assistance, direct them to a suitable support contact rather than asking them to reply with private details to a shared group message.

Loopyah's seating charts let buyers select seats. Check that the tickets show the seats the buyer selected and that the entry instructions match the venue's signage. If the confirmation doesn't list seats, make sure its ticket link opens the assignment clearly.

A paid workshop with a chosen session

Workshops often need a little preparation information. Include the part that could stop someone attending correctly, such as the booked session, location or a genuine requirement to bring equipment. Save optional reading and the full agenda for a clearly labelled follow-up when needed.

A fictional workshop summary might read:

Your booking: 1 x Saturday morning printmaking workshop

Session: Saturday 14 November 2026, 10:00 AM to 12:00 PM, Sydney local time

Where: Studio Two, 24 Example Street, Sydney

Please bring: Closed-toe shoes. Materials are supplied.

Entry: Open your ticket link when you arrive at Studio Two.

The preparation line in this example is an invented event requirement. Only include it if it applies to your workshop and was clear during booking. If materials cost extra, the email should agree with the purchase terms rather than suddenly announcing another payment.

A workshop with multiple sessions also needs careful testing. Buy or preview the morning option, then check whether the confirmation actually shows morning. An event-level start time can be misleading when several different bookings share the same event name.

One person buying for a group

A group order needs to make quantity and ticket handling clear. The buyer may be the only person who receives the purchase message, while several people intend to attend. Don't assume the platform automatically emails every attendee or that forwarding the confirmation transfers ownership.

A portable wording pattern is:

Your order contains [quantity] tickets. Open the ticket link to see them. Follow [the platform's verified instructions] if group members need to receive or use their tickets separately. For help with this order, use [support destination] and include [order reference].

Replace that middle instruction with the actual process. If no separate distribution option is available, explain the arrangements your system and door team can support. Don't promise wallet passes, ticket transfer or individual attachments without checking them.

On Loopyah, ticket transfer requires the organizer to enable it. The recipient accepts the transfer through the supported process, which includes signing in. If you use that option for your event, explain it accurately. "Forward this email to your friend" does not describe the same action and should not become a substitute instruction.

Decide whether the group needs distribution instructions immediately after purchase or nearer the event. If you include them now, put them after the ticket link and keep them short. The buyer should first be able to see all the tickets in the order, then understand the supported next step for the people attending.

Also test what happens when a group arrives separately. What should the second person show if the buyer has already entered? Your email, ticket access and door procedure should give the same answer. If staff cannot explain the arrangement, the buyer won't be able to either.

Get dates, arrival times and directions right

Event details are often accurate on the sales page and less accurate in the confirmation because someone copied an older date or venue description. Use the current event record as the starting point. Then review the message the buyer actually receives, including any information your template adds separately.

State the time zone when an audience could reasonably be confused. This matters for travelers as well as online events. "Sydney local time" is clearer than expecting every buyer to know an abbreviation. If you use an abbreviation, check it for the actual event date rather than assuming it stays the same all year.

Google explains how Calendar handles event time zones. Use that guidance when checking a calendar item. A buyer viewing a calendar elsewhere may see a converted time. Test the event's configured zone and make the email's venue time unambiguous.

If doors and the programme start at different times, label both. If admission closes at a particular time, only include that rule when it is confirmed and matches the ticket terms. "Arrive early" is much less helpful than an actual arrival instruction.

Directions should identify the place people need to reach. Give the full address and the relevant entrance where necessary. A venue with several buildings may need a room or building name. A maps link can help, but check where its pin lands before sending people there.

Keep changing travel advice separate from permanent purchase details. A confirmation sent months ahead may outlive a temporary parking arrangement or road closure. Put confirmed arrival facts in the order message, then send a targeted event update when you have information that buyers need closer to the date.

If the date or location changes after sales begin, the original confirmation remains in buyers' inboxes. Send an explicit update through your supported attendee messaging and follow the event's change process. Give the revised details and say what the buyer needs to do. A quiet edit to the event page is easy to miss.

Make the email work on a phone and without its images

The buyer may read the message on a phone in a queue. Design for that moment. The ticket link needs to stand out, and the details should remain readable without zooming or deciphering a poster.

Use real text for the date, address and entry instructions. Microsoft's guide to accessible email advises against using text in images as the only way to communicate information. That gives people more control over how essential information is displayed. A decorative event banner can sit above the message, but it should not be the only place the start time appears.

Name links by what they do. "View your tickets" tells the buyer what will open. "Find the venue entrance" tells them why a directions link is useful. The W3C's accessible writing guidance explains why readers need to understand a link's purpose from its text or context.

Avoid putting several competing buttons before the ticket link. A social follow request or offer for another event takes up space at the exact moment the buyer is trying to verify this purchase. Keep the order action dominant and place support information where it is easy to find.

Then test with images blocked. You should still be able to identify the event, purchase, date, location and ticket destination. If the email becomes a logo and an empty rectangle, you've found an actual problem. Fix the essential text before spending more time choosing the banner.

Check the message with a long event name and a long ticket type too. The example that fits neatly on your desktop may wrap badly for a real buyer. The same goes for missing first names. Use the platform's supported fallback where available so the greeting doesn't arrive with an unresolved field.

Send extra event instructions only when they add something

You don't need a second confirmation because you have more brand copy to share. You may need an event information message because the buyer must choose a meal, complete a genuinely required form or read instructions that weren't ready at purchase. Be specific about that difference.

On Loopyah, attendee email tools let you send event communications to selected audiences. Use that capability for relevant follow-up information rather than exporting buyers and creating a manual purchase-confirmation process. Check the available audience filters and message setup for the event you are handling.

An additional message should name the event and the new action. A fictional workshop follow-up could say, "Your Saturday workshop ticket is already confirmed. Please review the preparation instructions before you arrive." Then explain the actual requirement and link to the verified instructions. Don't make people wonder whether they need to pay again.

Keep reminders focused on arrival. A reminder nearer the date can repeat the ticket route, time and location, plus genuinely useful updates. It should agree with the purchase record and any later changes. Our event reminder email guide helps you prepare the arrival message. Check it against the same event details used in the confirmation.

Be careful when adding promotions to order messages. In the US, the FTC explains that CAN-SPAM treatment depends on a message's primary purpose, including how transactional and promotional content are combined. Calling an email a confirmation does not settle its classification. Keep the purchase information prominent and check the applicable requirements in the markets you serve.

You can build enthusiasm without turning the confirmation into an ad. Use the event's name, a friendly sign-off and helpful preparation. The buyer has already said yes. Make the next step easier.

Test the complete purchase before you open ticket sales

A template preview is useful, but it doesn't prove that a buyer can pay, receive the message and open the correct ticket. Use your platform's supported testing or preview process. If a real test purchase is necessary, plan it within the platform's rules and your accounting process.

Start with the simplest order. Follow the route a buyer will use from the event page through checkout. Look at the success message, the destination email address and the confirmation that arrives. Check the purchased ticket type against the ticket itself and the order record.

Keep the event page open beside the confirmation during this check. Compare the ticket's included benefits, any admission conditions and the booked date. If the message promises something the sales page never offered, find out why before leaving it in. If it leaves out an essential restriction, correct the information buyers receive throughout the purchase.

Then test the cases that change the information. For a reserved event, inspect seat details. For a workshop, inspect the selected session. For a group order, inspect quantity and the process for separate arrivals. These checks matter more than trying to manufacture every imaginable combination.

Ask someone who didn't build the event to open the message on their phone. Give them a simple task: find the tickets and explain when and where to arrive. Watch where they hesitate. If they have to ask which of several buttons opens the ticket, change the hierarchy. If they cannot tell doors time from start time, change the labels.

Test the ticket destination before and during the supported entry process. Don't scan or invalidate real customer tickets as a copy review shortcut. Use a test order or another platform-supported method. Your door lead should confirm what staff will accept and what happens if a buyer arrives with only the confirmation.

Finally, test support. Use the route the email names and check who receives the request. Make sure the team can find an order using the details you ask the buyer to provide. A perfectly written support instruction is useless if it points to an unmonitored inbox.

Keep a short record of what you checked and when. Repeat the relevant checks after changing dates, ticket types, seats, receipt arrangements or entry instructions. You don't need to redo every test for a punctuation edit, but a change to what the buyer purchased deserves a fresh look.

Handle missing confirmations without creating another paid order

A buyer saying "I haven't received my tickets" needs a calm, practical response. Begin by locating the purchase through your approved support process. Check the order status and the email address associated with it. A missing email alone does not tell you whether payment succeeded.

If the order is confirmed, use the platform's supported ticket retrieval or resend route. Tell the buyer which event and order you're helping with, and explain how they can access the tickets. Don't ask them to purchase again simply to generate another email.

For buyers using Loopyah, the find your tickets guide describes access through My Tickets and the event page. Use the confirmation's ticket link as the primary route, with the help guide as a fallback. Buying as a guest and finding tickets later are different steps. If the route you're sharing requires sign-in, tell the buyer that before they open it.

When you reply to a confirmed-order query, give one clear next action. For example, say that you have located the order and direct the buyer to the supported ticket-access route. If you need more information first, ask only for the details required by your support process. A long list of unrelated troubleshooting steps can make the buyer think you haven't checked the purchase.

If the order is pending, explain that status accurately and check the payment process. If there is no completed purchase record, investigate before promising entry. The support team should have a way to escalate uncertain payment cases rather than guessing from an email screenshot.

A mistyped address also needs a verified correction process. Follow the platform's identity and order-access rules before sending tickets somewhere else. Don't ask the buyer to post payment details or ticket codes on a public social thread. Move the issue to the monitored support route.

Some messages may be filtered or rejected. Google's email sender guidelines set requirements for senders delivering to personal Gmail accounts. If confirmations repeatedly fail, raise the pattern with the provider responsible for sending them and provide the information its support team requests. Telling every affected buyer to check spam does not resolve a recurring sending problem.

Give door staff a consistent escalation route too. A buyer standing at the entrance may have a valid order but no accessible message. Staff need to know who can check the record and what evidence the approved entry procedure requires. That decision should come from your ticketing and door arrangements, not an improvised promise in the email.

Your next step is to review a real buyer confirmation for your event. Can you see that the purchase succeeded, identify exactly what was bought, open the tickets and understand arrival without asking the organizer? If any answer is unclear, fix that part of the experience before adding more copy. The best event confirmation email gives a paying buyer confidence because everything they need is right there.