Event email subject lines: examples for each stage of ticket sales

Good event email subject lines tell people which event you're talking about, what's changed and why they might want to open the email now. Start with the buyer's situation: an early announcement needs a reason to care, a ticket launch needs a clear on-sale message, and a price deadline needs the actual deadline.

So you're selling tickets, you've got an email ready, and you're staring at the subject field. You can explain the whole event in the body. You've got much less room to earn someone's attention in their inbox. What do you put there?

The useful answer depends on who gets the email. Someone who came last time needs a different message from someone who has never heard of you. Someone who already bought a ticket needs to know when the doors open. Sending them another "last chance to book" email makes you look like you haven't noticed their purchase.

This guide gives you subject lines for the announcement, presale, public launch, quieter sales weeks, deadlines, checkout reminders and the next event. It also covers the emails buyers receive after paying, because those messages shape whether they'll trust your next invitation. The examples use fictional events. Replace the details with things you can actually promise.

Choose the reason to send before you choose the words

The first thing you want to do is finish this sentence: "I'm emailing these people because..."

Perhaps tickets just went on sale. Perhaps you've confirmed a speaker who answers a question your workshop audience keeps asking. Perhaps the early price ends tomorrow. Those are useful reasons. "We haven't sent anything this week" leaves you searching for excitement that the email doesn't contain.

Write down who receives the message and what you want them to do. If it's a launch, the action might be buying a ticket. If it's an announcement before sales open, the action might be checking the date or joining a list. A door-time update should help an existing buyer arrive at the right time. You can then write a subject that points towards that action.

Keep the event name where it helps recognition. An established series can use its short name. A new event may need its format or location too. "Fieldwork is back" means something to returning buyers. "Fieldwork: a Saturday photography workshop in Bristol" gives a new reader enough context to decide whether to care.

You don't need to fit the whole ticket page into the inbox. Pick the detail that matters for this send and put the supporting information in the preview text, also called the preheader. That's the short line many inboxes show beside or beneath the subject. Treat the two as a pair rather than repeating yourself.

For example, a subject could be "Fieldwork tickets open Friday". Its preview could be "Join the Bristol workshop on 14 November. Booking starts at 10am." The subject carries the news. The preview explains the date and place.

Before tickets open: help people recognise the event

Your announcement has a modest job. Give someone enough information to decide whether this event belongs in their plans. If they can't buy yet, say when they can or what they can do in the meantime.

Useful announcement subject lines include:

• "Fieldwork returns to Bristol this November"

• "Save 14 November for your next photography workshop"

• "Night Shift is back at the Foundry"

• "A new Sunday supper club in Leeds"

• "Your next Makers Assembly is on 21 March"

• "The autumn programme is here"

The first example fits a returning audience. The second fits someone interested in photography who may not recognise the series name. Neither needs "huge announcement" to make the news understandable.

Use the body to confirm the event date, location, format and ticket timing. Don't make readers scroll through a personal story to discover that the event happens in another city. If the venue is still unconfirmed, be clear about what is settled and what isn't. You can announce a city and date without pretending the rest is ready.

A waitlist or launch notification email can use:

• "Want first notice when Night Shift tickets open?"

• "Join the list for Fieldwork's November workshop"

• "Makers Assembly booking opens next week"

• "Tickets aren't open yet. Here's the date to save"

Only describe access as priority if joining actually gives people earlier access or a meaningful advantage. A notification sent at the same time as your public announcement is a notification. Buyers can understand that perfectly well.

The promise also needs to work after the open. If the subject says "The autumn programme is here", the programme should be in the email or one clear click away. An email that just tells people to keep an eye on your social channels hasn't delivered that promise.

For an unfamiliar event, a concrete activity often works better than your chosen brand name. "Learn to photograph Bristol after dark" gives the reader something to picture. Once people know the workshop, you can rely more on Fieldwork. Our guide to building an event brand people recognise explains how that familiarity develops across editions.

Presale: say who gets access and what that access means

