Event invitation email: templates, subject lines and getting delivered
Six event invitation email templates for client events, company events, conferences and webinars, plus subject lines, a reminder and a thank-you. And the part where many invitations fail before anyone reads them: when your CEO sends the invitation from their own address, SPF, DKIM and an allowlist entry in your mail gateway have to be in place.
A good event invitation email puts the occasion, date, time and place in the first lines, addresses the guest by name and has exactly one button to RSVP, with a deadline. It comes from a sender the guest recognizes, and that sender has to be authenticated: through SPF, DKIM and DMARC on the sending domain and, for internal recipients, an allowlist entry in your own mail gateway. Copy the templates below; placeholders are in square brackets.
How an event invitation email is structured
Guests decide within seconds whether to read on. So what they need to decide goes first; everything else follows after they RSVP, in the confirmation. A business event invitation email has nine building blocks.
| Building block | What goes in | Common mistake |
|---|---|---|
| Sender | A person or brand the guest knows; an address on your own domain | noreply@ or the sending service's address |
| Subject line | Occasion and date within the first 40 characters | Just "Invitation" or just the event name |
| Preheader | One line that adds to the subject, such as venue and host | Empty, so the inbox shows "View in browser" |
| Greeting | By name, from the guest list | "Dear valued customer" to people you know |
| First lines | What, when, where, for whom | Three paragraphs of preamble |
| Button | Exactly one: "RSVP now" or "Register", with a personal link | Several links of equal weight |
| Deadline | The RSVP date, next to the button | Missing, so replies trickle in until the night before |
| Attachments | Calendar file (.ics); the ticket comes with the confirmation | Large PDFs that trip spam filters |
| Footer | Contact for questions, postal address, opt-out for promotional email | Missing |
Images can carry the design but should not carry the message: many inboxes load images only after a click. If the invitation is one big image, guests first see an empty box. Date, place and button belong in the email as live text.
Subject lines for event invitation emails
The subject line is half the invitation. Name the occasion and the date and keep it short enough for a phone screen, ideally under 40 characters. Ten examples to adapt:
- You are invited: [Event] on [date]
- [First name], join us for [event] in [city]
- Save the date: [Event], [date]
- A personal invitation from [name], [title]
- Join us for our summer party on [date]
- [Event] [year]: registration is open
- Webinar on [date]: [topic in five words]
- [Number] seats left: [event] on [date]
- Reminder: please RSVP by [deadline]
- Thank you for joining us at [event]
The number in "[Number] seats left" has to be true. Invented scarcity is noticed by regular guests and costs trust next time.
Event invitation email: six templates to copy
Each template contains what an invitation needs: occasion, date and time, venue, one line about the program, an RSVP link and a deadline. Pick the tone that fits and replace the placeholders in square brackets.
Betreff: You are invited: [Event] on [date] in [city]
Dear [first name],
we would love to welcome you to [event]:
[Weekday], [date], from [time]
[Venue], [address]
Expect [two sentences on the program, such as a keynote, a product preview and dinner]. You will meet [whom, such as peers from your industry and our team].
Please RSVP by [deadline] so we can plan: [Button: RSVP now]. You are welcome to bring a guest; just add them when you register.
We look forward to seeing you.
Best regards,
[Name], [title]
Betreff: A personal invitation from [name], [title]
Dear [first name],
it would be a pleasure to welcome you on [date] to [occasion, such as our annual reception] at [venue].
[One personal sentence on why this guest is invited, such as last year's work together.]
The evening begins at [time] with [program item]. My assistant, [name], is happy to help with any questions; the easiest way to reply is here: [Button: Accept invitation].
Warm regards,
[Name]
[Title], [Company]
Betreff: Join us for [occasion] on [date]
Hi everyone,
on [date] from [time] we are celebrating [occasion] at [venue]. On the program: [program in one sentence].
Everyone at [location or team] is invited. [Partners are welcome.]
Please register by [deadline] so we can plan food and seating: [Button: Register]. You can add dietary needs there too.
See you there,
[Name] for the organizing team
Betreff: [Event] [year]: agenda is live, registration open
Hi [first name],
[Event] takes place on [date] in [city]. The agenda with [number] sessions and workshops is live: [three highlights in brief].
When you register, you pick the workshops you want to attend; seats are limited and assigned in order of registration.
[Button: See the agenda and register]
Registration is open until [deadline]. Questions? Reach us at [email address].
Best,
[Name], [team]
Betreff: Webinar on [date]: [topic]
Hi [first name],
in [length] minutes, [speaker] will show on [date] at [time] [time zone] [the benefit in one sentence].
After you register you receive the access link and a calendar file; everyone registered gets the recording. [Button: Save my seat]
Best,
[Name]
Betreff: Save the date: [Event] on [date]
Dear [first name],
please save [date] for [event] in [city]. Your personal invitation with the agenda and registration follows in [month].
[Button: Add to calendar]
Best regards,
[Name], [title]
Reminder and thank-you email
Send the reminder about a week before the deadline, and only to guests who have not answered. Those who said yes get the practical details shortly before the event instead. The thank-you after the event is the first invitation to the next one.
Betreff: Reminder: please RSVP by [deadline]
Hi [first name],
you received our invitation to [event] on [date]. To help us plan, please let us know by [deadline] whether you can make it: [Button: Accept or decline]. A no helps us as much as a yes.
Best,
[Name]
Betreff: Thank you for joining us at [event]
Hi [first name],
thank you for being part of [event]. [One sentence on a highlight.] Photos and the session slides are here: [link].
How did we do? Three questions, one minute: [link to the feedback form]
We hope to see you again soon.
[Name], [title]
When the CEO sends it: SPF, DKIM, DMARC and allowlisting
The best invitation is worthless if it sits in the spam folder or never arrives. That happens most often in a situation every event team knows: the invitation is supposed to come from the CEO, with their address, but it is sent through an invitation tool or an email service. To the recipient's mail server this first looks like a forgery: a message from ceo@yourcompany.com arrives from a server that does not belong to yourcompany.com.
Whether it gets through anyway depends on three records in your domain's DNS. They have been standard for years, and since February 2024 Google and Yahoo require them from everyone who sends email in volume.
| Standard | What it checks | Who sets it up |
|---|---|---|
| SPF | Whether the sending server may send for the domain. One record lists the permitted servers and services. | Your IT in DNS, with the sending service's entry |
| DKIM | Whether the message was altered in transit and is really signed on behalf of the domain. | The sending service generates the key, your IT publishes it in DNS |
| DMARC | Whether SPF or DKIM match the visible From domain, and what happens on failure: nothing, spam or rejection. | Your IT; the policy applies to all email from your domain |
If your company has a strict DMARC policy (p=reject), messages without a matching signature are rejected. That is good against fraud and bad for the CEO's invitation if nobody added the sending service. The technical details are in the standards SPF (RFC 7208), DKIM (RFC 6376) and DMARC (RFC 7489).
Internal invitations rarely work without allowlisting
Invitations to your own employees face a second hurdle. Your mail gateway, whether Microsoft 365, Google Workspace or a filter in front of them, sees a message with your own domain in the From line that comes from outside. That is exactly what CEO-fraud phishing looks like. Many gateways therefore quarantine such messages, add a warning banner ("External sender") or rewrite the links.
The fix is an allowlist entry, formerly called whitelisting: your IT adds the sending service to the gateway as an approved sender. Do it before the first send, not after the first complaint, and plan a few days, because gateway changes at larger companies go through change management.
| Sender | Effect on the guest | Effort |
|---|---|---|
| ceo@yourcompany.com | Most personal; replies go to the CEO or, via reply-to, to the assistant | SPF and DKIM for the main domain, internal allowlist entry |
| ceo@events.yourcompany.com | Almost as personal; reputation and policies stay separate from the main domain | Subdomain with its own SPF, DKIM and DMARC; one-time IT setup |
| Sending service address, CEO's name | Looks unfamiliar, lands in spam more often, replies go nowhere | None, which is why it is common |
Outside guests: what you can do yourself
You cannot change your clients' gateways. What remains: a properly authenticated sender, a clean list without stale addresses, no sudden send to thousands from a new address, and for key guests a short note to their assistant that the invitation comes from address X and can be marked as safe. Before sending, run a test to your own inboxes at the major providers, such as Outlook, Gmail, Yahoo and iCloud.
A side effect of security filters: some gateways open links in incoming email automatically to scan them. Click rates right after sending should therefore be read with caution; the number of registrations is the more reliable figure.
CAN-SPAM: what applies to invitation emails
An invitation to a client event is usually a commercial email, and the CAN-SPAM Act applies to it, including business-to-business email. In short: honest From line and subject, your valid physical postal address in the email, a clear way to opt out of future promotional email, and opt-outs honored within ten business days. Confirmations, tickets and updates for an event someone registered for are transactional messages. If you invite guests from Europe or Canada, stricter consent rules apply there. This is not legal advice; your legal team can assess the specific case.
Checklist before you send the event invitation email
Invitation, RSVP and reminder on one guest list.
In AirLST you design the event invitation email in your own brand and send it under your own sender: sender name, sender address and reply-to are set per template, and your own addresses are set up as sender identities with address and domain verified. Every guest gets a personal RSVP link; the response sets their status, and the next message follows from it.
- Templates in the editor with placeholders, even in subject, CC and BCC
- Calendar file, PDF ticket and wallet pass as attachments
- Reminders only to guests without a reply
- Statistics on delivered, opened, clicked and bounced
Frequently asked questions about event invitation emails
How do I send an event invitation by email?
For a handful of guests your own mailbox works: recipients in BCC so addresses stay private, the date as a calendar file, replies by email. From a few dozen guests on, a tool pays off that sends every guest a personal RSVP link, records responses automatically and reminds only those who have not answered. Either way, the sender has to be authenticated for its domain, or the invitation lands in spam.
What is a good subject line for an event invitation email?
The occasion and the date, ideally within the first 40 characters, because phones cut off the rest. For example "You are invited: Client Dinner, March 12, Chicago". A recognizable sender name does more than an exclamation mark; all caps and words like "free" tend to hurt.
Why does my event invitation email go to spam?
Usually because the sender is not authenticated: the invitation goes out through a sending service but carries your company address, and SPF or the DKIM signature of your domain do not cover that service. If the domain has a strict DMARC policy, the message is rejected or quarantined. Other causes: many invalid addresses on the list, image-only emails, link shorteners and a sudden send to thousands from a new address.
What does allowlisting mean for invitation emails?
An entry in the recipient's mail gateway that marks a sender as trusted, formerly called whitelisting. It matters most for internal invitations: a message with your own company domain in the From line that arrives from an outside server looks like spoofing, so the gateway quarantines it or adds a warning. Your IT adds the sending service as an approved sender. For outside guests you cannot do that; there, SPF, DKIM and DMARC carry the load, and for key guests a note to their assistant helps.
Does CAN-SPAM apply to B2B event invitations?
Yes, if the email is commercial, meaning its main purpose is to promote your business, and an invitation to a client event usually is. CAN-SPAM makes no exception for business-to-business email. It requires honest headers and subject lines, your physical postal address and a working opt-out honored within ten business days. Confirmations, tickets and updates for an event someone registered for are transactional. This is not legal advice.
What is the difference between a save the date and an invitation?
A save the date announces the date early, typically six to twelve weeks ahead, without asking for a response. The invitation follows with the program, the venue and an RSVP link with a deadline. For conferences and executive events both are common; for smaller internal events the invitation alone is enough.