· 28 min read
How to Write an Event Invitation Email That Gets RSVPs (+5 Copy Examples)

Your event invitation email should tell someone why the event is worth their time, what a ticket includes and how to book. For a paid event, that last part matters. A reply saying "sounds good" hasn't paid for a seat. Build the invitation around a completed booking, then send useful reminders to people at the right stage. Litmus' 2025 State of Email reports teams earning $10 to $50+ for every $1 invested in email. These are self-reported results from a broad marketing survey, with different companies reporting different returns. They aren't an event-ticket benchmark or a forecast for your invitation. Your own ticket sales and campaign costs are the useful test.
This guide explains how to write an event invitation email, choose who receives it and make the booking journey match the promise. You'll find five adaptable email examples, a worked paid-workshop invitation, a reminder plan and a way to judge whether the campaign helped sell tickets.
The examples cover several event formats because the wording changes with the audience. The underlying decision stays the same. What does this person need to know before they can commit, and does the email answer it?
Why your event invitation email matters
Someone can like your lineup or workshop idea and still postpone buying. They may need to check the finish time, understand the ticket price or decide whether the event suits their experience. Your invitation should answer the questions that prevent a decision. A louder subject line won't fix missing information.
Email also lets you speak to people who already know your event business. A previous attendee doesn't need the same introduction as someone who joined your list yesterday. When you have permission to contact them, that familiarity gives you useful context for explaining the next event.
"Write the invitation so someone can decide whether to attend and understand exactly what booking commits them to."
Start with the booking decision, then work through the message in the order your reader sees it.
What to include in an event invitation email
Subject line: explain the event and the reason to open
Put the information that matters near the beginning of the subject line. Screen size, inbox settings and sender length all affect how much appears, so a character count can't guarantee the whole line will show. Use the preview text to add something useful, such as the date or what's included, rather than repeating the subject. Test the pair in an actual inbox.
Adapt these subject lines to facts you can support:
You're invited to [Event Name] on [Date]
[Event Name] tickets for past attendees presale
[Topic] roundtable for [Job Title], [Date]
[City] founders evening, [Date], tickets from [Price]
Live [Topic] workshop, [Date], recording included
See [Product] at our [Date] launch session
Want to go deeper on email messaging strategy and testing? See our guide on event email marketing strategy for a full framework you can reuse across campaigns.
Sender information: use the name people know
Use the event or organizer name people signed up to hear from. "Maya at [Event Brand]" works when Maya is a real person who handles replies. If most subscribers know the event name, don't hide it behind an unfamiliar staff name. Keep the sender consistent through the campaign and make sure the reply address reaches someone who can answer booking questions.
Personalization: explain why this event suits them
A first name is useful only when it's correct. More useful is a reason the event fits the recipient. A past workshop attendee may want the next level of the course. A local subscriber may care that the venue is close to home. Use information you genuinely hold, and avoid implying a relationship or interest you haven't established.
Need help tailoring your message? Start with these ideas and then refine using the playbooks in our event email marketing strategy article.
Event details: answer who, what, when, where and why
Make the event name, reason to attend, date and booking action easy to find early in the email. Include the venue or online format and the time zone where it matters. The message should still make sense when images don't load. For a paid event, make the ticket commitment clear before sending someone to checkout.
Example header: "[Topic] workshop with [Host] | [Date], [Start and End Time] [Time Zone] | [Venue] | [Total Ticket Price]"
Follow with a button such as "Book a workshop ticket" that opens the matching event page.
Call to action: make the commitment clear
Choose a button label that describes what happens next. "Buy tickets" suits a paid booking. "Register free" suits a genuinely free event. "Request an invitation" suits an approval process. You can repeat the same booking action after a longer explanation, but keep the destination consistent. A clear button also needs enough space around it for someone to tap comfortably on a phone.
Visual design: keep essential details readable
Use your event's branding to make the email recognizable, while keeping the details and booking link as actual text. A poster can support the message, but it shouldn't contain the only copy of the date, price or address. Describe meaningful images with useful alternative text. Check that the text and button labels remain easy to read against their backgrounds.
Mobile layout: check the whole booking journey
Open the test email on a phone, read it without zooming and follow the booking link. Check the event page and checkout as well. An invitation that reads well is only part of the job if the next screen hides the price or makes the buyer complete a difficult form. Use the email clients your audience actually uses when you can identify them.
How to plan the invitation and reminder sequence
Segmentation: separate buyers from people still deciding
Start with people who already hold a ticket, people who have attended before and other eligible subscribers. Buyers need practical information about the event they've booked. People still deciding need reasons to buy. Then make smaller groups when the distinction changes your message, such as city, previous ticket type or workshop level. Don't create extra versions just to change an adjective.
Timing: work backwards from the booking decision
Choose the first send around how much planning the event requires. Travel, accommodation, time off and a group booking need more notice than a local evening event. Pick a send time your audience is likely to find useful, then compare your own results across similar events. There isn't a weekday that guarantees better sales. Treat the reminder schedule below as a starting plan to adapt.
For a broader send plan from save‑the‑date to post‑event follow‑ups, see our event marketing timeline guide.
Clarity: explain the value before adding detail
Begin with what the attendee will do or get, then explain who the event suits and how to book. "Work through your own pricing with a tutor" tells a prospective workshop buyer more than "an inspiring learning experience." Add enough detail to support that promise. If the agenda is long, summarize the parts relevant to this audience and link to the full event page.
Incentives: explain the real deadline
If a ticket release closes on a specific date, say when it closes and what changes afterwards. If a package includes a bonus, explain who qualifies and what they receive. Only claim limited availability when you can verify it. You don't need a discount in every email, especially when the reader still doesn't understand what the ticket includes.
Social proof: use evidence that answers a concern
A specific comment from a previous attendee can help someone judge the experience. Get permission to publish it and explain which event it describes. Use attendee counts only when current and verified, and use company logos only with the right permission. Don't imply that a past guest or quoted attendee is booked for this edition unless they are.
Registration: ask for what the booking needs
Review each required field in the booking form. Keep information needed for the ticket, payment and delivery, and question anything you collect merely because it might be useful later. Baymard's ecommerce checkout research supports reducing unnecessary form work. Apply that principle carefully to events, which may also need attendee names or other information to deliver the booking.
See the research on minimizing form fields from Baymard Institute here. The research concerns ecommerce checkout rather than event RSVPs, so use it as a design principle rather than a prediction of your conversion rate. After booking, provide a confirmation with the event details and access instructions. Test any calendar link you choose to include.
Follow-up: change the message after someone books
Plan sales reminders for eligible subscribers who haven't bought, and practical reminders for ticket holders. Remove new buyers from the remaining sales messages. A webinar join link belongs in the attendee sequence; a "tickets close tonight" message belongs in the sales sequence only when that deadline is real. For example:
About a week before: send non-buyers a useful reason to attend, such as a session explanation, while ticket holders get preparation details if needed.
Before an actual booking deadline: remind non-buyers what closes, when it closes and how to book.
Before the event: send booked attendees the venue, arrival instructions or private online access details.
At the start of an online event: send a join reminder only to people registered to attend, if the format calls for it.
Five event invitation email examples
Use these as copy examples, not as evidence of a tested conversion rate. Replace the placeholders with confirmed facts and choose the booking label that matches your event. Where admission is paid, include the price and what it covers.
Example 1: a paid executive roundtable
Subject: [Topic] roundtable for [Job Title], [Date] | Preview: A facilitated discussion for [Audience], [Ticket Price] per seat
Hi [First Name],
Join [Host] for a small-group discussion about [Specific Problem]. We'll work through [Discussion Question] and compare how participants approach it. This session is for [Audience and Experience Level].
When and where: [Date], [Start and End Time] [Time Zone], at [Venue Name and Address].
Your ticket costs [Total Price] and includes [Facilitation, Materials or Other Confirmed Inclusions]. We have [Verified Capacity] places for this session.
The session includes [Agenda and Timings]. [Facilitator] will lead the discussion, with time for questions about your own situation.
Book by [Actual Booking Deadline]. You'll receive your ticket and [Any Confirmed Preparation Material] after checkout.
Suggested button label: Book admission
If you need to check whether the session is right for your role, reply to this email and [Contact Name] will help.
Example 2: a ticketed networking evening
Subject: Meet [Audience] in [City] on [Date] | Preview: [Total Ticket Price] includes [Confirmed Inclusions]
Hi [First Name], we're bringing [Audience] together for an evening of [Specific Format]. If you're looking to meet people working on [Relevant Problem], this is the session to join.
When and where: [Date], [Start and End Time] [Time Zone], [Venue and Full Address].
We'll begin with [Hosted Introduction Format], then [What Happens Next]. You can come on your own, and [Host] will explain how to join the conversations.
Tickets cost [Total Price], including [Confirmed Inclusions]. [State Any Age, Access or Booking Conditions That Matter].
Suggested button label: Buy a networking ticket
Example 3: an online workshop or webinar
Subject: Work through [Problem] live on [Date] | Preview: [Duration] with [Speaker], [Price or Free Admission]
Hi [First Name], join [Speaker] for a live session on [Specific Outcome]. It's for [Audience] who already [Relevant Starting Point].
Here's what we'll cover:
How to [Specific Task], using [Method or Example]
A live explanation of [Specific Problem or Submitted Example]
[Confirmed Material] you can use after the session
When: [Date], [Start and End Time] [Time Zone]. Admission is [Total Price or Free]. [State Whether a Recording Is Included and When Registered Attendees Receive Access].
Suggested button label: Book the workshop, or Register free when admission is free
Example 4: a charity gala with table bookings
Subject: Book a table for the [Cause] gala on [Date] | Preview: [Table Price] for [Number of Guests], supporting [Program]
Hi [First Name], please join [Organization] for an evening supporting [Specific Program]. [Add a Verified Description of What the Funds Support].
When and where: [Date], [Start and End Time] [Time Zone], at [Venue and Address].
Your table includes [Number of Seats, Meal and Other Confirmed Inclusions]. The evening's program is [Confirmed Program]. Individual tickets are [Available at Price or Not Available].
Tables cost [Total Price]. Book by [Real Deadline] and tell us [Essential Booking Information]. Reply to [Contact] if you need help arranging your group.
Suggested button label: Book a gala table
Example 5: a product launch with a clear admission policy
Subject: Try [Product] at our [Date] launch session | Preview: [Demo Format], questions with the team and [Admission Terms]
Hi [First Name], we're introducing [Product] for people who want to [Specific Job]. Join [Host] to see it used for [Demonstration] and ask the team your questions.
When and where: [Date], [Start and End Time] [Time Zone], [Venue and Address or Online Format]. Admission is [Total Price or Free].
You'll be able to [Confirmed Participation or Demo Activity]. [Explain Any Access Conditions, Equipment Needed or Verified Launch Offer].
Suggested button label: Book admission
Looking for more phrasing ideas? Browse our invitation message examples to fine‑tune tone and style for different audiences.
Common mistakes to catch before sending
Read the invitation as someone who hasn't been in your planning meetings. Look for these problems:
The benefit is vague, so the reader can't tell whether the event suits them.
The subject promises something the email or ticket doesn't deliver.
The sender name is unfamiliar or changes halfway through the campaign.
Important details appear only in an image, making them harder to access.
The email asks for an RSVP even though a paid ticket is required to confirm admission.
Tools that make the invitation easier to manage
Use your existing ticketing and email tools where they already do the job. The useful checks are whether you can select the right audience, test the message, schedule it and see the resulting bookings.
Email creation: use a readable template with editable text, descriptive links and a booking button.
Testing: check the delivered email, its personalization and the full path through checkout.
Reporting: compare delivered messages, clicks, bookings and revenue, with refunds and campaign costs considered separately.
If your contacts and ticket purchases already live in Loopyah, our Email Event Attendees page explains the built-in email builder, purchase-based segments, scheduling and campaign reporting. You can send a test before the campaign goes out. That saves you from rebuilding an attendee list in a separate tool for each send.
For broader context, see the benchmark highlights from Litmus. Use that survey to understand why teams invest in email, then judge your own campaign on completed bookings and the money left after its costs.
Plan Your Next Event With LoopyahStart with the information that makes the ticket worth buying
If you're staring at an invitation that says "You're invited to an unforgettable evening," the first thing to do is ask what someone actually gets. The phrase could describe almost any event. A prospective buyer still needs to know whether this particular evening is worth the ticket, the journey and the time away from something else.
That uncertainty shows up in Loopyah's research. In the Worth It Event Index, a Pollfish survey of 500 US consumers fielded in February 2026, 266 respondents selected "High price for unclear value" when asked what makes an event not feel worth it before buying. That is 53.2% of the sample. Another 205 selected "Unclear details," or 41%. Respondents could choose multiple answers, so these percentages overlap. The survey measures reported concerns, not the effect of changing an email.
| Label | Respondents (%) |
|---|---|
| High price for unclear value | 53.2 |
| Unclear details | 41 |
| Bad or no reviews | 40.2 |
| Weak lineup or program | 36.6 |
| Past negative experiences | 36 |
| Sketchy website or socials | 22.4 |
| Refund concerns | 15.6 |
| Organizational concerns | 9.8 |
| Other | 0.2 |
Source: Loopyah Worth It Event Index, Q14, February 2026, n=500 US consumers. Values are unweighted respondent counts divided by 500, not each option's share of all selections. Multiple answers were allowed. The full report provides the question and methodology.
For your invitation, the practical response is to explain the experience. A workshop ticket might include guided work on the attendee's own project, a materials pack and feedback. A music event might offer a particular artist, a clearly described set and an atmosphere people recognize from your previous editions. Tell the reader which of those things you can actually deliver. You don't have to defend the price with a long inventory of minor extras.
This also helps you decide what to leave out. If the email is selling an evening performance, a long paragraph about the history of your company may delay the information a buyer wants. Keep the host introduction long enough to establish who is responsible, then explain this event. Readers who need more background can find it on the event page.
Write one useful sentence before you write the subject line
Try completing this sentence in ordinary language: "This event is for people who want to [do something specific], and their ticket includes [the experience you provide]." If the result sounds vague, fix the offer or ask the event team for the missing information before writing five versions of a subject line.
For a practical workshop, that could become: "This session is for first-time course creators who want to price their first paid class, and their ticket includes a guided exercise using their own costs." That tells you who to invite, which benefit to lead with and what information the event page needs to support.
You can then explain the limits. Is the session suitable for someone who hasn't chosen a course topic? Will a tutor give individual feedback, or will the room discuss selected examples? Will attendees need a laptop? Details like these prevent an invitation from attracting people the event cannot serve well. Selling a ticket that later needs refunding isn't a useful improvement in campaign performance.
A complete paid-workshop invitation, with the reasoning behind it
Here's a fictional example to show how the parts work together. The event, host, prices and numbers below are illustrative, not customer results. Imagine you run practical classes for local small-business owners and are inviting eligible subscribers to a new pricing workshop.
Subject: Price your next workshop with us on 12 November
Preview: A two-hour guided session, $65 including materials.
Hi [First Name],
If you've picked a ticket price by looking at similar workshops and hoping it covers your costs, this session will help you work through your own numbers.
On 12 November, we're running a guided pricing workshop for people planning their first paid class. Bring your venue, materials and staffing estimates. You'll use them to calculate what you need to charge at different booking levels, with time to ask questions about the assumptions.
Your $65 ticket includes the two-hour session, a printed worksheet and the follow-up worksheet file. That's the full ticket price, including fees. Bring a laptop or a calculator and your current cost estimates. You don't need an existing spreadsheet.
The workshop runs from 6 pm to 8 pm, New York time, at Example Studio, 10 Example Street. Doors open at 5:45 pm. The venue entrance is step-free, and you can reply to this email with access questions before booking.
We're offering 20 places because the tutor will work through questions during the session. The event page explains the format and the cancellation policy before you pay.
Book a workshop ticket
If you're unsure whether the session suits the stage you're at, reply with a little about your class and we'll help you decide.
Why this invitation includes the price
The price is part of the decision. Someone can see what $65 covers before leaving the inbox. In this fictional example it is the full amount, so the event page and checkout must show that same total. If you offer several ticket types, explain the relevant starting price and what it buys, then make the other options clear on the page.
The invitation also explains what to bring. That detail helps someone picture taking part and stops them booking under a false assumption that everything will happen as a lecture. It is especially useful when an event expects attendees to do preparation. Explain that work before they buy, while they can still decide whether the session fits their schedule.
Notice that the capacity claim has a reason tied to the format. In a real email, you would verify that capacity against your actual ticket inventory. You wouldn't turn "20 places in the workshop" into "only two left" unless only two were genuinely available at the time of sending. A scheduled campaign may need its wording checked again before it goes out.
What would change for a returning attendee?
If the recipient had attended your earlier budgeting class, you could open with the connection: "You've already worked through the costs of your class. This session helps you choose a ticket price using those numbers." The rest of the invitation still needs the date, price and booking information. Familiarity with your business doesn't mean someone remembers every event detail.
If you don't know whether they attended, don't claim they did. Use a broader introduction or select a different group. A personalized opening creates extra risk when the underlying information is unreliable, especially if several people share an email address or one buyer purchased tickets for a group.
Who should receive the invitation?
Choose the audience before deciding how many follow-ups to write. A list of contacts can include ticket buyers, attendees, newsletter subscribers, people who asked about a previous event and people who have opted out. Those are different relationships. The fact that you hold an address does not, by itself, tell you which marketing messages the person should receive.
For an invitation promoting a new paid event, use the audience eligible to receive that promotion. Handle the rules that apply to your audience and market through your established consent process. Keep the unsubscribe option visible. If the campaign includes a partner's audience, confirm the arrangement rather than assuming you can upload all their contacts and begin mailing them.
Then check relevance. A previous attendee who lives near the venue and bought a similar event is a reasonable person to prioritize. A subscriber in another country may have little reason to receive repeated reminders about a local class. If you do invite them, explain an actual reason, such as an online option, rather than changing only the greeting.
Stop asking people to buy after they buy
This is an easy mistake when you schedule several emails at once. Someone books on Monday and receives Wednesday's "still thinking about joining us?" invitation because you used an old list. That makes the campaign feel careless and can leave the buyer wondering whether their order went through.
Use current purchase information to exclude buyers from the remaining sales sequence. Loopyah supports email automations that end when someone buys, so use that purchase condition to stop a sales sequence. If you use another setup, check how its buyer exclusions update before scheduling reminders. Test the condition with your own order. Once someone buys, the next useful message should confirm their booking or help them prepare.
Group orders need a little more care. The buyer may be the only contact you can reach directly, while several people hold tickets. Decide which information the purchaser should pass on and whether your event process collects attendee addresses for operational updates. Don't promise that every guest will receive instructions individually unless your system and data support it.
A practical send plan for a paid local event
Here is an illustrative plan for a workshop promoted over several weeks. Adjust it to your booking window and audience. A destination conference will need more lead time; a recurring local show may have an established buying pattern that makes a different schedule sensible.
Start with the invitation when the event page is complete and the tickets it describes are actually available. Explain the session, audience, date and price. Before scheduling it, decide what happens if someone clicks but doesn't book, and what happens when someone purchases. You need a usable answer for both.
A later sales email should add information. For the pricing workshop, you might explain one of the exercises and show what attendees should bring. Someone who ignored the first invitation because the session sounded too advanced now has a reason to reconsider. Resending the original copy with "Don't miss out" at the top hasn't answered that concern.
Send a deadline message when a real deadline approaches. That could be the last date for booking because you need to print materials or confirm catering. State the date, time and time zone. If booking will continue at another price, explain that change accurately. Don't call it the last chance to attend if another ticket release begins the next morning.
For booked attendees, send practical information close enough to the event to be useful. Include the entrance, arrival time, what to bring and a contact for problems. If there's a change, put the changed information at the beginning. A venue move should not appear beneath several paragraphs celebrating the event.
For an online session, the equivalent message should explain how to join, when to arrive and what to do if access fails. Keep private join details in the attendee communications. Don't include them in a general sales reminder where they could circulate beyond the people entitled to attend.
When someone replies instead of booking
A reply can tell you what the invitation failed to explain. If several people ask whether a recording is included, check that the event page and next email answer that question. If they ask about a detail already present, consider whether the wording or layout made it hard to find.
Give the person a direct answer and the appropriate booking link. A helpful reply might say, "Yes, the worksheet is included in the ticket price. You can check the full session details and book here." Avoid implying you've reserved a place when the customer still needs to complete payment. If you do hold tickets manually, make the expiry and confirmation process clear.
Make the email usable when images are blocked
Your invitation should work before the poster loads. Put the event name, date, price and action in editable text. Use the image for something it explains well, such as the event identity or a relevant view of the session, and give meaningful images an appropriate text alternative. The W3C guidance on image alternatives explains how an image's purpose determines the alternative it needs.
This matters for the booking link too. A button labelled "Book a workshop ticket" gives someone more information than a linked image with no useful description. Check the reading order, especially if your template puts several columns side by side. What reads clearly on a laptop can become confusing when those columns rearrange on a phone.
For text contrast, W3C's WCAG guidance specifies at least 4.5:1 for ordinary text and 3:1 for large text, with stated exceptions. Use a contrast checker on the actual text and background colors. A brand color that looks attractive in a large heading may be difficult to read as small text on a colored button.
You should also check the words you use to describe access. Say what you have verified about the venue, such as a step-free entrance, and explain how someone can ask for more information. Avoid a broad promise that an event is accessible to everyone when you haven't established what an individual attendee might need.
Check delivery before changing the copy again
If people aren't receiving the invitation, another subject-line rewrite won't solve the immediate problem. Send a test to real inboxes and check the delivered message. Ask whoever manages your sending domain to verify its setup with your email provider, particularly if you've changed providers or started sending from a new address.
Google's email sender guidelines set authentication requirements for messages sent to personal Gmail accounts, with additional requirements for senders exceeding 5,000 messages a day. Bulk marketing senders must support one-click unsubscribe and include a visible unsubscribe link in the body. Use the provider's setup process and have the responsible person check the applicable requirements before a large send.
Avoid disguising the invitation as a personal reply by adding "Re:" to the subject when it isn't a reply. Keep the sender identity accurate, make unsubscribing straightforward and investigate unexpected bounces or complaints before continuing the campaign. A recognizable name helps readers, but it doesn't replace correct sending setup or permission to contact them.
Measure bookings, then investigate the part that needs work
Keep the campaign's commercial purpose visible when you review the report. Opens can help diagnose a change, but they don't tell you whether someone understood the invitation or bought a ticket. Apple's Mail Privacy Protection guidance explains that the feature prevents senders from seeing whether recipients opened their email. That limits what an open-based comparison can tell you.
Start with delivered messages, people who clicked, completed orders, tickets sold and associated revenue. Keep people, orders and tickets separate because one person may buy several tickets. Check how your reporting tool associates a purchase with an email before treating its revenue figure as proof that the email caused every sale.
Here is a fictional calculation. You deliver an invitation to 1,000 eligible subscribers. Eighty people click, 12 orders complete and those orders contain 18 tickets at $65 each. Ticket revenue is $1,170 before refunds and event costs. The order rate among delivered recipients is 12 divided by 1,000, or 1.2%. It is different from tickets per delivered recipient, which is 18 divided by 1,000, or 1.8%.
If you spent $60 on sending and staff time for this campaign, that equals $5 per completed order or about $3.33 per ticket. Those figures still aren't event profit. You need to account for the cost of delivering the event, fees, discounts and refunds before deciding how much the campaign contributed. Treat these numbers as a worked example, not a target your own list should meet.
What to change after reading the report
If people click but rarely book, test the destination first. Does the page show the event and ticket the email promised? Has the price changed? Is the booking action obvious on a phone? Complete a test order and inspect required fields and error messages. The subject line already persuaded these readers to take a look, so the next explanation may be on the page or in checkout.
If clicks are weak among a relevant, reachable audience, reread the offer. Does the opening explain why this event suits them? Have you buried the date or failed to mention the price? Choose one plausible change for the next comparable send. Changing the subject, offer, audience and send time together makes it difficult to understand which decision helped.
For small lists, a handful of orders can change the apparent winner. Keep notes across similar events and avoid announcing a universal best subject line from one split test. Read replies and booking questions alongside the numbers. They often explain why the reader hesitated in a way the report cannot.
Choose the next invitation around a real booking decision
Before you send your next invitation, pick the group you're writing to and the question most likely to delay their booking. It may be the price, the program, the location or whether the session suits their experience. Answer that question in plain words and make the event page carry the same promise.
Then test the full journey yourself, including the confirmation, and set the reminder audiences correctly. You'll have a useful basis for learning from the next campaign because you can see where people clicked, where they booked and what still needs work.
Author: By the Loopyah Content Team
The Loopyah Content Team shares expert insights, practical guides, and industry updates to help event organizers create unforgettable experiences and stay ahead in the event planning world.