Presales work best when the recipient understands why they're receiving the offer. A returning buyer should be able to see that their earlier purchase matters. Someone who joined a presale list should get the access they signed up for.

Try these subject lines when the audience really receives earlier booking:

• "You can book Night Shift before the public sale"

• "Fieldwork presale opens tomorrow at 10am"

• "Your Makers Assembly presale link is inside"

• "Returning guests get first booking for Sunday Table"

• "Night Shift presale closes Thursday"

• "Your early access to the November workshop starts today"

Avoid using "exclusive" for an offer that anyone can access through a public link. And don't imply that the recipient has a reserved ticket unless you've actually reserved one. "Your ticket is waiting" can sound like an allocation, particularly when capacity is tight.

Here's a subject and preview pair you could use:

• Subject: "You can book Night Shift before the public sale". Preview: "Presale opens today. Public booking starts Friday at 10am."

• Subject: "Fieldwork presale opens tomorrow at 10am". Preview: "Your booking link arrives in this inbox before the public launch."

• Subject: "Returning guests get first booking for Sunday Table". Preview: "Reserve for the November supper before booking opens to everyone."

Notice how the preview makes the advantage specific. Earlier access doesn't automatically mean a discount. If the presale has the same price as public booking, you don't need to apologise for it. Getting a choice of dates or seats can matter to a returning customer.

You do need to make the mechanics clear. Is the link live now? Does the buyer need a code? When does public booking start? Is there a separate allocation? Put those details near the top of the body. If access ends at a set time, include the time zone where the audience might otherwise be uncertain.

Here's what's useful about sending a presale to past buyers: you're talking to people who already know what an evening with you feels like. You can refer to that shared experience without writing a fresh sales pitch. "You joined us at the Foundry in June. November booking opens for you today" is enough context.

The list still needs the right marketing permissions. Previous attendance doesn't give you unlimited permission to send promotions. In the UK, the ICO's direct marketing guidance explains the rules around electronic marketing. Check the rules that apply to your audience before choosing the recipients.

For more on the audience decision, see how to sell tickets to past attendees. A thoughtful subject line helps once you've chosen the right people to receive it.

Public launch: make buying the obvious next step

When tickets are available, say so. Someone scanning an inbox shouldn't have to interpret "It's happening" or "The wait is over" to find out whether you've announced a date or opened checkout.

Start with these:

• "Night Shift tickets are on sale"

• "Book your place at Fieldwork this November"

• "Sunday Table booking is open"

• "Makers Assembly tickets open today"

• "Tickets for the Foundry show are available now"

• "Choose your seat for the November performance"

If the event name is unfamiliar, add a useful reason to go:

• "Book a hands-on photography workshop in Bristol"

• "Sunday Table: November supper bookings are open"

• "Learn to price your work at Makers Assembly"

• "Night Shift: a live electronic night at the Foundry"

These versions make different promises. Choose the one your event actually delivers. A workshop subject that promises a skill should lead to a programme that teaches it. A performance subject can lead with the performer if that is the main reason people buy.

Keep pricing references precise. "Tickets from $25" needs a genuinely available ticket at that price and clear information about any applicable charges. If a lower-priced ticket has a narrow eligibility rule, don't make every recipient think that price is available to them. "Student tickets available" and "Tickets from $25" can create very different expectations.

A launch email should also acknowledge practical buying decisions. A potential attendee might need to ask a friend, check a work shift or arrange travel. Give them the date and location alongside the reason to attend. A clever subject can't rescue an event page that hides the information people need before paying.

Choose one primary booking link in the body. If there are several ticket types, the page can help buyers compare them. You don't need four competing buttons before you've explained the event.

During the quieter weeks: send a new reason to consider buying

Sales have slowed. You still have tickets available. It's tempting to send the same launch email with a louder subject. Before you do, ask what has changed for the reader.

A confirmed performer, a programme detail or an answer to a common buying question can give the email a clear purpose. Use the subject to name that news:

• "Lena Ortiz joins the Night Shift line-up"

• "What you'll make at Fieldwork's November workshop"

