The daily-ops prompt pack
Ten copy-paste prompts for the admin that eats a small-business week: review replies, estimate follow-ups, no-show reminders, invoice chasers, job posts. They work in ChatGPT or Claude — free tiers included. Fill in the [BRACKETS], paste, done.
Two rules make these work better than the prompts in most paid courses: every prompt feeds the AI your real material (past replies, real transcripts, your actual perks) instead of letting it invent, and every prompt carries the guardrail that keeps it from embarrassing you. The guardrails are half the value.
Prompt 1: The five-star review reply
You write Google review replies for [BUSINESS NAME], a [TYPE OF BUSINESS] in [CITY]. Reply to this 5-star review in my voice: warm, specific, 2–3 sentences. Rules: thank them by first name, mention ONE specific detail from their review so it doesn't read templated, and invite them back without offering a discount. Here are two of my past replies — vary your sentence openers from these so we never sound copy-pasted: [PASTE 2 PAST REPLIES] Review: [PASTE REVIEW]
Why it works: Replies that echo one concrete detail from the review read as human and rank the review higher in 'most relevant'. Feeding your past replies keeps a consistent voice without repetition.
Guardrail: No discounts in public replies — it trains future reviewers to fish for them.
Prompt 2: The negative review reply (with the healthcare-safe variant)
You handle a negative review for [BUSINESS NAME]. Write a reply that: 1) opens by acknowledging their specific complaint — never "we're sorry you feel that way", 2) states one concrete thing we're doing about it, 3) moves the conversation offline with a named person and a direct phone or email, 4) stays under 80 words and never argues facts in public. IF WE ARE A HEALTHCARE PRACTICE: do NOT confirm the reviewer is or was a patient. No reference to their visit, treatment, dates, or billing — write as if replying to a stranger. Shape: "We take feedback like this seriously. Please contact [NAME] at [PHONE] so we can look into it directly." Review: [PASTE REVIEW]
Why it works: The reply isn't for the reviewer — it's for the hundred people who read it later. Calm + concrete beats defensive every time.
Guardrail: Confirming someone is a patient in a public reply is a HIPAA violation that has cost practices five-figure settlements. The variant exists because of that sentence.
Prompt 3: The estimate follow-up ladder
Write 3 follow-up emails for a quote we sent to [FIRST NAME] for [JOB TYPE], roughly [PRICE RANGE]. Email 1 (2 days after the quote): share one useful detail we didn't put in the quote — a timing consideration, a material choice, a permit note — and ask one easy question. Not a discount. Email 2 (day 6): a short, true story of a similar job going well, then a soft close. Email 3 (day 12): a polite "closing the file" note that leaves the door open and asks what held them back. Each under 90 words, subject lines under 6 words, plain text, signed [YOUR NAME]. Banned phrases: "just checking in", "touching base", "circling back".
Why it works: Most estimates die from silence, not rejection. Three structured touches recover a real fraction of them, and the 'closing the file' email gets replies the first two don't.
Guardrail: Never discount unasked — it reprices your work and tells them the first number was padded.
Prompt 4: The no-show reducer
Write 2 SMS messages for an appointment on [DATE/TIME] at [BUSINESS NAME]: 1) Sent right after booking: confirm the slot, one line on what to bring or expect, then "Reply C to confirm or R to reschedule." 2) Sent 24 hours before: friendly reminder with the address and one practical note (parking, arrival time). Both under 160 characters so they fit one SMS segment. No links unless I gave you [BOOKING LINK]. No emojis.
Why it works: A confirm-or-reschedule choice converts silent no-shows into reschedules you can fill. The 24-hour reminder alone typically cuts no-shows by a third.
Guardrail: 160 characters = one SMS segment = cheaper sends and no mid-message truncation on old phones.
Prompt 5: The after-hours voicemail triage
Here are last night's voicemail transcripts from my phone system. For each one: - classify urgency: NOW / TODAY / THIS WEEK, - pull out the name, number, and what they want, in one line, - flag anything that sounds like an emergency, an existing-customer complaint, or a new-customer sales inquiry, - then give me a callback order for 8am with one sentence of reasoning each. Transcripts: [PASTE TRANSCRIPTS]
Why it works: Ten voicemails take 15 minutes to listen to and 30 seconds to read triaged. New-customer inquiries get called first before they call your competitor.
Guardrail: AI triage is a sorting aid, not a dispatcher — anything flagged 'emergency' still gets your human judgment before you trust the label.
Prompt 6: The job post that attracts
Write a job post for a [ROLE] at [BUSINESS NAME] in [CITY]. Pay: [RANGE]. Schedule: [SHIFT/DAYS]. Structure: - One honest opening line about what the job actually is day to day. No "fast-paced environment". - 5 bullets of real duties. - 3 bullets on why this job beats the same role elsewhere, using only these real perks: [YOUR REAL PERKS]. - Pay stated plainly. Applications in one step: [HOW TO APPLY]. 8th-grade reading level. Banned words: rockstar, ninja, family, wear-many-hats, self-starter.
Why it works: Posts that state pay and actual duties get more applicants and fewer ghosted interviews. The 'why here' bullets are what separates you from the identical listing above yours.
Guardrail: Only real perks go in — invented culture claims cost you the hire in week two.
Prompt 7: The Google Business Profile weekly post
Write this week's Google Business Profile post for [BUSINESS NAME]. Topic: [WHAT HAPPENED THIS WEEK — a job you finished, a question three customers asked, a seasonal reminder]. 100–150 words. Start with the useful fact, not "We're excited to announce". One clear next step (call, book, or stop by). Written like a person, no hashtags. Then suggest one photo I could take with my phone to attach to it.
Why it works: A weekly GBP post is the cheapest local-visibility habit that exists — profiles with fresh posts and photos win the map pack ties.
Guardrail: The topic comes from your actual week. Generic AI posts about 'the importance of maintenance' are visible filler and customers can smell them.
Prompt 8: The invoice chaser ladder
Write 3 payment-reminder emails for invoice #[NUMBER], $[AMOUNT], due [DATE], sent to [CLIENT NAME]: 1) 3 days past due: assume good faith. Resend the payment link and instructions — "resending in case it got buried." No apology for asking. 2) 14 days: firmer. Restate the terms, ask directly if there's a problem with the work (give them an out that isn't silence), offer a 10-minute call. 3) 30 days: final professional notice. State the next step plainly — [LATE FEE / WORK PAUSES / COLLECTIONS, per your contract] — without threats or heat. Each under 80 words.
Why it works: The day-14 'is there a problem with the work?' question is the one that gets silent clients to finally answer — silence usually hides a complaint, not an empty bank account.
Guardrail: Never apologize for asking to be paid, and never state a consequence (late fee, collections) that isn't actually in your contract.
Prompt 9: The FAQ page generator
Here are the 10 questions customers actually ask us on the phone, with my rough answers: [PASTE 10 Q&A PAIRS] Turn them into a website FAQ page: - Keep my facts EXACTLY as given — change nothing factual, invent nothing. - Tighten each answer to 2–4 sentences at an 8th-grade reading level. - Order them by how early in the buying decision each question comes. - Then list 3 more questions you'd EXPECT customers like mine to ask — questions only, leave the answers blank for me to fill in.
Why it works: Your phone log is the best FAQ research that exists, and a good FAQ page is what AI search engines quote when someone asks about businesses like yours.
Guardrail: The AI never invents answers about your business — blanks stay blank until you fill them. One hallucinated hour-of-operation costs real trust.
Prompt 10: The weekly schedule sanity check
Here is next week's schedule — jobs/appointments with times and locations: [PASTE SCHEDULE] Check it like a dispatcher: - flag double-bookings and gaps too short to be real, - estimate drive time between consecutive jobs in [CITY] traffic and flag the impossible ones, - tell me which day is overloaded and what you'd move where, - list every job missing info (no address, no phone, no scope). Output: a short priority-ordered list of problems, each with its fix. Don't restate the whole schedule back to me.
Why it works: Five minutes on Sunday catches the Tuesday that was never going to work. The 'missing info' list alone prevents the worst jobsite surprises.
Guardrail: Drive-time estimates are estimates — trust them for 'impossible', verify them for 'tight'.
Next: run the missed-call cost calculator — the 30-second math on what your unanswered phone costs, and the three fixes compared honestly.
Get new chapters by email
Optional — everything here stays free and ungated either way. One email when a chapter publishes, nothing else.