How to Request a Meeting With a Senior Leader Using AI

Why Senior Leaders Skim and Delete

Senior leaders are not ignoring you out of rudeness. They are triaging an inbox where most messages are requests, and the ones that survive are the ones that can be decided immediately. Anything that requires a reply to work out what is being asked gets pushed down the pile.

This is the part most guides get wrong. They tell you to be polite and professional, which you already are. The actual failure is almost never tone. It is that your email asks the reader to do work — work out the purpose, work out the length, work out whether they are even the right person — before they can say yes.

The same discipline applies whether you are asking your own director for thirty minutes or approaching a client’s C-suite contact for the first time. If the relationship is brand new, borrow the etiquette from writing an introduction email that earns a reply and fold it into a single opening line rather than a paragraph. And if what you actually need is a decision rather than a conversation, the general context, ask and benefit structure may serve you better than a meeting at all.

The Meeting Request Email Senior Leaders Answer

Every meeting request email senior leaders answer quickly contains the same four parts, always in this order: Standing, Ask, Slots, Preview. Write those four as rough notes, hand them to AI, and you get a usable draft on the first pass instead of the fifth.

The Preview is the part almost nobody includes, and it does the most work. One line naming what you will cover tells the reader whether to accept, delegate, or answer you in writing and skip the meeting entirely. All three of those are good outcomes for you.

Do not write an email. Write four fragments in a scratch file: your role and the connection, the single thing you need, two or three times you can actually make, and the two or three items you would cover. Ninety seconds, no polish.

The prompt below is deliberately prescriptive about length and order, because left to its own devices every model writes a warm, padded, four-paragraph business letter.

You are helping me write a short meeting request to a senior leader who is several levels above me and very short on time.

My role: [your job title] in [your team].
Their role: [their title], who owns [the area this touches].
How they know me, if at all: [previous contact, shared project, or "we have not met"].
The one thing I need from them: [a decision, an input, a steer — one item only].
Times I can offer: [two or three specific slots with time zone].
Meeting length I am asking for: [15, 20 or 30 minutes].
What I would cover: [two or three short items].

Write the email in this order and nothing else:
1. One sentence of standing — who I am and why this reaches them.
2. One sentence naming the single ask.
3. One sentence with the time options and the length.
4. One line previewing what we would cover.

Rules:
- Under 120 words in the body.
- No apology for taking their time, no flattery, no "I hope this finds you well".
- Plain sentences. No corporate filler.
- Do not invent any date, name, metric or project detail I did not give you.
- Give me three subject line options underneath, each under 8 words.

Read the draft as the recipient, not the sender. Every sentence that is not one of the four parts comes out. In practice that is usually the opening pleasantry and a line of background you added because you felt exposed asking for so little.

If the draft comes back warmer or stiffer than your relationship warrants, fix it in a second pass rather than rewriting the prompt. The technique in dialling an email’s tone to match the relationship works here without modification.

Here is my draft meeting request: [paste draft]

The recipient is [their title] and my relationship with them is [never met / met twice in large meetings / they know my work well].

Rewrite it so the register matches that relationship exactly. Keep the same four parts, the same length, and the same time options. Change only the warmth and the formality. Return the revised email and one line explaining what you changed.

Three Tools, One Prompt

The prompt above works in any of the major assistants. What differs is where you are standing when you need it, and that is usually the deciding factor.

ChatGPT is the one to reach for when you want to iterate. Paste your four notes, get a draft, argue with it, then paste the winner into your mail client. If you write these often, put your job title and team into Custom Instructions once so you stop retyping your Standing line.

Gemini in Gmail keeps you in the inbox. Open a new message, click Help me write, and paste a shortened version of the prompt. Google’s own prompting guide for executives shows the same pattern from the other side of the desk — short task, then the context that constrains it.

