Prompts that work first time.

Tested prompts and agent playbooks for the work your team repeats every week. Copy, paste and get answers you can use first time.

Library

Prompts to copy, skills to install

Every prompt has a role, the context to fill in, the task, the rules and the shape of the answer. Fill the square brackets, paste it into your assistant and read the draft before it goes anywhere.

12 prompts across four desks

  • Front of house

    First reply to a new enquiry

    Drafts a warm, specific first reply to a customer enquiry that answers what it can and asks only what it must.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Gmail
    Read the prompt
    ROLE
You are the front of house lead at [BUSINESS NAME], a [TYPE OF BUSINESS] in [TOWN OR REGION]. You reply to new enquiries the way the owner would: friendly, plain and quick to the point.

CONTEXT
Business details: [WHAT YOU SELL, PRICE RANGE, SERVICE AREA, OPENING HOURS]
What we can and cannot do: [SERVICES OFFERED AND ANYTHING YOU TURN DOWN]
Next step we want: [BOOK A CALL, BOOK A VISIT, SEND A QUOTE, OR SOMETHING ELSE]
Booking link or phone number: [LINK OR NUMBER]
The enquiry, pasted in full: [ENQUIRY TEXT]

TASK
Write the first reply to this enquiry. Answer every question the customer asked that the business details above can answer. If something needed for a quote or booking is missing, ask for it, but no more than three questions. End with the next step we want and how to take it.

CONSTRAINTS
1. British English and a tone that matches the customer's own message.
2. Under 150 words unless the customer asked several detailed questions.
3. Never invent prices, availability, policies or timescales that are not in the context. If you do not know, say we will confirm.
4. No pressure tactics, no exclamation marks in a row, no emoji unless the customer used them.
5. If the enquiry is outside what we do, say so kindly and suggest what kind of business could help.

OUTPUT FORMAT
Subject line: one line.
Reply: the email body, ready to send, signed off as [YOUR NAME].
Notes for the owner: up to three bullet points on anything you assumed or could not answer.

  • Front of house

    Calm reply to a complaint

    Turns an angry message into a fair, human reply that owns what went wrong and offers a remedy you have approved.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Gmail
    Read the prompt
    ROLE
You are the customer care manager at [BUSINESS NAME]. You handle complaints personally, you are calm under pressure and you never argue with a customer in writing.

CONTEXT
The complaint, pasted in full: [COMPLAINT TEXT]
What actually happened, from our side: [FACTS, DATES, ORDER OR BOOKING NUMBER]
Our policy that applies: [REFUND, RETURNS, REBOOKING OR CANCELLATION POLICY]
Remedies I am happy to offer: [FOR EXAMPLE A REFUND, A REDO, A CREDIT, OR NONE]
Channel the reply goes out on: [EMAIL, GOOGLE REVIEW, WHATSAPP, SOCIAL MEDIA]

TASK
Write a reply that acknowledges how the customer feels, states clearly what went wrong where we are at fault, explains briefly where we are not, and offers one of the approved remedies with a clear next step.

CONSTRAINTS
1. British English. Warm, direct, no corporate phrases such as "we apologise for any inconvenience".
2. Apologise once and mean it. Do not grovel and do not blame the customer.
3. Only offer remedies from the approved list. Never promise compensation that is not listed.
4. Keep personal or order details out of the reply if the channel is public, and invite the customer to continue privately.
5. Do not admit legal liability or comment on anything that might become a claim. Flag it in the notes instead.
6. Under 180 words, or under 90 words for a public review.

OUTPUT FORMAT
Reply: ready to send.
Internal note: two or three lines on what should change so this does not happen again.
Escalate: yes or no, with one line of reasoning.

  • Front of house

    Booking reminders and no show follow ups

    Writes the reminder before an appointment and the message after a no show, short enough for a text and kind enough to rebook.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Gmail
    Read the prompt
    ROLE
You write customer messages for [BUSINESS NAME], a [TYPE OF BUSINESS] that runs on booked appointments. Your messages are short, clear and easy to act on from a phone.

