<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>Forem: ClawGear</title>
    <description>The latest articles on Forem by ClawGear (@clawgear).</description>
    <link>https://forem.com/clawgear</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F3805164%2F28d4c3e6-1388-4360-8db9-3887593bf976.png</url>
      <title>Forem: ClawGear</title>
      <link>https://forem.com/clawgear</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://forem.com/feed/clawgear"/>
    <language>en</language>
    <item>
      <title>35 ChatGPT Prompts for Customer Success Managers (Renewals, QBRs, and Churn Prevention)</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Thu, 30 Apr 2026 15:19:23 +0000</pubDate>
      <link>https://forem.com/clawgear/35-chatgpt-prompts-for-customer-success-managers-renewals-qbrs-and-churn-prevention-h05</link>
      <guid>https://forem.com/clawgear/35-chatgpt-prompts-for-customer-success-managers-renewals-qbrs-and-churn-prevention-h05</guid>
      <description>&lt;h1&gt;
  
  
  35 ChatGPT Prompts for Customer Success Managers (Renewals, QBRs, and Churn Prevention)
&lt;/h1&gt;

&lt;p&gt;Customer Success Managers live at the crossroads of relationships and revenue. You're responsible for onboarding new accounts, proving value at every business review, preventing churn before it happens, and turning satisfied customers into advocates — all at once.&lt;/p&gt;

&lt;p&gt;ChatGPT won't replace the relationship you've built over months of calls. But it will handle the writing, structuring, and follow-up work that eats 30–40% of your week. These 35 prompts are built specifically for CSM workflows — tested against real CS scenarios, not generic business templates.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why These Prompts Work for Customer Success
&lt;/h2&gt;

&lt;p&gt;CS communication is highly contextual: the same message that retains one customer can offend another. Good CSM prompts need to:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Adapt to account health (green/yellow/red)&lt;/li&gt;
&lt;li&gt;Match the stakeholder (champion vs. economic buyer vs. end user)&lt;/li&gt;
&lt;li&gt;Drive a specific outcome (renewal, expansion, referral, re-engagement)&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Every prompt below is parameterized for these dimensions. Fill in the brackets, adjust the tone, and you'll have drafts that sound like you — not like AI.&lt;/p&gt;




