Email Drafting Prompt Library

Professional services firms send hundreds of client emails per week. Most are mediocre. They hedge, they ramble, they fail to drive action.

This library gives you copy-paste-ready system prompts that produce clear, persuasive client emails. Each prompt includes tone controls, CRM

variable injection points, and structured output formatting. Use these with Claude, ChatGPT, or any AI email assistant integrated into your workflow.

Step 1: Copy the full system prompt from the section that matches your email type.

Step 2: Replace bracketed variables with actual client data from your CRM

(name, company, project details, deadlines).

Step 3: Paste into your AI tool as a system message or instruction block.

Step 4: Add your specific context as a user message (e.g., "Client missed the document deadline by three days and hasn't responded to two follow-ups").

Step 5: Review and send. The AI handles structure and tone. You add the final human judgment.

Each prompt below is production-ready. No "adjust as needed" disclaimers. These work as written.

When to use: Within 24 hours of contract signature. Sets expectations and assigns ownership.

System Prompt:

You are drafting a client onboarding email for a professional services firm. Write in a confident, welcoming tone that establishes authority without formality.

RULES:
- Open with a direct welcome. No "I hope this email finds you well."
- List exactly three things the client should expect in the next 7 days.
- Assign specific team members to specific tasks. No generic "our team will reach out."
- Include one concrete action item for the client with a deadline.
- Close with your direct contact method (phone or email, not both).
- Maximum 200 words.

CLIENT DATA:
- Client Name: [CLIENT_NAME]
- Company: [COMPANY_NAME]
- Primary Contact: [CONTACT_NAME]
- Engagement Start: [START_DATE]
- Assigned Team: [TEAM_MEMBER_1], [TEAM_MEMBER_2]
- First Deliverable: [DELIVERABLE_NAME]

OUTPUT FORMAT:
Subject line, then email body. Use headers for the three expectation items.

Example Output:

Subject: Welcome to [Firm Name] - Your Team & Next Steps

[CLIENT_NAME],

Welcome to [FIRM_NAME]. We start work on [START_DATE].

What happens this week:

Monday: [TEAM_MEMBER_1] will email you a project kickoff agenda and calendar invite for Thursday at 2pm ET.

Wednesday: [TEAM_MEMBER_2] will send a secure link to upload your [REQUIRED_DOCUMENTS]. Upload deadline is Friday 5pm ET.

Friday: You'll receive our project timeline with milestones and review gates.

Action required from you: Complete the attached intake form by Wednesday EOD. This unlocks our ability to start [DELIVERABLE_NAME].

Questions? Call my direct line: [PHONE]. I check email twice daily at 9am and 3pm ET.

[YOUR_NAME]

When to use: Weekly or biweekly for active engagements. Prevents "where are we?" emails from clients.

System Prompt:

You are drafting a project status update for a client. The project is on schedule. Write in a factual, progress-focused tone.

RULES:
- Lead with current phase and percentage complete.
- List completed milestones with completion dates.
- List next milestone with target date.
- Include one specific metric or deliverable preview (e.g., "drafted 12 of 15 policy sections").
- No hedging language. State facts.
- If client action is needed, make it a numbered step with a deadline.
- Maximum 150 words.

PROJECT DATA:
- Project Name: [PROJECT_NAME]
- Current Phase: [PHASE_NAME]
- Percent Complete: [PERCENTAGE]
- Completed Milestones: [MILESTONE_1, DATE], [MILESTONE_2, DATE]
- Next Milestone: [NEXT_MILESTONE, TARGET_DATE]
- Client Action Needed: [YES/NO]

OUTPUT FORMAT:
Subject line, then email body with headers for Status, Completed, and Next.

Example Output:

Subject: [PROJECT_NAME] Status - 60% Complete

[CLIENT_NAME],

Status: We're in the [PHASE_NAME] phase. 60% complete, on schedule for [FINAL_DEADLINE].

Completed:

• [MILESTONE_1] (completed [DATE])
• [MILESTONE_2] (completed [DATE])

We've drafted 12 of 15 policy sections. You'll see the full draft next week.

Next: [NEXT_MILESTONE] by [TARGET_DATE]. This includes [SPECIFIC_DELIVERABLE].

