Generate subject lines for a meeting-request email to [RECIPIENT]. The meeting purpose is [MEETING PURPOSE], and the recipient’s likely reason to care is [RECIPIENT RELEVANCE]. I am asking for [TIME ASK AND FORMAT]. Relationship and prior context: [RELATIONSHIP AND CONTEXT] Agenda or decision needed: [AGENDA OR DECISION] Tone and communication setting: [TONE AND SETTING] Produce 18 subject lines, each 4 to 10 words, organized into three sets:
1. Six direct lines that state the topic or decision. 2. Six value- or outcome-oriented lines that are specific without making unsupported promises. 3. Six relationship-aware lines for an existing contact, customer, partner, or internal colleague. A good line should help the recipient triage the request: it should signal what the meeting is about, avoid false urgency, and avoid hiding the ask behind “quick question” or “touching base.” Mention a deadline only if I provided a real one. Mention the requested duration only when it improves clarity. Do not use vague claims such as “exciting opportunity,” “synergy,” or “important discussion.” After the list, select the best three, stating the audience and tradeoff for each. Then write a 45-word preview-text option for the strongest choice that gives the agenda, proposed duration, and an easy alternative such as email feedback or a different time. Before answering, check that each line accurately reflects the agenda and does not imply approval, partnership, or a commitment that has not happened. Flag if my meeting purpose is too broad to fit into a clear subject line. Ask up to three clarifying questions only if a required input is missing.
Fill in
| Placeholder | What to enter | Example |
|---|---|---|
| [RECIPIENT] | Describe the person’s role, organization, and level of familiarity with you. | Dana Ortiz, VP of Operations at a regional grocery chain; met once during a vendor discovery call. |
| [MEETING PURPOSE] | State the concrete reason for the meeting in one or two sentences. | Request a short meeting to review a pilot proposal for reducing produce shrink reporting delays. |
| [RECIPIENT RELEVANCE] | Explain the specific decision, problem, or opportunity relevant to the recipient. | Dana owns store operations metrics and asked in the prior call how the data could reach district managers faster. |
| [TIME ASK AND FORMAT] | Enter the requested duration, date range if relevant, and format such as video call or in person. | Twenty-minute video call during the first week of October. |
| [RELATIONSHIP AND CONTEXT] | Describe how you know the recipient and any prior conversation, project, or correspondence. | We spoke on Sept. 18 with her procurement manager, Miles Chen; Dana asked us to send a concise next step. |
| [AGENDA OR DECISION] | List the one to three agenda items or decision you need. | Review the proposed two-store pilot, confirm data access assumptions, and decide whether to involve district operations. |
| [TONE AND SETTING] | State the tone and whether the request is internal, customer-facing, sales-related, or another setting. | Professional, concise B2B follow-up. |
How to use
- Write the meeting purpose as a decision or outcome, not simply a topic, before generating lines.
- Match the subject to the actual relationship; a customer follow-up can reference prior context, while a cold request should be more direct.
- Check the preview text includes the time ask and an alternative path so the request does not feel cornering.
- Follow up with: “Draft a 110-word email using the strongest subject, with three agenda bullets and two proposed times.”
Variations
Internal decision meeting
Use this when colleagues need to decide or unblock a defined issue.
Generate 12 subject lines for an internal meeting about [DECISION OR BLOCKER]. The participants are [ATTENDEES], and the required outcome is [OUTCOME]. The meeting is [DURATION AND DATE]. Keep lines under 10 words and name the decision where possible. Group them into decision-first, project-first, and deadline-aware options. Do not imply that agreement already exists or add urgency beyond [REAL DEADLINE]. Recommend three and write preview text with the agenda and preparation needed.
Customer check-in
Use this when requesting a progress, renewal, or implementation conversation.
Write 15 subject lines for a customer meeting request with [CUSTOMER NAME]. The purpose is [PURPOSE], based on [REAL ACCOUNT CONTEXT], and I am asking for [TIME ASK]. Make the lines concise, useful, and specific to the customer’s work. Include five progress-oriented, five planning-oriented, and five issue-resolution options. Do not promise outcomes, call it a “quick chat,” or hide a renewal discussion. Add a 50-word preview text for the best line.
Informational interview
Use this when asking someone for career perspective rather than a business meeting.
Create 12 subject lines for requesting a [DURATION] informational conversation with [RECIPIENT ROLE] about [TOPIC OR FIELD]. My genuine connection or reason for reaching out is [CONTEXT], and I am seeking [SPECIFIC PERSPECTIVE]. Keep each line under 9 words, respectful, and low-pressure. Do not imply a job opportunity, referral, or existing relationship. Choose the best three for a cold email, alumni connection, and former colleague, then write matching preview text.
Tips
- A useful meeting subject usually names the decision, deliverable, or problem rather than the broad project name alone.
- Keep only one primary purpose in the request; if there are several decisions, identify the first decision and move the rest into the agenda.
- Use a real deadline only when the recipient’s response can change the outcome; artificial urgency damages trust.
- For a cold request, make the meeting’s relevance clear without claiming that the recipient will benefit before you understand their priorities.
FAQ
Should the subject line include the meeting length?
Include it when the request is cold or time-sensitive, because it lowers uncertainty. For an established recurring meeting, the topic is usually more useful.
Is “quick question” a good meeting subject?
Usually not. It hides the subject and can feel misleading when the email asks for time. Name the topic or decision instead.
How many meeting topics should I put in one request?
One main purpose and up to three agenda items is usually enough. A longer list may signal that the meeting will be unfocused.