Free AI Prompt Library for Business: 30 Copy-Paste Prompts

Sorts incoming email into categories and flags anything a person must read.

You are a support triage assistant for [COMPANY]. Read the email below and return JSON only, with these keys:
- category: billing, bug, how-to, sales, spam or other
- urgency: low, normal or high
- summary: at most 25 words
- needs_human: true or false

Set needs_human to true if the email mentions legal action, a refund above [AMOUNT], account deletion, a safety issue, or anything you are unsure about. Do not invent facts about our product.

Email:
{{email_body}}

Drafts a reply that a person reviews before anything is sent.

Draft a reply to the customer message below. A person will review it before it is sent.
Tone: [TONE, for example friendly and direct].
Use only facts from the knowledge snippets. If the answer is not in them, write NEEDS ANSWER: followed by the question for the team instead of guessing.
Keep it under 120 words.

Customer message:
{{message}}

Knowledge snippets:
{{snippets}}

Turns a batch of real customer questions into FAQ entries.

Below are real customer questions from the last [PERIOD]. Group the ones that mean the same thing. For each group write one FAQ entry: a short question in the customers own words, and an answer of at most 60 words using only the facts in the notes.
If the notes do not answer a group, write NEEDS ANSWER: and the question for the team.

Questions:
{{questions}}

Notes:
{{notes}}

Summarises a long support thread for the teammate taking over.

Summarise the support thread below for a teammate who has not seen it. Write: what the customer wants, what has been tried, how the customer feels (one line, based only on their words), and the next step you recommend.
Do not add facts that are not in the thread. If something is unclear, list it under Questions.

Thread:
{{thread}}

Drafts a steady reply for a person to review before sending.

A customer is upset. Draft a reply that a person will review before it is sent.
Acknowledge the specific problem in one sentence without admitting fault we have not confirmed. Do not promise a refund, date or fix unless it appears in the confirmed facts. Offer one clear next step. Keep it under 120 words.

Customer message:
{{message}}

Confirmed facts:
{{facts}}

Rates an enquiry against your ideal customer and lists what is missing.

Read the enquiry below and return JSON only with: fit (strong, possible or poor), budget_signal (stated, implied or none), urgency (low, normal or high), reason (at most 20 words), and missing_info (a list of questions to ask).
Our ideal customer: [DESCRIBE IDEAL CUSTOMER]. Base the answer only on the text. If it is unclear, use possible and say what is missing.

Enquiry:
{{enquiry}}

Drafts a short follow-up for a person to edit.

Write a follow-up email after a sales call. A person will edit it before sending.
Include: a one-line thanks, a recap of the three needs the prospect mentioned, the agreed next step with its date if one was given, and one question. Use only the call notes. Keep it under 150 words, plain and friendly.

Call notes:
{{notes}}

Prepares honest answers to the objections buyers raise most.

List the five objections a buyer is most likely to raise about [PRODUCT OR SERVICE]. For each, write a two-sentence answer using only the facts below. If the facts do not support a good answer, say so and suggest what we would need to find out.

Facts:
{{facts}}

Builds the structure of a proposal, not the final text.

Turn the discovery notes below into a proposal outline with these headings: Goal, Current situation, Proposed approach, Scope (included and not included), Timeline, Price (leave as [PRICE]), Risks and assumptions.
Use only what the notes say. Mark every gap with ASK CLIENT: and the question to ask.

Notes:
{{notes}}

Gives a writer a clear brief before drafting.

Create a content brief for an article on [TOPIC] for [AUDIENCE]. Include: the one question the article must answer, a suggested title and three alternatives, an outline of H2 headings, what the reader should be able to do afterwards, and a list of facts or figures that need a source before publishing.
Do not state any statistic yourself.

Creates short posts from an article you wrote.

Using only the article below, write [N] social posts for [PLATFORM]. Each must make one point from the article, stay under [LIMIT] characters, and avoid hype words. Do not add claims or numbers that are not in the article. End each with a plain call to read it.

Article:
{{article}}

Gives options to test, not a promise of results.

Write ten subject lines for the email below: five plain and descriptive, five curiosity-led. Each under 55 characters. No clickbait that the email body does not deliver on, and no all caps.

Email:
{{email}}

Drafts search snippets within the length limits.

Write a meta title (under 60 characters) and a meta description (under 155 characters) for the page below. Put the main phrase [KEYWORD] near the start of the title, describe what the reader gets, and do not promise anything the page does not contain. Give three options and count the characters of each.

Page content:
{{content}}

Tightens writing without changing its meaning.

Edit the text below for clarity. Shorten long sentences, replace jargon with plain words, and cut filler. Keep every fact, number and name exactly as written, and keep my voice. Return the edited text, then a short list of what you changed and anything you were unsure about.

Text:
{{text}}

Pulls structured fields out of messy receipt text.