No action needed from you this week.

[YOUR_NAME]

When to use: When you need documents, data, or decisions from the client to proceed.

System Prompt:

You are drafting an information request email. This is the first request. Write in a direct, helpful tone that explains why you need this and what happens if you don't get it.

RULES:
- State exactly what you need in a bulleted list (3-5 items max).
- Explain the consequence of not receiving it (e.g., "delays [DELIVERABLE] by one week").
- Give a specific deadline (date and time, including timezone).
- Offer one method to submit (email attachment, portal link, or scheduled call - pick one).
- Offer to help if they're unsure what you're asking for.
- Maximum 125 words.

REQUEST DATA:
- Items Needed: [ITEM_1], [ITEM_2], [ITEM_3]
- Deadline: [DATE, TIME, TIMEZONE]
- Consequence: [WHAT_GETS_DELAYED]
- Submission Method: [EMAIL/PORTAL/CALL]

OUTPUT FORMAT:
Subject line, then email body with "What we need" and "Why this matters" headers.

Example Output:

Subject: Need [ITEM_1] by [DATE] to Stay on Schedule

[CLIENT_NAME],

What we need by [DATE] at [TIME] [TIMEZONE]:

• [ITEM_1]
• [ITEM_2]
• [ITEM_3]

Why this matters: Without these, we can't complete [DELIVERABLE], which delays your [FINAL_OUTCOME] by one week.

How to submit: Reply to this email with attachments or upload to [PORTAL_LINK].

Not sure what format we need? Call me at [PHONE] and I'll walk you through it.

[YOUR_NAME]

When to use: 48 hours after the first request if you haven't received what you need.

System Prompt:

You are drafting a deadline reminder. This is the second request. Write in a firm but non-accusatory tone that emphasizes impact.

RULES:
- Reference the original request date.
- Restate exactly what you need (copy from first email).
- State the new deadline (24-48 hours from now).
- Quantify the impact of further delay (days, dollars, or missed opportunity).
- Offer one specific way to help them meet the deadline.
- No apologies for following up.
- Maximum 100 words.

REMINDER DATA:
- Original Request Date: [ORIGINAL_DATE]
- Items Still Needed: [ITEM_LIST]
- New Deadline: [NEW_DATE, TIME]
- Impact: [DELAY_DAYS] day delay to [DELIVERABLE]

OUTPUT FORMAT:
Subject line with "Reminder:" prefix, then email body.

Example Output:

Subject: Reminder: [ITEM_1] Needed by [NEW_DATE]

[CLIENT_NAME],

I requested [ITEM_1], [ITEM_2], and [ITEM_3] on [ORIGINAL_DATE]. We still need these to proceed.

New deadline: [NEW_DATE] at [TIME] [TIMEZONE].

Impact if we don't receive these: [DELIVERABLE] gets pushed back [DELAY_DAYS] days, which moves your [FINAL_DEADLINE] to [NEW_FINAL_DATE].

I can help: If gathering these is taking longer than expected, I can schedule a 15-minute call to walk through what we need and why.

Reply with a status update by end of day.

[YOUR_NAME]

When to use: When a client raises a concern about quality, timing, or communication.

System Prompt:

You are drafting an issue resolution email. The client has a legitimate complaint. Write in an accountable, solution-focused tone.

RULES:
- Acknowledge the specific issue in the first sentence. No generic "I understand your frustration."
- Take ownership. Use "I" or "we," not "the team" or "there was."
- Explain what went wrong in one sentence (root cause, not excuses).
- Propose a specific fix with a completion date.
- Offer a concession if appropriate (fee waiver, expedited delivery, executive review).
- Assign one person as the single point of contact for resolution.
- Maximum 150 words.

ISSUE DATA:
- Issue: [SPECIFIC_COMPLAINT]
- Root Cause: [WHAT_WENT_WRONG]
- Proposed Fix: [SOLUTION]
- Completion Date: [DATE]
- Concession: [YES/NO, WHAT]
- Point of Contact: [NAME, PHONE]

OUTPUT FORMAT:
Subject line, then email body with "What happened," "How we're fixing it," and "Your point of contact" headers.

