Key takeaways
- Demand spikes are predictable in type if not in date: first cold nights for heating, named storms for roofers, hot spells for wasps and gardens.
- Write the plan before the spike: what triggers it, who answers, which calls jump the queue and what everyone else is told.
- Use layers: main line, a second person, a call-back promise and an answering service or AI employee for the overflow.
- Hold honest scripts for the calls you cannot take this week, and keep a list so nobody is forgotten.
- Review missed calls and call-backs after every spike, and adjust the triggers for next time.
Spikes are predictable, even when the date is not
Every home services trade has its rush. Heating engineers get it on the first properly cold mornings of autumn, when boilers that have sat idle all summer refuse to fire. Roofers and gutter specialists get it the day after high winds. Pest controllers get it in the first warm weeks of summer, gardeners in spring, and electricians after storms that bring down lines or flood sockets. You cannot know the date, but you can know the shape.
Storms are a good example. The Met Office names storms on a list that runs from early September to late August, timed to the start of autumn when low-pressure systems become more likely[1]. There were four named storms in the 2025/26 season[2], and the 2026-27 season started early, with Storm Austen named on 20 October 2026 and Storm Boelo two days later[3]. A roofer who watches the warnings can see a spike coming days ahead.
Emergencies also tend to arrive at the worst time for a small office. Fire services in England, for instance, received over half of their incident calls in the year to March 2026 between 15:00 and 22:00, peaking from 17:00 to 21:00, largely after a typical working day[4]. Domestic breakdowns follow a similar human rhythm: people discover the cold radiator or the dripping ceiling when they get home.
- Called in between 15:00 and 22:00 50%
Source: Ministry of Housing, Communities and Local Government (GOV.UK), 2026[4]
Show the data
| Item | Value |
|---|---|
| Called in between 15:00 and 22:00 | 50% |
Set the triggers
An overflow plan that starts "when it gets busy" never starts. Pick specific triggers that anyone in the business can recognise, and agree that the plan switches on automatically when one is met.
- A forecast: a Met Office wind or cold weather warning for your area, or the first forecast frost after a mild spell.
- A queue: more than a set number of unanswered calls or voicemails in an hour.
- A diary: no free emergency slot left for the next working day.
- A season: a fixed date range, such as the first fortnight of October for heating firms, when cover is booked in advance anyway.
Write the triggers at the top of the plan and put the plan where everyone can find it, including family members who sometimes cover the phone.
Prepare before the season starts
Most of the work in an overflow plan happens weeks before the first busy day. A short preparation list, done once a year, means the plan can switch on in minutes rather than hours.
- Book cover in advance for the weeks you know will be busy, even if it is only a few mornings.
- Update the voicemail and website banner wording now, ready to switch on, rather than writing it in a rush.
- Check stock of the parts that fail most in your rush, such as pumps, fans, thermocouples or ridge tiles.
- Contact your service customers early so routine work is done before the spike, not during it.
- Agree with a trusted local firm which overflow jobs you might pass to each other, and how.
Build the layers of cover
Overflow works best in layers, each catching what the one before misses. Small firms rarely need all of them; choose the ones that fit your size and budget.
| Layer | Who or what | Best for | Watch out for |
|---|---|---|---|
| Main line | Office person or owner | Every call they can reach | Long calls blocking the line during peaks |
| Second person | Part-timer, partner or engineer on light duties | Peak hours only | Needs the same scripts and job notes format |
| Call-back promise | Voicemail and text with a time | Non-urgent calls | Only works if call-backs actually happen on time |
| Answering service or AI employee | External, by the hour or always on | Evenings, weekends, peaks | Must follow your triage rules and hand over urgent calls |
| Partner firm | A trusted local business | Jobs you cannot reach this week | Agree terms and customer ownership in advance |
If you use an outside service or an AI employee such as Ava for the overflow, give it the same triage order and the same holding wording as your office, so callers get one consistent answer however their call is routed.
Triage order for the busy week
When demand outstrips capacity, the order in which you book matters more than the speed at which you answer. Agree it in advance so the office does not have to make judgement calls under pressure.
Danger to people
Gas smell, carbon monoxide symptoms, exposed live wiring, a roof at risk of falling. Give safety advice and the emergency number, then act as your on-call rules say.
Vulnerable occupants without heat, power or shelter
Older, ill or disabled customers, and homes with babies, with no safe alternative.
Active damage
Water coming in, a leak that will spread, a blocked drain backing up.
Existing customers with booked work
Protect the jobs already in the diary wherever you can, and tell them early if anything has to move.
New non-urgent enquiries
Take full details and offer the first realistic date, or a call-back when the rush eases.
Decide in advance which planned jobs can move in a spike (often quotes and minor repairs) and which cannot (installs with materials delivered, jobs for vulnerable customers). Mark them in the diary at booking time.
Holding scripts for calls you cannot take this week
The worst outcome in a rush is not a polite "not this week". It is a promise that slips, or a caller who never hears back. Short, honest scripts protect your reputation.
- Non-urgent repair: "We're dealing with a lot of breakdowns after the cold snap, so our first slot for this is next Thursday. I can put you down now and call you if anything opens up sooner."
- Out-of-area or out-of-scope: "We can't get to you quickly this week, and I don't want to leave you waiting. You may get help faster from a firm closer to you."
- Quote request: "We're focusing on emergency calls for a few days. I've noted your details and we'll ring you on Monday to arrange the visit."
- Voicemail: "Thanks for calling. We're very busy because of the storm. If water is coming in or there's a danger to anyone, press 1 or call our emergency line. Otherwise leave your name, postcode and problem and we'll call back today."
Keep a call-back list that cannot be lost
During a spike the call-back list becomes the business's most important document. Keep it in one shared place rather than on scraps of paper or in one person's phone, and give every entry an owner and a time.
- Log name, number, postcode, problem, priority and the time you promised to call back.
- Sort by priority, then by promised time.
- Tick each call-back when made, with the outcome.
- At the end of each day, move anything unfinished to the top of tomorrow's list and send those customers a short update.
- After the spike, ring any customer still waiting, even if only to apologise and confirm their slot.
Example: a heating firm's first cold week
Example (fictional). A four-engineer heating firm in Derby switches its plan on when the forecast shows the first overnight frost of October. The owner's partner joins the office for the mornings, two routine services a day are moved to the following fortnight with customers told in advance, and evening calls go to an answering service that follows the firm's triage order and texts the on-call engineer for anything in the top two priorities.
By Friday the call-back list has been cleared every night, nobody has waited without an update, and the moved services are all rebooked. In the review the next week, the owner spots that most voicemails came between 7 and 8 am, before the office opened, and brings the morning start forward for next year's plan.
Review after every spike
A busy week leaves useful evidence. Within a few days, look at the calls answered and missed by hour, the call-back list and how long people waited, which planned jobs moved, and any complaints. Ask the team what slowed them down. Then update the triggers, the scripts and the cover for next time.
Over a couple of seasons the plan becomes routine, the phones stop being a source of panic and the busiest weeks turn into the most profitable ones, which is what they should be.
Frequently asked questions
What is a call overflow plan?
A written plan for what happens when more calls arrive than your normal team can answer: the triggers that switch it on, who covers the phones, how calls are prioritised and what callers are told.
When do home services firms get the most calls?
It depends on the trade: heating firms on the first cold snaps of autumn, roofers after named storms, pest controllers in early summer and gardeners in spring. Many emergencies are also reported in the evening.
Should I let calls go to voicemail when we're busy?
Only with a clear message that tells callers what to do in an emergency and when you will call back, and only if call-backs actually happen at the time promised.
How do I decide which jobs to move in a rush?
Decide in advance. Quotes and minor repairs can usually move; installs with materials on order and visits to vulnerable customers should not.
References
Met Office (2026). UK Storm Centre (opens in a new tab) ↑
Met Office (2026). UK storm season 2025/26 (opens in a new tab) ↑
Met Office (2026). UK Storm Centre (opens in a new tab) ↑
Ministry of Housing, Communities and Local Government (GOV.UK) (2026). Detailed analysis of fires and response times to fires attended by fire and rescue services, England, year ending March 2026 (opens in a new tab) ↑