Give an AI chat your services, prices and how many jobs you can fit each week, and ask for a dated eight-week calendar: a Google Business Profile post, a social caption, a message to past customers and a review ask for each week. Edit every draft for accuracy and local detail before posting, and keep safety wording factual.
The calendar below starts in mid-September. If your cold season starts earlier or later, keep the order and move every date by the same number of weeks. Capacity comes before copy: an offer should move demand into the weeks you would otherwise leave empty, not fill weeks that are already full.
Work out your slots before you write an offer
Marketing a chimney sweep is odd, because demand arrives in a rush and the supply is one person's day. Count first, write second. A sweep and a helper completing six jobs a day, five days a week, have 30 slots a week (illustrative figures), or 240 across the eight weeks in the table below. Hold back a fifth for call-backs, emergencies and bad weather and 192 are bookable.
Now count the demand you already have. Suppose 310 past customers are due, meaning their last sweep was ten to fourteen months ago. If six in ten rebook, which is a planning assumption to replace with last year's figure, that is 186 jobs: almost the whole autumn. So the question for this season is not "how do I get more customers" but "how do I stop the rush landing in two weeks". That changes what an offer is for.
| Week | Bookable slots | Booked by 15 September (illustrative) | Free | What the marketing should do |
|---|---|---|---|---|
| 15 to 21 September | 24 | 6 | 18 | Fill: first reminder wave, early-booking offer |
| 22 to 28 September | 24 | 4 | 20 | Fill: same offer, reminder follow-up |
| 29 September to 5 October | 24 | 2 | 22 | Fill: last week of the offer |
| 6 to 12 October | 24 | 12 | 12 | Hold: no discount, loyal customers pick first |
| 13 to 19 October | 24 | 14 | 10 | Protect: busiest week, waiting list not offers |
| 20 to 26 October | 24 | 10 | 14 | Protect: waiting list |
| 27 October to 2 November | 24 | 8 | 16 | Fill gently: neighbour offer |
| 3 to 9 November | 24 | 3 | 21 | Close: last slots, thanks, reviews |
Read the table the way the AI should. Weeks one to three have 60 free slots between them (18 + 20 + 22) while the week of 13 October has 10. An offer belongs in the first three weeks and nowhere near the fifth. Across all eight weeks 59 slots are taken and 133 are free, against roughly 127 more rebookings you expect from past customers, so the aim is to smooth the rush, not to find new customers. Giving the AI this table is what stops it writing "book now, slots filling fast" in a week with 20 free.

