Lesson 1 of 15 · 6 min

Peak-season surge plan (summer and winter)

Plan for the summer and winter call surges in HVAC.

Read the lesson

Goal: Plan an HVAC client's call handling, credits and calendar before the first heat wave or cold snap.

You need: A client on Core or Growth with a live voice agent. You should know Voice Agents and Workflows from the Catch courses.

Why this matters

HVAC demand is not steady. A mild week in May is quiet. The first 95 degree day in July can triple the calls by noon. The first freeze in December does the same for no-heat calls.

The office does not grow on those days. The same two people answer the phone. Every call they cannot take goes to voicemail, and the caller dials the next company. Industry studies put the missed-call rate for home service businesses at 14% to 27% on normal days. On surge days it is higher.

The money is also higher. A surge call is often a repair today, not a quote for next month. The customer is hot, cold or worried, and they book with whoever answers.

Your job is to make the surge boring. The AI answers the overflow. The calendar has room. The credits are already in the account. The owner sees a full board instead of a full voicemail box.

The plan changes with size:

  • Owner-operator (Rivera Heating and Air, 2 people, Core). The owner is in an attic when the phone rings. The AI takes almost every call on surge days. The main risk is running short of credits.
  • Fleet (Polar Air Services, about 20 techs, Growth). The office answers first and the AI takes the overflow. The main risks are the 10-call limit and a calendar with no open slots.
  • Multi-location. Each location has its own phone number and its own surge. Plan credits and calendars for each one.

The surge plan in four parts

A surge plan has four parts. You write it once a year, in the shoulder season, and review it before each peak.

  1. Forecast. Estimate calls per day and AI minutes per day for a peak week.
  2. Capacity. Check the AI call limit, the credit balance and open calendar slots.
  3. Flow. Shorten the agent's questions and update its answers for the season.
  4. Follow-up. Make sure every call that does not book becomes a task for a person.

The forecast uses one simple formula:

AI minutes per day = calls sent to the AI × average minutes per AI call.

Credits per day = AI minutes per day × 15.

Voice minutes are billed at 15 credits a minute, rounded up to the next full minute. A 2 minute 10 second call is billed as 3 minutes. Short calls save money only when they stay under a full minute boundary.

Peak concurrency matters too. ServiceAgent's AI answers up to 10 calls at the same time. An 11th caller hears ringing with no pickup. There is no overflow setting and no backup forwarding number. If your forecast comes close to 10 calls at once, ask ServiceAgent support to raise the limit before the season. The business can pay for a higher limit.

To estimate average concurrency, use: calls in the busiest hour × average minutes ÷ 60. Bursts run above the average, so leave a wide margin.

Fig 1

Will the surge pass the 10-call limit?

  1. Forecast the busiest hour of a peak day
  2. Average calls at onceCalls in the busiest hour × minutes ÷ 60
  3. Close to 10 at once, with bursts on top?YesAsk ServiceAgent support to raise the limit before the seasonNoKeep the limit and recheck next season
  4. Write the result in the surge plan
An 11th caller hears ringing with no pickup. Check before the season, not during it.
SeasonTypical surge triggerWhat callers need first
SummerFirst 90 to 95 degree daysNo cooling, booking today
WinterFirst freeze or cold snapNo heat, safety and urgency
Spring and fallMild weatherTune-ups and quotes
Fig 2

The HVAC surge year

  1. March to AprilWrite the summer plan; book spring tune-ups
  2. June to AugustSummer peak: no-cooling repairs, booked today
  3. September to OctoberWrite the winter plan; book fall tune-ups
  4. December to FebruaryWinter peak: no-heat calls, safety first
Plan in the quiet months so the busy months run on their own.

Build it in ServiceAgent

  1. Open Billing and review the last peak month in Usage history. Note the voice minutes used.
  2. Buy a credit pack before the season. Larger packs cost less per credit. Bought credits always roll over.
  3. Open Billing → Payment settings → Auto-reload Credits. Set Reload when below and Add amount with the owner.
  4. Open Voice Agents, then the agent, then Basics. Add a short seasonal block to the voice instructions.
  5. In that block, tell the agent to collect only the job essentials: name, address, the problem, and a time.
  6. Open Knowledge → Quick answers → Add FAQ. Add the owner's approved answers for wait times and the diagnostic fee.
  7. Open Actions and check Transfer to your team. Under Transfer when…, keep Emergency on for winter no-heat calls.
  8. Set After-hours behavior → Triage urgent vs routine. The client decides what counts as urgent.
  9. Open Follow-up. Attach a workflow on Call ended that runs Create CRM Task for every call that did not book.
  10. In Jobs, move tune-ups out of peak weeks. Book them in spring and fall instead.
  11. Open Test & publish. Run three calls with Talk in browser. These tests are free.
  12. Click Publish so live calls use the new version.

Check it works: Run one Call my phone test as the final check. It is a real call and uses credits. Confirm the task appears in Contacts for a call that did not book.

Fig 3