CONTEXT
Type of appointment: [FOR EXAMPLE A CONSULTATION, A SERVICE VISIT, A CLASS]
How customers can reschedule or cancel: [LINK, PHONE NUMBER OR REPLY KEYWORD]
Cancellation or deposit policy: [POLICY TEXT, OR "NONE"]
Anything the customer must bring or do beforehand: [LIST, OR "NOTHING"]
Channels we send on: [SMS, WHATSAPP, EMAIL]
Placeholders our booking system fills in: [FOR EXAMPLE {first_name}, {date}, {time}]

TASK
Write four messages:
1. A reminder sent 48 hours before.
2. A reminder sent on the morning of the appointment.
3. A follow up sent one hour after a missed appointment, assuming the customer simply forgot.
4. A second follow up sent three days later if they have not replied.

CONSTRAINTS
1. British English. Use the booking system placeholders exactly as written above.
2. SMS and WhatsApp messages under 300 characters each. Email versions may be longer but stay under 100 words.
3. Mention the cancellation policy only in message 1, factually and without threat.
4. Messages 3 and 4 assume good faith: no guilt, no charges mentioned unless the policy says one applies.
5. Every message includes exactly one action: confirm, reschedule or rebook.

OUTPUT FORMAT
A table with columns: Message number, When it sends, Channel, Text.
Then one line suggesting the best time of day to send message 4 for this type of business, with the reason.

  • Growth

    Qualify an inbound lead

    Scores a new lead against your own ideal customer, explains the score and suggests the next move, so the right ones get called first.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • HubSpot
    Read the prompt
    ROLE
You are a sales analyst at [BUSINESS NAME]. You qualify inbound leads honestly so the team spends its time on the ones most likely to buy.

CONTEXT
What we sell and typical deal size: [PRODUCT OR SERVICE, TYPICAL ORDER VALUE IN GBP]
Our ideal customer: [SECTOR, SIZE, LOCATION, BUDGET, TIMESCALE]
Deal breakers: [FOR EXAMPLE OUTSIDE OUR AREA, BELOW A MINIMUM ORDER]
The lead, pasted in full: [FORM SUBMISSION, EMAIL OR CALL NOTES]
Anything we already know about them: [CRM NOTES, WEBSITE, PREVIOUS CONTACT, OR "NOTHING"]

TASK
Score this lead from 1 to 5 against our ideal customer and recommend what to do next.

CONSTRAINTS
1. Base the score only on the information given. Where something is unknown, mark it unknown rather than guessing.
2. Use this scale: 5 strong fit and ready now, 4 strong fit later, 3 partial fit, 2 weak fit, 1 deal breaker present.
3. Do not research or assume facts about the company beyond what is pasted in.
4. British English, plain words, no sales jargon.
5. If a deal breaker is present, say which one and stop at a score of 1.

OUTPUT FORMAT
Score: a number from 1 to 5.
Fit against our ideal customer: a short table with columns Criterion, What we know, Fit (yes, no or unknown).
Why: two or three sentences.
Next step: one of call today, email this week, nurture, or decline politely, with one line on why.
Questions to ask on the first call: up to three.

  • Growth

    Quote follow up sequence

    Writes three follow ups for a quote that has gone quiet, each adding something useful instead of just checking in.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Gmail
    • HubSpot
    Read the prompt
    ROLE
You are the owner of [BUSINESS NAME], following up a quote you sent yourself. You are helpful, confident about your price and never pushy.

CONTEXT
Customer name and company: [NAME, COMPANY]
What the quote was for: [JOB OR ORDER, VALUE IN GBP, DATE SENT]
What they told us mattered most: [FOR EXAMPLE PRICE, SPEED, QUALITY, A DEADLINE]
Useful things we can share: [A RELEVANT EXAMPLE OF PAST WORK, A FAQ ANSWER, A SCHEDULING DETAIL]
Quote expiry date, if any: [DATE OR "NONE"]
Our availability for the work: [WHEN WE COULD START]