• "Your Sunday Table menu is ready"

• "Which Makers Assembly session is right for you?"

• "Coming to Night Shift with friends? Start here"

• "What's included in your Fieldwork ticket"

The names and events here are fictional. The point is to use the actual performer, activity or buying question, rather than fill the subject with "unmissable experiences".

Choose news that changes someone's decision. A new supplier behind the scenes might matter greatly to you and mean little to the buyer. A published menu may help someone decide whether the supper suits them. A workshop outline may answer whether the session is too advanced.

If people keep asking whether materials are included, make that the email. A subject such as "Your Fieldwork ticket includes the materials" gives a hesitant buyer a useful answer. The body can explain what's provided, what to bring and how the session runs. You can link to booking once you've resolved the question.

When you use a testimonial, get permission and quote it accurately. A specific comment about the experience is more useful than a vague claim that everyone loved it. Don't invent a customer voice to make a subject feel warmer. If you don't have a suitable quote, describe a real programme detail instead.

Be careful with social proof in the subject. "Everyone's booking" doesn't tell people much and may overstate your sales. "Saturday's early release has sold out" states something you can verify. If later tickets remain available, explain that in the preview and body so the recipient doesn't assume the whole event is full.

Price deadlines and limited availability: tell the truth precisely

Urgency belongs in a subject when something genuinely changes. A ticket price goes up at a stated time. A sales release closes. A particular session has very few places left. The reader needs enough detail to understand what they'll miss by waiting.

For a scheduled price change:

• "Night Shift early tickets end tomorrow"

• "Book Fieldwork before the price changes Friday"

• "Makers Assembly's early price ends at 6pm"

• "Last day for Sunday Table's launch price"

For a release or booking deadline:

• "Night Shift presale closes tonight"

• "November supper bookings close Thursday"

• "Fieldwork booking closes tomorrow at noon"

• "Last day to book the Saturday workshop"

For verified availability:

• "Only the afternoon Fieldwork session has places left"

• "Night Shift VIP tickets have sold out"

• "The final Sunday Table sitting is now booking"

• "A few places remain for Saturday's workshop"

A quantity can be helpful, but think about the gap between sending and reading. "8 tickets left" may be true when you schedule the email and wrong when it arrives. Check availability close to the send. Where stock changes quickly, a less exact subject with a live booking page can age better.

Don't write "Last chance" if another planned release opens tomorrow. Don't extend an advertised deadline casually after telling buyers it was final. Sometimes plans change for a real reason. Explain the change when it does, instead of acting as though the earlier deadline never existed.

A price deadline should match your ticket settings. Loopyah's ticket release guide covers staged releases such as early tickets and general admission. Set the release correctly, then write the email around that actual change. The subject, preview, email body and checkout should agree.

If your audience spans time zones, a deadline such as "midnight tonight" needs more care than it first appears. Use a clear date and local time in the body. The subject can say "Early tickets end Thursday" while the preview names "22 October, 11:59pm UK time". Make sure those details describe the same deadline.

Misleading subjects also carry a legal issue. The FTC's US CAN-SPAM compliance guide says commercial email subject lines must accurately reflect the message. That is a good operating rule wherever you sell tickets. If the email doesn't contain the offer or news the subject promises, rewrite it.

Checkout reminders: help someone finish without pretending they bought

A buyer starts checkout and leaves. You don't know why. They might have been interrupted, encountered a payment problem or decided against the event. A reminder should make returning easy without inventing an explanation.

Possible subject lines include:

• "Still thinking about Night Shift?"

• "Finish booking your Fieldwork place"

• "Need another look at Sunday Table?"

• "Your Makers Assembly booking isn't complete"

• "Here's the link to return to Night Shift booking"

Only use "Your seats are reserved" if the seats remain held for that person under a real reservation policy. Only use "Your tickets are still waiting" if the body makes availability clear and avoids implying an indefinite hold. A checkout session is not proof of ownership.

