Event invitation emails for business events, with 6 templates
Who should send a business event invitation, what it has to answer, how to follow up, and six templates for dinners, side events, summits and conferences.
· 12 min read

Key points
- The person who knows the guest best should send the invitation, from their own name, to one guest at a time.
- Give every guest one invitation owner, so a rep's note and a marketing email never land on the same person.
- Answer what a busy guest checks first: why you, what it is, who's in the room, when, what's expected, and how to reply.
- Keep personal invitations short and plain, and put the full details on the event page.
- Follow up once with something new, send the calendar file only after a yes, and judge it all by replies, not opens.
Who should send the invitation?
The person who knows the guest best. Not the company, not events@, and not whoever owns the email tool.
The evidence points one way. In a trial at a UK jobcentre, texts inviting jobseekers to an employer’s recruitment day brought in 10.5% when they listed only the facts. When the text used the jobseeker’s name, was signed by their own advisor and said “I’ve booked you a place,” 26.8% came.
Jobseekers aren’t executives. But executives say the same thing in their own words.
In January 2026, an organizer asked IT leaders on Reddit why they skip executive dinners. One answered: “I’ll go to these sort of events when invited by someone I know and trust. Cold call? No.”
Pick the sender by the guest:
| Guest | Who sends |
|---|---|
| Existing customer | Their account manager or customer success lead |
| Prospect in an open deal | The rep working the deal |
| Senior exec you want at a dinner | Your exec, as the host |
| Partner | Their partner manager |
| Investor or analyst | Investor relations, on behalf of the CEO or CFO |
| Nobody on your team knows them | The event lead, under their own name |
When an assistant or the event lead writes on an exec’s behalf, say so in the first line. “Maya asked me to invite you” is honest, and it still carries Maya’s name.
Give every guest one invitation owner
The fastest way to annoy an exec is to invite them twice. A rep sends a warm note, then marketing sends the designed version two days later, and now it reads like a campaign.
Reps feel this too. A salesperson on Reddit put it plainly: “Last thing I would want is for marketing to spam my prospects with a standard event invite template.”
So split the work this way:
- One owner per guest. Put the owner’s name next to every guest on the shared list before anyone sends.
- The owner asks. Their note is the invitation. It’s short, and it’s theirs.
- The event team confirms. Once the guest says yes, the event team sends the details and the registration link, saying who asked. That’s the confirmation, never a second ask.
- No owner, one sender. Guests without an owner get the invitation from the event lead.
Give reps a draft with one blank line for their own reason, a send date and a place to log replies. Then chase them.
Copy is rarely the problem. Unsent invitations are.
What does a busy guest check first?
An exec, or the assistant who screens their inbox, scans for a few facts before deciding. Answer each one in a sentence or two.
- Why you. One line only this sender could write. “You moved your team off spreadsheets last year” beats “As a valued customer.”
- What it is. The format, the topic as a real question, and how long it lasts.
- Who’s in the room. Describe guests by role, such as “8 heads of finance from Bay Area software companies.” Use names only with permission.
- When and where. Date, start and end time, and the city or venue.
- What’s expected. Is there a talk, a demo or a pitch? Will they be asked to speak? Is it recorded?
- Who can come. Just them, or a colleague in their place.
- How to answer, and by when. One reply-by date with a real reason, such as the venue’s final numbers.
The “who’s in the room” line matters more than most writers think. One IT leader in the same Reddit thread wrote: “Generally i need to see confirmed participants and moderators. Not “invited” or “tentative” or “TBD” but confirmed.”
Be honest about the pitch. Another told the organizer: “I see your invite and it sounds like I am going to be trapped in the CIO equivalent a three-hour timeshare presentation.” Their advice was to say what the guest gets out of the evening.
If a sponsor speaks for 5 minutes, say so. If no rep will call the next morning, say that too, then keep the promise.
On names, the Irish Data Protection Commission says asking first is “good manners and good practice.” Its test is whether people would be surprised by how you use their details.
If your dinner runs under the Chatham House Rule, say so in the invitation. Guests want to know before they agree to speak freely.
Ask for a reply or a registration click?
It depends on how well the sender knows the guest, and how many seats there are.
| Event | How to ask | Format |
|---|---|---|
| Dinner, roundtable or advisory board, under about 40 | “Can you join us?” Ask for a reply, then send their personal link | Plain text from a person |
| Side event, partner summit or launch preview, about 40 to 150 | A short note with one personal registration link | Plain text from a person |
| Open workshop or conference | A button to the registration page | A designed email is fine |
The cut-offs are rough. What matters is that a person someone knows can be answered with a reply. A stranger’s form can only be filled in.
Plain beats designed when the sender is known. When Litmus tested its own webinar invitations, the plain version won with existing customers and made no real difference with people who weren’t customers yet.
If you do design the email, keep the date, place and button as real text. Section508.gov’s email guidance says to “avoid text on images,” since some readers and some inboxes never load them.
How far ahead should you send it?
Travel sets the lead time, not the size of the room.
| Event | Send the invitation | Why |
|---|---|---|
| Local dinner or roundtable | 3 to 5 weeks before | Most guests answer in the last few weeks |
| Side event at a trade show | 4 to 6 weeks before the show | Guests plan their show week early |
| Partner summit people fly to | 2 to 3 months before | Flights, hotels and approvals |
| Customer advisory board | Set the dates 6 to 12 months out | Members commit to a term, not one evening |
| Investor day | Save the date 5 to 6 months out | The investor relations firm ICR advises this for analysts and top shareholders |
| Open conference | Announce 10 to 12 weeks out, keep inviting | Many people register in the last month |
For the open conference, don’t give up on late sign-ups. Maritz’s 2024 report on trade show registration found 45% came in the final 4 weeks.
In its data, 22% registered in the final week, including people who signed up on site.
For dinners and roundtables, our invite-only guide has data on when guests actually say yes.
Six business event invitation templates
Each one is a filled-in example. Swap the parts in brackets.
1. Executive dinner, from the host
Subject: Dinner on [May 14], [San Francisco]
Hi [Priya],
I'm hosting a dinner for 10 heads of product in [San Francisco] on [May 14], 6:30 to 9:00 PM.
You mentioned your team is rebuilding its pricing pages, so I thought of you. The whole evening is one question: what actually changes buying decisions for B2B software?
[Daniel Kim] from Northwind has said yes. No slides and no pitch. We'll pick up the bill.
Can you join us? I need final numbers for the restaurant by [April 30].
[Maya]
2. Rep note for a trade show side event
Subject: Breakfast during Retail Data Expo?
Hi [Avery],
Are you going to Retail Data Expo in [San Francisco] next month? We're hosting a breakfast for about 30 customers and prospects on [May 14], 7:30 to 9:00 AM, a short walk from the convention center.
It ends before the first keynote, so it won't cost you a session.
Want me to save you a spot? If yes, I'll have our events team send the details.
[Sam]
3. Confirmation after a rep’s note
Send this only after the guest says yes to their rep.
Subject: Your spot at breakfast on [May 14]
Hi [Avery],
[Sam] told me you can join us. Thank you.
Here's your personal registration link. It takes a minute and tells us about any dietary needs: [link]
Once you register, you'll get a calendar invitation with the address.
[Maya], Events team
4. Customer advisory board invitation
Subject: Would you join our customer advisory board?
Hi [Priya],
I'd like to invite you to our customer advisory board for 2027. It's 12 customers who help shape what we build next.
What it involves: two in-person meetings in [San Francisco], on [May 14] and in October, plus two 1-hour video calls. We cover travel and hotel. It's a one-year term, and you can step down at any time.
I'm asking because your team's feedback on reporting changed our roadmap this year.
Can we talk for 15 minutes next week? I'll walk you through it and answer any questions.
[Maya]
5. Partner summit, with seats per partner
Subject: Partner Summit seats for Northwind
Hi [Daniel],
Our partner summit is on [May 14] in [San Francisco], one day of roadmap sessions and planning time with our product team.
Northwind has 3 seats. Please send me the names of the people you'd like to bring by [April 15], and I'll send each of them their own registration link. Seats are named, so please don't forward the link.
Travel is on each partner. We cover meals and the evening event.
[Jordan], Partner team
6. Open conference, to your list
Subject: [Product Summit 2027]: [May 14], [San Francisco]
Hi [Priya],
Registration is open for [Product Summit 2027], our one-day conference for product and revenue teams, on [May 14] in [San Francisco].
Sessions include pricing, onboarding and what 20 customers learned moving to usage-based billing. [Avery Chen] gives the opening talk.
It's free for customers. Register here: [link]
[Maya]
You're getting this because you're a customer of ours. [Unsubscribe]
[Lumen Software, 500 Market Street, San Francisco, CA 94105]
Template 6 is a marketing email to a list, so it needs your postal address and a way to opt out. The FTC’s CAN-SPAM guide says the law “makes no exception for business-to-business email.” Personal notes from reps don’t need the footer, but they still need to be real one-to-one notes.
How should you follow up?
Follow up once, with something new. Then stop chasing and start confirming.
| When | What to send | Who gets it |
|---|---|---|
| About a week after the invitation | One follow-up with news: a confirmed guest, the menu, the speaker | People who haven’t answered |
| A few days before the reply-by date | A short last call | Warm contacts, and only if seats are open |
| Right after a yes | Confirmation with the calendar file | Everyone who said yes |
| The day before | A reminder with an easy way to say “I can’t make it now” | Everyone confirmed |
Never send “just bumping this up.” It says you have nothing new.
Send the calendar file only after a yes. Google Calendar lets people add invitations only from senders they know, and since August 2026 Workspace admins can turn that on for a whole company. A hold dropped on a stranger’s calendar may never reach it. If it does, it reads as pushy.
Don’t sign people up on their behalf, either.
In a trial with Irish public sector staff invited to online events, 95.2% of those registered automatically stayed on the list. Only 9.8% of them showed up. A yes the guest didn’t give fills the list, not the room.
What not to do
- Don’t fake urgency. The FTC lists false low-stock messages and fake countdown timers among the dark patterns it warns about. Execs also talk to each other. A real limit, stated calmly, does more: “It’s one table of 10.”
- Don’t judge invitations by opens. Apple’s Mail Privacy Protection loads emails in the background, so opens stopped meaning much in 2021. Omeda saw average open rates nearly double after it launched, while clicks stayed flat. Count replies, registrations and arrivals.
- Don’t A/B test subject lines on 60 people. A list that small can’t tell two subject lines apart unless one is a disaster. Change one thing per event and compare acceptances.
- Don’t fake the personal touch. Openers that pretend to have studied someone’s profile came up again and again as a complaint in that Reddit thread. A real reason in one line beats any first-name token.
How Gatherment handles it
Gatherment sends branded invitations with personal links from your own verified sender. Each guest can have an invitation owner, the teammate who knows them best, so everyone sees who’s inviting whom on one shared list.
You can import guests from a CSV file or a HubSpot list, with duplicates removed before anything sends. Once a guest registers, confirmations and calendar invitations go out from the guest list. The list also shows any invitation that bounced, so you can fix the address.