Copilot in Outlook is the strongest option if your organisation runs on Microsoft, because the draft appears in the actual email you are about to send. One thing catches people out, and Microsoft’s own documentation on drafting an email message with Copilot in Outlook is explicit about it: Copilot in Outlook supports work or school accounts and Microsoft addresses such as outlook.com, hotmail.com, live.com and msn.com. A Gmail or Yahoo address you read inside Outlook will not show the Copilot drafting features at all.

Subject Lines That Get Opened

The subject line is doing one job: telling the reader what decision is in the email. Not the topic. The decision. A subject naming the outcome gets opened at the desk; a subject naming a theme gets opened on the train, if at all.

Three formulas cover almost every internal request. Lead with the length when the meeting is short, because the number does the persuading. Lead with the decision when the decision is the interesting part. Lead with the deadline when there is a real one, and only when there is a real one.

Here is my meeting request: [paste the email body]

Write six subject line options for it, each under 8 words:
- Two that lead with the meeting length.
- Two that lead with the decision I need.
- Two that lead with the deadline, only if my email actually names one. If it does not, say so instead of inventing a deadline.

No colons used as clickbait, no questions, no "quick" or "just". Plain internal-email register.

The same instinct applies outside your organisation, where the stakes on a subject line are higher still. If that is your situation, the cold email approach that avoids sounding like spam is the closer sibling to what you are doing here.

Mistakes That Get Requests Ignored

Four failure modes account for most unanswered requests, and three of them are things AI will do on your behalf if you let it. Run your draft past this table before a meeting request email senior leaders need to act on ever leaves your outbox.

The invented-detail failure is the dangerous one. A model asked for a meeting request with no times supplied will cheerfully propose next Tuesday at 2pm, and it reads so naturally that people send it. Always paste real slots, and always read the draft once for facts you did not supply.

The three-asks failure is quieter but just as costly. If you genuinely need a decision, an introduction and a budget steer, that is three emails or one very different conversation. Bundling them guarantees the reply addresses whichever one was easiest. Where the underlying issue is a stalled decision rather than a missing conversation, writing a professional escalation email is often the more honest move.

Following Up Without Nagging

One follow-up. That is the whole policy. Silence from a senior leader is almost never a judgement on you, and a second chase converts far less often than it annoys. A meeting request email senior leaders have not answered in three days is usually sitting unread, not rejected.

The mechanics are the same as any other chase, so the structure in writing a follow-up email in under a minute transfers directly. What changes is the length: upward, a nudge that runs longer than two sentences reads as pressure.

Write a follow-up to this unanswered meeting request: [paste the original email]

Rules:
- Under 45 words.
- Reply in the same thread, so do not repeat the background.
- Re-offer the time slots, updating them if they have now passed: [new slots].
- Give them an easy exit: offer to send the question in writing instead if a meeting is not the right use of their time.
- No guilt, no "just following up", no "bumping this".

That written-answer exit is the underrated part. Roughly as often as not, a senior leader would rather give you three lines by email than find twenty minutes, and you got what you needed either way. If the meeting does land, spend ten minutes preparing properly for the conversation and send a real agenda first, built the way a meeting agenda that keeps things on track is built. The one-line Preview got you the slot; it is not the agenda.

What AI Cannot Do Here

AI is drafting the email. It is not doing the judgement, and on a request upward the judgement is most of the job.

There is a data question too, and it is a real one. Writing this email means typing a named executive, an internal project and sometimes a live commercial decision into a tool. What is safe depends on your employer’s rules, not on the tool’s marketing.

A work-account tool inside your own tenancy is a different risk profile from a personal consumer account, and your IT policy is the one that decides. When in doubt, draft with square-bracket stand-ins and fill the real names in your mail client afterwards. It costs you fifteen seconds. The same caution is worth applying to any high-stakes upward conversation, including preparing for a salary negotiation with AI.

Run the four parts by hand two or three times and you will stop needing the prompt for anything but the tone pass. That is the point. The system is what you keep; the tool is just where you happen to be standing.