The body can acknowledge the incomplete booking, provide a return link and explain where to get help. Keep the language calm. "Something went wrong with your payment" is an assumption unless you know that happened. "Your booking wasn't completed" states the situation.

Check that people who have since bought don't receive the reminder. Loopyah's event email tools describe checkout reminder automations that can end when someone buys. That matters more than trying ten versions of the word "waiting". Once a customer pays, the message they need changes.

Use this type of email only through a process that respects the relevant permission and sending rules. Don't treat an abandoned checkout as a blanket invitation to put someone into every promotional campaign you run.

You also don't need to open with a discount. If the buyer was interrupted, a clear route back may be enough. If you reduce the price immediately, you're giving away revenue before you know why the booking stopped. Any offer should have a deliberate commercial purpose and clear conditions.

After purchase: make the subject useful to a ticket holder

A confirmation subject should be easy to find later. The buyer may be searching their inbox while arranging travel or standing outside the venue. Event name and booking information are more useful here than a playful slogan.

Try:

• "Your Night Shift booking is confirmed"

• "Your Fieldwork workshop tickets"

• "Sunday Table booking confirmation for 14 November"

• "Makers Assembly: your ticket and booking details"

Don't say "confirmed" if payment or approval is still pending. Write "We've received your booking request" when that's the actual state. The body should explain what happens next and whether the customer needs to act.

For practical reminders and changes:

• "Night Shift tomorrow: doors, tickets and travel"

• "What to bring to your Fieldwork workshop"

• "Sunday Table starts at 7pm on Saturday"

• "Night Shift door time has changed to 6:30pm"

• "New venue for your Makers Assembly booking"

An important change belongs at the start of the subject. "A quick update" hides information the attendee may need to act on. Put the changed detail in the subject and explain the consequences near the top of the email. If the venue changes, tell people where to go and how to get help.

Keep promotional offers separate from essential event information. A person who opted out of marketing still needs relevant updates about the event they purchased. Loopyah's email product page describes distinguishing event updates from promotions and selecting recipients accordingly. You write the message; the sending system handles the eligibility checks it supports. Keep the content consistent with the message's purpose.

Our event confirmation email template covers the booking details to include after purchase. For this subject line, the main test is simple. Could the customer find the email quickly when they need their ticket?

After the event: make the next invitation feel connected

Once the event ends, you can thank people, ask a useful question or invite them to a relevant next date. Those are different emails. Choose the subject around the actual message instead of putting all three purposes into one vague "What a night" send.

Examples include:

• "Thanks for joining us at Night Shift"

• "How was your Fieldwork workshop?"

• "Your Sunday Table feedback would help us"

• "Night Shift returns on 12 December"

• "Your next Fieldwork workshop is open for booking"

• "First booking for the next Makers Assembly"

Be accurate about attendance. If you only know someone bought a ticket, don't write a personal opening that assumes they came. They may have missed the event or transferred their ticket. Where attendance data is available, use it to choose who receives an attendance-based message.

A feedback email should explain what you're asking and make responding manageable. A next-event email should say why this event is relevant. Someone who booked a beginner workshop may need a different invitation from a repeat attendee who wants a more advanced session.

Don't use "first booking" merely to make a standard launch sound personal. Give past attendees real earlier access if that's the promise. And check that the next event is ready to buy before scheduling the email. A warm invitation that lands on a broken checkout wastes the goodwill you earned at the event.

Edit the subject and preview together

Read the inbox version before reading the body. That means sender name, subject and preview together. Does a recipient know who's writing? Can they identify the event? Is there a reason to open that matches what's inside?

A clear sender name helps the subject do its job. Keep it recognisable across sends. If buyers know the event as Night Shift, an unexplained personal name may make the email harder to place. You can use a human sender where the relationship is real, but don't make customers guess who you are.

Google's email sender guidelines call for accurate subjects and sender information. They also warn against using "Re:" or "Fwd:" when a message isn't a real reply or forward. You don't need a fake conversation to earn an open.