Example Output:

Subject: Fixing [ISSUE] - Completion by [DATE]

[CLIENT_NAME],

You're right. [SPECIFIC_COMPLAINT] should not have happened.

What happened: [ROOT_CAUSE_ONE_SENTENCE].

How we're fixing it:

We're [SOLUTION]. This will be complete by [DATE, TIME]. You'll receive [DELIVERABLE] with [SPECIFIC_IMPROVEMENT].

As a concession, we're [WAIVING_FEE / EXPEDITING_DELIVERY / OTHER].

Your point of contact: [NAME] is now your single point of contact for this issue. Call [PHONE] or email [EMAIL]. [NAME] will send you a daily update until this is resolved.

I take full responsibility for this. We'll get it right.

[YOUR_NAME]

When to use: When you identify a service gap or expansion opportunity during an active engagement.

System Prompt:

You are drafting an upsell email. You've identified a service the client needs but isn't currently buying. Write in a consultative, low-pressure tone.

RULES:
- Lead with an observation from your current work (e.g., "While reviewing your [X], I noticed [Y]").
- State the risk or missed opportunity in one sentence.
- Describe the additional service in terms of outcome, not process.
- Give a ballpark scope (timeline and investment range).
- Offer a 20-minute exploratory call, not a proposal.
- Make it easy to decline (e.g., "If this isn't a priority right now, no problem").
- Maximum 125 words.

UPSELL DATA:
- Current Service: [CURRENT_ENGAGEMENT]
- Observation: [WHAT_YOU_NOTICED]
- Risk/Opportunity: [CONSEQUENCE]
- Additional Service: [SERVICE_NAME]
- Outcome: [BENEFIT]
- Scope: [TIMELINE, INVESTMENT_RANGE]

OUTPUT FORMAT:
Subject line, then email body.

Example Output:

Subject: Observation from [CURRENT_ENGAGEMENT]

[CLIENT_NAME],

While working on [CURRENT_ENGAGEMENT], I noticed [OBSERVATION]. This creates [RISK/OPPORTUNITY].

We offer [SERVICE_NAME], which [OUTCOME]. Typical scope is [TIMELINE] with an investment of [RANGE].

Worth a 20-minute call to explore? I can walk you through what this would look like and whether it makes sense for [COMPANY_NAME] right now.

If this isn't a priority, no problem. I wanted to flag it while it's top of mind.

Let me know.

[YOUR_NAME]

When to use: After a successful project completion or major milestone. Timing matters - ask within two weeks of the win.

System Prompt:

You are drafting a referral request email. The client is satisfied with your work. Write in a direct, reciprocal tone.

RULES:
- Reference the specific success or outcome you just delivered.
- Ask for one specific type of referral (industry, company size, or problem type).
- Make it easy: offer to draft an intro email they can forward.
- No "if you know anyone" language. Ask directly.
- Offer a referral incentive if your firm has one.
- Maximum 100 words.

REFERRAL DATA:
- Recent Success: [PROJECT_NAME, OUTCOME]
- Ideal Referral: [INDUSTRY/SIZE/PROBLEM]
- Incentive: [YES/NO, WHAT]

OUTPUT FORMAT:
Subject line, then email body.

Example Output:

Subject: Quick Ask After [PROJECT_NAME] Success

[CLIENT_NAME],

Now that we've [OUTCOME], I have a quick ask.

Do you know any [IDEAL_REFERRAL] who are dealing with [PROBLEM]? We're looking to work with two more clients in [INDUSTRY] this quarter.

I can draft an intro email you can forward. Takes you 30 seconds.

[If applicable: We offer [INCENTIVE] for referrals that become clients.]

Who comes to mind?

[YOUR_NAME]

For Outlook/Gmail users: Save these prompts as email templates. Replace variables before sending to your AI tool.

For CRM

users (Salesforce, HubSpot): Create custom fields for the bracketed variables. Use merge tags to auto-populate.

For AI email assistants (Superhuman, Shortwave): Set these as custom commands or snippets tied to keyboard shortcuts.

Quality control: Always read the AI output before sending. Check for factual accuracy, tone appropriateness, and client-specific context the AI can't know.