Pre-season surge checklist

  • Credit pack bought and Auto-reload Credits set
  • Seasonal block added to the voice instructions
  • Wait-time and fee answers in Quick answers
  • Transfer when… Emergency checked
  • Call ended task workflow published
  • Peak concurrency checked against the 10-call limit
Six checks before the first hot or cold day.

Worked example: Polar Air Services

Polar Air has about 20 techs and runs Growth. The office answers first. Missed calls forward to the AI by carrier no-answer forwarding.

These are example inputs. Use the client's own numbers from Analytics → Calls.

  • A normal July day brings 80 calls.
  • A heat wave day brings 200 calls.
  • On heat wave days, the office misses 35% of calls. That sends 70 calls to the AI.
  • An average AI call lasts 3 billed minutes.

AI minutes per day: 70 × 3 = 210 minutes.

Credits per day: 210 × 15 = 3,150 credits.

Fig 4Example numbers

Heat wave credit forecast for Polar Air

Calls to the AI: 200 × 35%70
AI minutes: 70 × 3210
Credits a day: 210 × 153,150
×Heat wave days10
Credits for the heat wave31,500
Forecast credits from minutes, not from calls. Voice is billed by the minute.

A heat wave of 10 days needs 31,500 credits. Growth includes 6,000 plan credits a month. Polar Air buys a 10,000-credit pack for $269 three times, or one 50,000-credit pack for $1,100. Three 10,000 packs cost $807 and cover 30,000 credits. The owner picks the 50,000 pack because the extra credits roll over.

Fig 5ServiceAgent pricing

Two ways to buy the heat wave credits

3 × 10,000-credit packs
  • $269 each, $807 in all
  • 30,000 credits
  • About 2.7 cents a credit
1 × 50,000-credit pack
  • $1,100
  • 50,000 credits
  • 2.2 cents a credit; the rest rolls over
Bigger packs cost less per credit, and bought credits roll over.

Cost per day at the 10,000-pack rate: $269 ÷ 10,000 = about 2.7 cents a credit. 3,150 credits cost about $85 a day.

Now the upside. Use the approved booking rate of 42% on answered calls as a planning example. 70 × 42% = 29.4, so about 29 booked jobs a day. At an example repair ticket of $450, 29.4 × $450 = about $13,230 of work a day.

Fig 6Example numbers

One heat wave day at Polar Air

about $85Credits for 70 AI calls
about 29Booked jobs at 42%
about $13,230Work booked at a $450 ticket
Example inputs. The 42% booking rate is a planning figure, not a promise.

Concurrency check: say 20 of the 70 AI calls land in the busiest hour. 20 × 3 ÷ 60 = 1 call at a time on average. Polar Air is far below 10, even with bursts.

Common mistakes

  • Waiting for the heat wave to plan. Fix: write the plan in April and October. The office has time then.
  • Long seasonal questions. Fix: collect name, address, problem and time. Every extra minute costs 15 credits per call.
  • No credit buffer. Fix: buy a pack before the season and set Auto-reload Credits. Service does not stop at zero, but small top-ups cost more per credit.
  • Tune-ups booked in peak weeks. Fix: move maintenance visits to the shoulder months. Keep peak slots for repairs.
  • Calls that end with no next step. Fix: every unbooked call creates a task. Give it an owner and a due date.

Do this now

Open your practice account or a client account. Write a one-page surge plan with four headings: Forecast, Capacity, Flow and Follow-up. Fill the forecast with the client's last peak month from Usage history. Then add one seasonal block to the agent and test it with Talk in browser.

Practice the conversation

  1. Operator Last July, how many calls went to voicemail on the hottest days?
  2. Owner Too many. The girls up front were buried by ten in the morning.
  3. Operator This year, the office still answers first. Any call they miss goes to the AI.
  4. Owner And it just takes a message?
  5. Operator No. It books the repair on your calendar, or it makes a callback task for your team.
  6. Owner What does that cost me on a crazy day?
  7. Operator On your numbers, about $85 of credits on a 70-call day. Those calls book about 29 jobs.
  8. Owner And if it gets slammed?
  9. Operator The AI takes 10 calls at once. You are far below that, and I checked it.
  10. Owner Okay. What do you need from me?
  11. Operator Your diagnostic fee, your wait-time answer, and what counts as urgent in winter.

Quick check

  1. A Growth HVAC client expects 90 AI calls a day in a heat wave, at 3 billed minutes each. How many credits a day should you plan for?
    • 270
    • 1,350
    • 4,050
    • 6,000
  2. Rivera Heating and Air is a 2-person shop on Core. The owner fears the AI line will go silent mid-surge. What do you set up?
    • A second voice agent to share the load
    • A credit pack before the season and `Auto-reload Credits`
    • A backup forwarding number in settings
    • A move to Franchise for more AI calls
  3. Why move tune-ups out of July and January?
    • Tune-ups cost more credits in peak months
    • The AI cannot book tune-ups during a surge
    • Peak slots should go to repairs that customers need today
    • Recurring appointments stop working in peak months

ServiceAgent UniversityLearn to run a service business on autopilot. Free courses, Blueprints and certification for Service Operators.

Learn

Get certified

Community