There isn't one magic subject length that works in every inbox. The visible space changes with the device, app, sender name and preview layout. Put the useful detail early, then check a test email on the devices your team uses. If the end gets cut off, will the remaining words still make sense?

Compare "A little something we've been working on for your next Saturday" with "Fieldwork tickets open Saturday". The second gives the reader the news before the inbox runs out of room. You can keep warmth in the preview and body without hiding the point.

Use plain words. "General admission opens Friday" works for buyers familiar with ticket releases. "Standard tickets open Friday" may be clearer for an audience that doesn't use ticketing language. The W3C's accessible writing guidance recommends clear, concise content. Apply that approach to the inbox too.

Check any personalisation with a test contact that has no first name. A broken greeting can make a thoughtful email look careless. Using someone's name also doesn't make an irrelevant offer relevant. Start with their relationship to the event, then decide whether a name adds anything.

Before settling on a subject, try rewriting one weak version. Suppose your team suggests "Something exciting is coming" for the workshop launch. Ask what the customer needs to know. Tickets are available, the activity is night photography, and the event happens in Bristol. "Book your Bristol night photography workshop" now gives a reader a reason to open. The preview can carry the date and explain that materials are included.

Try the same exercise with "Don't miss out!" for a price reminder. What exactly changes, and when? If the early price ends Friday, "Fieldwork's early price ends Friday" is a clearer starting point. You can explain the later price in the body without squeezing every detail into the subject.

Keep an ear on the event's own voice while you edit. A supper club can sound warm and personal. A specialist conference may need to name the topic directly. Neither has to sound like a generic sales campaign. Read the draft as though a regular customer had asked you what's happening next.

Finally, ask a teammate to read only the inbox version before sending it and tell you what they expect inside. If they expect a confirmed booking but you've written an invitation, you've found a problem before a customer has. Correct the subject or preview, then repeat the check. It's a useful way to catch ambiguity when you've been staring at the same email all afternoon.

Test the buying reason and review the sales

If you test two subjects, make the difference worth learning from. You could compare an event-name launch subject with a skill-focused version. If your sending tool supports it, randomly split one eligible audience between the versions. Keep the body, offer and timing comparable so you're mainly testing the subject.

For Fieldwork, the comparison might be:

Version A could be "Fieldwork tickets are on sale". You're asking whether recognition of the series leads people back to booking.

Version B could be "Book your Bristol night photography workshop". You're asking whether naming the activity and place gives readers a stronger reason to consider it.

Treat a small result cautiously. A handful of purchases doesn't establish a permanent rule for every event. Record what happened, try the useful idea again when the context fits and avoid declaring that one phrase always wins.

Look beyond reported opens. Apple says Mail Privacy Protection prevents senders seeing whether a message was opened. That makes open reporting an imperfect way to judge reader behaviour. Clicks and completed purchases give you more relevant information about a ticket-selling email, though neither proves every sale was caused by the subject alone.

Loopyah's campaign reports connect clicked emails with ticket purchases through its checkout. Use that reporting to examine what the campaign sold, while remembering that the customer may also have seen an ad, spoken with a friend or attended your previous event. The subject is one part of that decision.

A lively subject that brings curious clicks without purchases may be pointing at the wrong promise. A quieter subject that attracts people who understand the event may serve you better. Read the subject alongside the landing page before deciding which words to repeat.

Keep a short record of the audience, sales stage, subject, preview, offer and result. That gives your next campaign somewhere sensible to start. Keep it useful.

Before you send the next ticket email

Choose one real reason to contact that audience. Write a subject that names it, then use the preview to add the detail that helps someone decide. Read the body to check you've delivered the promise, and check the booking page to make sure the ticket, price and deadline are correct.

Then look at the recipients. People who bought should get the message a buyer needs. People receiving a promotion should be eligible to receive it. A good subject sent to the wrong audience still creates a poor experience.

For your next campaign, start with the examples for the stage you're actually in. Replace the fictional event details, read the result aloud and send yourself a test. If it sounds like something you'd say to a customer who asked about the event, you're much closer to a subject worth sending.