Key Takeaways
- The closing line does the work. Subject and sign-off decide the outcome. The middle of a meeting request email is the part you can safely copy from a template.
- Offering two or three times is the most expensive habit in this format. If none of them fit, the recipient has to write a reply proposing alternatives, and that reply is where most requests die.
- A booking link removes the reply, not the decision. It works when the recipient already wants to meet you, and reads badly when they don't know you yet.
- Seven templates cover cold, warm, internal and client requests. Each ships with two endings so you can pick the right close for the relationship.
Most advice about writing a meeting request email spends its energy on the greeting and the introduction. Those parts almost never decide anything. What decides the outcome is how you end: whether the recipient can say yes in one motion, or whether saying yes requires them to compose a reply, check a calendar, and propose a time that then has to be checked against yours.
That last part is the hidden cost. meetergo puts the typical email-only scheduling exchange at four to five messages per meeting, and every one is a chance for the thread to go quiet. The useful question isn't how to write a polite request. It's how to write one that costs the recipient a click instead of an email.
What a meeting request email is actually asking for
You are asking a stranger or a colleague to give up a block of time that currently belongs to them. Two things stand between you and a yes: whether they want the meeting, and how much work it takes to confirm it.
Persuasion handles the first. Almost nothing in a template handles the second, which is why so many well-written requests get read and then forgotten. The recipient means to reply, opens their calendar later, and by then your email is four screens down.
The subject line and the value sentence buy you the want. The closing line removes the work.
The five parts that matter
Put the actual ask in the subject line
Subject lines that describe a topic ("Q3 pipeline") get opened and then deferred. Subject lines that name the ask and its size get answered.
Write the meeting, the length, and the reason: "15 min on the Q3 renewal?" or "Quick call re: your Series B timeline". Length is the part people skip and the part that lowers resistance most, because 15 minutes is a decision someone can make from their phone. Avoid "Touching base" and "Following up", which tell the reader nothing about what they're agreeing to.
Open with why you're writing, not who you are
Your name is in the From field. Spending the first sentence on your job title costs you the only line most people read before deciding whether to keep going.
Lead with the reason the email exists, then put your identity in the second sentence where it works as credibility rather than preamble. For a cold email, the reason should reference something specific about them: a funding round, a job posting, a product change. Generic openers signal a mail merge, and readers are good at spotting one.
Say what they get in one sentence
This is the value sentence, and it should be uncomfortable to write. If you can't name what the recipient walks away with, the meeting probably shouldn't happen yet.
Good version: "I'd like to show you how two other B2B teams halved their onboarding time, and get your read on whether it fits your setup." Bad version: "I'd love to connect and see whether there's a fit." One promises a specific thing, the other promises a conversation about having a conversation.
Close with one ask, not a menu
Here's where most templates go wrong. The standard advice is to propose two or three concrete times. It sounds considerate and it works fine in one narrow case: when you already know roughly what the recipient's week looks like.
Everywhere else it fails quietly. Your three slots are a guess. If none of them fit, the recipient owes you a reply proposing alternatives, which you then have to check, which produces another message. That's the four-to-five-message exchange. If the relationship calls for naming dates anyway, there's a separate craft to proposing meeting dates by email worth getting right.
If you do write times into the body, the format matters as much as the count. We cover how to write your availability in email separately, with five formats that depend on who is reading and where they sit.
The alternative is to let them choose from your real availability. A booking link shows the times you can meet, in their timezone, and writes the event to both calendars when they pick one. The reply disappears, and so does the timezone arithmetic.
Make the yes reversible
Add one line that lowers the stakes: "If 15 minutes turns out to be the wrong use of your time, say so and I'll send what I have in writing instead."
That gives a hesitant reader an exit that isn't silence, and signals you won't treat the meeting as a foot in the door. People agree faster when leaving is easy.
7 meeting request email templates
Each template has two closings. Use the link close when the recipient has a reason to meet you. Use the times close when a link would read as presumptuous. More on that distinction below.
1. Cold outreach to a prospect
Subject: 15 min on [specific thing you noticed]?
Hi [Name], I saw [company] just [specific trigger: opened a second office, shipped X, posted for three CS roles]. Teams hitting that stage usually run into [specific problem] within a quarter or two.
I work with [role] at [two comparable companies] on exactly that, and I'd like 15 minutes to show you what they changed and get your take on whether it applies to you.
Link close: Pick any slot that works here: [booking link].
Times close: Would Tuesday 14:00 or Thursday 10:00 work? Happy to fit around you.
2. Warm lead who downloaded something
Subject: Following your download: 15 min?
Hi [Name], you picked up [asset] last week. The question it doesn't answer is [the specific next question], which depends entirely on how your [team/stack] is set up.
Fastest way through it is a short call. I'll come with two or three concrete options for your situation rather than a demo.
Link close: Grab a time that suits you: [booking link].
Times close: I'm open Wednesday afternoon or Friday morning if either helps.
3. Client check-in or account review
Subject: 30 min quarterly review, [Month]?
Hi [Name], we're a quarter into [project], and there are two decisions coming up that are easier to make together than over email: [decision one] and [decision two].
I'll send an agenda beforehand so nothing is a surprise, and I'll keep it to 30 minutes.
Link close: Here's my availability for the next two weeks: [booking link].
Times close: Does the week of [date] work? I can flex around your team's schedule.
4. Asking your manager for time
Subject: 20 min this week on [topic]?
Hi [Name], I'd like 20 minutes to talk through [topic]. I've got a recommendation ready and one open question I can't resolve on my own.
Not urgent, but it's blocking [thing], so this week would be better than next.
Link close: I've put a hold on Thursday at 11:00, feel free to move it.
Times close: Any time Wednesday or Thursday works on my side.
5. Cross-team internal request
Subject: [Project]: 25 min with someone from [team]?
Hi [Name], we're scoping [project] and we've hit a dependency on [their team's area]. Rather than guess, I'd rather get 25 minutes with whoever owns it.
I'll bring the three specific questions in advance so the meeting is short.
Link close: Send whoever's right my way, or book directly here: [booking link].
Times close: Early next week suits us, but we'll work around your sprint.
6. Reconnecting with a dormant contact
Subject: Been a while, [Name]. 20 min?
Hi [Name], we last spoke about [specific thing] back in [rough timeframe]. Since then we've [relevant change], which changes the answer I gave you then.
No pitch. I'd like 20 minutes to hear what changed on your side and tell you what changed on ours.
Link close: Whenever suits: [booking link].
Times close: I'm around most of next week if you have a gap.
7. Post-event or networking follow-up
Subject: Following our conversation at [event]
Hi [Name], good to meet you at [event]. You mentioned [specific detail], and I've been thinking about it since.
I'd like 20 minutes to pick that thread up properly, without a conference hall in the background.
Link close: Here's my calendar: [booking link].
Times close: Would sometime in the next fortnight work?
When a booking link is the wrong close
A booking link is not a universal improvement, and vendor advice on this topic tends to pretend otherwise.
Skip it when you're writing to someone senior who doesn't know you: a link asks them to do the calendar work inside your system, which reverses the status order of the request. Skip it on genuinely cold first contact, where it reads as a mass-send tell before they've decided you're worth a meeting. Skip it in regulated correspondence, where a third-party URL in a first email is a compliance conversation you don't want.
There's also a deliverability angle. Links in a first-contact email are one of several signals that can push a message into a spam folder, especially at volume from a new sending domain. If your requests have started disappearing, the pattern behind scheduling invites landing in spam is worth reading before you blame the copy.
The workable middle ground: propose one specific time in the sentence, and put the booking link in your email signature rather than the body. The recipient can use it if they want to, and nobody has been asked to. If you don't have a signature set up for this, there are signature layouts built around a booking link that keep it discreet.
Following up without nagging
Most meeting requests need a second message. Two follow-ups, three to five business days apart, and each has to add something rather than repeat the ask.
Follow-up one adds a reason: a piece of relevant news, a result from a comparable company, a shorter version of the meeting. Follow-up two closes the loop and lets them off the hook: "I'll assume the timing isn't right and leave you be. If that changes, my calendar is here." Ending the thread cleanly is worth more than another nudge.
If the meeting gets booked and then needs moving, the etiquette for rescheduling an appointment and for responding when someone cancels is a different craft again.
Common mistakes
- Asking for "a quick chat" without a length. Undefined time is expensive time. Name 15, 20 or 30 minutes.
- Proposing times without a timezone. "Tuesday at 2" is ambiguous the moment one of you is in another country. Write the zone, or use a timezone planner to find an overlap that isn't someone's evening.
- Stacking two asks in one email. A meeting request plus a document request means the recipient answers the easy one and forgets the other.
- Writing five paragraphs. If it doesn't fit on a phone screen, it gets deferred. Four short paragraphs is the ceiling.
- Sending it Friday at 16:00. Tuesday to Thursday mornings survive the inbox better.
Tools that help
For a handful of requests a week, a well-written email and a calendar is the whole toolkit. Tooling only matters once the reply round-trip is costing you meetings.
meetergo is a Cologne-built scheduling and pipeline tool with coverage across sales, recruiting, consulting and other verticals, and it's the relevant option here because the booking page, the reminders and the follow-ups sit in one place rather than three. Its own sales figures put the effect at roughly 30% shorter sales cycles and 40% more booked demos across 5,000+ sales teams.
Booking pages that show real availability
The link in your email opens a page built from your connected calendars, in the recipient's timezone. When they pick a slot it writes to both calendars and sends the confirmation, so the meeting exists without anyone typing a reply.
Reminders and follow-ups on a schedule
Getting the meeting booked is half the job. Automated email and SMS reminders run before the meeting and follow-ups run after it, which is where the no-show reduction comes from.
Team routing when the request isn't for you
If the meeting should land with whoever's next in rotation rather than with you specifically, round-robin distribution assigns it on the way in. Useful for the cross-team template above.
Polls when a link is too rigid
For a group of five people where no single calendar governs, a scheduling poll collects preferences first and converts the winning slot into a real booking.
Honest limitation: none of this rescues a weak value sentence. A booking link removes friction from a yes that was already leaning toward yes. It will not make a cold recipient want a meeting they didn't want, and pointing one at a genuinely cold list mostly produces a cleaner measurement of your reply rate. The free plan is €0 forever with one active meeting type, which is enough to test whether the link close changes anything for you; unlimited meeting types start at €29.90 per month on the Suite plan.
Try the link close on your next ten requests and count the replies you didn't have to send. Start free with meetergo and connect a calendar in under two minutes. No credit card required.
Booking + video conferencing in one tool.
Booking + video conferencing in one tool.
Frequently asked questions
How long should a meeting request email be?
Four short paragraphs or fewer, roughly 80 to 130 words. It should fit on a phone screen without scrolling. Anything longer gets marked for later, and later usually means never.
Should I attach an agenda to a meeting request?
Not to the first email. Attachments and long agendas raise the perceived cost of saying yes. Offer to send one after the meeting is confirmed, then use a proper structure from a set of meeting agenda templates.
How many times can I follow up on a meeting request?
Two follow-ups, three to five business days apart, each adding new information. The second should explicitly close the thread rather than ask again. Beyond that you're training the recipient to ignore your name.
What subject line works best for a meeting request email?
One that names the ask and its length: "15 min on [specific topic]?". Avoid "Touching base", "Quick question" and "Following up", which describe your intent rather than what the reader is being asked to agree to.
Is it rude to send a booking link instead of proposing times?
It depends on the relationship, not on the link. With a warm contact, a client or a colleague, it saves everyone a message. With a senior stranger on first contact, it puts the calendar work on them inside your system, and proposing one specific time reads better. Put the link in your signature in that case.
How do I request a meeting across time zones?
Write every proposed time with its zone spelled out, and anchor it to the recipient's zone rather than yours. A booking page renders slots in the visitor's local time, which is why scheduling across regions is usually where teams stop proposing times by hand.
