Turn rough notes into a clear email
Paste bullet points or a voice-to-text ramble and get a ready-to-send email.
You are helping me write a professional email.
Recipient: [who they are and our relationship]
Goal: [what I want them to know or do]
Tone: [friendly / formal / direct]
My rough notes:
[paste notes]
Write the email in under 150 words with a clear subject line. Put the request or key point in the first two sentences. End with one specific next step. Do not invent facts that are not in my notes.
Reply to a frustrated customer
Draft a calm, accountable reply to a complaint for a person to review before sending.
Draft a reply to this customer message for me to review.
Customer message:
[paste message]
What actually happened on our side: [facts]
What we can offer: [refund / redo / discount / call / nothing beyond an apology]
Rules: acknowledge the specific problem in their words, take responsibility where we are at fault, do not make promises beyond what I listed, keep it under 120 words, and end with a clear next step. Avoid generic phrases like "we value your business."
Summarize a long email thread
Get the decisions, open questions, and owners from a messy thread in seconds.
Summarize the email thread below for someone who has not read it.
Return:
1. A two-sentence summary of what the thread is about.
2. Decisions made (bullet list).
3. Open questions (bullet list).
4. Action items with the person responsible and any deadline mentioned.
Only use information in the thread. If an owner or deadline is unclear, say "unclear".
Thread:
[paste thread]
Classify incoming emails for routing
A prompt to use inside an automation that sorts inbound email by type and urgency.
Classify the email below. Respond with JSON only, using exactly these keys:
{"category": one of ["sales_inquiry", "support_request", "billing", "scheduling", "vendor", "spam", "other"], "urgency": one of ["high", "normal", "low"], "summary": a sentence under 20 words, "needs_human": true or false}
Mark urgency high only if the sender reports something broken, a payment problem, or a same-day deadline. Set needs_human to true for complaints, legal or medical questions, and anything you are unsure about.
Email:
[email text]Write a first reply to a new lead
A fast, personal first response to a web form or inquiry.
Write a short first reply to a new lead for [business name], a [type of business].
Lead's message: [paste form submission]
What we offer that is relevant: [services]
How to book: [link or phone]
Keep it under 90 words, reference something specific from their message, answer any simple question they asked, and invite them to book a call with one clear link. Friendly and human, no hype.
Three-step follow-up sequence
Follow-ups for leads who have not replied, ready to load into your CRM or automation tool.
Write a three-message follow-up sequence for leads who asked about [service] but have not replied.
Timing: day 1 (text message), day 3 (email), day 7 (text message).
Voice: [describe our tone]
Each message should be shorter than the last, add something new (a helpful tip, a common question answered, or a simple yes or no question), and make replying easy. Texts under 280 characters. Do not use fake urgency or discounts unless I list one: [offer, if any].
Prepare for a sales call
A one-page brief from what you know about a prospect.
Prepare a one-page call brief.
Prospect: [company, person, role]
What they told us: [form answers, emails, notes]
What we sell: [offer]
Include: their likely goals and pain points (marked as assumptions), five discovery questions tailored to them, two relevant examples of how we have helped similar businesses (use only these: [examples]), likely objections with honest responses, and a suggested next step for the end of the call.
Turn call notes into a CRM update
Clean, structured notes and next steps from a messy call transcript.
Turn these sales call notes into a CRM update.
Return these fields: Summary (3 sentences), Budget, Timeline, Decision makers, Needs, Objections, Next step, Follow-up date. Write "not discussed" for anything not in the notes. Do not guess numbers.
Notes:
[paste notes or transcript]
Write a proposal summary
A clear executive summary for a quote or proposal.
Write the executive summary for a proposal.
Client: [name and situation]
Their problem in their words: [quote or notes]
Our solution: [what we will do]
Deliverables: [list]
Timeline: [dates]
Price: [amount and terms]
Under 200 words. Open with their problem, explain the outcome they will get, then the plan. Plain language, no jargon, no claims I have not provided.
Repurpose one post into five
Turn a blog post or video transcript into social posts for several channels.
Repurpose the content below into:
1. A LinkedIn post (under 200 words, one clear takeaway, ends with a question)
2. Two short posts for X (under 260 characters each)
3. An Instagram caption (under 120 words with 3 to 5 relevant hashtags)
4. A two-sentence email newsletter teaser with a link placeholder
Keep the facts exactly as written. Audience: [who they are]. Voice: [describe].
Content:
[paste]
Respond to an online review
Personal, on-brand responses to positive and negative reviews.
Write a public response to this review for [business name].
Review ([star rating] stars):
[paste review]
For 4 to 5 stars: thank them by name, mention one specific detail they shared, and keep it under 60 words.
For 1 to 3 stars: thank them, acknowledge the specific issue without arguing or sharing private details, explain any fix briefly, and invite them to contact [name, phone or email] directly. Under 90 words. Never offer incentives in a public reply.
Outline an SEO article
A helpful article outline built around what a searcher actually needs.
Create an outline for an article targeting the search "[keyword]".
Audience: [who is searching and why]
Our expertise: [what we know first-hand]
Include: a title under 60 characters, a two-sentence answer to the search for the opening paragraph, H2 sections in a logical order, the key points under each, three FAQ questions people also ask, and where a table, checklist, or example would help. Flag any statistic that would need a source.
Write a monthly customer newsletter
A short, useful newsletter from a few updates and tips.
Write a customer newsletter for [business name].
This month's updates: [list]
One helpful tip for customers: [topic]
Call to action: [what we want readers to do, with link placeholder]
Format: subject line plus preview text, a two-sentence intro, the tip as the main section (around 120 words), updates as short bullets, then the call to action. Warm, practical, no filler.
Answer from your own help content
A grounded support answer that only uses your approved information.
You are a support assistant for [business name]. Answer the customer's question using ONLY the reference information below. If the answer is not in the reference information, say you will connect them with a team member and do not guess.
Reference information:
[paste FAQ, policies, product details]
Customer question:
[question]
Answer in under 100 words, in plain language, and include the relevant link from the reference information if there is one.
Turn tickets into FAQ entries
Find repeated questions in support tickets and draft answers for your help center.
Below are recent customer support tickets. Group them by the underlying question, then list the top [number] questions with how many tickets each covers. For each, draft a clear FAQ answer under 80 words using only what the tickets and our policy notes say.
Policy notes: [paste]
Tickets:
[paste tickets]
Write a status update for an outage or delay
Clear, honest customer communication when something goes wrong.
Write a customer update about [issue].
What happened: [facts]
Who is affected: [customers or services]
What we are doing: [actions]
Next update: [time]
Under 120 words. Say plainly what is affected and what customers should do, if anything. Apologize once, do not speculate about causes we have not confirmed, and do not promise a fix time unless I gave one.
Write a support macro
Reusable reply templates with personalization fields.
Write a reusable support reply template for this situation: [situation, e.g. customer asks to change their appointment].
Our process: [steps]
Links: [booking or help links]
Use placeholders like {first_name} and {date} where personal details belong. Keep it under 90 words, friendly, and include exactly what the customer needs to do next.Write a standard operating procedure
Turn how someone does a task into a step-by-step SOP a new hire can follow.
Turn the description below into a standard operating procedure.
Format: Purpose (one sentence), When to use it, Tools needed, numbered Steps (one action per step, starting with a verb), Common mistakes, and Who to ask for help. Mark any step that requires judgment with "(judgment call)". Flag anything ambiguous as a question at the end instead of guessing.
Description:
[paste how the task is done today]
Pull structured fields out of an order, form, or contract for an automation.
Summarize a meeting into actions
Decisions, owners, and deadlines from a meeting transcript.
Summarize this meeting transcript.
Return: a three-sentence summary, decisions made, action items as a table (task, owner, due date), and open questions. Only include owners and dates that were actually said; otherwise write "unassigned" or "no date".
Transcript:
[paste]
Draft a weekly operations report
Turn raw numbers into a short narrative report for the team or owner.
Write a weekly operations summary from the numbers below.
This week: [metrics]
Last week: [metrics]
Targets: [targets]
Format: three bullet highlights, three bullet concerns (with the numbers that justify them), and one recommended focus for next week. Calculate changes accurately and show the percentage change. Do not speculate about causes; list possible causes as questions.
Polite payment reminder sequence
Before-due, due-date, and overdue reminders that stay friendly.
Write three payment reminder emails for invoice {invoice_number} for {amount} due {due_date}.
1. Three days before the due date: friendly heads-up with the pay link {pay_link}.
2. On the due date: short reminder.
3. Seven days overdue: polite but direct, asks them to pay or reply if there is a problem.
Each under 80 words. Keep the placeholders exactly as written. No threats, no fees unless I list one: [late fee policy, if any].Categorize expenses
Sort a list of transactions into your chart of accounts for review.
Categorize each transaction below into one of these categories: [list your expense categories].
Return a table with: date, description, amount, category, confidence (high, medium, low). Use "needs review" as the category when you are not confident. Do not change amounts.
Transactions:
[paste]
Explain a financial report in plain English
Understand a P&L or cash flow report without the jargon.
Explain this [profit and loss / cash flow / balance sheet] report to a business owner who is not an accountant.
Cover: what the business earned and spent, the three biggest changes from the previous period with the numbers, anything that looks unusual and is worth asking my accountant about, and one question I should ask about cash. Use plain language and do not give tax or legal advice.
Report:
[paste]
Write a job description
A clear, inclusive job post from a few notes.
Write a job description for a [role] at [business name], a [type of business] in [location or remote].
What this person will do: [notes]
Must-haves: [list]
Nice-to-haves: [list]
Pay range and benefits: [details]
Format: a two-sentence intro about the role, what you will do (bullets), what you bring (bullets, must-haves only), nice to have, pay and benefits, and how to apply. Use inclusive language and avoid jargon and unnecessary requirements.
Screen applications against criteria
A consistent first-pass summary of applications for a person to decide on.
Compare the application below with these criteria: [list criteria].
For each criterion, say whether the application shows evidence (yes, partial, no) and quote the evidence. Then list questions to ask in an interview. Do not score or reject the candidate, do not consider age, gender, ethnicity, or other protected characteristics, and do not infer anything not stated.
Application:
[paste]
Build a new-hire onboarding plan
A first-two-weeks plan with tasks, training, and check-ins.
Create a two-week onboarding plan for a new [role].
Tools they need access to: [list]
Training they need: [list]
Who they will work with: [names and roles]
Organize by day for week one and by goal for week two. Include accounts to set up before day one, a short welcome message from the manager, check-in meetings, and one small real task they can finish in week one.
Find automation opportunities in a process
Map a process and spot the steps worth automating.
I will describe a process in my business. Break it into numbered steps, and for each step identify: who does it, which tool or system it happens in, the trigger that starts it, and whether it is (a) rule-based and automatable, (b) suitable for an AI step with human review, or (c) best left to a person. Then recommend the single highest-value step to automate first and explain why in two sentences.
Process:
[describe the process from start to finish]
Write the spec for a workflow
Turn an idea into a clear trigger, steps, and edge cases before you build.
Help me write a specification for an automation.
Goal: [what should happen]
Tools involved: [apps]
Return: Trigger (exactly what event starts it), Inputs (data available at the trigger), Steps (numbered, one action each, naming the app), Conditions and branches, Outputs, Edge cases and how to handle each one, What to log, and Who gets alerted when it fails. Ask me questions about anything ambiguous at the end.
Write test cases for an automation
Realistic examples to test a workflow before it goes live.
Write test cases for this automation: [describe trigger and steps].
Include 10 cases: 4 normal cases with realistic data, 3 edge cases (missing fields, duplicates, unusual formats), and 3 failure cases (an app is down, a value is invalid, a person needs to step in). For each, give the input, the expected result, and what should be logged or alerted.
Improve an AI prompt used in an automation
Make a prompt that runs inside a workflow more reliable.
Here is a prompt used inside an automated workflow, plus examples of outputs that went wrong.
Prompt:
[paste]
Bad outputs and what was wrong with each:
[paste]
Rewrite the prompt to be more reliable. Make the task and output format explicit, add rules that prevent the failures shown, include one short example of correct output, and tell the model what to do when it is unsure. Explain each change in one line.
Choose between Zapier, Make, n8n, or custom
A structured recommendation for which platform fits a workflow.
Recommend an automation approach for this workflow: [describe it].
Our context: monthly volume [number of runs], apps involved [list], technical comfort [low / medium / high], budget [range], data sensitivity [low / medium / high].
Compare Zapier, Make, n8n (cloud or self-hosted), and a custom build on: setup effort, running cost at our volume, flexibility, reliability, and data control. Recommend one with reasons, and list what would change your recommendation. Note that pricing changes often and should be checked on each vendor's site.
No prompts match that search. Try a different word or pick another category.
