A garden maintenance firm gets perhaps six enquiries a week in January. By the second week of April it gets sixty, the owner is up a ladder from seven until dusk, and the inbox has quietly become a place where good customers go to be ignored.
That is the seasonal business problem in one picture. The work arrives in a lump, the people who could answer enquiries are busy doing the work, and every unanswered message in peak season is a customer who books someone else and remembers that next year too.
An AI receptionist for a seasonal business does not create extra capacity on the tools. What it can do is stop the front door from falling apart when the diary is full, and keep enquiries organised well enough that you can act on them in the evening instead of losing them.
The year has four phases, and each needs different wording
Most businesses set up a website assistant once and leave it. Seasonal firms cannot, because the right answer to "can you come next week" changes completely between March and June.
| Phase | What visitors ask | What the assistant should do |
|---|---|---|
| Pre-season build-up | Prices, availability, whether you do a specific job | Answer from current content, capture details early, mention that spring slots fill quickly if that is true |
| Peak | When can you come, can you squeeze me in | State the honest lead time, offer the waitlist, capture flexible dates |
| Tail end | Last-minute jobs, next year's bookings | Say what is still possible this season, take next-season enquiries without false urgency |
| Off-season | Maintenance, small jobs, quotes for next year | Explain what you do in winter, if anything, and collect interest for later |
Write one short block of content for each phase. When the phase changes, swap the block. It takes ten minutes and prevents the assistant from cheerfully promising June availability in May.
Saying 'fully booked' without losing the customer
The worst peak season reply is no reply. The second worst is a vague "we'll be in touch", which the customer reads as "we won't". A clear lead time is better than both, even when the lead time is bad.
Here is the kind of exchange that works when the diary is full:
Visitor: Hi, can someone come and cut back a hedge next week? It's quite overgrown.
Assistant: We're fully booked for new hedge work until the week of 16 June. I can put you on our waiting list, and if a slot opens earlier because of a cancellation, the team will contact you. Could I take your postcode, a rough length of hedge and which days you could do at short notice?
Visitor: SW18, about 20 metres, any weekday really.
Assistant: Thanks. I've noted that. What's the best phone number or email for the team to reach you?
Two things are doing the work there. The date is specific, so the visitor can decide for themselves whether to wait. And the question about short-notice days turns a disappointed visitor into someone you can call the moment a job cancels.
The assistant can only say that date if you have written it down. SpideyChat answers from the content you give it and does not read your diary, so the lead time needs updating by hand whenever it moves. Put a reminder in your calendar for every Monday of peak season.
Build a waitlist you can actually use
A waiting list that is just a pile of names is almost useless when a Tuesday job falls through at 8am. You need to know who is nearby, who is flexible and whose job fits the gap.
Ask the assistant to collect these, and only these:
- Location. A postcode or town, so you can fill a cancellation with someone on the same route.
- Job size in their words. "Twenty metres of hedge" or "two-bedroom flat" is enough to judge whether it fits a slot.
- Flexibility. Which days, and whether they can take a call the same morning.
- Contact method. One number or email they will actually answer.
Turn on lead capture so each enquiry arrives with those details attached. If you work from a spreadsheet, a webhook can drop each lead into a row, which makes sorting by postcode on a busy morning far quicker than scrolling an inbox. The webhook guide covers the setup.
Resist asking for more. Every extra question in peak season lowers the number of people who finish the conversation, and you only need enough to make a phone call.
A worked example you can redo with your own numbers
This is an illustration, not a benchmark. Replace every figure with yours.
Say a pool servicing company gets 45 website enquiries a week in peak season. The owner reckons about a third arrive in the evening or at weekends, and in a normal year roughly half of those never get a reply in time because everyone is out on jobs.
- Evening and weekend enquiries: 45 × 1/3 = 15 a week
- Previously lost for lack of reply: 15 × 1/2 = 7.5 a week
- Across a 16-week season: 7.5 × 16 = 120 enquiries
If even one in five of those would have booked, that is 24 jobs. At an average job value of $180, that is $4,320 of work in one season that was walking away because nobody answered. Against that, a Pro plan at $59 a month for four peak months is $236.
The honest caveat: you still need the capacity to do the work, or at least a waitlist that fills cancellations. Capturing enquiries you can never serve just moves the disappointment later. The ROI calculator lets you test different assumptions quickly.
What the quiet months are for
Off-season is when a seasonal assistant gets better. Peak season is too busy for anything but reacting.
- Open the unanswered questions from last season and group them. You will find the same five or six gaps asked dozens of times.
- Write a short answer for each and add it as a Q&A pair or a page on your website.
- Re-crawl the site so the assistant picks up anything you changed.
- Read twenty peak season conversations end to end and note where visitors dropped off. A long question sequence is the usual culprit.
- Draft next season's content block now, with a placeholder for the lead time.
This is also when to decide on your plan. Some seasonal firms run the free plan through winter, which covers 100 messages a month, and move to Starter or Pro a few weeks before the rush. The pricing page lists what each tier includes.
Before your next busy season starts
Pick the date, roughly six weeks before your usual peak, and put three jobs in the diary for that week. Write the peak season content block with your realistic lead time. Set up the waitlist questions and send one test enquiry through to check it lands where you will see it.
Then choose who updates the lead time each Monday once things get hectic. If that person is you, keep the update to one sentence, because in week six of peak season you will not do anything longer. For the bigger picture on covering evenings without hiring, the after-hours playbook is worth a read before the rush begins.