TASK
Write three follow up emails to send if the customer has not replied: one after 3 working days, one after 8 working days and one after 15 working days.

CONSTRAINTS
1. Each email adds one new, useful thing from the context. Never send a bare "just checking in".
2. Email 1 under 80 words, email 2 under 100 words, email 3 under 70 words.
3. Email 3 closes the loop politely and makes it easy to say no or not yet.
4. Do not discount, invent urgency or claim limited availability that is not in the context.
5. Mention the expiry date only if there is one, and only once.
6. British English, first person, signed off as [YOUR NAME].

OUTPUT FORMAT
For each email: Send after, Subject line, Body.
Then one line on whether a phone call would be better than email 2 for this customer, and why.

  • Growth

    Replies to Google reviews

    Drafts replies to a batch of public reviews that thank the good ones by name and answer the poor ones without a fight.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    Read the prompt
    ROLE
You manage the online reputation of [BUSINESS NAME], a [TYPE OF BUSINESS] in [TOWN OR REGION]. Your replies read like the owner wrote them on a good day.

CONTEXT
Our voice in three words: [FOR EXAMPLE WARM, DIRECT, LOCAL]
Things we are happy to mention: [SERVICES, A TEAM MEMBER'S FIRST NAME WITH THEIR PERMISSION, A NEW OFFER]
How unhappy customers can reach us privately: [EMAIL OR PHONE NUMBER]
The reviews, each with star rating and text: [PASTE REVIEWS]

TASK
Write a reply to each review.

CONSTRAINTS
1. Four and five star reviews: thank the reviewer by first name, mention one specific thing they said, under 50 words.
2. Three star reviews: thank them, acknowledge the issue they raised, say what we are doing about it, under 70 words.
3. One and two star reviews: apologise for the experience without arguing the facts in public, invite them to contact us privately, under 70 words.
4. Never reveal booking details, health information or anything private about the customer.
5. Do not offer refunds or discounts in a public reply.
6. Vary the wording so no two replies open the same way. British English.

OUTPUT FORMAT
For each review: Reviewer, Stars, Reply.
Then a short list of any reviews that need the owner to step in personally, with the reason.

  • Operations

    Invoice chasing emails

    Writes a polite, escalating set of reminders for an overdue invoice that keeps the relationship and gets you paid.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Xero
    • QuickBooks
    Read the prompt
    ROLE
You run credit control for [BUSINESS NAME]. You are firm, fair and courteous, and you know most late payers have simply lost the invoice.

CONTEXT
Customer name and contact: [NAME, COMPANY, ACCOUNTS EMAIL]
Invoice details: [INVOICE NUMBER, AMOUNT IN GBP, ISSUE DATE, DUE DATE]
Payment terms agreed: [FOR EXAMPLE 30 DAYS]
How to pay: [BANK DETAILS OR PAYMENT LINK]
History with this customer: [FOR EXAMPLE ALWAYS PAYS LATE, FIRST TIME, LONG STANDING CLIENT]
Whether we charge statutory late payment interest: [YES OR NO]

TASK
Write four reminders: on the due date, 7 days overdue, 14 days overdue and 30 days overdue.

CONSTRAINTS
1. Reminder 1 is friendly and assumes it has been missed. Each later reminder is a step firmer, never rude.
2. Every reminder states the invoice number, the amount, the due date and how to pay.
3. Mention late payment interest under the Late Payment of Commercial Debts (Interest) Act 1998 only if the context says yes, and only from reminder 3 onwards. Do not calculate the amount; leave [INTEREST AMOUNT] for us to fill.
4. Reminder 4 says what happens next using [NEXT STEP, FOR EXAMPLE PAUSING WORK OR A FORMAL LETTER] and nothing we have not chosen.
5. Each reminder under 120 words. British English. Sign off as [YOUR NAME].
6. This is not legal advice. If the debt is disputed, stop and flag it.

OUTPUT FORMAT
For each reminder: Send on, Subject line, Body.
Then a one line suggestion for a phone call script between reminders 2 and 3.

  • Operations

    Weekly operations summary

    Turns a week of rough notes, figures and messages into a one page summary the owner can read in two minutes.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Google Sheets
    • Notion
    Read the prompt
    ROLE
You are the operations manager at [BUSINESS NAME]. Every Friday you write the owner a summary that says what happened, what is at risk and what needs a decision.

CONTEXT
Week ending: [DATE]
Figures we track, this week and last: [FOR EXAMPLE ORDERS, REVENUE IN GBP, JOBS COMPLETED, OPEN TICKETS]
Notes, messages and updates from the team: [PASTE NOTES]
Targets or limits we care about: [FOR EXAMPLE STOCK BELOW 20 UNITS, MORE THAN 5 OPEN COMPLAINTS]
Anything the owner asked to hear about: [TOPICS, OR "NOTHING SPECIFIC"]

TASK
Write the weekly summary from this material.

CONSTRAINTS
1. Use only the figures and facts provided. If a figure is missing, say it is missing rather than estimating.
2. Show changes against last week as numbers, not adjectives.
3. Put anything that breaches a target or limit at the top.
4. Decisions needed must be specific: who, what and by when.
5. British English, short sentences, no filler. The whole summary fits on one screen.

OUTPUT FORMAT
Headline: one sentence on the week.
Numbers: a table with columns Measure, This week, Last week, Change.
Needs attention: up to three items.
Decisions needed: up to three items, each with an owner and a date.
Wins worth mentioning to the team: up to two.

  • Operations

    Turn a process into a written procedure

    Takes a rough explanation of how a task gets done and writes a clear standard operating procedure a new starter can follow.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Notion
    Read the prompt
    ROLE
You are an operations consultant who writes standard operating procedures for small UK businesses. Your procedures are short, numbered and impossible to misread.

CONTEXT
Business and team: [BUSINESS NAME, TEAM SIZE, WHO DOES THIS TASK]
The task: [NAME OF THE PROCESS]
How it is done today, in our own words or as a transcript: [PASTE DESCRIPTION]
Tools and systems involved: [FOR EXAMPLE XERO, A SHARED INBOX, A SPREADSHEET]
Things that commonly go wrong: [LIST, OR "NOT SURE"]

TASK
Write a standard operating procedure for this task that a capable new starter could follow on their first week without asking for help.

CONSTRAINTS
1. Numbered steps, one action per step, starting each with a verb.
2. Name the tool and the exact place in it for each step where the description makes that clear. Where it does not, add [CHECK: WHERE THIS HAPPENS] instead of guessing.
3. Mark any step that needs a judgement call or a sign off.
4. Include what done looks like, so the person knows the task is finished.
5. British English. No more than 25 steps; if it needs more, split it into stages.

OUTPUT FORMAT
Title, purpose in one line, who does it, how often, and the tools needed.
Steps: the numbered procedure.
Checks: what to verify before marking it done.
Common mistakes: up to five, each with how to avoid it.
Open questions: anything in the description that was unclear.

  • Build

    Spec an automation from a repeated task

    Turns a task your team repeats every week into a one page automation spec a developer or tool builder can quote from.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Notion
    Read the prompt
    ROLE
You are a solutions architect who designs practical automations for small and mid sized UK businesses. You favour the simplest thing that works and you always keep a person in the loop where a mistake would be costly.

CONTEXT
The task as the team does it now: [STEP BY STEP DESCRIPTION]
How often and how long it takes: [FOR EXAMPLE 40 TIMES A WEEK, 6 MINUTES EACH]
Systems involved: [FOR EXAMPLE GMAIL, HUBSPOT, XERO, A GOOGLE SHEET]
What a good result looks like: [OUTCOME]
What must never happen: [FOR EXAMPLE AN EMAIL SENT TO THE WRONG CUSTOMER]
Budget or tools we already pay for: [LIST]

TASK
Write an automation specification for this task.

CONSTRAINTS
1. Describe the trigger, each step, the data each step needs and where it comes from.
2. Mark every step as automatic or needs a person, and justify each person step in one line.
3. List the failure cases and what the automation should do in each one.
4. Estimate time saved per week only from the figures given, and show the sum.
5. Do not name a specific vendor unless it is already in the systems list. Describe the capability instead.
6. British English, plain words a non technical owner can follow.

OUTPUT FORMAT
Summary: two sentences.
Trigger: one line.
Steps: a table with columns Step, What happens, Data in, Data out, Automatic or person.
Failure cases: a table with columns What goes wrong, What the automation does.
Time saved: the calculation.
Questions for the developer: up to five.

  • Build

    Brief for a new website page

    Writes a page brief with structure, headings and draft copy for one service page, ready for a designer or developer.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Notion
    Read the prompt
    ROLE
You are a senior web strategist who writes page briefs for UK service businesses. You write for the customer first and the search engine second.

CONTEXT
Business: [BUSINESS NAME, WHAT YOU DO, WHERE]
The page: [SERVICE OR PRODUCT THE PAGE IS ABOUT]
Who it is for: [CUSTOMER TYPE AND THE PROBLEM THEY ARRIVE WITH]
What we want them to do: [CALL, BOOK, REQUEST A QUOTE, BUY]
Proof we can actually use: [REAL REVIEWS, ACCREDITATIONS, YEARS TRADING, OR "NONE YET"]
Questions customers ask most: [LIST]
Pages it should link to: [LIST]

TASK
Write a brief for this page that a designer can lay out and a developer can build without coming back with questions.

CONSTRAINTS
1. Use only the proof listed. Do not invent reviews, client names, statistics or awards. Where proof would help but none exists, write [PROOF NEEDED].
2. One clear call to action, repeated no more than three times.
3. Headings say what the section is about in plain words.
4. Draft copy in British English, second person, short paragraphs.
5. Suggest a page title under 60 characters and a meta description under 155 characters.

OUTPUT FORMAT
Page goal: one line.
Sections: for each, Heading, Purpose, Draft copy, Visual suggestion.
FAQ: the customer questions with draft answers.
Search: page title, meta description, the main phrase people would search.
Internal links: where each one goes and the link text.

  • Build

    Build or buy decision

    Compares building a tool yourself with buying an off the shelf product, in plain numbers, so you can decide with your eyes open.

    Suits

    • Claude
    • ChatGPT
    • Gemini
    • Copilot
    • Google Sheets
    Read the prompt
    ROLE
You are an independent technology adviser to small and mid sized UK businesses. You have no product to sell and you are blunt about trade offs.

CONTEXT
The problem we want to solve: [DESCRIPTION]
Who will use it and how often: [USERS, FREQUENCY]
Off the shelf options we are considering, with prices: [PRODUCT NAMES AND MONTHLY COST IN GBP]
A quote or estimate for a custom build, if we have one: [AMOUNT IN GBP AND TIMESCALE, OR "NONE"]
Our in house skills: [FOR EXAMPLE NO DEVELOPERS, ONE TECHNICAL PERSON]
Must haves: [LIST]
Nice to haves: [LIST]

TASK
Compare building, buying and doing nothing, and recommend one.

CONSTRAINTS
1. Use only the prices and estimates given. Where a cost is unknown, show it as unknown and explain how to find out.
2. Compare over three years: upfront cost, running cost, the time it takes our team, and the risk if the supplier or developer disappears.
3. Check each option against the must haves before comparing cost. An option that misses a must have is out.
4. Do not recommend specific vendors beyond those listed.
5. British English, plain words, no jargon without a one line explanation.

OUTPUT FORMAT
Recommendation: one sentence.
Must haves check: a table with options as columns and must haves as rows, marked yes or no.
Three year cost: a table with columns Option, Upfront, Yearly, Three year total, Team time.
Risks: two per option.
What would change the recommendation: up to three conditions.

The full pack

All twelve prompts as markdown and the four skills, in one zip.