Write a meeting request email to [RECIPIENT] from [SENDER]. The purpose is [MEETING PURPOSE], and the desired outcome of the meeting is [DESIRED OUTCOME]. Use the relationship context and facts below; do not invent familiarity, referrals, research, shared contacts, results, or urgency. Recipient and context: [RECIPIENT CONTEXT] Relevant reason to meet: [RELEVANT VALUE OR TOPIC] Meeting details: [MEETING DETAILS] Tone: [TONE] Produce: 1. Three subject lines of six words or fewer. Do not use deceptive “Re:” or “Fwd:” framing. 2. One primary email of 90–130 words. 3. One shorter follow-up of 45–65 words for use after five business days if there is no response. The primary email must have this order: a personalized opening based only on supplied context; one sentence connecting the topic to the recipient’s work or current priority; a concrete reason the conversation could be useful; a specific ask for a meeting length; and a low-friction scheduling path. Include a focused two- or three-item agenda only if I provide enough detail to make it credible. Offer no more than two time windows, or a scheduling link if supplied. Make it easy to decline or redirect the request when appropriate. Avoid vague phrases such as “pick your brain,” “synergies,” “quick chat,” and “I’d love to connect.” Do not overstate the sender’s authority or promise outcomes that depend on the recipient. Never attach a calendar invite without an accepted time. Before answering, check that the email identifies why this recipient specifically is relevant and that the request has a clear duration and next action. Flag anything unsupported or too sensitive to include by email. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT] | Provide the recipient’s name, title, and organization if appropriate. | Priya Nair, Director of RevOps at Greenfield Analytics |
| [SENDER] | Provide the sender’s name, role, organization, and any accurate connection to the recipient. | Marcus Chen, Partnerships Manager at IntakeLoop; Priya attended Marcus’s webinar in May |
| [MEETING PURPOSE] | State why you are requesting the meeting in one specific sentence. | Discuss whether IntakeLoop’s lead-routing audit could help Greenfield reduce response delays for enterprise demo requests |
| [DESIRED OUTCOME] | State what a useful meeting should accomplish, such as agreeing on a pilot scope or getting feedback. | Decide whether a two-week audit is worth scoping with Priya’s operations team |
| [RECIPIENT CONTEXT] | Provide a truthful detail about the recipient’s role, work, prior interaction, or publicly stated priority. | Priya attended our May webinar on lead handoffs and posted that Greenfield is standardizing its Salesforce routing rules this quarter. |
| [RELEVANT VALUE OR TOPIC] | Explain the specific issue, idea, or information that makes the conversation relevant to the recipient. | Our audit maps routing exceptions and response-time gaps using existing Salesforce data; it does not require a platform migration. |
| [MEETING DETAILS] | Provide desired duration, agenda if known, time windows or scheduling link, and meeting format. | 20-minute Zoom meeting; possible agenda: current routing objective, known exceptions, audit scope. Offer Tuesday 2:00–4:00 p.m. ET or Thursday 10:00–11:30 a.m. ET; no scheduling link. |
| [TONE] | Describe the desired voice, such as peer-to-peer and concise or formal and deferential. | Peer-to-peer, concise, and respectful of a busy operator |
How to use
- Choose one reason for the meeting and write it in terms of a decision, problem, or result relevant to the recipient.
- Paste only facts you can substantiate, especially any reference to their company initiative, mutual contact, or prior interaction.
- Check that the email includes a duration, scheduling route, and an agenda narrow enough for the requested time.
- Then send: “Rewrite this for a recipient who has not interacted with us before; remove the webinar reference and keep it under 85 words.”
Variations
Internal stakeholder
Use when aligning colleagues across teams.
Draft an internal meeting request from [SENDER] to [RECIPIENTS] about [DECISION OR BLOCKER]. Use [CONTEXT] and request a [DURATION]-minute meeting by [DATE]. Produce a subject line and an email under 130 words with the decision needed, brief pre-read or data source, proposed agenda, and two time options from [AVAILABILITY]. State what will happen if the group cannot meet, but do not invent authority or deadlines. Use a direct, collaborative tone and avoid adding attendees who do not need to decide or contribute.
Customer check-in
Use when requesting a meeting with an existing customer.
Write a customer check-in email to [CUSTOMER CONTACT] from [SENDER] about [ACCOUNT CONTEXT]. Request a [DURATION]-minute meeting to discuss [PURPOSE]. Include a brief account-specific observation from [VERIFIED FACT], a proposed agenda of up to three items, and [SCHEDULING OPTION]. Keep it under 140 words and use [TONE]. Do not imply product usage, results, or renewal risk beyond the facts supplied. End with a respectful option to redirect the meeting to the appropriate owner.
Research interview
Use when recruiting someone for a discovery interview.
Write a research interview invitation to [RECIPIENT] about [RESEARCH TOPIC]. The participant profile is [WHY THEY FIT], and the interview will take [DURATION] by [FORMAT]. Explain that the purpose is to learn about their workflow, not to sell a product. Include [INCENTIVE OR NONE], a short privacy or recording note from [CONSENT DETAILS], and [SCHEDULING METHOD]. Produce a subject line and an email under 150 words. Do not claim anonymity, compensation, or use of findings unless explicitly supplied.
Tips
- Make the value proposition about the recipient’s current decision or workload, not a broad description of your company or capabilities.
- Limit the agenda to what can genuinely be covered in the requested time; a 20-minute request with five topics signals poor preparation.
- For cold outreach, use one accurate personalization detail and connect it to the ask; a list of scraped facts can feel intrusive.
- Send a follow-up that adds a useful detail, alternate time, or graceful close rather than repeating the original request unchanged.
FAQ
How long should a meeting request email be?
Most requests work in 90–130 words. The recipient should understand why, what, and how long without opening another document.
Should I include a scheduling link?
Use one when the recipient is likely comfortable with it or when you already have a relationship. For a senior or cold contact, two specific windows can feel more considerate.
How many follow-ups should I send?
One follow-up after about five business days is usually appropriate. If there is still no reply, close the loop unless you have a new, relevant reason to contact them.