Extract these fields from the receipt text below: vendor, date (YYYY-MM-DD), currency, subtotal, tax, total, payment_method.
Return JSON only. Use null for any field you cannot find. Do not guess or calculate missing values.

Receipt text:
{{text}}

Writes the wording of a weekly update from numbers you have already calculated.

You are writing a weekly update for [AUDIENCE]. Using only the numbers below, write five bullets: what changed, by how much (absolute and percent), the likely reason only if the data supports one, and one thing to check next week.
If a number looks like a data error, say so instead of explaining it.

Data:
{{table}}

A sanity check to run next to the AI API cost calculator above.

Here is my planned AI feature: [DESCRIPTION].
Average input tokens per request: [N]. Average output tokens per request: [N]. Requests per month: [N].
Price per 1M input tokens: [PRICE]. Price per 1M output tokens: [PRICE].

Calculate the monthly model cost step by step, list three assumptions that could make the real cost higher, and suggest one way to cut cost without hurting quality.

Turns messy notes into a numbered procedure.

Turn the rough notes below into a standard operating procedure for [TASK]. Use numbered steps, name who does each step and which tool they use, add a check after each risky step, and end with what to do if something goes wrong.
If a step is missing or unclear, write ASK: and the question instead of inventing it.

Notes:
{{notes}}

Lines up quotes on the same terms.

Compare the vendor quotes below in a table with one row per vendor and these columns: price, what is included, what costs extra, contract length, cancellation terms, and anything unclear.
Use only the text provided. Write NOT STATED where a quote is silent. Finish with three questions to ask each vendor.

Quotes:
{{quotes}}

Drafts a firm but friendly reminder for review.

Write a polite payment reminder for invoice [NUMBER], amount [AMOUNT], due [DATE], now [N] days overdue. Tone: [TONE]. Mention how to pay and who to contact. Do not threaten, add fees or invent terms that are not listed below. Keep it under 100 words.

Payment terms:
{{terms}}

Turns a transcript into decisions, owners and open questions.

From the transcript below, list:
1. Decisions made
2. Action items, each with an owner and a due date (write unassigned if either is missing)
3. Open questions

Keep dates exactly as spoken, and do not add tasks nobody mentioned. Quote nothing longer than 10 words.

Transcript:
{{transcript}}

Builds an agenda with time boxes.

Create an agenda for a [LENGTH]-minute meeting about [PURPOSE] with [ATTENDEES]. For each item give the question to settle, who leads it and a time box. Put decisions first and updates last. End with five minutes for actions. Flag any item that could be an email instead.

Summarises a thread and pulls out what you owe.

Summarise the email thread below in this order: the decision or question at the centre, what each person wants, what is agreed, what is still open, and anything I need to reply to or do (with who asked and any date they gave).
Quote nothing longer than 10 words and add no facts.

Thread:
{{thread}}

Records why a decision was made.

From the notes below write a decision log entry with: the decision, the date, who decided, the options considered, why this one was chosen, what would make us revisit it, and the review date. Use only the notes and mark gaps with UNKNOWN.

Notes:
{{notes}}

Lists what to check before you repeat an article.

Read the text below and list every factual claim that could be checked: numbers, dates, names, quotations and cause-and-effect statements. For each, say what kind of source would confirm it. Do not say whether it is true.

Text:
{{text}}

Scores options on what matters to you.

I am choosing between [OPTION A], [OPTION B] and [OPTION C] for [PURPOSE]. My criteria, in order of importance: [CRITERIA]. Make a table with one row per option and one column per criterion, using only the information I provide below. Write UNKNOWN where it is missing, then list what I should check first.

Information:
{{info}}

Finds failure points before you build.

We plan to automate [PROCESS] using [TOOLS]. Imagine it failed badly three months from now. List the ten most likely reasons, ordered by likelihood times damage. For each give an early warning sign and one safeguard, such as human approval, a spending cap or a log. Mark which risks involve customer data.

Writes a job description around results.

Write a job description for [ROLE] at [COMPANY]. Start from the outcomes this person should deliver in the first 90 days: [OUTCOMES]. Include a short overview, responsibilities, must-have skills, nice-to-have skills, and what we offer from the facts below. Avoid unnecessary requirements and exclusionary wording. Do not invent pay or benefits.

Facts:
{{facts}}

Creates consistent questions for every candidate.

Write eight screening questions for [ROLE]. Each should test one skill from this list: [SKILLS]. For each question give what a strong answer includes and what a weak answer sounds like. Use the same questions for every candidate and avoid questions about age, family, health or other protected topics.

Keeps scoring consistent across interviewers.

Create an interview scorecard for [ROLE]. Use 5 to 7 criteria taken from the outcomes below. For each, give a 1 to 4 scale with a plain description of each score, and a space for evidence quotes. Add a reminder to score before discussing with other interviewers.

Outcomes:
{{outcomes}}