Seasonal demand planning for trades
Agentric Team ·
Every trade has a rhythm: boilers break in cold snaps, gardens grow in spring, accounts have January, weddings have summer. The businesses that ride the season well treat it as forecastable demand, not weather — and the biggest lever is being reachable when the surge hits.
The surge problem
Seasonal peaks are concentrated demand arriving fast: the first frost, the first warm weekend, the January tax panic. What defines a surge:
- Call volume spikes 3–10x in days.
- Everyone needs it now.
- Your capacity can't stretch — but your phone answering can.
This is where AI reception earns its keep in a specific way: the surge doesn't break it. Calls answered at 9pm on the coldest night of the year get the same quality as a quiet Tuesday — while your human capacity is fixed, your phone answering isn't.
Preparing for your peaks
- Map your seasons. When do you get slammed? Boiler trades: October–February. Gardens/landscaping: March–June. Accountants: December–January. Weddings: April–September. Write it down.
- Pre-load the knowledge. Update FAQs for seasonal questions before the season ("do you do emergency call-outs in a cold snap?" → answer ready).
- Set surge pricing in the FAQs — if emergency rates apply in peak season, say so plainly; the assistant quotes them consistently.
- Configure escalation for real emergencies — the actual burst-pipe calls go to your mobile; the "can you quote for spring" calls get captured.
The counter-seasonal opportunity
Quiet months are for the jobs callers put off: boiler services in summer, landscaping quotes in autumn, bookkeeping before the panic. The assistant can offer those proactively — "we're booking services for July at £75" is a sellable message to June callers.
The pattern
Surges reward the businesses that scale their answering, not their workforce. The phone call surge is the one part of seasonality you can fully automate.