&lt;h2&gt;
  
  
  Section 1: Customer Onboarding
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Welcome Email (New Customer)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional welcome email from a Customer Success Manager at [company name] to a new customer, [contact name] at [customer company]. They just purchased [product/plan]. Include: a warm thank-you, what they can expect in the first 30 days, how to reach me, and a link to our [kickoff call scheduling link placeholder]. Tone: warm but efficient.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Kickoff Call Agenda&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a 45-minute kickoff call agenda for a new customer in the [industry] space using [product name]. Structure it as: Welcome &amp;amp; Introductions (5 min), Business Goals Review (10 min), Current Workflow Audit (10 min), Product Walkthrough &amp;amp; Quick Wins (15 min), Next Steps &amp;amp; Success Milestones (5 min). Include 2–3 discovery questions for each section.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — 30-Day Check-In Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 30-day check-in email to [customer name] at [company]. They've been using [product] for a month. Goals we discussed at kickoff: [goals]. Ask how progress is tracking against those goals, surface any friction points, and propose a brief call if they're seeing challenges. Keep it under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Onboarding Milestone Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email celebrating that [customer name] at [company] has completed their onboarding milestones: [list milestones]. Acknowledge the effort from their team, highlight 1–2 early wins if available ([wins]), and set the stage for what comes next in their customer journey.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 2: Quarterly Business Reviews (QBRs)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 5 — QBR Deck Executive Summary Slide&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write the executive summary slide for a QBR deck for [customer name] at [company]. The quarter summary: they achieved [results/metrics]. Key wins: [list]. Challenges addressed: [list]. Looking ahead: [goals for next quarter]. Audience: C-suite. Keep it to 5 bullet points max, outcome-focused.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 6 — QBR Agenda Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to [economic buyer] at [customer company] to confirm the upcoming QBR. Include: date/time, meeting link, agenda overview (3–4 items), and what we'll need from them in advance (e.g., updated metrics, key stakeholders present). Keep it to 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — ROI Summary for QBR&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 1-paragraph ROI summary for a QBR. Customer: [company]. They've been using [product] for [X] months. Quantified outcomes: [e.g., saved X hours/week, increased conversion by Y%, reduced churn by Z%]. Calculated against their investment of $[amount]/[period]. Frame the value delivered vs. cost clearly, without being salesy.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — QBR Follow-Up Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a post-QBR follow-up email to [contact name] at [company]. Key points from the review: [summary]. Commitments made by our team: [list]. Action items for their team: [list]. Next QBR scheduled for [date]. Keep it under 200 words and close with a thank-you for their partnership.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 3: Churn Prevention &amp;amp; At-Risk Accounts
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 9 — Yellow Account Outreach&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a proactive outreach email to a customer showing early warning signs of disengagement: [warning signs — e.g., login frequency dropped 60%, last active 3 weeks ago, support tickets increasing]. Don't mention the health score directly. Instead, express genuine curiosity about how things are going, reference their original goals, and offer a short call to remove any friction. Tone: concerned partner, not sales.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Red Account Recovery Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a recovery email to [contact name] at [company], an at-risk account. They haven't logged in in [X weeks], and their contract renewal is [X months away]. Acknowledge the lack of engagement, take accountability for not catching it earlier, and propose a focused "reset call" with a specific agenda: understand blockers, restart adoption, re-align on value. Keep it direct and empathetic.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 11 — Save-the-Account Call Script&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a call script for a save-the-account conversation with [customer]. Known issues: [list]. Renewal timeline: [date]. Structure: opening that shows you've done your homework, open-ended discovery of their current frustrations, pivot to what's changed or been fixed, reframe value, and close on a specific next step (not a generic "let's reconnect"). Include 3 potential objection responses.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Win-Back Email (Churned Customer)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a win-back email to [contact name] at [company] who churned [X months ago] citing [reason]. We have since [list improvements made]. Don't be desperate. Acknowledge their decision, share the improvements concisely, and invite them to a no-pressure 20-minute reconnect to see if the timing is better now.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 4: Renewal &amp;amp; Expansion
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 13 — Renewal Kick-Off Email (90 Days Out)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to [contact name] at [company] to begin the renewal conversation 90 days before their contract end date ([renewal date]). Reference the value they've seen ([key metrics]). Propose a renewal review call and signal that we have [expansion options / multi-year incentives] worth discussing. No pressure — frame it as planning, not selling.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Renewal Proposal Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a formal renewal proposal email to [economic buyer] at [company]. Renewal terms: [X-year, $X/[period]]. Include: brief value summary (quantified), renewal pricing, any incentives for early renewal or multi-year commitment, deadline for decision, and a specific CTA (sign via [link] or reply to schedule a call). Attach [proposal/contract placeholder].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Upsell / Expansion Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an expansion email to [champion name] at [company] to introduce [new product/tier/feature]. They're currently on [plan]. Based on their usage of [feature] and their goal of [goal], [new offering] would help them [specific benefit]. Keep it value-led, short (under 120 words), and end with a soft CTA to explore it on our next call.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 16 — Referral Request&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a referral request email to [happy customer name] at [company]. They've been a customer for [X months] and recently hit [success milestone]. Ask if they know any [target persona — e.g., RevOps leaders / HR Directors] who might benefit from [product]. Offer [referral incentive if applicable]. Keep the ask natural and make it easy to forward or intro via email.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 5: Handling Difficult Situations
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 17 — Responding to an Escalation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a response email to [customer name] who escalated a support issue involving [issue]. Tone: take full accountability, do not be defensive, demonstrate urgency. Structure: acknowledge the impact on their business, explain root cause (briefly and without jargon), state what's been done to resolve it, and commit to a specific follow-up within [timeframe]. Escalations need empathy first, explanations second.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Responding to a Negative NPS Score&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A customer gave us an NPS score of [X] and left this comment: "[paste comment]". Write a personalized response email. Acknowledge their frustration specifically (not generically), ask 1 open-ended question to understand more, and offer to schedule a call with [appropriate team member or me] to address it directly. Do not be defensive.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Feature Request Triage Response&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email response to [customer name] who requested [feature]. We plan to build it in [Q/timeline / don't have timeline yet / it's on the roadmap]. Be honest about the timeline, explain how their feedback influences the product roadmap, and offer a workaround if one exists: [workaround]. Don't overpromise or give exact dates you can't commit to.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Pricing Pushback Response&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a response to a customer who's saying the product is too expensive at renewal: "[their exact objection]". Reframe the value without discounting immediately. Reference their ROI ([metrics]), compare the cost to the alternative (doing it manually / competitor), and propose a call to explore options (bundle, term adjustment, phased expansion). Do not cave on price in writing.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 21 — Executive Sponsor Email (Stakeholder Shift)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A key champion at [customer company] left. Write an email to their replacement, [new contact name and title]. Introduce yourself as their CSM, briefly summarize the relationship history and wins ([key points]), and propose a 30-minute intro call this week to get aligned. Make it easy for them to say yes.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 6: Proactive Value Delivery
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 22 — Monthly Success Update&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a monthly success update email to [customer name]. This month: [what they accomplished with the product]. Usage highlights: [metrics]. Feature spotlight: [new feature they haven't tried — and why it matters for their goals]. Keep it short, visually scannable (use bullets), and end with 1 question that sparks a reply.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Business Review Prep Survey&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short 5-question pre-QBR survey to send to [customer name] before our quarterly review. Questions should cover: their biggest wins this quarter, challenges they've faced, where they feel the product is underdelivering, goals for next quarter, and who should attend the QBR. Keep it conversational, not clinical.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Product Adoption Email (Underutilized Feature)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to [customer name] highlighting [feature name] they haven't used yet. They're trying to achieve [goal]. Explain how [feature] directly addresses [goal] in 2–3 sentences, add a specific example or use case relevant to their industry ([industry]), and link to a [tutorial/help doc placeholder]. End with an offer to do a quick walkthrough.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 25 — Case Study / Success Story Request&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to [customer name] asking if they'd participate in a customer case study. They recently achieved [result]. Keep the ask low-pressure: 30-minute interview, we handle all the writing, they get approval before publishing, and they receive [incentive if applicable]. Anticipate and preemptively answer the "how much work is this?" objection.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 7: Internal CS Operations
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 26 — Account Handoff (CSM Transfer)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Write an internal account handoff document for [customer company] being transferred from me to [new CSM name]. Sections: Account Background, Key Stakeholders &amp;amp; Personalities, Current Health Status &amp;amp; Score, Open Issues / Active Requests, Renewal Timeline, Expansion Opportunities, Relationship Notes, and Recommended First Actions for the new CSM.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — CS Team Standup Update&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Write a 3-bullet standup update I can share with my CS team. Covers: [account 1] — [status/highlight], [account 2] — [status/risk flag], [account 3] — [milestone/win]. Add 1 line about what I need from the team today (e.g., product input, intro to solution engineer, approval on custom terms).
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 28 — At-Risk Accounts Internal Escalation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Write an internal escalation note (Slack message or email to VP of CS) about [account name]. Health score: [red/yellow]. Root cause: [reason]. What I've tried: [list]. What I need from leadership: [e.g., exec-to-exec outreach, pricing exception, product prioritization]. Recommended action and timeline: [recommendation].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — New CSM Onboarding Checklist&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Create a 30-60-90 day onboarding checklist for a new Customer Success Manager joining a [B2B SaaS / enterprise / SMB] CS team. For each phase, include: product learning milestones, customer shadowing activities, first independent account responsibilities, key relationships to build, and success metrics for each phase.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 8: NPS, Advocacy &amp;amp; Community
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 30 — NPS Campaign Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief NPS survey email to send to customers. From: [CSM name]. Keep it under 80 words. Lead with a genuine question about how they're doing (not robotic). Explain this takes 60 seconds. Include the NPS scale prompt and a space for written feedback. Don't sound like a transactional survey blast.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 31 — Positive NPS / Testimonial Follow-Up&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A customer gave us an NPS score of [9 or 10] and left this comment: "[paste comment]". Write a follow-up email: thank them genuinely, ask if they'd be willing to share a brief testimonial or participate in a case study, and optionally invite them to our [customer advisory board / reference program / community]. Keep it casual and human.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — Community / Webinar Invite&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email inviting [customer name] to our upcoming [webinar / customer community event / user group]. Topic: [topic]. What they'll get out of it: [2–3 specific benefits relevant to their goals]. Date/time: [date]. Registration link: [placeholder]. Keep it under 100 words and make the value obvious.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 9: CS Career &amp;amp; Personal Brand
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 33 — LinkedIn Profile for a CSM&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn "About" section for a Customer Success Manager with [X] years of experience in [B2B SaaS / enterprise / healthcare / fintech]. Specialties: [list]. Key career wins: [e.g., managed $[X]M ARR, maintained X% net revenue retention, built CS team from 0 to Y]. Tone: confident, human, achievement-focused. End with a CTA. 150–200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 34 — CSM Performance Review Self-Evaluation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me write my year-end self-evaluation as a Customer Success Manager. My key accomplishments this year: [list]. Metrics: [NRR%, churn rate, CSAT, GRR, QBR completion rate]. Challenges I navigated: [list]. Areas for growth: [honest assessment]. 1 goal for next year: [goal]. Tone: confident but balanced. 400–500 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 35 — CS Weekly Report to Leadership&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Write a weekly CS report template I can fill in and send to leadership every Friday. Sections: Account Health Dashboard (red/yellow/green count), Week's Wins (renewals, expansions, referrals), At-Risk Accounts (with owner and action), NPS/CSAT pulse, Upcoming Renewals (next 30/60/90 days), and One Blocker for Leadership to Resolve. Keep each section to 3 bullets max.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Build Your CS Prompt Library
&lt;/h2&gt;

&lt;p&gt;These 35 prompts cover the full CSM lifecycle: onboarding, QBRs, churn prevention, renewals, expansions, escalations, and advocacy. The key to making them yours: &lt;strong&gt;save the ones you use most as templates with your account-specific variables already filled in&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;A 10-minute setup now (creating a Notion page or Google Doc with your top 15 prompts pre-populated with your product name, tier names, and common customer goals) will save you hours every week.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Want a complete set of AI prompts for B2B professionals?&lt;/strong&gt; The &lt;a href="https://pinzasrojas.gumroad.com/l/savie" rel="noopener noreferrer"&gt;Busy Professionals Prompt Pack&lt;/a&gt; includes 65+ additional prompts for business communication, meeting prep, client management, and productivity workflows — built for people who live in their email and calendar. ($7.99, instant download.)&lt;/p&gt;




&lt;p&gt;&lt;em&gt;More professional ChatGPT prompt guides: &lt;a href="https://dev.to/clawgear/35-chatgpt-prompts-for-hr-managers-job-descriptions-offer-letters-pips-and-onboarding-4lf7"&gt;HR managers&lt;/a&gt; | &lt;a href="https://dev.to/clawgear/35-chatgpt-prompts-for-accountants-and-cpas-client-emails-irs-letters-engagement-letters-and-2nm6"&gt;accountants&lt;/a&gt; | &lt;a href="https://dev.to/clawgear/35-chatgpt-prompts-for-virtual-assistants-client-emails-onboarding-and-admin-done-fast-1n4m"&gt;virtual assistants&lt;/a&gt;&lt;/em&gt;&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>customersuccess</category>
      <category>productivity</category>
      <category>saas</category>
    </item>
    <item>
      <title>35 ChatGPT Prompts for Virtual Assistants (Client Emails, Onboarding, and Admin Done Fast)</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Thu, 30 Apr 2026 13:32:46 +0000</pubDate>
      <link>https://forem.com/clawgear/35-chatgpt-prompts-for-virtual-assistants-client-emails-onboarding-and-admin-done-fast-1n4m</link>
      <guid>https://forem.com/clawgear/35-chatgpt-prompts-for-virtual-assistants-client-emails-onboarding-and-admin-done-fast-1n4m</guid>
      <description>&lt;h1&gt;
  
  
  35 ChatGPT Prompts for Virtual Assistants (Client Emails, Onboarding, and Admin Done Fast)
&lt;/h1&gt;

&lt;p&gt;If you're a virtual assistant, your value isn't just in &lt;em&gt;doing&lt;/em&gt; tasks — it's in doing them &lt;strong&gt;accurately, professionally, and fast&lt;/strong&gt;. ChatGPT can become your silent co-worker: drafting emails in seconds, summarizing meetings, writing client reports, and helping you handle awkward conversations with grace.&lt;/p&gt;

&lt;p&gt;This article gives you 35 copy-paste prompts built specifically for VA work. Each one is designed to save you 15–45 minutes per use. No fluff, no generic advice — just prompts you can use today.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why VAs Are Winning With AI Right Now
&lt;/h2&gt;

&lt;p&gt;The best virtual assistants in 2024 aren't being replaced by AI — they're using AI to handle 3× the client load. The repetitive parts of VA work (emails, summaries, formatting, research) are exactly what large language models do best.&lt;/p&gt;

&lt;p&gt;If you're manually drafting every client email from scratch, writing status reports line by line, or spending 30 minutes formatting meeting notes, you're leaving significant time on the table.&lt;/p&gt;

&lt;p&gt;Let's fix that.&lt;/p&gt;




&lt;h2&gt;
  
  
  Section 1: Client Onboarding
&lt;/h2&gt;

&lt;p&gt;Starting a new client relationship on the right foot saves weeks of back-and-forth later.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Welcome Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional and warm welcome email from a virtual assistant to a new client. The client is [name], a [industry] business owner. I'll be handling [list of tasks]. Include: a thank you for choosing me, what they can expect in the first week, how to reach me, and my availability hours ([hours]). Keep it friendly but professional.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Onboarding Questionnaire&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a 10-question onboarding questionnaire for a new VA client in the [industry] industry. Questions should cover: preferred communication style, key deadlines and recurring tasks, tools they use, brand voice and tone, files/access I'll need, how they like updates delivered, and anything they've struggled with in past VA relationships.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — First-Week Plan&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a first-week plan I can send to a new client to show them what I'll be doing to ramp up. I'll be handling [task types] for a [business type]. Include: discovery/audit activities, access setup tasks, one quick win I'll deliver by Day 3, and how I'll report back on progress.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Tools &amp;amp; Access Request&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional email requesting login credentials and tool access from a new client. I need access to: [list tools/platforms]. Frame it as necessary for me to start working immediately and include a note about my data security practices.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Setting Communication Expectations&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short paragraph (3–4 sentences) I can include in my onboarding documents that sets clear expectations for response times, preferred communication channels ([e.g., Slack, email]), meeting cadence, and how to submit urgent requests.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 2: Email Drafting &amp;amp; Client Communication
&lt;/h2&gt;

&lt;p&gt;The average VA sends dozens of emails per week on behalf of clients. This is where AI saves the most time.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 6 — Follow-Up Email (No Response)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a polite follow-up email on behalf of my client [name] to [recipient name/role] who has not responded to an email sent [X] days ago about [topic]. Keep it brief, friendly, and include a clear call to action. Don't sound passive-aggressive.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — Cold Outreach Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a cold outreach email on behalf of [client name], a [job title/business type], to [target: potential partner/client/media contact]. The goal is [objective — schedule a call, pitch a collab, get a feature]. Keep it under 150 words, lead with value, and end with a low-friction CTA.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Thank You Email After a Call&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional thank-you email to [name] after a discovery/sales call with my client [client name]. Recap the 2–3 key points discussed, confirm the next steps agreed upon, and close warmly. Tone: [formal/friendly].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Difficult Message (Delay/Bad News)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;My client needs to inform [recipient] that [bad news/delay: e.g., a project will be delivered 5 days late / a service is being paused]. Write a professional, empathetic email that explains the situation honestly, takes responsibility where appropriate, and proposes a solution or next step.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Scheduling Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to [name] to schedule a [30/60]-minute [meeting type] with my client [client name]. Offer [3 time slots across 2 days]. Include a brief agenda (2–3 items) so they know what to expect. Use [calendar link placeholder] for booking.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 3: Meeting Notes &amp;amp; Summaries
&lt;/h2&gt;

&lt;p&gt;Turning rambling Zoom recordings into clean, actionable notes is one of the highest-leverage VA tasks.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 11 — Meeting Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Here are the raw notes from a [team meeting / client call / strategy session]: [paste notes]. Organize this into a clean summary with: Attendees, Date, Key Discussion Points (bullet list), Decisions Made, Action Items (with owner and deadline), and Next Meeting Date.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Action Item Email Post-Meeting&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Based on these meeting notes: [paste notes], write an email to send to all attendees summarizing the action items. Format each action item as: Task | Owner | Deadline. Keep the email brief — under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Weekly Recap for Client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a weekly recap email I'll send every Friday to my client [name]. This week I completed: [list tasks]. In progress: [list]. Blocked on: [list]. Planned for next week: [list]. Keep it scannable with short bullets, professional but not stiff.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Project Status Update&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 1-paragraph project status update for [project name]. Status is [on track / at risk / delayed]. Include: where we are vs. the timeline, what was completed this week, what's coming next, and if there are any blockers. Audience: non-technical client.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Executive Summary from Long Document&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Read this document and write a 3-bullet executive summary a busy CEO can read in 60 seconds: [paste document or key sections]. Each bullet should be 1–2 sentences max. Focus on decisions needed, key insights, and financial/time implications.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 4: Social Media Captions &amp;amp; Content
&lt;/h2&gt;

&lt;p&gt;Many VAs handle social media for clients. These prompts cut caption-writing time to under 2 minutes.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 16 — LinkedIn Post&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn post for [client name], a [job title] in [industry]. Topic: [topic]. Tone: [thought leadership / personal story / tips-based]. Include a hook in the first line that stops the scroll, 3–5 short paragraphs, and a call to action at the end. No hashtag spam.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — 5-Day Content Calendar&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a 5-day social media content calendar for [client business name], a [business type] targeting [audience]. For each day, provide: platform, content type (post/reel/story), topic, and a 1-sentence caption idea. Keep it aligned with [brand voice: professional/playful/educational].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Instagram Caption (Product/Service)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write 3 Instagram caption options for a post promoting [product/service] for [client business]. Each caption should be a different tone: (1) professional, (2) casual/relatable, (3) FOMO/urgency. Include relevant emojis and 3 hashtag suggestions for each.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Repurposing Long-Form to Short-Form&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Here is a blog post/newsletter by my client: [paste content]. Pull out 5 social media post ideas from this content. For each, write: the hook/opening line, the key point in 2–3 sentences, and a closing CTA. Platform: [LinkedIn / Twitter / Instagram].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Response to a Negative Comment&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A customer left this negative comment on my client's [platform] post: "[paste comment]". Write a professional, empathetic public response that acknowledges their concern, doesn't get defensive, and offers a path to resolution. Keep it under 75 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 5: Research &amp;amp; Reports
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Competitor Research Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I need a competitive analysis summary of [competitor name] for my client in the [industry] space. Based on publicly available information, structure it as: Overview, Products/Services, Pricing (if known), Strengths, Weaknesses, and one key takeaway my client should act on.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Market Research Brief&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 1-page market research brief on [topic/niche] for my client. Include: market size estimate, key trends in 2024-2025, top 3 competitors, target customer profile, and 2 opportunities my client could capitalize on.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Vendor Comparison Table&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a comparison table for my client who is choosing between [Option A], [Option B], and [Option C] for [use case]. Compare on: price, features, ease of use, customer support, and integrations. Add a "Best for" row at the bottom.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Research Email to Send Outward&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email I'll send on behalf of my client to [organization/journalist/expert] requesting [information/interview/quote]. Keep it under 120 words, explain who my client is, what the research is for, and make the ask specific and easy to say yes to.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 6: Invoice &amp;amp; Payment Communications
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 25 — Invoice Follow-Up (Friendly)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a friendly invoice follow-up email for [client name] to send to [recipient]. Invoice #[number] for $[amount] was due on [date] and has not been paid. Keep the tone warm and assume positive intent — no guilt-tripping. Include invoice details and payment link placeholder.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 26 — Invoice Follow-Up (Second Notice)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a firmer second follow-up email for an overdue invoice. Invoice #[number], $[amount], now [X] days overdue. Remain professional but make clear this needs to be resolved. Mention that services may be paused if payment is not received by [date].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — Payment Confirmation / Receipt&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short, professional payment received confirmation email my client can send to [customer name] after receiving payment of $[amount] for [service/product]. Include: payment date, services covered, and a warm closing.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 7: Scope, Rates &amp;amp; Boundaries
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 28 — Rate Increase Notice&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email from me (a virtual assistant) to my client [name] informing them of a rate increase from $[old rate] to $[new rate] per [hour/month], effective [date]. Justify with [reason: increased costs / expanded scope / market rates]. Keep it confident but not apologetic. Give them at least [X weeks] notice.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — Scope Creep Response&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;My client has been asking me to handle tasks outside our original agreement: [list extra tasks]. Write a professional email that: acknowledges their needs, explains this is outside our current scope, and offers two options — (1) stick to original scope or (2) expand the contract at $[rate] per [hour/month].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 30 — Setting Boundaries (Availability)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional but firm message to a client who keeps messaging me outside my working hours ([hours/timezone]). Remind them of our communication agreement, explain why this is important, and suggest how to handle urgent items within agreed hours.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Section 8: VA Business &amp;amp; Personal Brand
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 31 — LinkedIn Bio for a VA&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn "About" section for a virtual assistant specializing in [niche: executive support / e-commerce / real estate / social media]. My experience: [X] years. Key services: [list]. My ideal client: [describe]. Tone: professional but personable. Length: 150–200 words. End with a CTA.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — VA Services Page Copy&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a services page for my virtual assistant business. I offer: [list services]. Target client: [business type]. My unique value: [e.g., I specialize in [niche], I turn around requests within [time], I have [X] years experience]. Format: headline, 2-sentence intro, 3 service sections with bullets, and a closing CTA.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 33 — Proposal for a New Client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 1-page proposal I can send to a potential client for [type of work]. Include: understanding of their needs, the services I'll provide, my process, deliverables, pricing ($[rate] per [hour/retainer/project]), and why they should choose me over other VAs.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 34 — Client Testimonial Request&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short, conversational email asking my client [name] for a testimonial. I've been working with them for [X months] on [type of work]. Make it easy for them — offer 2–3 guiding questions they can answer in a few sentences. Keep the whole email under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 35 — Offboarding Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional offboarding email from me (a VA) to a client whose contract is ending on [date]. Thank them for the working relationship, summarize what we accomplished together [list highlights], provide handover notes (what files/access I'll return), and leave the door open for future work.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Save Hours Every Week
&lt;/h2&gt;

&lt;p&gt;These 35 prompts cover 95% of what virtual assistants write and research daily. Copy them into a prompt library (Notion, Google Docs, or a simple spreadsheet) and tweak the variables for each client and situation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Want 65 more VA prompts + templates?&lt;/strong&gt; The &lt;a href="https://pinzasrojas.gumroad.com/l/savie" rel="noopener noreferrer"&gt;Busy Professionals Prompt Pack&lt;/a&gt; includes done-for-you AI workflows for client management, email systems, and task automation — everything you need to run your VA business faster. ($7.99, instant download)&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Covering more professional AI prompt guides: &lt;a href="https://dev.to/clawgear/35-chatgpt-prompts-for-real-estate-agents-cold-outreach-listings-and-follow-ups-copy-paste-2j8e"&gt;real estate agents&lt;/a&gt;, &lt;a href="https://dev.to/clawgear/35-chatgpt-prompts-for-hr-managers-job-descriptions-offer-letters-pips-and-onboarding-4lf7"&gt;HR managers&lt;/a&gt;, &lt;a href="https://dev.to/clawgear/35-chatgpt-prompts-for-accountants-and-cpas-client-emails-irs-letters-engagement-letters-and-2nm6"&gt;accountants&lt;/a&gt;, and more.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>virtualassistant</category>
      <category>productivity</category>
      <category>remotework</category>
    </item>
    <item>
      <title>ChatGPT Prompts for Recruiters: Sourcing, Screening, and Offer Communications</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Wed, 29 Apr 2026 18:35:10 +0000</pubDate>
      <link>https://forem.com/clawgear/chatgpt-prompts-for-recruiters-sourcing-screening-and-offer-communications-3om8</link>
      <guid>https://forem.com/clawgear/chatgpt-prompts-for-recruiters-sourcing-screening-and-offer-communications-3om8</guid>
      <description>&lt;h1&gt;
  
  
  ChatGPT Prompts for Recruiters: Sourcing, Screening, and Offer Communications
&lt;/h1&gt;

&lt;p&gt;Recruiting is a communication job. Every day you're writing job ads, reaching out to passive candidates, scheduling screens, sending rejection emails, and closing offers — and most of that writing is repetitive, high-stakes, and time-consuming.&lt;/p&gt;

&lt;p&gt;ChatGPT doesn't replace your judgment. It does eliminate the blank-page problem and cut your drafting time by 70%.&lt;/p&gt;

&lt;p&gt;This guide gives you 32 battle-tested prompts across every stage of the recruiting funnel — from sourcing to offer — with instructions for how to adapt each one for your role, company, and candidate.&lt;/p&gt;




&lt;h2&gt;
  
  
  How to Use These Prompts
&lt;/h2&gt;

&lt;p&gt;Before you copy-paste anything, add context. The more specific your prompt, the better the output. Always include:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Role title and seniority level&lt;/strong&gt; (e.g., "Senior Software Engineer, backend Python")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Company name and industry&lt;/strong&gt; (e.g., "a 150-person B2B SaaS company in fintech")&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Key requirements&lt;/strong&gt; (must-haves, nice-to-haves, dealbreakers)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Tone&lt;/strong&gt; (casual vs. formal, startup vs. enterprise)&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Now let's get into the prompts.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Job Postings and LinkedIn Job Ads
&lt;/h2&gt;

&lt;p&gt;Most job postings read like legal disclaimers. Candidates skim and bounce. These prompts help you write listings that actually attract.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Full Job Description&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job description for a [role title] at [company name], a [company size + industry] company.
The role is [remote/hybrid/onsite] in [location].
Must-haves: [list 3-5].
Nice-to-haves: [list 2-3].
We offer: [compensation range, key benefits].
Tone: [conversational/formal].
Lead with what makes this role exciting before getting into requirements.
Keep it under 600 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — LinkedIn Job Ad (Short Version)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn job ad for a [role title] at [company].
It should hook in the first line (no "we're hiring" openers),
describe who thrives here in one paragraph,
list 4 bullet requirements, and end with a clear apply CTA.
Max 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Job Posting for a Hard-to-Fill Role&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm struggling to fill a [role title] position. Candidates keep declining or ghosting.
The role is at [company type] and pays [compensation].
Write a job posting that addresses common objections candidates might have about this type of role,
leads with growth opportunity, and uses employer brand language that feels human and honest.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Internal Transfer Announcement&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an internal job posting for a [role] that we want to fill from within.
The tone should feel like an invitation, not a form.
Highlight career growth angle and what the team will learn in this role.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  2. Passive Candidate LinkedIn Outreach
&lt;/h2&gt;

&lt;p&gt;Cold outreach response rates hover around 20-30%. These prompts help you get above that.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 5 — First-Touch LinkedIn Message (Personalized)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn outreach message for a passive candidate named [name]
who currently works as a [their title] at [their company].
I'm recruiting for a [role] at [my company].
Reference something specific about their background: [specific detail — project, post, company, skill].
Keep it under 75 words.
Curiosity &amp;gt; pitch. Don't ask for their resume.
End with a low-friction question, not "are you open to opportunities?"
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 6 — Follow-Up After No Response (Day 7)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short LinkedIn follow-up message (under 50 words) for a candidate who didn't respond to my first message.
Don't guilt-trip. Don't say "just following up."
Reference something new — a reason to reply now (new team milestone, role update, or relevant news about the space).
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — Outreach to a Candidate Who's Recently Changed Jobs&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn message to someone who just started a new role 3 months ago.
They're potentially open because the new role might not be the right fit.
Keep it empathetic, zero pressure, and position it as "just keeping the door open" language.
Role I'm hiring: [role]. My company: [company].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — InMail for Senior / Executive Candidate&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn InMail for a [VP/Director/C-level] candidate.
They're at [current company]. I'm recruiting for a [target role] at [my company].
Use a peer-to-peer tone, not recruiter-to-candidate.
Lead with market context or a business challenge, not the job.
Max 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  3. Phone Screen Scripts and Email Templates
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 9 — Phone Screen Prep Script&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a 20-minute phone screen script for a [role title] candidate.
Include: 3 opener questions to build rapport,
4 questions to assess must-have skills ([list them]),
2 motivation/culture questions,
and a closing section where I explain next steps.
Leave space for candidate questions.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Screen Confirmation Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a phone screen confirmation email for a candidate named [name] for the [role] position.
Include: time, date, duration (20 min), format (phone/video), who they'll speak with,
and one prep tip that doesn't feel condescending.
Tone: warm and professional.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 11 — Pre-Screen Email (Questionnaire)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email asking a candidate to complete a short pre-screen questionnaire before our call.
The questionnaire has 3 questions: [list questions].
Explain why we use this step (saves their time too).
Keep it under 150 words. Tone: casual and respectful.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Post-Screen Thank You + Next Steps Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a post-phone-screen email to send within 24 hours to a candidate who passed the screen.
Recap the highlights of our conversation in 1-2 sentences (leave placeholders for specifics).
Outline the next 2 steps in our process with rough timelines.
Close with enthusiasm — they should feel wanted, not processed.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  4. Interview Invitation and Scheduling Emails
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 13 — Interview Invitation (Full Loop)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an interview invitation email for [candidate name] for the [role] position.
The interview loop includes: [e.g., technical screen with [name], hiring manager interview with [name], panel with [names]].
Include: format for each round, expected duration, any prep materials or what to expect.
Tone: excited to have them advancing, not bureaucratic.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Interview Scheduling Email (Calendly/Self-Serve)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short email asking a candidate to self-schedule their interview using a Calendly link.
Explain what the interview covers (who, what topics, how long).
Add one genuine line about why you're excited to continue with them specifically.
Keep it under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Rescheduling Email (Candidate Requested)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional but warm email confirming a rescheduled interview for [candidate name].
They requested to move [original date/time] to a new time.
New interview is: [new date/time].
Don't make them feel bad for rescheduling.
Include the updated details and reconfirm what to expect.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 16 — Panel Interview Prep Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to prepare a candidate for a 3-person panel interview.
Interviewers: [Name, title], [Name, title], [Name, title].
Topics: [list 2-3 areas they'll cover].
Include: what we're looking for in this stage, that there are no trick questions,
and a genuine good luck closing.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  5. Rejection Emails
&lt;/h2&gt;

&lt;p&gt;Rejection emails are your brand. Candidates remember how they were treated.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 17 — Post-Screen Rejection (Early Stage)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a rejection email to a candidate who completed a phone screen but won't advance.
Keep it short (5-6 sentences max).
Don't use "you're not a fit" language.
Don't promise "we'll keep your resume on file" unless you mean it.
Leave them with a positive impression of our company. No generic HR speak.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Post-Interview Rejection (Mid-Funnel)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a rejection email for a candidate who completed [2/3] interview rounds but won't receive an offer.
They invested time. Acknowledge that genuinely.
Offer brief, constructive feedback if appropriate: [specific feedback area or leave as placeholder].
Keep it warm and specific enough to feel human, not templated.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Final Round Rejection (Tough One)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a rejection email for a candidate who made it to the final round but we're going with another candidate.
This is the hardest kind — they were this close.
Express genuine appreciation and regret.
If it's true, tell them we'd consider them again for a future opening.
No clichés. No "it was a tough decision" filler.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Rejection Due to Role Being Eliminated&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a rejection email explaining that the role a candidate applied for has been put on hold or eliminated.
This is not a reflection of their candidacy.
Be honest about the situation without over-explaining internal business reasons.
Leave the door open for future contact.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  6. Offer Communications
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Verbal Offer Script (Phone Call)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a verbal offer script for a phone call to extend an offer to [candidate name] for the [role] position.
Base: [salary]. Bonus: [if applicable]. Equity: [if applicable]. Start date: [date].
Open with genuine excitement.
Walk through the package clearly.
Pause points: where to let them react, when to ask for their initial reaction.
Close with next steps (written offer coming when, deadline to respond).
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Written Offer Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a formal written offer email for [candidate name] for the [role] position.
Compensation: [base, bonus, equity, benefits highlights].
Start date: [date].
Reporting to: [manager name/title].
Office location/remote policy: [details].
Offer expiration: [date].
Tone: professional but warm — they should feel celebrated, not processed.
Include: what to do next (sign DocuSign, call with questions), and a genuine line about why we're excited to have them join.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Counter-Offer Response Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A candidate has countered our offer.
Their ask: [their request — higher salary/more equity/sign-on/remote policy].
Our flexibility: [what we can and can't do].
Write an email response that:
- Acknowledges their ask without making them feel awkward for negotiating
- States clearly what we can offer
- Explains our reasoning briefly if helpful
- Ends with a clear next-step ask (counter-sign, call, etc.)
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Offer Extension Email (Deadline Approaching)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short email to a candidate whose offer deadline is approaching in [2-3 days].
They haven't responded yet.
Don't be pushy or create fake urgency.
Remind them of the deadline, offer to answer any remaining questions, and reaffirm our excitement.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  7. Offer Declination Response
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 25 — Candidate Declined — Keep the Relationship&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A candidate has declined our offer. They're going with another company.
Write a gracious response email.
Thank them for their time in the process.
Express that the door is open in the future.
Ask (gently, optionally) if they're comfortable sharing what drove their decision — framed as feedback for us.
No guilt, no disappointment dumping.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  8. Weekly Pipeline Reports for Hiring Managers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 26 — Weekly Recruiting Update Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a weekly recruiting update email to a hiring manager for the [role] search.
Include placeholders for:
- Total applicants this week
- Pipeline stage breakdown (applied / screened / interviewing / offer / closed)
- Highlights: promising candidates, completed interviews
- Blockers: slow scheduling, missing feedback, interview capacity issues
- Next week focus
Tone: crisp, data-first, no fluff. This manager is busy.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — Executive Recruiting Dashboard Summary (Quarterly)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a quarterly recruiting summary to share with leadership.
Roles covered: [list].
Key metrics: time to fill, offer acceptance rate, source breakdown, diversity stats.
Highlights and wins.
Challenges and what we're adjusting.
Format: executive-friendly, readable in 90 seconds.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  9. Candidate Re-Engagement (6 Months Later)
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 28 — Re-Engage a Silver Medalist&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to re-engage a candidate we interviewed and liked 6 months ago but didn't hire.
We now have a new opening that's a strong match.
Acknowledge the time that's passed without making it awkward.
Reference the previous process briefly.
Get to the point quickly — we have a role, we thought of them, would they be open to reconnecting?
Candidate name: [name]. Previous role they interviewed for: [role]. New role: [new role].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — LinkedIn Re-Engagement Message (Warm)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn message to a passive candidate I sourced 6 months ago who was interested but not ready to move.
Keep it under 60 words.
Acknowledge time has passed.
Share what's changed that might make the timing better now: [new development — funding, team growth, comp increase, remote policy change].
Soft ask: would it make sense to reconnect?
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  10. Employer Branding Posts
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 30 — LinkedIn Culture Post (Employee Story)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn post from our company's perspective about [employee name or role]'s story.
Theme: [what makes working here meaningful — a specific project win, growth moment, team culture].
Format: story-driven, 150-200 words.
No buzz words like "passionate" or "synergy."
End with a subtle hiring note or values statement.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 31 — "Why We're Different" Employer Brand Post&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn post for our company that explains what makes us different as an employer.
Avoid generic claims (great culture, competitive pay).
Lead with something specific and provable: [one concrete example of how we treat people differently].
150 words max. End with a CTA for candidates to learn more or apply.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — Job Teaser Post (Pre-Launch)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job teaser LinkedIn post for a role we're about to post publicly.
Don't reveal full details yet — create curiosity.
What kind of person would love this role? Describe them.
End with "DM me if this sounds like you" or "posting next week — follow to be first to see it."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Make These Prompts Work Faster
&lt;/h2&gt;

&lt;p&gt;A few things that improve output quality every time:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Paste in examples.&lt;/strong&gt; If you have a past email that worked, include it: "Write something in this style: [paste email]."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Specify what NOT to do.&lt;/strong&gt; "Don't use the phrase 'exciting opportunity.' Don't open with 'I hope this finds you well.'"&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Ask for multiple versions.&lt;/strong&gt; "Give me 3 variations: one formal, one casual, one punchy."&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Edit, don't accept.&lt;/strong&gt; Use the first draft as a starting point. Your specific context and voice will always improve it.&lt;/p&gt;




&lt;h2&gt;
  
  
  Want the Full Recruiter AI System?
&lt;/h2&gt;

&lt;p&gt;These 32 prompts cover the core of the recruiting funnel. If you want a complete, organized system — 100+ prompts across HR, Talent Acquisition, Onboarding, and People Ops — check out the &lt;strong&gt;Professional AI Toolkit Bundle&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;It includes ready-to-use prompt libraries for every HR function, organized by workflow so you can find and use them in seconds — not spend 20 minutes prompting from scratch.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;&lt;a href="https://pinzasrojas.gumroad.com/l/qrphev" rel="noopener noreferrer"&gt;Get the Professional AI Toolkit Bundle →&lt;/a&gt;&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;Use code &lt;strong&gt;LAUNCH30&lt;/strong&gt; for 30% off — active now.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Found this useful? Save it and share it with your recruiting team. Drop a comment with which prompt you'll use first.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>recruiting</category>
      <category>hiring</category>
      <category>productivity</category>
    </item>
    <item>
      <title>35 ChatGPT Prompts for Accountants and CPAs: Client Emails, IRS Letters, Engagement Letters, and Advisory Memos</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Wed, 29 Apr 2026 17:40:17 +0000</pubDate>
      <link>https://forem.com/clawgear/35-chatgpt-prompts-for-accountants-and-cpas-client-emails-irs-letters-engagement-letters-and-2nm6</link>
      <guid>https://forem.com/clawgear/35-chatgpt-prompts-for-accountants-and-cpas-client-emails-irs-letters-engagement-letters-and-2nm6</guid>
      <description>&lt;p&gt;Tax season or not, accountants and CPAs spend enormous amounts of time writing things that follow the same patterns every time.&lt;/p&gt;

&lt;p&gt;Client summary emails. Engagement letters. Advisory memos. Audit prep checklists. Responses to IRS notices.&lt;/p&gt;

&lt;p&gt;None of these tasks require CPA-level judgment. They require good writing. And ChatGPT can produce a solid first draft of any of them in under 60 seconds — if you have the right prompt.&lt;/p&gt;

&lt;p&gt;These 35 prompts cover the writing and communication tasks that eat up accounting professionals' billable and non-billable time the most.&lt;/p&gt;




&lt;h2&gt;
  
  
  Client Communication
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Tax return summary email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a plain-English summary email for a tax client explaining their completed return.
Client type: [individual / small business / both].
Key figures: [refund of $X / tax owed of $X, key deductions taken, any notable items].
Tone: professional but conversational. No jargon. Reassuring if they owe money.
Under 200 words. Sign off as [your name, CPA].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Estimated tax payment reminder&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a reminder email to a client about their upcoming estimated tax payment.
Payment due: [date]. Amount: [$X or "based on our calculation"].
Include: how to pay (IRS Direct Pay / check / EFTPS), what happens if they miss it.
Friendly urgency. Brief. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Year-end tax planning email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a year-end tax planning email to a [individual / business] client.
Key opportunities to highlight: [retirement contributions, charitable giving, capital gains harvesting, accelerating deductions, etc.].
Deadline reminders: [December 31 actions vs. April 15 actions].
Tone: proactive advisor. Show we're thinking ahead for them. Under 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Response to client tax question&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a response to a client who asked: "[paste their question]"
Answer the question accurately and in plain language.
If there are caveats or it depends on their situation, say so clearly.
End with: what information you need from them, or next steps.
Professional but accessible. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Bad news delivery (unexpected tax liability)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email informing a client they owe more taxes than expected.
Amount owed: [$X more than anticipated]. Reason: [brief explanation].
Tone: calm, matter-of-fact, supportive. Acknowledge it's disappointing.
Include: payment options or next steps. Do not over-apologize.
Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 6 — Referral thank-you to existing client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief thank-you email to a client who referred a new client to us.
New client referred: [first name only or "your contact"].
Express genuine appreciation. Don't offer a discount unless that's your policy.
Short, personal, warm. Under 80 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Engagement &amp;amp; Onboarding
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 7 — Engagement letter (tax preparation)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a tax preparation engagement letter for a [individual / S-Corp / LLC] client.
Services included: [federal + state returns / estimated taxes / etc.].
Fees: [$X flat / hourly at $X / based on complexity].
Client responsibilities: [providing documents by X date, etc.].
Include: limitations of engagement, confidentiality, e-signature request.
Professional and clear. 350 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Engagement letter (advisory / CFO services)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft an engagement letter for ongoing advisory or fractional CFO services.
Services: [monthly bookkeeping review / cash flow forecasting / strategic planning / etc.].
Frequency: [monthly / quarterly]. Fee: [$X/month].
Term: [month-to-month / 12-month with 30-day termination].
Clear scope to prevent scope creep. 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — New client onboarding checklist email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an onboarding email to a new tax client explaining what we need from them.
Documents needed: [W-2s, 1099s, last year's return, business income statements, etc.].
How to send: [secure portal link / encrypted email / in-person].
Deadline: [date needed by].
Warm welcome + clear instructions. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Document request follow-up (polite nudge)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a polite follow-up email to a client who hasn't sent requested tax documents.
Original request: [brief description of what was asked].
Documents still needed: [list].
Deadline impact: [if we don't receive by X, we may need to file an extension].
Friendly but direct. No guilt-tripping. Under 120 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  IRS &amp;amp; Regulatory Communication
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 11 — IRS notice response letter&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a response letter to an IRS notice for a client.
Notice type: [CP2000 / CP504 / Letter 2205 / etc.].
Client situation: [brief summary of the issue].
Our response: [we agree / we disagree because X / we need more time].
Professional, factual, formal IRS correspondence format. Include client name, TIN, tax year. 250 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Penalty abatement request letter&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an IRS penalty abatement request letter for a client.
Client: [name, TIN].
Penalty type: [failure-to-file / failure-to-pay / accuracy-related].
Grounds for abatement: [first-time abatement / reasonable cause: describe the circumstances].
Include: acknowledgment of the penalty, request for waiver, supporting documentation mentioned.
Professional, factual. 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Extension filing notification to client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email notifying a client we're filing an extension on their behalf.
Extension filed: [personal/business]. New deadline: [date].
Important: extension of time to file ≠ extension of time to pay. Any estimated tax owed is still due [date].
Clear, reassuring, no alarm. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — State audit response cover letter&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a cover letter to accompany a response to a state tax audit.
State: [state name]. Tax type: [income / sales / payroll].
Audit period: [years]. Our position: [brief summary].
Documentation enclosed: [list key items included].
Formal, organized, professional. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Nexus / multi-state tax explanation to client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a plain-English explanation for a business client about nexus and multi-state tax obligations.
Their situation: [they hired remote employees in / sold into / opened an office in X states].
Explain: what nexus means, which states are triggered, what filings are now required.
Non-alarming but clear about compliance requirements. Under 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Advisory &amp;amp; Business Services
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 16 — Cash flow advisory memo&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief cash flow advisory memo for a small business client.
Current situation: [positive / tight / concerning — describe briefly].
Key observations: [3–4 data points from their financials].
Recommendations: [practical actions to improve or maintain cash position].
Advisor tone — insightful, not alarming. One page max.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — Quarterly business review summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a quarterly business review summary for a small business client.
Period: [Q1/Q2/Q3/Q4 YYYY].
Revenue: [$X, up/down X% from last quarter].
Key expenses: [notable changes].
Profit: [$X, margin of X%].
Observations: [3–4 bullets]. Recommendations: [2–3 action items].
Executive-summary format. Clear, concise.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Entity structure recommendation memo&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a memo recommending an entity structure for a client considering [LLC / S-Corp / C-Corp].
Client situation: [solo consultant / small partnership / growing business, etc.].
Cover: tax implications, liability protection, compliance requirements, cost.
Make a clear recommendation with reasoning.
Non-legalistic language. Under 400 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Retirement plan recommendation email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email recommending a retirement plan option to a self-employed client or small business owner.
Options to compare: [Solo 401k vs. SEP-IRA vs. SIMPLE IRA — pick 2–3 relevant to their situation].
Their situation: [income level, employees if any].
Recommend one with clear rationale. Include contribution limit for current year.
Advisor tone. Under 250 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Financial statement analysis narrative&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief narrative analysis of this client's financial statements.
Key figures: [revenue, gross margin, operating expenses, net income, key balance sheet items].
Period: [month/quarter/year].
What's working: [positive indicators]. Concerns: [areas to watch]. Action items: [what to address].
Executive summary style. Under 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Business Development
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Cold email to prospective small business client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a cold prospecting email to a [business type] owner about accounting services.
Pain point to address: [disorganized books / missed deductions / compliance risk / scaling without CFO].
What we offer: [brief, specific value proposition].
CTA: 15-minute discovery call. Under 130 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — LinkedIn post — tax tip for business owners&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn post sharing a practical tax tip for small business owners.
Tip topic: [home office deduction / Section 179 / retirement contributions / QBI deduction / etc.].
Make it: actionable, specific, surprising if possible.
First-person advisor voice. Not a textbook. Under 150 words. 3 hashtags.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Referral ask email to client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email asking a satisfied client for referrals.
Reference our recent work together: [brief mention].
Ideal referral: [small business owners / real estate investors / self-employed professionals / etc.].
Make it easy and low-pressure. Offer to be introduced however works best for them.
Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Service proposal email (new scope)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a proposal email for an expanded service scope to an existing client.
New service: [bookkeeping / payroll / advisory / tax planning].
Why now: [their situation has evolved — describe briefly].
Estimated fee: [$X/month or custom quote].
Value they'll get: [specific benefit]. CTA: 20-minute call.
Professional, not pushy. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 25 — Speaking/webinar pitch email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email pitching myself to speak at a [chamber of commerce / small business event / industry association] on [tax topic].
My credentials: [CPA, X years, specialty].
Topic I can present: [title + 2-sentence description].
What attendees will learn: [3 bullet points].
CTA: 15-minute call to discuss. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Internal &amp;amp; Administrative
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 26 — Staff training memo (policy or procedure)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief internal memo to staff about [new policy / procedure change / software update].
What's changing: [describe clearly].
Effective date: [date]. Who it affects: [all staff / specific team].
What they need to do: [action items].
Clear, direct. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — Performance feedback for staff accountant&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write constructive performance feedback for a staff accountant.
Strengths: [specific example of good work].
Improvement area: [specific behavior or skill gap — not personal attributes].
Development suggestion: [concrete next step].
Balanced and specific. Professional tone. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 28 — Client termination letter&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional letter terminating our engagement with a client.
Reason: [non-payment / scope disagreement / the relationship isn't working — keep vague].
Effective date: [date]. Final work to be completed: [list if any].
Documents to be returned: [original documents, if applicable].
Professional, final, no drama. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — Workflow documentation (internal SOP)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Write a step-by-step internal SOP for [accounting task: month-end close / new client setup / tax return prep / payroll processing].
Format: numbered steps. Include: who does each step, what tools are used, what to check at each stage.
Clear enough that a new hire could follow it.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 30 — Staff meeting agenda&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create an agenda for a [weekly / monthly] team meeting for an accounting firm.
Duration: [X minutes]. Attendees: [partners / managers / all staff].
Recurring items: [pipeline update, deadline check, staff issues, wins].
One-time items this meeting: [add specific topics].
Time-blocked format.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Tax Season Survival
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 31 — Extension list client email (mass communication)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief email to clients whose returns are being extended.
Reason: [volume / information still outstanding / complexity].
Their deadline: [October 15 for individuals / other].
If they owe: [reminder that any tax owed is still due April 15].
Reassuring, organized. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — Tax season kickoff email to all clients&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a tax season kickoff email to send to all individual tax clients in January.
Include: when to expect outreach from us, what documents to start gathering, our deadline for receiving docs, link to secure portal.
Warm, organized, sets expectations clearly. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 33 — Complex return explanation email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email explaining why a client's tax return is more complex this year.
New complexity: [RSU vesting / sale of property / business formation / foreign income / cryptocurrency / etc.].
What additional information we need: [list].
Estimated fee impact: [X% increase / custom quote].
Educational tone, not alarming. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 34 — Client interview prep questions (tax planning meeting)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Generate 10 interview questions for a tax planning meeting with a [individual / small business] client.
Focus areas: [life changes this year, business changes, investment activity, major purchases, retirement planning].
Questions that uncover opportunities, not just gather data.
Mix of open-ended and specific prompts.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 35 — Post-tax-season thank-you email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief thank-you email to clients at the end of tax season.
Acknowledge: the season is complete, appreciate their patience and responsiveness.
Looking ahead: [one value-add teaser for the rest of the year — mid-year review, estimated taxes, planning].
Warm, brief. Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  How to Use These Prompts
&lt;/h2&gt;

&lt;p&gt;Fill in the &lt;code&gt;[brackets]&lt;/code&gt; with real client details. More specificity = better output, less editing.&lt;/p&gt;

&lt;p&gt;Workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Find the prompt for your task&lt;/li&gt;
&lt;li&gt;Fill in the brackets&lt;/li&gt;
&lt;li&gt;Copy into ChatGPT&lt;/li&gt;
&lt;li&gt;Review and adjust for your firm's voice&lt;/li&gt;
&lt;li&gt;Send or use&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These produce first drafts. Tax law nuance and client-specific judgment are always yours.&lt;/p&gt;




&lt;h2&gt;
  
  
  Need More?
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;Accountant &amp;amp; CPA AI Toolkit&lt;/strong&gt; packages 100+ prompts for tax professionals across every client communication, advisory, compliance, and business development scenario.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://pinzasrojas.gumroad.com/l/qshjao" rel="noopener noreferrer"&gt;&lt;strong&gt;Accountant &amp;amp; CPA AI Toolkit → $14.99&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;30-day money-back guarantee. Instant download.&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>accounting</category>
      <category>productivity</category>
      <category>tax</category>
    </item>
    <item>
      <title>35 ChatGPT Prompts for Nurses: Documentation, Patient Education, and Clinical Communication (Copy-Paste Ready)</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Wed, 29 Apr 2026 15:02:07 +0000</pubDate>
      <link>https://forem.com/clawgear/35-chatgpt-prompts-for-nurses-documentation-patient-education-and-clinical-communication-obd</link>
      <guid>https://forem.com/clawgear/35-chatgpt-prompts-for-nurses-documentation-patient-education-and-clinical-communication-obd</guid>
      <description>&lt;p&gt;Nurses spend up to 35% of their shift on documentation. Charting, care summaries, patient education handouts, shift reports — all of it follows predictable patterns that take far longer to write than they should.&lt;/p&gt;

&lt;p&gt;ChatGPT won't replace clinical judgment. But it can write the first draft of a discharge instruction in 20 seconds instead of 20 minutes.&lt;/p&gt;

&lt;p&gt;These 35 prompts cover the tasks nurses spend the most time writing — organized by workflow so you can find what you need fast.&lt;/p&gt;




&lt;h2&gt;
  
  
  Patient Education &amp;amp; Discharge Instructions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Discharge instructions (general)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write patient discharge instructions for a patient being sent home after [condition/procedure].
Include: activity restrictions, diet instructions, medication reminders, wound care (if applicable), warning signs to watch for, and when to call the doctor.
Plain language, 6th-grade reading level. Numbered list format. No medical jargon.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Medication education handout&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a patient-friendly explanation of [medication name].
Include: what it's for, how to take it, common side effects to expect, serious side effects to report, and what to avoid while taking it (food, alcohol, other medications).
Simple language. Reassuring tone. Under 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Condition explanation for patient/family&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Explain [diagnosis/condition] to a patient and their family in plain, non-frightening language.
Cover: what it is, what caused it (briefly), what treatment looks like, what recovery involves, and what to watch for at home.
Avoid catastrophizing. Empathetic, clear. Under 400 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Post-procedure care instructions&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write post-procedure instructions for a patient who just had [procedure].
Include: normal vs. concerning symptoms, activity level, diet (if applicable), follow-up appointment reminders, contact information for concerns.
Format: numbered list. Plain English. Reassuring tone.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Pediatric discharge instructions (parent-facing)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write discharge instructions for parents taking a child home after [condition/procedure].
Age of child: [X years old].
Use parent-friendly language. Include: what's normal, what to watch for, when to go to the ER vs. call the pediatrician, and care instructions at home.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Documentation &amp;amp; Charting Support
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 6 — SBAR handoff summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an SBAR (Situation-Background-Assessment-Recommendation) handoff summary for:
Patient: [brief description — age, admission reason]
Situation: [current issue]
Background: [relevant history, medications, allergies]
Assessment: [current status, vital signs, notable findings]
Recommendation: [what the next nurse or provider needs to do]
Keep it concise and structured.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — Nursing note draft (narrative format)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a nursing progress note for a patient with [condition].
Patient status: [brief description of how they're doing].
Assessment findings: [list vitals, relevant neuro/respiratory/cardiovascular/pain status].
Interventions: [list what was done].
Response to interventions: [patient response].
Format: narrative nursing note. Clinical but readable. Avoid unnecessary repetition.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Incident report narrative&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me write an objective, factual incident report narrative for the following event:
What happened: [describe the incident without assigning blame].
Time: [time]. Location: [unit/room].
Patient information: [relevant details].
Staff involved: [roles, not names for this draft].
Actions taken immediately: [list].
Write in third-person, past tense, factual tone. No speculation.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Pain assessment documentation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief pain assessment nursing note for a patient reporting [pain description].
Include: pain scale rating, location, quality (sharp/dull/burning/etc.), what makes it better or worse, current medications on board, interventions taken, and patient response.
Short, structured format for charting.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — End-of-shift summary note&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an end-of-shift nursing summary for a patient with [primary diagnosis].
Current status: [stable / improving / declining — brief description].
Key events this shift: [list 3–5 notable events or changes].
Pending items for next shift: [list].
Format: concise nursing handoff note.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Care Planning &amp;amp; Patient Communication
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 11 — Care plan goal statements&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write 3 nursing care plan goal statements for a patient with [nursing diagnosis, e.g., Impaired mobility / Acute pain / Risk for infection].
Each goal: patient-centered, measurable, time-bound.
Format: "Patient will [action] by [timeframe] as evidenced by [measurement]."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Teach-back script for patient education&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a teach-back script I can use to verify a patient understands their [discharge instructions / medication / self-care task].
Include: how to introduce the teach-back, the key questions to ask, and how to re-explain if they don't understand.
Conversational, non-intimidating tone.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Motivational message for long-term patient&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief, encouraging message for a patient who has been hospitalized for [X weeks/days] and is feeling discouraged.
Acknowledge the difficulty without minimizing it. Highlight progress where possible.
Warm, genuine, human. Not generic. Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Family update communication&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a brief family update for a patient's family members regarding their loved one's status.
Patient condition: [current status].
What's been happening: [key developments this shift/day].
Next steps: [what happens next in care].
Compassionate, clear, no alarm unless warranted. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Refusal of treatment documentation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me document a patient's informed refusal of [treatment/medication/procedure].
Patient stated: [brief quote or summary of their reason].
Education provided: [what was explained].
Risks communicated: [what they were told].
Patient confirmed understanding. Attending notified.
Write as objective nursing documentation.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Professional Communication
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 16 — Physician notification (SBAR phone call script)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a script for calling the physician about a patient concern.
Patient: [age, gender, diagnosis].
Concern: [what I'm calling about].
Relevant vitals/labs/assessment: [data].
What I've already done: [interventions].
What I'm requesting: [orders, evaluation, clarification].
Format: SBAR phone call — I'll read this to feel prepared.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — Escalation to charge nurse or supervisor&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a structured escalation message to my charge nurse/supervisor about a concerning patient situation.
Patient situation: [describe clinical concern].
What I've assessed: [findings].
What I've done: [interventions taken].
What I need: [support, resources, decision].
Clear, factual, non-panicked. 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Interdisciplinary team communication note&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief interdisciplinary communication note for the care team regarding:
Patient: [diagnosis/situation].
Update: [relevant clinical or psychosocial findings this shift].
Concerns: [issues requiring team attention].
Requests: [consults, social work, PT/OT, dietary, etc.].
Concise and professional. Format for care team communication.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Difficult conversation prep (patient declining)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me prepare talking points for a difficult conversation with a patient who is declining recommended treatment.
Treatment they're refusing: [describe].
Their stated reason: [if known].
My goal: understand their perspective, provide complete information, respect autonomy.
Give me 5 conversation points that are compassionate, not coercive. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Email to manager requesting schedule accommodation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional email requesting a schedule accommodation from my nurse manager.
Reason: [brief explanation — medical appointment, family obligation, school schedule, etc.].
Specific request: [dates/shifts needing to swap or change].
What I've done to cover: [any arrangements you've already made].
Respectful, brief. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Continuing Education &amp;amp; Professional Development
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Study guide for certification exam topic&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a concise study guide for [NCLEX topic / certification exam topic, e.g., cardiac arrhythmias / pediatric fluid management / wound staging].
Format: key concepts, key terms, clinical pearls, common exam traps to watch for.
Length: enough to review in 15 minutes. Bullet points preferred.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Case study summary for learning&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Summarize the key learning points from this clinical case:
[Describe the patient case briefly — diagnosis, treatment, outcome, complications].
What should nurses take away from this case?
Format: 3–5 bullet point lessons. 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Professional development goal statement&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me write a professional development goal statement for my annual review.
Goal area: [clinical skill / leadership / certifications / specialty knowledge].
Current state: [where I am now].
Target: [what I want to achieve and by when].
Format: SMART goal. 2–3 sentences.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Nursing research article summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Summarize this nursing research article for me in plain English:
[Paste abstract or key sections here]
What did they study? What did they find? What does it mean for bedside practice?
3 short paragraphs max.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 25 — LinkedIn bio for nurse transitioning to new role&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn summary for a nurse transitioning from [current specialty, e.g., med-surg] to [target area, e.g., informatics / case management / NP program].
Years of experience: [X]. Key skills: [list 3–5].
Tone: confident, focused on transferable skills. Not self-deprecating. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Workplace &amp;amp; Administrative
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 26 — Policy compliance reminder for staff&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief, non-preachy reminder to staff about compliance with [policy — e.g., hand hygiene, documentation timeliness, PPE use].
Tone: collegial, not scolding. Frame it as a team habit, not a rule enforcement.
Under 80 words. For posting in a break room or team chat.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — New nurse orientation welcome message&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a welcoming orientation message from the unit/team to a new nurse joining our floor.
Unit: [type, e.g., cardiac step-down / NICU / ED].
Include: what to expect in the first week, who to ask for help, one piece of genuine advice.
Warm, team-spirit tone. Not a handbook excerpt. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 28 — Preceptor feedback notes&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me write constructive feedback notes for a nursing student or new grad I'm precepting.
Observed behavior (positive): [specific example].
Area to improve: [specific behavior, not personality].
Suggestion: [concrete action to improve].
Format: two-part feedback — what they did well, what to work on. Professional and kind.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — Complaint response to patient (written)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional written response to a patient complaint about [the specific concern].
Acknowledge: their experience without admitting liability.
Explain: what we do to ensure quality care (general).
Offer: a path forward (follow-up call, patient relations contact).
Empathetic, not defensive. Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 30 — Self-evaluation for annual performance review&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me write a nursing self-evaluation for my annual performance review.
Specialty/unit: [where I work].
Accomplishments this year: [list 3–5 things you're proud of].
Areas of growth: [what you've improved].
Goals for next year: [what you want to develop].
Professional, confident, specific. 300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Self-Care &amp;amp; Burnout Prevention
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 31 — Journal prompt for post-shift processing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me 5 reflective journal prompts for a nurse to decompress and process a difficult shift.
Goals: release the emotional weight of the day, identify what went well, protect against burnout.
Prompts that invite honest reflection, not toxic positivity.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — Boundary-setting script with difficult coworker&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief, professional script for setting a boundary with a coworker who is [describe the behavior: taking on extra work without asking / making dismissive comments / etc.].
Keep it: direct, calm, not accusatory. First-person "I" statements.
Something I could actually say in a 60-second conversation.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 33 — Advocacy email to hospital administration&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional email from a bedside nurse to hospital administration advocating for [staffing improvement / equipment upgrade / process change].
State the problem with data where possible: [what you've observed].
Explain patient impact: [how it affects care quality or safety].
Request: [specific, reasonable ask].
Firm but respectful. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 34 — Thank-you note to a helpful colleague&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short thank-you note to a colleague who [describe what they did — helped during a code, covered my patients, mentored me, etc.].
Specific, genuine, brief. Not over-the-top. Under 80 words.
Could be sent via text, email, or posted on a bulletin board.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 35 — Personal mission statement for nursing career&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me write a personal nursing mission statement.
What drives me to nursing: [your reason — patient connection, advocacy, science, etc.].
The kind of nurse I want to be: [values, approach].
What I'm working toward: [long-term professional goal].
Format: 2–3 sentences, first person. Authentic, not generic.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  How to Use These Prompts
&lt;/h2&gt;

&lt;p&gt;Fill in the &lt;code&gt;[brackets]&lt;/code&gt; with the actual patient situation, diagnosis, or context. The more specific you are, the better the output — and the less editing you'll need.&lt;/p&gt;

&lt;p&gt;Quick workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Find the prompt for your task&lt;/li&gt;
&lt;li&gt;Fill in the &lt;code&gt;[brackets]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Copy into ChatGPT (or Claude, Gemini)&lt;/li&gt;
&lt;li&gt;Read the output — adjust anything that doesn't match your charting style or facility's standards&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Always review AI-generated clinical content before using it with patients&lt;/strong&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These prompts handle the &lt;em&gt;writing&lt;/em&gt;, not the clinical reasoning. That part is yours.&lt;/p&gt;




&lt;h2&gt;
  
  
  Need a Full Toolkit?
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;Nurse &amp;amp; Healthcare Professional AI Toolkit&lt;/strong&gt; packages 100+ prompts across every nursing workflow — documentation, patient education, interdisciplinary communication, professional development, and self-advocacy — into a single searchable PDF.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://pinzasrojas.gumroad.com/l/xprrr" rel="noopener noreferrer"&gt;&lt;strong&gt;Nurse &amp;amp; Healthcare Professional AI Toolkit → $14.99&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;30-day money-back guarantee. Instant download.&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>nursing</category>
      <category>healthcare</category>
      <category>productivity</category>
    </item>
    <item>
      <title>35 ChatGPT Prompts for HR Managers: Job Descriptions, Offer Letters, PIPs, and Onboarding (Copy-Paste Ready)</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Wed, 29 Apr 2026 11:10:15 +0000</pubDate>
      <link>https://forem.com/clawgear/35-chatgpt-prompts-for-hr-managers-job-descriptions-offer-letters-pips-and-onboarding-4lf7</link>
      <guid>https://forem.com/clawgear/35-chatgpt-prompts-for-hr-managers-job-descriptions-offer-letters-pips-and-onboarding-4lf7</guid>
      <description>&lt;p&gt;Real estate agents have ChatGPT prompts articles. Sales reps do. EAs do.&lt;/p&gt;

&lt;p&gt;HR managers? Still writing job descriptions from scratch at 11 PM.&lt;/p&gt;

&lt;p&gt;The average HR manager spends 6–8 hours a week on writing tasks alone — job postings, offer letters, rejection emails, PIPs, onboarding checklists. That's a full day of your week on documents that follow predictable patterns every time.&lt;/p&gt;

&lt;p&gt;ChatGPT can produce a solid first draft of any of these in under 60 seconds. These 35 prompts show you exactly how.&lt;/p&gt;




&lt;h2&gt;
  
  
  Job Descriptions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Standard job description&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job description for a [Job Title] at a [company size/type] company in [industry].
Key responsibilities: [list 4–6 core duties].
Requirements: [years of experience, must-have skills, nice-to-haves].
Tone: [professional and straightforward / conversational and welcoming / etc.].
Include an EEO statement at the end. 300–400 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Technical role (engineering / data)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job description for a [Software Engineer / Data Analyst / etc.] at a [company type].
Tech stack: [list languages, tools, frameworks].
Team size: [X engineers]. Reporting to: [role].
Avoid buzzwords. Be specific about what they'll actually work on day one.
Include remote/hybrid policy. 350 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Leadership / director-level role&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job description for a [VP of Marketing / Director of Operations / etc.].
Scope: [team size, budget responsibility, key outcomes they'll own].
Ideal background: [industry, years of experience, leadership style].
Emphasize impact and ownership over tasks. No bullet-point laundry lists. 350 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Internship / entry-level&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job description for a [role] internship or entry-level position.
What they'll learn: [key skills / projects].
What we need: [major, basic skills, attitude].
Make it sound like a real growth opportunity, not a coffee-fetching role.
Friendly, encouraging tone. 250 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Rewrite an existing job description&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Rewrite this job description to be clearer, more compelling, and bias-reduced.
Original: [paste your JD here]
Goals: remove jargon, cut requirements that aren't truly necessary, add a strong opening hook.
Keep the length similar to the original.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Candidate Outreach &amp;amp; Screening
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 6 — Cold LinkedIn outreach to passive candidate&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn message to a passive candidate for a [role] position.
Their profile shows: [notable experience or achievement].
Keep it under 100 words. Compliment something specific. Don't oversell the role.
Make them curious, not pressured. End with a low-commitment question.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — Initial screening email after application&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to a job applicant confirming we received their application for [role].
Next step: [phone screen / skills assessment / video interview].
Instructions: [what they need to do / expect].
Warm but efficient. Brand voice: [professional / casual / etc.]. 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Interview invitation email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an interview invitation email for a [role] candidate.
Interview type: [phone / video / on-site].
Date/time options: [provide 2–3 slots or direct them to scheduling link].
Interviewers: [names/titles if sharing].
Include any prep tips (e.g., review company website, prepare examples using STAR method). 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Reference check questions&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me 8 reference check questions for a [role] candidate.
Focus areas: [e.g., collaboration, handling pressure, initiative, specific technical skills].
Mix of open-ended and behavioral questions.
Include one question about what conditions bring out their best work.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Candidate pipeline update email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief email to a candidate letting them know their application is still under review.
We haven't made a decision yet. Timeline: approximately [X more weeks].
Keep them warm without making promises. Under 80 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Offer Letters &amp;amp; Rejection Emails
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 11 — Offer letter (standard)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a job offer letter for [Candidate Name] for the [Role] position.
Start date: [date]. Salary: [$X/year or $X/hour]. Reports to: [manager name/title].
Benefits summary: [health, PTO, 401k, etc.].
Include standard at-will language. Warm, welcoming tone. 300 words.
Sign-off: [Your name, title].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Offer letter (negotiation follow-up)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an offer letter that reflects a negotiated compensation package.
Revised offer: [$X salary + $Y signing bonus / equity adjustment / etc.].
Acknowledge that we worked together to get here. Express genuine excitement about them joining.
Professional but personal. 250 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Rejection email (after initial screen)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a kind rejection email to a candidate who didn't pass the initial screen for [role].
Keep it short. Thank them for applying. Wish them well.
Do NOT say "we'll keep your resume on file" unless we mean it.
Under 80 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Rejection email (after final round)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a respectful rejection email to a finalist candidate for [role].
They made it to the final round. Acknowledge that it was a competitive process.
Be honest: we went with someone whose experience aligned more closely with [specific area].
Leave the door open for future roles. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Offer rescission letter (due to budget freeze)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a letter rescinding a job offer due to a budget freeze / headcount hold.
Candidate: [name]. Role: [title]. Original start date: [date].
Express genuine regret. Explain it's entirely a company situation, not a reflection of them.
Offer to reconnect when hiring resumes. Legal and human. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Onboarding
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 16 — Welcome email from HR (day before start)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a welcome email to a new hire the day before their first day.
Name: [name]. Role: [title]. Start date: [date].
Include: what time to arrive/log on, who to ask for, what to bring or set up, a genuine "we're excited" message.
Warm and practical. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — First-week onboarding schedule&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight markdown"&gt;&lt;code&gt;Create a structured first-week onboarding schedule for a new [role] hire.
Include: orientation sessions, team introductions, tool access, key meetings, and learning milestones.
Format as a day-by-day table (Mon–Fri). Mix of structured time and self-guided exploration.
Company size: [startup / mid-size / enterprise].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — 30-60-90 day plan template&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a 30-60-90 day success plan for a new [role].
30 days: learning and observing.
60 days: contributing and building relationships.
90 days: owning outcomes and showing impact.
Format: bullet points per phase. 3–5 items each.
Include a "success looks like" metric for each phase.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Onboarding survey questions&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write 10 onboarding survey questions for new hires to complete at the end of their first month.
Cover: clarity of role, quality of onboarding, manager support, cultural fit, tools/systems.
Mix of rating scales and open-ended questions.
Goal: identify gaps in our onboarding process, not just measure satisfaction.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — IT setup checklist email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to IT requesting setup for a new hire.
New hire: [name]. Role: [title]. Start date: [date]. Manager: [name].
Systems needed: [laptop, email, Slack, Notion, CRM, etc.].
Access level: [standard employee / admin / etc.].
Include a deadline for completion. Professional and clear. 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Performance Management
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Performance improvement plan (PIP)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a Performance Improvement Plan (PIP) for an employee in [role].
Concerns: [describe the specific performance issues — use facts, not opinions].
Goals: [3–4 measurable improvements needed].
Timeline: [30/60/90 days].
Check-ins: [weekly / biweekly with manager].
Consequence if not met: [state clearly but professionally].
Include a section for employee signature. Formal, documented, fair.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Performance review template&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a performance review template for [role / department].
Sections: goal achievement, core competencies, collaboration, growth areas, manager comments, employee self-assessment.
Rating scale: [1–5 / exceeds/meets/below expectations].
Keep each section to 2–3 prompts so managers don't write novels.
End with: development goals for the next review period.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Difficult conversation prep (performance)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me prepare talking points for a difficult performance conversation with an employee.
Issue: [describe the behavior or performance gap with specifics].
Goal: [what you want them to change and why it matters].
What I want to avoid: being vague, getting defensive, or letting it turn into a debate.
Give me 5 clear, human talking points.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Recognition email to high performer&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a recognition email for an employee who [specific accomplishment].
Employee: [name]. Role: [title].
Be specific about what they did and why it mattered to the team/company.
Warm, genuine tone. Not generic praise. Under 150 words.
CC their manager? [yes/no].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 25 — Termination talking points&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Help me prepare talking points for a termination conversation for [role] due to [reason: performance / layoff / conduct].
Keep it: clear, brief, compassionate, and legally safe.
What to cover: the decision (final), effective date, next steps (COBRA, final check, equipment return).
What NOT to say: anything that implies the decision is negotiable.
5–7 bullet points. Not a script — talking points.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  HR Communications &amp;amp; Policy
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 26 — Policy announcement email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an all-staff email announcing a new [policy: remote work / PTO / expense / etc.].
Policy summary: [key changes in plain English].
Effective date: [date].
Where to find the full policy: [location].
Questions: [contact or FAQ link].
Tone: clear and positive. No legal jargon. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — Open enrollment reminder email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an open enrollment reminder email for employees.
Deadline: [date]. What they need to do: [enroll in/change benefits via portal/link].
New this year: [any plan changes if applicable].
What happens if they don't act: [default enrollment / no changes / etc.].
Friendly urgency. Clear action step. 120 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 28 — Employee survey intro email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email introducing our annual employee engagement survey.
Survey takes: [X minutes]. Deadline: [date].
Anonymity: [fully anonymous / department-level reporting only].
Why it matters: [we use results to make real changes — give a past example if possible].
Authentic tone. Not corporate fluff. 120 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — Return-to-office policy announcement&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email announcing a new return-to-office policy.
New policy: [hybrid X days / full return / flexible].
Effective date: [date].
Reason: [brief, honest reason].
Acknowledge it's a change. Thank people for their flexibility.
Include a Q&amp;amp;A or contact for questions.
Empathetic, clear, no spin. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 30 — Layoff communication to affected employees&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write the communication script for notifying an employee of a layoff.
Reason: [company restructuring / economic conditions / role eliminated].
Severance: [X weeks pay + benefits continuation].
Effective date: [immediate / 2-week notice].
Outplacement support: [yes/no — describe if yes].
Tone: Direct, humane, no euphemisms like "let you go." Cover: what happens next step by step.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Employer Branding &amp;amp; Social Media
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 31 — LinkedIn post — culture highlight&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn post highlighting our company culture or a team win.
Event/achievement: [describe briefly].
Who was involved: [team / individuals].
What it says about who we are: [values or way of working].
First-person company voice. Authentic, not a press release. Under 150 words. 3 hashtags.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — Job posting intro for LinkedIn&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a compelling LinkedIn job post intro for a [role] opening.
This is the teaser before the full JD — 3 short paragraphs max.
Hook: why someone would want this role specifically.
Team/company snapshot: what makes us different.
CTA: link to apply. 120 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 33 — Glassdoor response to negative review&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a professional response to this Glassdoor review:
[Paste the review]
Acknowledge their experience. Don't be defensive. Mention 1–2 specific things we're working to improve.
Invite them to connect directly if they want to share more.
Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 34 — Exit interview summary template&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a template for summarizing exit interview responses for leadership.
Sections: departure reason (primary), satisfaction ratings, key feedback themes, manager-specific feedback (anonymized), actionable recommendations.
Format: executive summary style. Half a page max.
The goal is to surface patterns, not report on individuals.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 35 — Employer value proposition (EVP) draft&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft an employer value proposition for [company name / type].
Our strengths as an employer: [list 3–5 genuine differentiators — remote flexibility, mission, growth path, compensation, culture, etc.].
Target candidate: [role type / career stage / values they hold].
Format: 3–4 sentences that could go on our careers page.
No clichés like "fast-paced environment" or "work hard, play hard."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  How to Use These Prompts
&lt;/h2&gt;

&lt;p&gt;Fill in the brackets with real details. The more specific you are, the less editing you'll need to do.&lt;/p&gt;

&lt;p&gt;Workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Find the prompt for your task&lt;/li&gt;
&lt;li&gt;Fill in the &lt;code&gt;[brackets]&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Paste into ChatGPT&lt;/li&gt;
&lt;li&gt;Read the output once — fix anything that doesn't match your company's voice&lt;/li&gt;
&lt;li&gt;Done&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;These aren't magic. They're a starting point that replaces the blank page.&lt;/p&gt;




&lt;h2&gt;
  
  
  Need More Than Prompts?
&lt;/h2&gt;

&lt;p&gt;The &lt;strong&gt;HR Manager AI Workflow Toolkit&lt;/strong&gt; includes 100+ prompts organized across every HR function — talent acquisition, onboarding, performance, compliance communications, and culture building — in one searchable PDF.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://pinzasrojas.gumroad.com/l/lfzsqb" rel="noopener noreferrer"&gt;&lt;strong&gt;HR Manager AI Workflow Toolkit → $14.99&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;30-day money-back guarantee. Instant download.&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>hr</category>
      <category>productivity</category>
      <category>hiring</category>
    </item>
    <item>
      <title>35 ChatGPT Prompts for Real Estate Agents: Cold Outreach, Listings, and Follow-Ups (Copy-Paste Ready)</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Tue, 28 Apr 2026 15:37:17 +0000</pubDate>
      <link>https://forem.com/clawgear/35-chatgpt-prompts-for-real-estate-agents-cold-outreach-listings-and-follow-ups-copy-paste-2j8e</link>
      <guid>https://forem.com/clawgear/35-chatgpt-prompts-for-real-estate-agents-cold-outreach-listings-and-follow-ups-copy-paste-2j8e</guid>
      <description>&lt;p&gt;Real estate agents spend 40% of their workday on tasks that have nothing to do with selling homes.&lt;/p&gt;

&lt;p&gt;Writing listing descriptions. Drafting cold emails. Following up with leads who went silent. Preparing CMAs. Crafting social captions.&lt;/p&gt;

&lt;p&gt;These are all things ChatGPT can do in 30 seconds — if you have the right prompts.&lt;/p&gt;

&lt;p&gt;I've compiled 35 of the most useful ChatGPT prompts for real estate agents, organized by the exact workflows that eat up your time. Copy them, tweak the details, and you're done.&lt;/p&gt;




&lt;h2&gt;
  
  
  Listing Descriptions
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Standard MLS listing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a compelling MLS listing description for a [X bed/X bath] home in [city/neighborhood].
Key features: [list 5–8 features like open floor plan, updated kitchen, primary suite, backyard, 2-car garage, proximity to schools, etc.]
Tone: warm and inviting. Keep it under 250 words. Include one sentence about the neighborhood lifestyle.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Luxury listing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a luxury listing description for a [X sq ft] home in [neighborhood].
Highlight: [custom finishes, chef's kitchen, spa bath, smart home features, views, etc.]
Use elevated language. Target buyers who value privacy, craftsmanship, and lifestyle. 200–300 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Fixer-upper / investment property&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a listing description that frames this fixer-upper as an opportunity for the right buyer.
Property: [address/type], [brief condition notes], [ARV estimate if known].
Target audience: investors and house flippers. Emphasize upside, not problems. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Condo / townhome&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a listing for a [X bed/X bath] condo at [building name/neighborhood].
HOA includes: [amenities like pool, gym, concierge, etc.]
Commuter or urban buyer focus. Mention walkability, transit, nearby restaurants. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Social media caption from listing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Take this listing description and turn it into a 150-character Instagram caption with 5 relevant hashtags.
[Paste your listing description here]
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Cold Outreach &amp;amp; Lead Generation
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 6 — Cold email to FSBO seller&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short, non-pushy cold email to a homeowner trying to sell their house without an agent (FSBO).
Acknowledge their decision. Offer one specific thing I can do that they can't easily do themselves (e.g., MLS access, buyer network, negotiation).
CTA: 15-minute call. 120 words max. My name: [name]. My agency: [agency name].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — Cold email to expired listing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a cold email to a homeowner whose listing expired on the MLS without selling.
Empathize with the frustration. Identify one likely reason it didn't sell (price, marketing, or timing) without being accusatory.
Offer a fresh approach. CTA: free new market analysis call. 150 words. My name: [name].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Follow-up after open house (no contact)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a follow-up email to someone who attended my open house at [address] but didn't leave contact info.
They were sent this as a follow-up mailer. Warm, not desperate. Remind them of 2–3 property highlights.
Include a soft CTA to schedule a private showing. 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Text message to warm lead who went cold&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short text message (under 160 characters) to a buyer lead who went quiet 3 weeks ago.
Context: We toured 2 homes together. They seemed interested but stopped responding.
Make it feel human and curious, not sales-y. Include one open question.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — LinkedIn DM to relocating professional&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn direct message to a professional who just posted about relocating to [city].
Keep it casual and helpful, not salesy. Offer one specific resource (neighborhood guide, market snapshot, relocation checklist).
Under 80 words. My name: [name]. I specialize in [area].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Client Follow-Ups &amp;amp; Nurture Sequences
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 11 — Post-showing follow-up email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a follow-up email to buyers after we toured [number] homes together today.
Homes we saw: [brief list with addresses or nicknames].
Ask for honest feedback on each. Suggest next step (another tour, narrowing criteria, making an offer).
Warm, helpful tone. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — 30-day check-in for buyers not ready yet&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a nurture email for a buyer who told me they're planning to buy in 6 months.
It's been 30 days since we last spoke. Don't pitch. Provide value: one market stat, one tip for their search, one reason to stay engaged.
CTA: "reply and let me know if anything has changed." 120 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Annual check-in to past client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a friendly annual check-in email to a past client I helped buy a home [X years] ago.
Reference that it's been [X years]. Ask how the house is treating them. Mention that home values in their area have changed.
Light CTA: "if you ever think about moving, I'd love to help again." 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Seller update email during listing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a weekly seller update email for a home that's been on the market for [X weeks].
Stats to include: [number of showings, online views, inquiries if any].
Market context: [any relevant updates like interest rate shifts, new comps, etc.]
Keep the seller engaged and confident. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Offer declined — keep buyer motivated&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to buyers whose offer on [address] was declined.
Acknowledge the disappointment. Reframe it: explain what you learned, what this means for their next offer strategy, and what's coming to market soon.
Motivating tone. No empty promises. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Negotiation &amp;amp; Offer Prep
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 16 — Offer letter from buyer to seller&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a personal offer letter from a buyer to a seller.
Buyer situation: [first-time buyers / growing family / relocating for work / etc.]
Things they loved about the home: [specific features].
Tone: sincere, brief, human. Not manipulative. 150 words. Don't mention price.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — Counter-offer email to listing agent&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Draft a professional email from a buyer's agent to a listing agent presenting a counter-offer.
Our offer: [price, key terms].
Their ask: [their terms].
Justify our position with [comparable sales / inspection findings / market conditions].
Collaborative tone. 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Negotiation talking points for inspection issues&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me 5 negotiation talking points for requesting repair credits after a home inspection.
Issues found: [list 3–5 issues and estimated repair costs].
Format: one-sentence talking point per issue. Professional, not aggressive.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Open House &amp;amp; Showing Scripts
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 19 — Open house invitation post (social media)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a Facebook/Instagram post inviting followers to an open house at [address] this [day/time].
Highlight: [2–3 features of the home].
Include neighborhood info. Casual, welcoming tone. Include address, date, time, and a call to share.
120 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Conversation starter for open house visitors&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me 5 conversation-starter questions I can ask visitors at an open house to understand what they're looking for — without making them feel interrogated.
Format: short, natural questions. Not obvious sales questions.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 21 — Open house follow-up sequence (3 emails)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 3-email follow-up sequence for open house attendees who signed in.
Email 1 (same day): thank them, invite questions.
Email 2 (day 3): share one piece of market data relevant to their search.
Email 3 (day 7): soft CTA to schedule a private tour or consultation.
Each email: under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Market Updates &amp;amp; Client Education
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 22 — Monthly market update email to sphere&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short monthly market update email I can send to my contact list.
Market data: [include 3–5 local stats: median price, DOM, active inventory, interest rates, etc.]
Make it easy to read: use 2–3 bullet points, not paragraphs. Include one insight or prediction.
Sign off with a soft CTA. 150 words. My name: [name], [area].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — First-time buyer explainer email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an educational email explaining the homebuying process to a first-time buyer who just reached out.
Cover: pre-approval, making offers, inspections, closing.
Use plain language. No jargon. Keep it encouraging. Under 250 words. Include a "what happens next" CTA.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Explainer: why now is (or isn't) a good time to buy&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a balanced, honest email to a buyer who asked me if they should buy now or wait.
Current conditions: [brief local market summary].
Present both sides fairly. Don't push either way. End with: "let's talk through your specific situation."
150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Reviews &amp;amp; Referrals
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 25 — Ask for Google review (text message)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short text message asking a happy past client to leave a Google review.
Keep it personal, not copy-paste generic. Remind them of [one thing about the transaction that went well].
Include my Google review link: [URL]. Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 26 — Referral ask email to past client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email asking a satisfied past client for referrals.
Reference their transaction at [address/timeframe]. Tell them the best clients you can serve are people like them.
Make it easy: offer to have a casual intro call with anyone they refer. 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Social Media Content
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 27 — "Market update" Instagram carousel&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me 5 slide captions for an Instagram carousel about the [city] real estate market in [month/year].
Stats to include: [3–5 data points].
Slide 1: hook. Slides 2–4: one stat each with a 1-sentence insight. Slide 5: CTA.
Each caption: under 30 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 28 — Behind-the-scenes listing post&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a casual, behind-the-scenes Instagram caption for a photo of me [preparing a listing / hosting an open house / at the closing table].
First-person, authentic voice. No hashtag dumps. End with one question to prompt comments.
80 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — "Just sold" announcement post&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a "just sold" post for a property at [address/neighborhood].
Mention [brief fun fact about the deal — multiple offers, sold above asking, sold in X days, etc.].
Thank the clients (without naming them). Celebrate the achievement. Include a CTA for buyers/sellers watching.
100 words. 5 hashtags.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 30 — Video script for a neighborhood tour (60 seconds)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 60-second video script for a neighborhood tour of [neighborhood name].
Cover: what the area is known for, who it's great for, 2–3 specific highlights (restaurants, parks, commute, schools).
Conversational, walking-tour style. No teleprompter stiffness. End with "DM me if you want to see what's available."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Admin, Offers &amp;amp; Contracts
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 31 — Email summarizing an offer for a seller client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a clear, plain-English email summarizing an offer I received for my seller client.
Offer terms: [price, contingencies, closing date, earnest money, financing type].
Explain what each term means in plain language. Flag any unusual terms.
No opinion yet — just facts. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 32 — CMA cover letter to seller&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a cover letter to accompany a Comparative Market Analysis (CMA) I'm presenting to a potential seller.
My recommended price range: [$X–$Y].
Key comps: [briefly note 2–3 comparables].
Explain my methodology briefly. Focus on earning trust, not closing them on a price.
150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 33 — Pre-listing checklist email to seller&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to a seller with a pre-listing preparation checklist.
Include: decluttering, deep cleaning, minor repairs, staging tips, curb appeal.
Friendly but direct. Frame it as "what buyers notice first." 
Format as a numbered checklist. 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Bonus: Objection Handlers
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;Prompt 34 — Response to "I'll just sell it myself" (FSBO objection)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me a 3-sentence response to a homeowner who says: "I think I'll just sell it myself and save the commission."
Don't be defensive. Acknowledge it's a valid option. Offer one specific stat or risk they may not know about.
Conversational tone, not a script.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 35 — Response to "I'm going to wait until rates drop"&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Give me a 3-sentence response to a buyer who says: "I'm going to wait until interest rates come down before buying."
Acknowledge their reasoning is sound. Offer one alternative perspective (price appreciation, rent cost, refinance option).
Don't push. Plant a seed. 
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  How to Use These Prompts
&lt;/h2&gt;

&lt;p&gt;These work best when you &lt;strong&gt;fill in the brackets with real details&lt;/strong&gt;. The more specific your input, the better the output.&lt;/p&gt;

&lt;p&gt;Quick workflow:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Copy the prompt&lt;/li&gt;
&lt;li&gt;Fill in the &lt;code&gt;[brackets]&lt;/code&gt; with your real info&lt;/li&gt;
&lt;li&gt;Paste into ChatGPT&lt;/li&gt;
&lt;li&gt;Read it out loud — edit anything that doesn't sound like you&lt;/li&gt;
&lt;li&gt;Send&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;None of this replaces the judgment, relationships, or local expertise that make great agents irreplaceable. But it does mean you spend 20 minutes on email instead of 90.&lt;/p&gt;




&lt;h2&gt;
  
  
  Want the full Real Estate AI Toolkit?
&lt;/h2&gt;

&lt;p&gt;I packaged 100+ prompts across every real estate workflow — listings, CMA presentations, buyer consultations, database management, and referral systems — into a single PDF you can keep open next to your MLS.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://pinzasrojas.gumroad.com/l/qrphev" rel="noopener noreferrer"&gt;&lt;strong&gt;Professional AI Toolkit Bundle (includes Real Estate + HR + EA) → $49&lt;/strong&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;30-day money-back guarantee.&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>realestate</category>
      <category>productivity</category>
      <category>ai</category>
    </item>
    <item>
      <title>ChatGPT for Project Managers: Templates for Stakeholder Updates, Risk Logs, and Retrospectives</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Tue, 28 Apr 2026 11:02:39 +0000</pubDate>
      <link>https://forem.com/clawgear/chatgpt-for-project-managers-templates-for-stakeholder-updates-risk-logs-and-retrospectives-2612</link>
      <guid>https://forem.com/clawgear/chatgpt-for-project-managers-templates-for-stakeholder-updates-risk-logs-and-retrospectives-2612</guid>
      <description>&lt;p&gt;Monday morning. Sprint review in two hours. Three stakeholder emails unread, a risk register that hasn't been touched since last week, and a retro to run this afternoon.&lt;/p&gt;

&lt;p&gt;This is where most PMs fall behind — not because they lack skills, but because the communication overhead never stops. Status emails, charter drafts, risk escalations, go-live announcements. Each one takes 20–40 minutes to write well.&lt;/p&gt;

&lt;p&gt;Here's how I cut that time by 70%: I stopped writing from scratch.&lt;/p&gt;

&lt;p&gt;These 25 ChatGPT prompts handle the five communications every project manager deals with weekly. Copy them, fill in the brackets, and send. The prompt itself saves the thinking time.&lt;/p&gt;




&lt;h2&gt;
  
  
  1. Stakeholder Updates
&lt;/h2&gt;

&lt;p&gt;Status emails are the tax every PM pays. These prompts write them fast, in the format stakeholders actually read.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Weekly Status Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a weekly project status email for [project name]. Current status: [RAG: Green/Amber/Red].
Completed this week: [list 2-3 items]. Coming next week: [list 2-3 items]. One risk to flag:
[describe risk]. Audience: [executive sponsor / broader team / client]. Tone: direct and brief —
no more than 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;This prompt saved my Monday morning status meeting prep. I run it at 8 AM and have the email approved before standup.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 2 — Executive Summary (for non-technical stakeholders)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 3-paragraph executive summary for [project name] to present to [C-suite / board /
steering committee]. Translate this technical progress into business impact: [describe what
was built]. Budget status: [on track / X% over / X% under]. Timeline: [on track / slipped
by X weeks]. Frame everything around business value, not features.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Risk Escalation Message&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a risk escalation email to [recipient's role]. Risk: [describe risk]. Likelihood:
[high/medium/low]. Impact if it hits: [describe impact]. What we need from them: [specific
decision or resource]. We need a response by [date]. Keep it under 100 words and make the
ask clear.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — RAG Status Change Notification&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;We need to change the project RAG status from [previous] to [new status]. Reason: [explain
cause]. Write a message to the steering committee that explains what changed, what we're
doing about it, and what we need from them. Do not sugarcoat, but do not panic either.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — End-of-Phase Milestone Announcement&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a milestone announcement for [project name] completing [phase name]. What was
delivered: [list]. Who contributed: [team names or roles]. What happens next: [next phase
or next milestone]. Audience: [internal team / all company / external stakeholders]. Keep
it celebratory but factual.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  2. Project Kickoff
&lt;/h2&gt;

&lt;p&gt;The documents no one wants to write but everyone needs to have.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 6 — Project Charter Draft&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a project charter for [project name]. Objective: [what this project achieves in one
sentence]. Scope: [what's in scope]. Out of scope: [what's explicitly excluded]. Key
stakeholders: [names/roles]. Constraints: [budget / timeline / resources]. Success criteria:
[how we'll know it worked]. Format as a clean one-page document.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 7 — RACI Matrix Explanation Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to the project team explaining the RACI matrix for [project name]. Attach
the matrix (I'll add it separately). Explain what R, A, C, and I mean in practice — not
in theory. Tell them exactly what they're expected to do when they see their name in each
column. Keep it under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Scope Statement&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a scope statement for [project name]. In-scope deliverables: [list]. Out-of-scope
items: [list]. Assumptions: [list 3-4]. Dependencies: [what we need from others]. This
should be specific enough that if a stakeholder asks 'does this project include X?',
we can point to this document for the answer.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Kickoff Meeting Agenda&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Create a 60-minute kickoff meeting agenda for [project name]. Attendees: [roles].
Objectives of the meeting: introduce the team, align on scope, review RACI, identify
early risks. End with a clear action list. Include time allocations for each section.
Don't pad it with unnecessary slides or welcomes.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Assumptions and Constraints Register&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Turn these raw notes into a clean assumptions and constraints register for [project name].
Notes: [paste your raw notes]. Format: two columns — Assumption/Constraint | Impact if
wrong/violated. Sort by impact level: high, medium, low.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  3. Risk and Issue Management
&lt;/h2&gt;

&lt;p&gt;Risk registers get ignored when they're vague. These prompts write entries specific enough to act on.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 11 — Risk Register Entry&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a risk register entry for this risk: [describe the risk in plain English]. Include:
risk description, likelihood (H/M/L), impact (H/M/L), risk score (likelihood × impact),
owner ([name or role]), mitigation plan (3 specific actions), and contingency plan (what we
do if mitigation fails). Be specific — "monitor closely" is not a mitigation plan.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Mitigation Plan&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a detailed mitigation plan for this project risk: [risk description]. The plan should
include: (1) preventative actions we can take now, (2) early warning indicators to watch,
(3) who owns each action, and (4) the trigger point for escalating to the steering committee.
Output as a numbered list.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Issue Log Update&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Update this issue log entry: [paste current entry]. New status: [resolved / in progress /
escalated]. What happened: [describe what changed]. Next action: [who does what by when].
If resolved, add a root cause note so we don't repeat it.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Risk Review Meeting Notes&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Convert these messy meeting notes into a clean risk review summary: [paste notes]. Format:
top 3 risks discussed, decisions made, new risks identified, actions assigned (name + action
+ due date). Keep it under one page.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Stakeholder Risk Briefing&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a risk briefing email to [stakeholder name/role] covering the top 3 risks on the
project right now. For each risk: what it is, the current mitigation, and what you're
monitoring. Do not alarm them unnecessarily. Do flag that risk #[X] requires their
input. Be direct.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  4. Retrospectives
&lt;/h2&gt;

&lt;p&gt;Retros fail when they're vague or when action items die in a Confluence page nobody checks. These prompts fix both problems.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 16 — Retro Facilitation Script&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 45-minute sprint retrospective facilitation script for a team of [X] people.
Sprint: [sprint name or number]. Use the Start/Stop/Continue format. Include specific
discussion questions for each section that push the team past surface-level answers.
Add a 10-minute action item assignment session at the end.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — Action Item Tracker Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Convert these retro action items into a follow-up email to the team: [paste raw action
items]. For each item include: owner, action, success criterion, and due date. Add a
note that these will be reviewed at the start of next sprint. Keep the tone accountable,
not punishing.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Improvement Proposal&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a short improvement proposal based on this recurring retro theme: [describe the
issue — e.g., 'sprint planning takes too long', 'QA always gets squeezed at the end'].
Include: current state, proposed change, expected outcome, who needs to approve, and
how we'll measure success. One page max.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — Sprint Health Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a sprint health summary for sprint [X]. Velocity: [story points completed / planned].
Bugs introduced: [X]. Bugs resolved: [X]. Team capacity: [X% of planned]. Key learnings:
[paste 2-3 bullet points]. Format as a short internal document the team can review in
under 3 minutes.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — Retro Anti-Patterns Debrief&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Our last retrospective had these problems: [describe — e.g., no one spoke honestly,
action items from last retro were ignored, the same issues keep coming up]. Write a
brief debrief I can share with the team that names the problems directly and proposes
one concrete change to how we run retros. Do not be diplomatic at the expense of being
useful.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  5. Client Communications
&lt;/h2&gt;

&lt;p&gt;The messages where tone matters most — and where most PMs spend too long getting the words right.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Timeline Slip Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write an email to [client contact name/role] informing them that [project name] has slipped
by [X weeks]. Reason: [honest explanation — don't hide it]. New target date: [date]. What
we're doing to prevent further slippage: [2-3 actions]. What we need from the client, if
anything: [describe or say 'nothing at this time']. Do not over-apologize. Be direct and
solution-focused.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Change Request Explanation&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a change request explanation for this scope change: [describe the change]. Why it's
needed: [reason]. Time impact: [+X days or 'no impact']. Cost impact: [$X or 'no impact'].
Risk if we don't do it: [describe]. Format this so a client can read it in under 2 minutes
and make a decision. End with a clear yes/no ask.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Go-Live Announcement&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a go-live announcement for [project/product name] launching on [date]. Audience:
[client team / end users / both]. Include: what's going live, what users can expect,
known limitations or issues we're aware of, support contact, and next steps. Keep the
tone confident but not hype-driven.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Meeting Recap for Client&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Convert these meeting notes into a clean client-facing recap: [paste notes]. Include:
key decisions made, action items (owner + due date), open questions still to resolve,
and next meeting date. Remove internal comments. Format for someone who was in the
meeting but will skim this in 90 seconds.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 25 — Project Close-Out Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a project close-out summary for [project name] to share with the client. Include:
original objectives vs. what was delivered, key milestones hit, any scope changes and
why, final budget vs. estimate, and lessons learned (keep it honest). End with a clear
statement of project completion and next steps (warranty period, support handover, etc.).
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  How to Use These in Practice
&lt;/h2&gt;

&lt;p&gt;Don't run them raw. Add context before you hit enter:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Name the audience&lt;/strong&gt; — "executive sponsor" reads differently than "junior dev."&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Give the RAG / status first&lt;/strong&gt; — the model needs to know the tone before it writes.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Paste your real data&lt;/strong&gt; — prompts are 10× better with actual numbers and names.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Edit the output&lt;/strong&gt; — treat the first draft as a 70% draft. Tighten it.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I keep these in a Notion page and run them through ChatGPT 4 or Claude. The whole set takes about 90 minutes to set up once, then pays back daily.&lt;/p&gt;




&lt;h2&gt;
  
  
  Want the Full PM Prompt System?
&lt;/h2&gt;

&lt;p&gt;If you run sprints, manage clients, or just spend too much time writing project updates, the &lt;a href="https://pinzasrojas.gumroad.com/l/lqdwpy" rel="noopener noreferrer"&gt;&lt;strong&gt;Project Manager AI Workflow Toolkit&lt;/strong&gt;&lt;/a&gt; has 100+ prompts, templates, and frameworks organized by workflow — kickoff through close-out.&lt;/p&gt;

&lt;p&gt;Use code &lt;strong&gt;LAUNCH30&lt;/strong&gt; at checkout for 30% off. Currently $14.99 → $10.49 with the code.&lt;/p&gt;

&lt;p&gt;If you manage multiple professional contexts, the &lt;a href="https://pinzasrojas.gumroad.com/l/whhsfz" rel="noopener noreferrer"&gt;&lt;strong&gt;Complete AI Prompt Pack Library&lt;/strong&gt;&lt;/a&gt; bundles the PM toolkit with packs for HR, Real Estate, Healthcare, and Sales — better value if you wear more than one hat.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;25 prompts. 5 workflow categories. Zero filler.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;&lt;em&gt;Save this for when your boss asks why the project is running late and you have 20 minutes to write a stakeholder update.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>projectmanagement</category>
      <category>chatgpt</category>
      <category>productivity</category>
      <category>agile</category>
    </item>
    <item>
      <title>AI Prompts for Small Business Owners: 25 Copy-Paste Prompts for Operations, Marketing, and Hiring</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Mon, 27 Apr 2026 15:38:56 +0000</pubDate>
      <link>https://forem.com/clawgear/ai-prompts-for-small-business-owners-25-copy-paste-prompts-for-operations-marketing-and-hiring-2b8j</link>
      <guid>https://forem.com/clawgear/ai-prompts-for-small-business-owners-25-copy-paste-prompts-for-operations-marketing-and-hiring-2b8j</guid>
      <description></description>
      <category>chatgpt</category>
      <category>productivity</category>
      <category>smallbusiness</category>
      <category>ai</category>
    </item>
    <item>
      <title>Best ChatGPT Prompts for Sales Reps: Cold Outreach, Follow-ups, and Closing (Copy-Paste Ready)</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Mon, 27 Apr 2026 15:37:45 +0000</pubDate>
      <link>https://forem.com/clawgear/best-chatgpt-prompts-for-sales-reps-cold-outreach-follow-ups-and-closing-copy-paste-ready-37dp</link>
      <guid>https://forem.com/clawgear/best-chatgpt-prompts-for-sales-reps-cold-outreach-follow-ups-and-closing-copy-paste-ready-37dp</guid>
      <description>&lt;h1&gt;
  
  
  Best ChatGPT Prompts for Sales Reps: Cold Outreach, Follow-ups, and Closing (Copy-Paste Ready)
&lt;/h1&gt;

&lt;p&gt;Cold outreach. Follow-up sequences. Discovery calls. Objection handling. Proposals.&lt;/p&gt;

&lt;p&gt;Sales reps spend a significant portion of their week on writing tasks — and most of that writing is repetitive. The cold email that starts the exact same way as the last one. The follow-up that says nothing new. The proposal that takes three hours and loses anyway.&lt;/p&gt;

&lt;p&gt;I use ChatGPT for all of it now. Not to replace the relationship — that's still mine — but to eliminate the startup friction on every writing task. Here are the 25 prompts I actually use, organized by the moment in the sales cycle when you need them.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Generic Sales Prompts Fail
&lt;/h2&gt;

&lt;p&gt;"Write me a cold email" produces garbage. "Write me a follow-up email" produces the same garbage as last time.&lt;/p&gt;

&lt;p&gt;The prompts that work are &lt;strong&gt;role-loaded&lt;/strong&gt;, &lt;strong&gt;context-specific&lt;/strong&gt;, and &lt;strong&gt;output-constrained&lt;/strong&gt;. You're not asking ChatGPT to think for you. You're giving it enough context that it can't phone it in. Every prompt below follows that structure.&lt;/p&gt;




&lt;h2&gt;
  
  
  Category 1: Cold Outreach (Prompts 1–6)
&lt;/h2&gt;

&lt;p&gt;The most valuable prompts in this list. Cold outreach is where reps waste the most time staring at a blank screen.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — First cold email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;You are a B2B sales copywriter who writes cold emails for [your industry] reps.
Write a 3-line cold email to [role] at [company type].
Line 1: reference one specific, observable thing about their company (use: [observation]).
Line 2: one outcome I delivered for a similar company in [timeframe].
Line 3: a low-friction CTA — a 15-min call, not a demo.
No "I hope this finds you well." No subject line. First word is not "I."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Subject line variants&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write 7 subject lines for a cold email to [role/industry].
Mix of approaches: curiosity gap, specific stat, name drop (just "[Company] + [our company]"), question, direct benefit.
Under 40 characters each. No clickbait. No emojis unless one actually fits.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — LinkedIn connection request&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn connection request to [role] at [company].
Max 200 characters. Reference a specific reason I'm reaching out — not "I'd love to connect."
Context: [1 sentence about what I sell and why it's relevant to them].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — LinkedIn DM after connection&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;They accepted my LinkedIn connection request. We haven't spoken before.
Write a first message that opens a conversation without a pitch.
Context about them: [what I know about their role/company].
Context about me: [what I sell, who I help].
Under 100 words. Ends with one question, not multiple.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Personalized opening line&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write 5 different opening lines for a cold email to [name], [role] at [company].
Each should reference something real and specific: their recent content, company news, a job posting, or an industry shift.
Context: [specific things I found about them or their company].
No "I saw your LinkedIn post." That's everyone. Be more specific.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 6 — Multi-channel sequence outline&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm prospecting [role] at [company type]. I have their email and LinkedIn.
Write a 7-touch outreach sequence across both channels over 14 days.
Include: touchpoint number, channel, timing, and a one-line message direction.
Don't write the full messages — just the sequence architecture.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 2: Follow-Up Sequences (Prompts 7–11)
&lt;/h2&gt;

&lt;p&gt;The money is in the follow-up. Most reps give up after one email. These prompts make follow-up systematic.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 7 — After-first-email follow-up&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I sent a cold email to [prospect] on [date]. No reply.
Write a Day 3 follow-up that adds value — not just "checking in."
Add one piece of relevant information they might not have: [something useful to them].
Under 60 words. Reference the first email briefly without repeating it.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Post-meeting follow-up&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I just had a [call type] with [prospect name], [role] at [company].
What we covered: [key points discussed].
Their main concern was: [specific objection or interest].
Next step agreed on: [action item].
Write a follow-up email that: confirms the next step, recaps one insight from the call, and adds one new piece of value.
Tone: direct, not overly formal.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Stalled deal follow-up&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A deal has gone quiet after [last touchpoint]. Last contact: [date].
Their situation: [what they were evaluating, where we stood].
Write a "resurface" email that: doesn't pressure them, acknowledges time has passed, and reframes our value around something that may have changed.
Under 80 words. No "just following up."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Breakup email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I've tried reaching [prospect] [number] times over [timeframe]. No response.
Write a breakup email that:
— Closes the loop professionally
— Leaves the door open without begging
— Optionally surfaces a final piece of value
Under 60 words. Tone: confident, not passive-aggressive.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 11 — Re-engagement after a lost deal&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;We lost a deal to [competitor or "no decision"] [timeframe] ago.
The prospect is: [role] at [company].
Reason we lost: [what they said or my read].
Write a re-engagement email for [timing — e.g. 90 days later] that: acknowledges time has passed, mentions something that may have changed in their situation, and offers a low-friction next step.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 3: Discovery Call Prep (Prompts 12–16)
&lt;/h2&gt;

&lt;p&gt;Walk into every discovery call knowing what questions you're asking and why.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 12 — Discovery question set&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I have a discovery call with [role] at [company] in [industry].
Their probable pain points: [what I know or suspect].
Write 10 discovery questions that surface: urgency, budget authority, current process, and what "good" looks like to them.
Format: question + one-sentence note on what it uncovers.
Don't list generic questions. These should be specific to [industry/role].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 13 — Hypothesis about their problems&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;[Company name] is a [company type] in [industry] with [size/context].
Based on what I know about companies like them, write a hypothesis paragraph about their top 3 operational or strategic pain points related to [your solution area].
I'll use this to frame my opening in the discovery call.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Call agenda&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 20-minute discovery call agenda for [prospect type].
I want to: build rapport briefly, understand their current situation, qualify them on budget and timeline, and set a specific next step.
Format: time block + goal for each section.
Don't pad it. 20 minutes means 20 minutes.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — SPIN questions for a specific pain&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Using the SPIN selling framework, write a question set for a prospect who likely has this problem: [specific pain].
Situation: 2 questions.
Problem: 3 questions.
Implication: 3 questions.
Need-payoff: 2 questions.
Keep them conversational, not interrogative.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 16 — Pre-call research brief&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I have a call with [prospect name], [role] at [company].
Their company: [brief description or LinkedIn/website info].
The prospect's background: [what I know from LinkedIn].
Write a 1-page research brief: company context, suspected priorities, conversation hooks (recent news or content), potential landmines (risks in pitching to them), and three things I want to confirm in the call.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 4: Objection Handling (Prompts 17–20)
&lt;/h2&gt;

&lt;p&gt;Objections aren't rejections. They're questions in disguise. These prompts help you respond with specificity.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 17 — Handle a specific objection&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A prospect just said: "[exact objection]."
Write 3 responses. Each should:
1. Acknowledge the concern (not dismiss it)
2. Reframe it based on what it usually signals
3. Bridge to a next step
Under 75 words each. Tone: confident but not combative.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — Price objection&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A prospect said: "This is more than we budgeted."
Context: they're [company size], our price is [price], their budget is roughly [budget range].
Write a response that:
— Doesn't discount immediately
— Reframes value around [specific ROI metric relevant to them]
— Offers an alternative path (smaller scope, phased approach, or ROI calculation)
Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 19 — "We're already using a competitor" objection&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Prospect says they're using [competitor].
Write a response that:
— Doesn't trash the competitor
— Asks one targeted question about what's working (to find the crack)
— Plants a seed about what's different about us: [your specific differentiation]
Conversational tone. Under 80 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — "We need to think about it" objection&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;After my pitch, the prospect said "we need to think about it."
This usually means: no clear next step, not enough urgency, or a concern they haven't named.
Write a response that:
— Acknowledges it without pressure
— Asks one question to surface the real hesitation
— Locks in a specific next step with a time and date
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 5: Proposals and Closing (Prompts 21–25)
&lt;/h2&gt;

&lt;p&gt;The close isn't one moment. It's the last 20% of every email, every call, every proposal.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 21 — Proposal structure&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a proposal outline for [client type] who needs [deliverable].
Budget: [range]. Timeline: [timeframe].
5 sections: executive summary, problem statement, proposed solution, pricing/scope, next steps.
Each section: title + 2-sentence description of what goes there.
Don't write the full proposal. Just the architecture and what each section must prove.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Executive summary for a proposal&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a proposal executive summary for [prospect name] at [company].
Their main problem: [problem]. Our solution: [what we're proposing].
Expected outcome: [what they get]. Investment: [price].
Format: 3 paragraphs. Paragraph 1 — their problem in their language. Paragraph 2 — what we're doing and why. Paragraph 3 — the outcome and the ask.
Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — ROI calculator narrative&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm selling [product/service] at [price] to [prospect].
Metrics I can tie our solution to: [list 2-3 metrics].
Write a 1-paragraph ROI narrative for the proposal that frames the investment as a business decision, not a cost.
Use conservative estimates. Show the math clearly. Under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Verbal close script&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm at the end of a demo call that went well. The prospect is interested.
Write a closing script for the last 5 minutes that:
— Confirms the problem we're solving is the right one
— Gets verbal buy-in on the solution fit
— Proposes the next step as a decision point, not a follow-up
Tone: collaborative, not pushy. I'm not asking if they want to buy — I'm asking if we've addressed their needs.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 25 — Post-proposal check-in&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I sent a proposal [days] ago. The contact said they'd respond by [date] and haven't.
Write a check-in message that:
— References the proposal without being passive
— Asks if anything has changed on their side
— Proposes a short call to address any questions
Under 60 words. Not "just checking in."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  The Pattern Across Every Prompt
&lt;/h2&gt;

&lt;p&gt;Every prompt above follows the same structure:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Role&lt;/strong&gt; — you're telling ChatGPT who it's being (B2B copywriter, sales strategist)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Context&lt;/strong&gt; — specifics about the prospect, situation, objection&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Constraints&lt;/strong&gt; — word count, format, what NOT to do&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Strip any of the three and output quality drops immediately.&lt;/p&gt;




&lt;h2&gt;
  
  
  What to Do With These
&lt;/h2&gt;

&lt;p&gt;Use them as-is for the first pass. Then build your own variants with specific details from your industry, your common objections, your ICP. Save the prompts that produce your best outputs as templates in a doc you actually revisit.&lt;/p&gt;

&lt;p&gt;If you want 50+ prompts organized by role — financial advisors, HR managers, project managers, and more — the &lt;a href="https://pinzasrojas.gumroad.com/l/whhsfz" rel="noopener noreferrer"&gt;Complete AI Prompt Pack Library&lt;/a&gt; has them. Includes the Sales Prompt Pack. Use code &lt;strong&gt;LAUNCH30&lt;/strong&gt; for 30% off.&lt;/p&gt;

&lt;p&gt;Or grab the &lt;a href="https://pinzasrojas.gumroad.com/l/mixiz" rel="noopener noreferrer"&gt;free ChatGPT Starter Kit&lt;/a&gt; to test the format before you buy anything.&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>sales</category>
      <category>productivity</category>
      <category>ai</category>
    </item>
    <item>
      <title>I Built a Solopreneur Workflow Using ChatGPT Prompts — Here Are the 30 That Actually Work</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Mon, 27 Apr 2026 09:24:21 +0000</pubDate>
      <link>https://forem.com/clawgear/i-built-a-solopreneur-workflow-using-chatgpt-prompts-here-are-the-30-that-actually-work-c00</link>
      <guid>https://forem.com/clawgear/i-built-a-solopreneur-workflow-using-chatgpt-prompts-here-are-the-30-that-actually-work-c00</guid>
      <description>&lt;h1&gt;
  
  
  I Built a Solopreneur Workflow Using ChatGPT Prompts — Here Are the 30 That Actually Work
&lt;/h1&gt;

&lt;p&gt;Six months ago I was billing 40 hours a week and keeping maybe 20 for actual client work. The rest? Proposals, invoices, content drafts, status emails, strategy decks — the invisible overhead nobody puts on a timesheet but that eats your evenings anyway.&lt;/p&gt;

&lt;p&gt;I'm not going to tell you "AI changed my life." What I'll tell you is this: I rebuilt my entire workflow around 30 ChatGPT prompts across five categories, and my overhead dropped from ~20 hours to ~6 hours a week. Same output. A third of the admin grind.&lt;/p&gt;

&lt;p&gt;Here are the prompts. Use them as-is or strip the structure for your own use.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Most ChatGPT Prompts Don't Work for Solopreneurs
&lt;/h2&gt;

&lt;p&gt;Generic prompts get generic outputs. "Write me a proposal" gets you a proposal that sounds like a content mill wrote it in 2019.&lt;/p&gt;

&lt;p&gt;The prompts that work are &lt;strong&gt;role-scoped&lt;/strong&gt;, &lt;strong&gt;context-loaded&lt;/strong&gt;, and &lt;strong&gt;output-specific&lt;/strong&gt;. Every prompt below follows that structure. You'll see the pattern as you go.&lt;/p&gt;




&lt;h2&gt;
  
  
  Category 1: Client Acquisition (Prompts 1–6)
&lt;/h2&gt;

&lt;p&gt;This is where revenue starts. Most solopreneurs burn hours on proposals that go nowhere. These prompts cut that waste.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 1 — Cold outreach opener&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;You are a B2B copywriter specializing in direct outreach for [your niche] consultants.
Write a 3-sentence cold email for [specific company/role].
Line 1: reference their specific situation (use: [observation about their business]).
Line 2: one specific outcome I've delivered for similar clients.
Line 3: low-friction CTA (15-min call, not a demo).
No subject line. No "I hope this email finds you well."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 2 — Discovery call prep&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I have a discovery call with [prospect type] at [company type] in [industry].
Their main pain is likely [pain point].
Generate 8 qualifying questions that surface: budget, decision authority, urgency, and whether they've tried solving this before.
Tone: consultative, not interrogative.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 3 — Proposal structure&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm writing a proposal for [client type] who needs [deliverable].
Budget range: [range]. Timeline: [weeks].
Write a 5-section proposal outline. Each section: title + 2-sentence summary of what it covers + why it builds buyer confidence.
Do not write the full proposal — only the outline.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 4 — Objection handling&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm a [your role] and a prospect just said: "[objection]".
Write 3 responses. Each should: acknowledge the concern, reframe it, and bridge to a next step.
Voice: confident, not defensive. Under 75 words each.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 5 — Follow-up sequence&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I sent a proposal to [prospect] on [date]. No response in [days].
Write a 3-email follow-up sequence:
Email 1 (Day 3): value add, no pressure.
Email 2 (Day 7): social proof or case study angle.
Email 3 (Day 12): breakup email with a door-open close.
Each email under 80 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 6 — LinkedIn DM sequence&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I want to connect with [ideal client type] on LinkedIn.
Write a connection request (under 300 characters) and a follow-up DM (under 150 words) for after they accept.
Angle: genuine interest in their work, no pitch in the first message.
Industry: [industry]. My offer: [1-sentence description].
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 2: Project Delivery (Prompts 7–12)
&lt;/h2&gt;

&lt;p&gt;Once you win the client, the clock starts. These prompts compress delivery overhead without cutting quality.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 7 — Kickoff document&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm starting a [project type] for a [client type]. Duration: [weeks]. Deliverables: [list].
Write a one-page kickoff document covering: project goal, success metrics, weekly milestones, communication cadence, change request policy.
Tone: professional, not bureaucratic.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 8 — Weekly status update&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a weekly status update email for a [project type] project.
Progress this week: [brief summary].
Next week: [brief summary].
Blockers: [any blockers or "none"].
Format: 3 short paragraphs. Under 120 words total. No bullet lists.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 9 — Scope creep response&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A client just asked for [out-of-scope request] on a project that includes [original scope].
Write a professional email that: acknowledges the request, clarifies it's outside scope, offers to quote it as an add-on.
Do not be confrontational. Keep the relationship warm. Under 100 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 10 — Client feedback summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I received this feedback from a client: "[paste feedback]"
Summarize it in 3 bullet points:
1. What they liked
2. What they want changed
3. Implied priorities not stated explicitly
Then suggest 2 ways to respond that maintain project momentum.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 11 — Retainer pitch&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I just delivered [project] for [client type].
Write a retainer pitch email. Frame around: maintaining results, ongoing optimization, and the risk of losing momentum without continued support.
Include: proposed scope, 2-3 pricing tiers (leave amounts blank), and a soft-close CTA.
Under 200 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 12 — Project retrospective questions&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I just completed a [project type] project.
Ask me 10 questions that will surface: what worked, what I'd do differently, client satisfaction signals, and what to document as a repeatable process.
Format as a numbered list. Do not provide answers — only questions.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 3: Admin &amp;amp; Operations (Prompts 13–18)
&lt;/h2&gt;

&lt;p&gt;The invisible overhead. Nobody talks about how much time solopreneurs lose to admin. These prompts cut through it.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 13 — Invoice follow-up&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;A client invoice for [amount] is [X] days overdue.
Write 3 escalating follow-up messages:
Message 1 (Day 1 past due): friendly reminder.
Message 2 (Day 7): firmer, references original terms.
Message 3 (Day 14): final notice before collections process.
Tone: firm but professional, no emotional language.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 14 — Contract clause&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I need a [specific clause] for a freelance [service type] contract.
Write a plain-English clause (not legalese) that covers: [specific scenario].
Include what happens if [edge case].
Flag any assumptions I should verify with a lawyer.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 15 — Weekly planning&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;It's Monday morning. I have these priorities this week: [list].
My available hours are [X]. Known interruptions: [list or "none"].
Build a daily task block schedule.
Constraints: deep work before noon, admin in afternoon.
Flag any priority conflicts.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 16 — Email triage system&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I get [X] emails per day. Most fall into these categories: [categories].
Design an email triage system using labels, response templates, and a processing schedule.
Include: 3 canned response templates for my most common email types.
Keep it implementable without plugins or paid tools.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 17 — Subcontractor brief&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I need to brief a subcontractor on [task type].
They have [experience level] experience with [relevant skill].
Write a project brief covering: objective, deliverables, quality standards, revision policy, deadline, and payment terms.
Under 300 words. Plain language.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 18 — SOP builder&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I want to document [repeatable task] as a standard operating procedure.
Ask me the 12 questions needed to write a complete SOP for this task.
Then, after I answer, write the SOP in a format a new hire could follow on day one.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 4: Content &amp;amp; Marketing (Prompts 19–24)
&lt;/h2&gt;

&lt;p&gt;Your content is your sales team. These prompts build the pipeline without burning your hours.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 19 — Content angle generator&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I create content for [target audience] about [topic area].
Generate 10 content angles for [specific topic].
For each: angle name, hook sentence (under 15 words), and which platform it's strongest on (LinkedIn, Twitter, newsletter, blog).
Avoid: listicles, "X things I learned," "unpopular opinion" openers.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 20 — LinkedIn post&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a LinkedIn post about [topic] for [audience type].
Hook: specific, contrarian, or data-backed — not a question.
Body: one insight, one example, one implication. Under 150 words.
CTA: one action, not two.
Do not use: "I'm excited to share," "game-changer," "at the end of the day."
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 21 — Newsletter section&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a 200-word newsletter section on [topic] for [audience].
Voice: direct, first-person, slightly opinionated.
Structure: opening claim → one concrete example → so-what takeaway.
End with a single question or observation, not a CTA.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 22 — Case study outline&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I want to write a case study about [project outcome] for [client type].
Write a 5-section case study outline: Situation → Problem → Approach → Results → Lessons.
For each section: what to include, what to leave out, and what makes it credible.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 23 — Lead magnet concept&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I sell [service/product] to [audience].
Generate 5 lead magnet concepts that: solve a specific micro-problem, can be consumed in under 20 minutes, and pre-qualify buyers for my offer.
For each: title, format (checklist/template/guide), and 1-sentence value prop.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 24 — Product description&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a product description for [product name] targeting [audience].
Include: what it is (one sentence), who it's for (specific), what they get (3 bullet points), and what changes after they buy.
End with a risk-reversal line.
Under 120 words. No hype.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 5: Strategy &amp;amp; Planning (Prompts 25–30)
&lt;/h2&gt;

&lt;p&gt;The thinking work that compounds. These prompts cut through the strategic paralysis that kills solopreneur momentum.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Prompt 25 — Revenue gap analysis&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;My current monthly revenue is [amount]. My target is [amount] in [timeframe].
My current offers: [list with prices].
Run a gap analysis: what's the delta, what offer mix closes it at [conversion rate assumption], and what's the single highest-leverage action this month.
Be direct. Don't hedge.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 26 — Offer positioning&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I offer [service/product] to [audience]. My three competitors are [C1, C2, C3].
Write a positioning statement that: names who I'm for, what I do, and why I'm different — without using "passionate," "results-driven," or "proven."
Then write a 1-sentence version for my bio.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 27 — Pricing strategy&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm about to price [new offer]. Comparable offers in the market range from [low] to [high].
My differentiation: [1-2 sentences].
Recommend: anchor price, launch price, and the psychological framing that justifies the gap between the two.
Reason through it, don't just give numbers.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 28 — 90-day plan&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I want to hit [goal] in 90 days. Current state: [brief description].
Constraints: [time, money, skills].
Build a 90-day plan in 3 phases (30/30/30). Each phase: primary objective, 2-3 key actions, single metric to track.
Flag the single biggest risk to the plan.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 29 — Decision framework&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;I'm deciding whether to [decision]. Stakes: [what's at risk].
Arguments for: [list]. Arguments against: [list].
Apply a decision framework (your choice — name it first) and give me a recommendation.
Then tell me what information would change your recommendation.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;Prompt 30 — Monthly review&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;It's the end of [month].
Revenue: [amount]. Target: [amount].
Top win: [describe]. Biggest miss: [describe].
Generate 5 reflection questions that will surface the root cause of the miss and a 1-paragraph summary of what to carry forward into next month.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  The System Behind the Prompts
&lt;/h2&gt;

&lt;p&gt;Prompts alone aren't the system. The system is knowing &lt;em&gt;which prompt to reach for, when&lt;/em&gt;.&lt;/p&gt;

&lt;p&gt;Here's how I actually use these 30:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Sunday night (15 min):&lt;/strong&gt; Prompt 15 (weekly planning) + Prompt 19 (content angles for the week)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Every new lead:&lt;/strong&gt; Prompts 1–3 in sequence, Prompt 4 on standby&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Client onboarding:&lt;/strong&gt; Prompts 7, 8, 14 in that order&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Month-end:&lt;/strong&gt; Prompts 25, 29, 30 in sequence&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;The prompts don't replace judgment. They compress the time between "I need to do this" and "this is done."&lt;/p&gt;




&lt;h2&gt;
  
  
  Want These as Copy-Paste Templates?
&lt;/h2&gt;

&lt;p&gt;I packaged all 30 prompts — plus 70+ more across 8 solopreneur roles — into the &lt;strong&gt;Busy Professionals ChatGPT Prompt Bundle&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;Use code &lt;strong&gt;LAUNCH30&lt;/strong&gt; for 30% off at launch.&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://pinzasai.gumroad.com" rel="noopener noreferrer"&gt;Grab the bundle on Gumroad&lt;/a&gt; | Use code &lt;strong&gt;LAUNCH30&lt;/strong&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Built these over 6 months of real use. If you're a solopreneur, consultant, or freelancer looking to cut admin overhead without cutting output — this is the workflow.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>solopreneur</category>
      <category>chatgpt</category>
      <category>productivity</category>
      <category>ai</category>
    </item>
    <item>
      <title>ChatGPT Prompts for Financial Advisors: Client Reports, Market Summaries, and Compliance Emails</title>
      <dc:creator>ClawGear</dc:creator>
      <pubDate>Tue, 21 Apr 2026 04:49:21 +0000</pubDate>
      <link>https://forem.com/clawgear/chatgpt-prompts-for-financial-advisors-client-reports-market-summaries-and-compliance-emails-1k4m</link>
      <guid>https://forem.com/clawgear/chatgpt-prompts-for-financial-advisors-client-reports-market-summaries-and-compliance-emails-1k4m</guid>
      <description>&lt;h1&gt;
  
  
  ChatGPT Prompts for Financial Advisors: Client Reports, Market Summaries, and Compliance Emails
&lt;/h1&gt;

&lt;p&gt;You billed $300/hour on Wednesday. Then spent Thursday morning writing the same quarterly client summary you've written 87 times.&lt;/p&gt;

&lt;p&gt;That math doesn't work.&lt;/p&gt;

&lt;p&gt;Financial advisors who manage 100+ client relationships spend an estimated 30–40% of their work week on administrative writing — reports, market commentary, compliance emails, meeting notes. According to Cerulli Associates, the average advisor manages 114 client households. Multiply the time cost across that book of business and you're looking at 600+ hours a year on tasks that don't require a CFP designation. They require a good writer and the patience to repeat yourself.&lt;/p&gt;

&lt;p&gt;ChatGPT is neither your analyst nor your compliance officer. It's your writing infrastructure — the layer that turns your knowledge into a first draft in 30 seconds instead of 30 minutes.&lt;/p&gt;

&lt;p&gt;This article gives you 15 copy-pasteable prompts across the three categories where advisors lose the most time: client reporting, market summaries, and compliance communications. Every prompt is production-ready. Use them as-is, or modify the bracketed fields to match your client's situation.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Important:&lt;/strong&gt; All AI-generated output must be reviewed against your firm's compliance policies and your RIA's guidelines before sending. These prompts are templates for administrative communication — they do not constitute investment advice and should not be treated as such.&lt;/p&gt;




&lt;h2&gt;
  
  
  Why Financial Advisors Are Slow to Adopt AI (And Why That's Your Advantage)
&lt;/h2&gt;

&lt;p&gt;Most advisors haven't touched AI tools because the financial services industry is cautious by design. FINRA, the SEC, and individual RIA compliance programs add friction to anything new. That's legitimate.&lt;/p&gt;

&lt;p&gt;But that friction is also creating a gap. Early-adopting advisors are already using ChatGPT for the boring administrative layer — the writing tasks that don't touch regulated advice — and recapturing 8–12 hours a week.&lt;/p&gt;

&lt;p&gt;The prompts in this article are designed for the communication and administrative layer only. None of them generate portfolio recommendations, performance projections, or investment opinions. They generate the words around your work — so you can do more of the actual work.&lt;/p&gt;




&lt;h2&gt;
  
  
  Category 1: Client Reporting Prompts
&lt;/h2&gt;

&lt;p&gt;Client reports are the most time-intensive administrative task advisors face. The quarterly summary alone requires pulling performance data, translating it into client-friendly language, contextualizing market conditions, and maintaining a consistent tone across hundreds of households.&lt;/p&gt;

&lt;p&gt;These five prompts handle the writing layer. You supply the data. ChatGPT supplies the draft.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Prompt 1 — Quarterly Performance Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a quarterly portfolio summary email for a client in the [conservative / moderate / aggressive] risk category.

Portfolio performance this quarter: [X]%
Benchmark (e.g., S&amp;amp;P 500) performance: [Y]%
Key holdings that contributed positively: [list 2-3]
Key holdings that detracted: [list 1-2]
Notable market events that affected the portfolio: [brief notes]

Tone: professional but plain English. No jargon. 150–200 words. End with a sentence inviting the client to schedule a review call.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 2 — Annual Review Letter&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a personalized annual review letter for a [relationship length]-year client.

Client name: [First name or "Mr./Ms. Last name"]
This year's portfolio return: [X]%
Progress toward stated financial goal (e.g., retirement at 65, college fund, home purchase): [brief update]
One significant adjustment we made this year and why: [explain the change]
What we're monitoring going into next year: [1–2 items]

Tone: warm and relationship-focused. 200–250 words. Do not include specific investment advice or forward-looking performance guarantees.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 3 — Mid-Year Portfolio Check-In&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief mid-year portfolio check-in email for a client.

Context: It's mid-[year]. Markets have been [describe: volatile / trending up / choppy / mixed].
Their portfolio is [up X% / flat / down X%] year-to-date.
One rebalancing action we took: [describe]
One thing they should be aware of but not alarmed by: [explain]

Length: 100–150 words. Tone: steady, reassuring, factual. No performance predictions.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 4 — New Client Welcome Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a welcome email for a new wealth management client.

Client name: [First name]
Services they're receiving: [e.g., financial planning, portfolio management, tax coordination]
Their primary goal: [e.g., retire by 60, fund children's education, build generational wealth]
First steps we've completed together: [e.g., completed risk assessment, reviewed existing holdings, established IPS]
Next scheduled touchpoint: [date / type of meeting]

Tone: warm and confidence-building. 150 words. Do not make performance promises.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 5 — Portfolio Update After a Market Event&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief client update email following a significant market event.

Event: [describe: e.g., Federal Reserve rate decision, equity market selloff, sector-specific volatility]
How it affected this client's portfolio: [specific impact or "minimal direct impact"]
Our position / what we did or didn't do in response: [action or rationale for holding]
What clients should watch for next: [1 item, factual only]

Tone: calm, clear, authoritative. 120–150 words. Avoid alarmist language. Do not predict future market movements.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 2: Market Summary Prompts
&lt;/h2&gt;

&lt;p&gt;Weekly market commentary is a relationship-retention tool. Clients who receive regular market updates stay longer and refer more. But writing original commentary takes time you don't have.&lt;/p&gt;

&lt;p&gt;These prompts turn your raw notes into polished client-facing summaries.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Prompt 6 — Weekly Market Recap (Client Newsletter)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a weekly market recap suitable for a client newsletter.

Time period: week ending [date]
Equity market performance: [e.g., S&amp;amp;P 500 +1.2%, Nasdaq -0.8%, Dow +0.9%]
Bond market movement: [brief note]
Key economic data released this week: [e.g., CPI print, jobs report, Fed minutes]
One theme or story that defined the week: [describe in plain language]

Format: 150–200 words, bullet points for the data section, one narrative paragraph for the theme. No forward-looking predictions. Plain English — assume the reader is not a financial professional.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 7 — Asset Class Commentary (Monthly)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write brief monthly commentary for each of the following asset classes. Keep each to 2–3 sentences. Plain English, no predictions.

US Equities: [key moves, sectors, headline]
International Equities: [key moves, regions, headline]
Fixed Income: [rate environment, duration impact]
Alternatives / Commodities: [gold, oil, or other relevant data]
Cash / Money Market: [current yield context]

Audience: retail investors with moderate financial literacy. Tone: educational and neutral.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 8 — Macro Outlook Summary for Clients&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a macro outlook summary for clients. This is NOT a forecast — it is a summary of what major institutions and economists are currently discussing.

Key themes in the current macro environment (supply from your own research or notes): [list 3–4 themes, e.g., sticky inflation, labor market softening, election uncertainty, AI capex cycle]

Format: 200 words, organized by theme. End with one sentence reminding the reader that macro environment does not necessarily predict short-term portfolio outcomes. Do not make investment recommendations.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 9 — Sector Spotlight (Client Education Piece)&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a client education piece on the [sector name] sector.

Why it's relevant right now: [brief context]
How it's performed recently: [data if available, or qualitative note]
Key risks in this sector: [2–3 factual risks]
Key tailwinds: [2–3 factual tailwinds]
How this might appear in a diversified portfolio: [general note only — not advice]

Length: 200–250 words. Tone: educational, balanced. No buy/sell recommendations. No specific stock names unless they're already public information you are commenting on factually.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 10 — Rate Environment Update&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a client-facing summary of the current interest rate environment.

Current Fed Funds Rate target: [X.XX%]
Last Fed action: [raised / held / cut] at [month] meeting
Market expectations (per CME FedWatch or similar): [brief summary]
How the current rate environment affects: (a) bond prices, (b) mortgage rates, (c) savings accounts / money market yields

Length: 150 words. Tone: factual and plain. No rate predictions. No investment recommendations.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  Category 3: Compliance and Communication Prompts
&lt;/h2&gt;

&lt;p&gt;Compliance-safe communication is the most legally fraught writing task in your practice. The prompts below are designed for administrative and disclosure communication only — not for marketing claims, performance projections, or testimonials.&lt;/p&gt;

&lt;p&gt;Review every output with your compliance officer before using in regulated contexts.&lt;/p&gt;




&lt;p&gt;&lt;strong&gt;Prompt 11 — ADV Part 2 Plain-Language Summary&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Rewrite the following excerpt from our ADV Part 2 in plain English for a new client introduction document. Do not change the substance — only the readability. Maintain all disclosures and material facts.

[Paste your ADV Part 2 excerpt here]

Target reading level: 8th grade. Length: match the original word count approximately. Flag any sentences where the meaning is unclear and you are unsure of the intent.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 12 — Compliant Prospecting Email&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a compliant prospecting email for [target audience: e.g., business owners approaching exit, recently divorced individuals, retirees in wealth transition].

Services to mention: [list 2–3]
Key differentiator of our firm: [one specific, factual differentiator — not "best" or "top-rated"]
CTA: schedule a 30-minute introductory call

Constraints: No performance claims. No testimonials. No guarantees. No language like "beat the market" or "guaranteed returns." Include a brief disclosure line: "Past performance is not indicative of future results." Keep under 150 words.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 13 — Client Meeting Follow-Up with Action Items&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a post-meeting follow-up email summarizing a client meeting.

Meeting date: [date]
Attendees: [names / roles]
Topics discussed: [list 3–5 topics in bullet point form]
Decisions made: [list any confirmed decisions]
Action items with owners:
  - Advisor to do: [list]
  - Client to do: [list]
Next meeting: [date or "TBD"]

Tone: professional, clear, and organized. Do not include any investment advice, performance commentary, or forward-looking statements beyond the scope of what was discussed.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 14 — Disclosure Language for Marketing Materials&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a compliance disclosure block suitable for [email newsletters / social media bios / website service pages].

Our firm type: [RIA / broker-dealer / dual registrant]
State(s) of registration: [list]
Required disclosures to include: [list any specific disclosures your compliance officer requires]

Format: 2–4 sentences, suitable for small print at the bottom of a document. Do not include specific investment claims.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;p&gt;&lt;strong&gt;Prompt 15 — Sensitive Communication: Client Experiencing Loss&lt;/strong&gt;&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Write a brief, compassionate email to a client who recently experienced [bereavement / divorce / job loss] and may need to revisit their financial plan.

Tone: human first, advisor second. Acknowledge the situation briefly. Do not pivot immediately to financial planning. Offer availability without pressure. Close with warmth.

Length: 80–100 words. Do not include investment commentary or performance data.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;






&lt;h2&gt;
  
  
  What ChatGPT Cannot Do (The Honest Section)
&lt;/h2&gt;

&lt;p&gt;Advisors who over-rely on AI for client communication will create problems. Here's what ChatGPT genuinely cannot do in your practice:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;
&lt;strong&gt;Verify compliance with your specific RIA policies.&lt;/strong&gt; Every firm's compliance manual is different. ChatGPT doesn't know yours.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Assess client suitability.&lt;/strong&gt; It has no access to your client's financial profile, risk tolerance documentation, or investment policy statement.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Generate defensible performance data.&lt;/strong&gt; Never use AI to create performance statistics — use your portfolio management or reporting system.&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Replace relationship judgment.&lt;/strong&gt; A client who just lost a spouse doesn't need a prompt. They need a phone call.&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Use these prompts for the writing layer. Keep the judgment layer firmly in your hands.&lt;/p&gt;




&lt;h2&gt;
  
  
  The 15 Prompts in Summary
&lt;/h2&gt;

&lt;div class="table-wrapper-paragraph"&gt;&lt;table&gt;
&lt;thead&gt;
&lt;tr&gt;
&lt;th&gt;#&lt;/th&gt;
&lt;th&gt;Category&lt;/th&gt;
&lt;th&gt;Prompt Use&lt;/th&gt;
&lt;/tr&gt;
&lt;/thead&gt;
&lt;tbody&gt;
&lt;tr&gt;
&lt;td&gt;1&lt;/td&gt;
&lt;td&gt;Client Reporting&lt;/td&gt;
&lt;td&gt;Quarterly performance summary&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;2&lt;/td&gt;
&lt;td&gt;Client Reporting&lt;/td&gt;
&lt;td&gt;Annual review letter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;3&lt;/td&gt;
&lt;td&gt;Client Reporting&lt;/td&gt;
&lt;td&gt;Mid-year portfolio check-in&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;4&lt;/td&gt;
&lt;td&gt;Client Reporting&lt;/td&gt;
&lt;td&gt;New client welcome&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;5&lt;/td&gt;
&lt;td&gt;Client Reporting&lt;/td&gt;
&lt;td&gt;Post-market-event update&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;6&lt;/td&gt;
&lt;td&gt;Market Summaries&lt;/td&gt;
&lt;td&gt;Weekly recap newsletter&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;7&lt;/td&gt;
&lt;td&gt;Market Summaries&lt;/td&gt;
&lt;td&gt;Asset class commentary&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;8&lt;/td&gt;
&lt;td&gt;Market Summaries&lt;/td&gt;
&lt;td&gt;Macro outlook summary&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;9&lt;/td&gt;
&lt;td&gt;Market Summaries&lt;/td&gt;
&lt;td&gt;Sector spotlight&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;10&lt;/td&gt;
&lt;td&gt;Market Summaries&lt;/td&gt;
&lt;td&gt;Rate environment update&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;11&lt;/td&gt;
&lt;td&gt;Compliance&lt;/td&gt;
&lt;td&gt;ADV Part 2 plain-language rewrite&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;12&lt;/td&gt;
&lt;td&gt;Compliance&lt;/td&gt;
&lt;td&gt;Compliant prospecting email&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;13&lt;/td&gt;
&lt;td&gt;Compliance&lt;/td&gt;
&lt;td&gt;Meeting follow-up with action items&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;14&lt;/td&gt;
&lt;td&gt;Compliance&lt;/td&gt;
&lt;td&gt;Disclosure language block&lt;/td&gt;
&lt;/tr&gt;
&lt;tr&gt;
&lt;td&gt;15&lt;/td&gt;
&lt;td&gt;Compliance&lt;/td&gt;
&lt;td&gt;Sensitive client communication&lt;/td&gt;
&lt;/tr&gt;
&lt;/tbody&gt;
&lt;/table&gt;&lt;/div&gt;




&lt;h2&gt;
  
  
  Go Deeper: The Full Financial Advisor AI Workflow Toolkit
&lt;/h2&gt;

&lt;p&gt;These 15 prompts cover the communication layer. The &lt;strong&gt;&lt;a href="https://pinzasrojas.gumroad.com/l/vfvrae" rel="noopener noreferrer"&gt;Financial Advisor AI Workflow Toolkit&lt;/a&gt;&lt;/strong&gt; goes further — with 50+ structured prompts for client segmentation, prospect nurturing, estate planning communication, tax-loss harvesting documentation, and practice management workflows.&lt;/p&gt;

&lt;p&gt;Built specifically for RIAs, wealth managers, and fee-only advisors who want to cut admin time without cutting corners on compliance.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Use code LAUNCH30 for 30% off — limited uses remaining.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;→ &lt;a href="https://pinzasrojas.gumroad.com/l/vfvrae" rel="noopener noreferrer"&gt;Get the Financial Advisor AI Workflow Toolkit&lt;/a&gt;&lt;/p&gt;




&lt;p&gt;&lt;em&gt;All prompts in this article are for administrative and communication purposes only. Nothing in this article constitutes investment advice. Always review AI-generated output with your firm's compliance team before distribution.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>chatgpt</category>
      <category>finance</category>
      <category>productivity</category>
      <category>ai</category>
    </item>
  </channel>
</rss>