The Complete Excel Course with AI Integration
From formulas and pivot tables to Power Query, DAX, VBA and AI with Copilot, ChatGPT and Claude — hands-on from the first lesson.
By Sagnik Bhattacharya and Virginia Thorn, Primetime Emmy Award winner
Buy nowAn eight-week calendar with dates
Every row below is a job for the AI to draft from facts you supply, and a job for you to edit. The right-hand column keeps the slots table in view, so each week's posts push in the direction the diary needs.
| Dates | Google Business Profile | Social caption | Customer message | Aim |
|---|---|---|---|---|
| 15 to 21 Sep | Update: autumn booking is open, with the next free date and the Book button | What a sweep includes, with one clear photo of your kit | Reminder wave 1 to customers due | Fill |
| 22 to 28 Sep | Offer post: early-booking offer with a title and an end date of 5 October | The offer in one line and how to book | Wave 2 to non-responders, offer included | Fill |
| 29 Sep to 5 Oct | Update: a before-and-after photo pair from a real job, explained plainly | The same photos, with the customer's permission and no address | Last offer reminder on 3 October | Fill |
| 6 to 12 Oct | Update: a first-fire checklist the owner can do alone | The checklist as three short points | Message to repeat customers: first pick of slots | Hold |
| 13 to 19 Oct | Update: fully booked this week, next slots from 26 October (only if true) | Invitation to the waiting list | Waiting-list message | Protect |
| 20 to 26 Oct | Update: pre-winter Q&A on what to ask your sweep about fuel and appliance | One question answered per post | Replies to enquiries only | Protect |
| 27 Oct to 2 Nov | Offer post: neighbour offer, ending 9 November | The neighbour offer | Message asking customers to tell a neighbour | Fill gently |
| 3 to 9 Nov | Update: thanks, plus last slots with dates | Thanks and last slots | Final reminder to anyone still due | Close |
Three Google features make this practical. The posts screen has three types (Update, Offer and Event), and Google's help page asks for a descriptive title and start and end dates, which an offer needs anyway. The Schedule this post switch publishes a post at a set date and time, so a month of drafts can be loaded in one sitting. And posts older than six months are archived unless they carry a date range, which is why the offers above have end dates and the updates are written to be seasonal. Leave phone numbers out of the post text: Google's posts policy says it may remove posts carrying unverified contact details, phone numbers included, and suggests a Call now button, which uses the verified number on your profile.
Block one hour each Sunday for the week ahead: ten minutes for the AI to draft, twenty to edit against your facts, ten to schedule the posts, twenty for the customer message. Google advises against auto-generated post content, so use the AI to produce drafts and then make each post your own before it goes out, posted under your own login. If you want the weekly routine itself explained, writing Google Business Profile posts with AI every week goes through it.
One prompt that builds the whole calendar from your slots table
The table above is the input that matters, so paste it into the prompt rather than describing it. Keep this prompt in a ChatGPT Project or a Claude Project along with your price list and the exact wording of any qualification you hold, so every season starts from the same rules.
You are helping a chimney sweep plan autumn marketing. Use only the facts below. If a fact is missing, ask me instead of guessing.
FACTS
Services and prices: [list]
Bookable slots and slots already booked, by week: [paste the table]
Past customers due this autumn: [number]
Offer limit: up to $[amount] off a job, only in weeks marked Fill.
Qualifications I hold, in exact words: [list, or none]
TASK
For each week from [first date] to [last date], write:
1. One Google Business Profile post. Say whether it is an Update, Offer or Event; offers need a title and an end date.
2. One social caption.
3. One message to past customers, only where my table shows one.
4. The aim for the week, copied from my table.
RULES
No claim that sweeping prevents fires or makes anything safe. No statistics. No phone numbers in posts. Never say certified, qualified or approved beyond the exact words I gave. No urgency the table does not support. Each post under 120 words.
Ask for the first four weeks and then the last four, because long outputs drift. Check three things in what comes back: the dates (an offer must end before the week it is meant to stop), the aim column (no discount in a Hold or Protect week) and the safety rules. The first draft is usually good at structure and loose on those three, and fixing them takes ten minutes against the hour it would take to write from nothing.
Turning one real job into one Google post
Posts built from a real job beat anything a generic prompt produces, because the details cannot be copied by a competitor. Photograph the work (with permission, with no house number visible), jot four facts, and give them to the AI with firm limits.
Write a Google Business Profile update for a chimney sweep, 80 to 120 words.
Use only these facts:
- Job: sweep of a wood-burning stove flue, 1930s house.
- Photo shows a heavy deposit of soot and tar on the flue walls before sweeping.
- Next free booking date: [date].
Rules: no phone numbers; no claim that sweeping prevents fires or makes anything safe; no statistics; do not say certified, qualified or approved; no exclamation marks; end by pointing to the Book button.
A typical first draft (illustrative) reads: "Don't let your chimney become a fire hazard this winter! Our certified experts will make your home 100% safe. Call now to book!" It breaks four rules at once: fear, a certification claim you did not give it, an absolute promise and a call to phone. Rerun with the rules restated and you get something close to this, which only needs your own edit:
This stove flue was swept yesterday. The photo shows the soot and tar that had built up on the flue walls since the last sweep. A sweep removes that deposit, and we look over the parts of the flue we can reach so we can tell you if anything needs a closer look. If you burn wood or coal, check how often your appliance's maker or your trade body says it needs sweeping. We have slots from [date]: use the Book button on this profile.
What you still fix by hand: the "yesterday" so it matches reality, a mention of your real qualification if you hold one (name the actual body or scheme, never just "certified"), and the sentence about the maker's advice if the AI paraphrased it badly. Ten seconds of reading catches each of these, and none can be skipped, because a post is public and dated.
Offer wording that is still true when it is read
An offer is a promise with a date on it. Give the AI the terms and make it repeat them back before it writes a word of copy: what is included, the price, the end date, who qualifies and how many slots exist. Then check five wordings against what you can honour.
- Early booking. "$10 off any sweep booked and completed by 5 October." Dated, specific and tied to the weeks you need to fill. Drop "limited time" unless the date appears next to it.
- Sweep plus camera check. "Sweep and a camera look at the flue together for $[x], instead of $[y] separately." Only run it if you offer the camera check and the saving is real; otherwise "free inspection" becomes a claim you cannot support.
- Neighbour pair. "Book on the same day as a neighbour and you each save $10." Fair to both sides, and it saves you a drive. Say how the pairing works, so nobody is surprised by the small print.
- First pick. "Customers who booked last autumn can choose their slot until 12 October." This is priority, not a discount, and it rewards loyalty in the weeks you want to protect.
- Waiting list. "Fully booked until 26 October. Join the list and we'll text if a slot opens." Honest scarcity: it is true, so it works, and it costs nothing.
Things to cut from any AI draft: "last chance" repeated every week, "only 3 slots left" unless there are three, "free inspection" when the visit is a visual check, and "guaranteed safe" in any form. Also never write "leave us a review for $10 off". Google prohibits offering incentives for reviews, so keep the review ask and the offer in different messages, and never mention one in the other.
Honest safety wording: what a sweep does and does not do
Safety is why customers book, and it is the easiest place to overclaim. Keep a short table next to the prompt and tell the AI to use the left column and never the right.
| Say | Do not say | Why |
|---|---|---|
| "A sweep removes soot and tar deposits from the flue." | "A sweep prevents chimney fires." | The first describes your work. The second promises an outcome you do not control |
| "We check the parts of the flue we can see and tell you if anything needs a closer look." | "Full safety inspection." | Say the scope you actually cover; a camera survey is a separate service |
| "Ask how often your appliance and fuel need sweeping." | "Everyone needs a sweep twice a year." | Intervals depend on fuel and appliance; quote your trade body or the maker |
| "A sweep does not replace a working carbon monoxide alarm." | "Get swept and you're safe from carbon monoxide." | The alarm is a separate safeguard and the post should say so |
| "We found damage to the liner and recommend a repair. Here is the photo." | "Your chimney is dangerous." | Report the finding and the next step, not alarm |
| "We hold [named qualification or scheme]." | "Fully certified" with no detail | A claim a customer can check is worth more than a badge word |
Never put a statistic in a post unless you can name its source in the same post. This is the quickest way to get a fact wrong in public, and AI drafts reach for numbers readily. Put "no statistics" in the prompt rules, as the example above does. When you write about what the camera found, turning camera findings into plain English shows how to describe damage without scaring the customer or hiding it.
The message to past customers, in three waves
Past customers are the cheapest autumn marketing there is, because they already trust you and your records say who is due. Filter the list by last sweep date (ten to fourteen months ago), and send in three waves rather than once, so the people who missed the first message still get a reminder without being nagged.
- Wave 1, 15 September: a plain reminder with your next free dates and one way to book.
- Wave 2, 22 September: to those who have not booked or replied, with the early-booking offer and its end date.
- Wave 3, 3 October: a short last reminder before the offer ends, then stop. Nobody should get a fourth message.
Hi [first name], it's [your name], your chimney sweep. Your last sweep was in [month and year], so you're due before the cold weather. I have slots from [date]. Reply with a day that suits, or book here: [link]. [Opt-out wording your messaging service requires]
As a planning sum rather than a forecast: if one in four of the 310 due customers books in direct reply to the three waves, rather than ringing in later of their own accord, that is about 78 jobs, and at $95 a sweep it is $7,410 from three short messages. Replace the one in four with last year's own response rate once you have it, and the $95 with your price. If you already send reminders by software, chimney sweep software for reminders and online booking shows what can be automated so the three waves run themselves.
Review asks that stay inside Google's rules
Reviews are the fastest proof a sweep can post, and an autumn rush is the best moment to collect them: you will do dozens of jobs in weeks. Ask on the day, by text, with the direct review link from your Business Profile (Google's own help pages describe how to share a link or QR code), and ask everyone. Google's policy prohibits incentives for reviews and prohibits selectively asking only the customers likely to be positive, so the ask goes to every customer, with no reward attached.
Thanks for having me today, [first name]. If you have a minute, a Google review helps other households find a sweep they can trust: [your review link]. Thanks, [your name].
Send it once. If you want a single reminder, make it five days later and make it shorter. Do not offer a discount, a free extra or a prize, and do not write "we only ask happy customers".
When a negative review does arrive, a reply inside a day or two is worth more than a perfect one a week later, and Google's own tips page lists replying in a timely manner under the advice for negative reviews. Reply calmly, thank the customer, say what you will do, and take the details offline: "I'm sorry the visit didn't go as you expected. Please ring me on the number on this profile so I can look into it." Google says replies usually take up to 10 minutes to appear, occasionally longer. The tutorial on getting more reviews after every job with AI follow-ups covers the follow-up routine in more depth.
A reply bank for the questions that follow the posts
Posts bring messages, and the same six questions arrive every autumn. Write the answers once, from your own facts, and keep them where an AI chat can draft replies in your voice. The right-hand column is the check before you send.
| Question | Answer to write, with your facts | Check |
|---|---|---|
| How much is a sweep? | "A sweep is $[price] and includes [what]. A camera check is $[price] extra." | Say what is and is not included |
| How long will you be? | "About [x] minutes for a stove and [y] for an open fire. I'll give you an arrival window." | Times you can keep, not best cases |
| How messy is it? | "I use dust sheets and [your equipment], and leave the hearth as I found it." | Only promise what you do |
| I burn wood. How often? | "It depends on your appliance and what you burn. Your stove maker or trade body gives the interval; tell me what you burn and I'll say what applies." | No made-up interval |
| Does a sweep cover my carbon monoxide alarm? | "No. A sweep doesn't replace one, so please test yours when you light the first fire." | Always say this |
| Can you come on a Saturday? | "[Your weekend policy and any extra fee.]" | The fee is stated up front |
Give the AI the table and one rule: draft a reply from these answers only, and if the question is not covered, say so and propose a question for me to answer. That keeps the assistant from improvising a price or a safety claim at nine in the evening, and it shows you which new questions deserve a row.
Reading the results in mid-November
A calendar is only worth repeating if you can see what worked. Four numbers are enough, and you can collect all of them without a dashboard.
| Number | How to get it | What it tells you |
|---|---|---|
| Jobs by source | Ask "how did you hear about us?" at every booking and tick one of: reminder, Google, social, neighbour, other | Which channel earned its hour |
| Fill rate by week | Booked slots divided by bookable slots, compared with the table you made in September | Whether the offers moved demand into the quiet weeks |
| Reviews gained | Count of new reviews against jobs completed | Whether the ask went to everyone |
| Post actions | The profile's performance screen, checked monthly because its search terms refresh monthly | Whether the Book and Call buttons were used |
Write the figures next to this year's calendar and keep it. Next September the AI can start from the real fill rates, the offers that worked and the wording you edited out, and the whole exercise becomes a thirty-minute refresh instead of a fresh blank page. The most useful single change to make for next year is nearly always to move the first reminder wave a week earlier.
Further reads
- AI Chatbots for Websites: What a Chimney Sweep Should Let Them Handle — What a sweep should let a website chatbot answer.
- AI Marketing for HVAC: A Worked Spring and Autumn Tune-Up Campaign — Another seasonal service campaign, worked end to end.
- AI Marketing for Plumbers: A Worked 12-Month Posts and Offers Calendar — A twelve-month posts and offers calendar to borrow from.
- How to Get More Google Reviews With Automated Review Requests — Automate the review ask once the manual one works.
- How to Optimise Your Google Business Profile With AI — Tidy the profile your posts appear on.
- AI Tools and AI Development: The Complete 2026 Guide — the AI hub, including every tutorial in the AI-for-business series.
Sources: Google Business Profile Help pages on creating posts, the posts content policy, managing reviews and tips for getting reviews (read November 2026). No statistics are quoted, and every price, date and booking figure in the examples is illustrative.