Most meeting requests fail before the reader gets to the point. They open with a greeting, a pleasantry, and a paragraph of throat clearing, and the actual reason for the meeting shows up in sentence four. By then the recipient has already decided this can wait. A request that leads with the purpose and makes the yes easy gets answered the same day.
Say why before you say when
The first line should tell the recipient exactly why you want their time. Not “hope you are doing well”, not “I wanted to reach out”: the actual topic. If they cannot tell what the meeting is about from the first sentence, you have already lost some of their attention. Everything else, the pleasantries, the context, the scheduling, comes after.
Make the yes take ten seconds
A meeting request is a small decision for the recipient, and small decisions get made faster when there is less to decide. If you have times that work for you, name them and ask for a simple confirmation rather than leaving the whole calendar open. If you genuinely do not know your own availability yet, do not write an open-ended “let me know when works for you”: ask something specific and narrow, like whether any time this week or next would suit them. A narrow question is easier to answer than an open one.
Keep it short on purpose
A meeting request is not the place for the full background. Give enough context for the recipient to understand why the meeting matters, then stop. If there is more detail worth sharing, mention that you will bring it to the meeting itself rather than cramming it into the email. Length signals importance in the wrong direction here: a request that takes thirty seconds to read gets a faster reply than one that takes three minutes.
Example
Common mistakes
- Opening with pleasantries instead of the reason for the meeting.
- Asking an open-ended “let me know when works” instead of a specific, easy question.
- Padding the request with background that belongs in the meeting, not the invite.