A meeting request email is one of the most common professional messages you'll ever send, yet most people write them too long, too vague, or too apologetic. The reader needs to understand in seconds what you want, why it matters to them, and what they need to do next. Get those three things right and your reply rate climbs. Miss any one of them and the email sits unread.
What a meeting request email needs to do
Before you write a single word, be clear on the outcome you want. You're not just asking someone to clear a slot in their calendar. You're making a case for why this conversation is worth their time. That means the email needs a specific purpose, a named recipient (not a vague "team"), and a concrete ask.
Most failed meeting requests collapse at one of three points:
- The subject line doesn't say what the meeting is about.
- The body explains your need without connecting it to the reader's interest.
- The call to action forces the reader to do more work than they should (for example, "let me know when you're free" with no times offered).
Fix those three, and you've fixed most of the problem.
The subject line
Your subject line has one job: tell the reader what the meeting is about before they open the email. Don't be clever. Don't be vague. Be specific.
Bad: Quick catch-up?
Bad: Meeting request
Good: 30-minute call to discuss the Q4 marketing budget
Good: Can we meet to review the supplier contract? 20 mins needed
Including the duration in the subject line is genuinely useful. It signals respect for the reader's time and reduces friction, because they know immediately whether this is a five-minute call or a two-hour workshop.
For guidance on subject lines more broadly, the principles in subject lines that get your email opened apply directly to meeting requests.
The opening line
Don't start with "I hope this email finds you well." Start with the reason you're writing. One sentence, active voice.
I'd like to schedule a 30-minute call to walk you through the revised project timeline before we present it to the board.
That's it. The reader knows immediately what's being asked and, critically, why it might matter to them. Context comes after the ask, not before it.
How to structure the body
Keep it short. Three to four sentences is the target for most internal requests. Six to eight sentences is the outer limit for an external or first-contact request. The body should answer four questions in order:
- What is the meeting about? One sentence on the topic and purpose.
- Why does it matter to the reader? One sentence connecting the meeting to their role, project, or interest.
- How long will it take? State the duration explicitly.
- When could you meet? Offer 2 or 3 specific time options.
Offering specific times is the single most effective thing you can do to increase your response rate. "Let me know when suits you" puts the entire scheduling burden on the other person. "I'm free Tuesday at 2 PM, Wednesday morning, or Friday after 3 PM" requires nothing more than a one-word reply.
Sample email: internal request
Subject: 20-minute catch-up on the onboarding process — this week?
Hi Sarah,
I'd like a quick call to talk through the new onboarding checklist before it goes live next Monday. A few steps need sign-off from your team and I want to make sure we're aligned before the launch.
It should take about 20 minutes. I'm free Thursday at 10 AM or 3 PM, or Friday before noon. Happy to work around your schedule if none of those times suit.
Thanks,
James
Notice what this email doesn't do. It doesn't apologise for taking up Sarah's time. It doesn't over-explain the background. It doesn't end with a vague "just let me know." It's short, specific, and easy to act on.
Sample email: external or first-contact request
When you're writing to someone you haven't met before, the same principles apply, but you need to add one more element: a brief reason they should want to meet you. Keep it to one sentence. This is not a sales pitch; it's a reason to say yes.
Subject: Meeting request: supply chain partnership opportunity — 30 mins
Dear Ms. Okafor,
My name is David Chen and I manage supplier partnerships at Northridge Logistics. I'm reaching out because we work with several manufacturers in your sector and I believe there's a partnership worth exploring.
I'd like to schedule a 30-minute call to introduce Northridge and hear more about your current supplier arrangements. If the fit isn't there, I'll say so and we won't take up more of your time.
I'm available Tuesday 12 November at 10 AM or 2 PM, or Thursday at any time after noon. A video call works well, or I'm happy to come to your office if you prefer.
Best regards,
David Chen
Northridge Logistics
The phrase "if the fit isn't there, I'll say so" does real work here. It lowers the perceived risk of agreeing to the meeting. The reader doesn't feel trapped.
Tone and register
Match your tone to the relationship. For a colleague you speak to daily, a two-sentence message is fine. For a senior executive you've never met, a slightly more formal structure is appropriate. Neither version needs to be stiff.
Avoid hedging language that undermines the ask. Phrases like "I was just wondering if maybe we could possibly find a time" communicate anxiety, not professionalism. Ask directly. "I'd like to schedule a call" is confident. "I hope I'm not bothering you but I was wondering if you might be able to spare a few minutes" is not.
For more on how opening and closing lines set the right tone, the same principles that apply to general business email apply here. Your closing should state what happens next, not just trail off.
What to do if you hear nothing back
One follow-up is reasonable. Two is the limit. Wait at least two business days before following up on an internal request, and five business days for an external one.
Keep the follow-up short. One sentence referencing your original message, one sentence restating the ask, and a fresh set of time options. Don't re-explain everything. Don't apologise for following up. The detailed guidance on writing a polite follow-up when you hear nothing back covers this situation step by step.
A note on using scheduling tools
Tools like Calendly let you share a booking link instead of proposing specific times. This works well in certain contexts, especially for recurring external meetings or high-volume scheduling. It works less well when you're contacting a senior stakeholder or a first-time external contact, where sharing a link can read as impersonal or presumptuous. Read the relationship before reaching for the tool.
Quick checklist before you send
Before you hit send, run through these five points:
- Does the subject line name the topic and the duration?
- Does the first sentence state the purpose of the meeting?
- Have you connected the meeting to something that matters to the reader?
- Have you offered at least 2 specific times?
- Is the email under 150 words for an internal request, or under 250 words for an external one?
If you can tick all five, send it. The email is doing its job.