ChatGPT is useful at work only when your prompts are specific. Vague prompts produce vague copy. Strong prompts give the model a role, audience, constraints, and an output format—so you get drafts you can edit in minutes instead of rewriting from scratch.
Affiliate Disclosure: Some links in this article are affiliate links. If you buy through them, we may earn a commission at no extra cost to you. We only recommend products we believe are useful. See our full policy at /affiliate-disclosure/.
This guide gives you 30 copy-ready business prompts: 10 for sales, 10 for support, and 10 for content. Each one is designed to turn messy inputs (meeting notes, tickets, briefs) into usable drafts. Adapt names, tone, and product details to your company.
How to Use These Prompts Well
Before you paste anything into ChatGPT, remember four rules:
- Never paste secrets. Strip customer PII, passwords, contract terms, and unreleased roadmap details.
- Give examples of your voice. One short sample of a past email often improves output more than ten adjectives.
- Ask for options. Request 2–3 variants so you can mix the best lines.
- Edit like a human. AI drafts are starting points. Fact-check claims and add what only you know.
When you want a larger reusable library with industry variants and fill-in blanks, a prompt pack helps.
Sales Prompts (10)
1. Turn Discovery Notes into a Follow-Up Email
You are a B2B sales rep. Using these discovery notes, write a concise follow-up email (120–160 words) that:
- Restates the prospect’s top 2 goals and 1 pain
- Proposes a next step with a clear CTA
- Avoids hype words (revolutionary, game-changing)
Notes: [PASTE NOTES]
Tone: professional, warm, specific
2. Cold Outreach for a Specific Persona
Write 3 cold email variants for [persona] at [company type].
Offer: [1-sentence value prop]
Proof: [metric or case snippet]
Constraints: under 90 words each, no attachments mentioned, one question CTA.
Include subject lines.
3. Objection Handler (Price)
Prospect said: “[objection about price].”
Product: [product]
Competitive alternatives: [list]
Write a reply that acknowledges the concern, reframes value with 2 concrete outcomes, and offers a low-friction next step. Keep under 140 words.
4. Proposal Outline from Call Transcript
Create a one-page proposal outline from this call summary.
Sections: Situation, Goals, Recommended Approach, Timeline, Investment Options (leave prices blank), Next Steps.
Use bullet points only. Flag any missing information as [NEED INPUT].
Call summary: [PASTE]
5. LinkedIn Connection Note
Write a LinkedIn connection note (under 300 characters) for [name/role].
Why I’m reaching out: [reason]
Do not pitch. End with a curiosity question.
6. Re-Engage a Stalled Opportunity
Deal stalled for [N] days after [last touch].
Last known interest: [detail]
Draft a short bump email with 2 options for next steps and one helpful resource idea (no fake links). Tone: respectful, not needy.
7. Competitive Differentiation Talking Points
We sell [product]. Competitor often mentioned: [competitor].
Give me 5 talking points that differentiate without bashing. Format: Claim → Why it matters → Question to ask the buyer.
8. Demo Agenda Email
Write a pre-demo email for [persona].
Include: agenda (4 bullets), what they should prepare, and expected outcomes. Under 150 words.
9. ROI Narrative from Customer Inputs
Using these inputs, draft a simple ROI narrative in plain language.
Inputs: current cost/time, expected savings, payback goal.
Do not invent numbers. Mark unknowns as [ASSUMPTION NEEDED].
10. Handoff Notes for Customer Success
Turn this closed-won summary into a CS handoff brief:
- Customer goals
- Success metrics
- Risks / sensitivities
- Promised deliverables
- First 30-day priorities
Closed-won notes: [PASTE]
Customer Support Prompts (10)
11. Empathetic Reply to Frustrated Customer
Write a support reply for this ticket.
Tone: calm, accountable, clear. Structure: acknowledge → restate issue → next steps → timeline → offer escalation path.
Do not apologize more than once. Avoid corporate clichés.
Ticket: [PASTE]
12. Macros from Repeated Tickets
Here are 8 similar tickets. Create 3 reusable macros with:
- Title
- When to use
- Reply text with [PLACEHOLDERS]
Tickets: [PASTE]
13. Bug Report Triage Summary
Summarize this customer report for engineering.
Fields: Summary, Steps to Reproduce, Expected vs Actual, Environment, Severity guess, Customer impact.
Do not invent missing steps—list questions instead.
Report: [PASTE]
14. Refund / Policy Explanation
Explain our policy on [topic] in customer-friendly language.
Policy facts: [paste policy points]
Customer request: [paste]
Goal: be fair, clear on what is/isn’t possible, and offer an alternative if declining.
15. Status Update During an Outage
Draft a status update for affected customers.
Known facts: [paste]
Unknowns: [paste]
Include: current impact, workaround if any, next update time. Keep under 120 words. No speculation.
16. De-escalate a Public Review
Write a public reply to this review (under 80 words) that:
- Thanks them
- Owns the issue without oversharing internal details
- Invites offline resolution
Review: [PASTE]
17. Knowledge Base Article Draft
Turn this solved ticket thread into a KB article.
Include: title, who it’s for, symptoms, step-by-step fix, related articles placeholders.
Audience: non-technical users.
Thread: [PASTE]
18. SLA Breach Internal Note
Write an internal postmortem note for a missed SLA.
Facts: [paste]
Include: what happened, customer impact, root cause hypotheses, immediate fix, prevention idea.
Tone: factual, blameless.
19. Feature Request Acknowledgment
Customer asked for [feature]. We can’t commit.
Write a reply that validates the need, explains current alternatives, and asks one clarifying question to improve our roadmap insight.
20. Multilingual Tone Check
Rewrite this support reply for clarity at a Grade 8 reading level.
Keep meaning identical. Shorten sentences. Remove idioms.
Original: [PASTE]
Content Prompts (10)
21. Meeting Notes → Blog Outline
Turn these meeting notes into a blog outline for [audience].
Include: working title, hook, 5 H2s, key takeaways, CTA idea.
Notes: [PASTE]
Avoid hype. Prefer practical steps.
22. SEO Brief from a Keyword
Create an SEO content brief for “[keyword]”.
Include: search intent guess, outline, FAQs, internal link themes, what NOT to cover.
Target length: [words]. Audience: [persona].
23. Social Posts from a Long Article
Convert this article into:
- 1 LinkedIn post (120–180 words)
- 3 X/Twitter posts under 240 characters
- 1 email subject + preview line
Preserve the core insight; do not invent stats.
Article: [PASTE]
24. Case Study Skeleton
Build a case study skeleton from these notes.
Sections: Challenge, Approach, Results (mark missing metrics), Quote placeholders, Lessons.
Notes: [PASTE]
25. Webinar Follow-Up Sequence
Write a 3-email follow-up sequence after a webinar.
Email 1: recording + key takeaway
Email 2: practical checklist
Email 3: soft CTA to [offer]
Tone: helpful teacher, not hard sell. Under 130 words each.
Webinar topic: [TOPIC]
26. Product Update Changelog → Customer Email
Rewrite this changelog for customers.
Lead with benefits, then changes, then action required (if any).
Changelog: [PASTE]
27. Repurpose a Podcast Transcript
From this transcript excerpt, extract:
- 5 quotable lines
- 1 how-to listicle outline
- 1 myth vs reality table
Transcript: [PASTE]
28. Competitor Comparison Page (Fair)
Draft a fair comparison section for [our product] vs [alternative].
Criteria: [list]
Rules: no insults, acknowledge competitor strengths, be specific about who we fit best.
29. Headline Variants with Constraints
Write 10 headline options for this draft.
Constraints: under 60 characters, include the benefit, no clickbait punctuation.
Draft summary: [PASTE]
30. Editorial Calendar Themes
Propose a 4-week content calendar for [product/niche].
For each week: theme, 1 pillar post idea, 2 supporting posts, 1 CTA type.
Audience: [persona]. Goal: [goal].
A Simple Prompt Workflow You Can Steal
Use this loop so prompts stay useful:
- Capture raw input (notes, ticket, brief).
- Choose a prompt from the matching category.
- Add constraints: length, tone, audience, forbidden claims.
- Generate 2–3 variants.
- Human edit for facts, brand voice, and compliance.
- Save the winning prompt with a name your team understands.
Teams that skip step 6 reinvent prompts every week. Teams that keep a shared library get faster, more consistent drafts.
Quality Checklist Before You Hit Send
- Does the draft include claims you can verify?
- Did you remove placeholder text and brackets?
- Would you send this to a customer you respect?
- Is the CTA clear and proportional (not pushy)?
- Did you check for confidential details you accidentally left in?
If any answer is no, revise before publishing or sending.
Putting It All Together
You do not need hundreds of prompts. You need a tight set you reuse until muscle memory kicks in. Start with three: discovery follow-up (sales), empathetic ticket reply (support), and meeting notes → outline (content). Expand only when a workflow repeats weekly.
For a fuller prompt library with fill-in templates, role packs, and editing checklists, use a ChatGPT business prompt pack. Treat it as a living toolkit—customize prompts with your product names and brand voice so every draft sounds like your team, not a generic chatbot.