Pricing the heat-wave call: dynamic dispatch when demand spikes 4x

Every HVAC operator knows what a heat wave does to the phone. A normal Tuesday in June: 30–40 calls. The first 95°F day: 140 calls before noon.

The challenge isn't just capacity — it's prioritization and pricing. When demand spikes 4x with the same number of trucks, every decision you make in those first hours ripples through the rest of the week.

Here's the framework we've developed across five summers at Bell Electric, adapted for HVAC based on what Calling Matrix operators have shared with us.

The pricing matrix

First, accept that surge pricing is appropriate and necessary. Your techs are working 12-hour days in attics at 130°F. Your parts cost more when you're expediting. And critically: customers calling during a heat wave are often in genuine distress, and they're willing to pay for immediate response. Pretending otherwise while undercharging leaves money on the table and undervalues your team's work.

The multiplier applies to labor, not parts. Parts pricing doesn't change. Customers understand labor surges; they resent parts markups during emergencies.

The triage queue

When you have 80 calls in queue and 5 trucks, the order you dispatch matters enormously. Our queue priority, in order:

1. Safety escalations: Elderly or medically vulnerable, no AC above 95°F outside. These dispatch first, always.
2. Maintenance plan holders: They paid for priority. Honor it. This is the entire value proposition of your maintenance plan.
3. Existing customers (past 12 months): They have a relationship with you. They're more likely to wait 4 hours with a clear ETA than a cold caller is.
4. New customers, system failures: Complete system failure, not just reduced cooling.
5. New customers, performance issues: Unit running but underperforming. These can often wait until the surge breaks.

What your AI receptionist should be doing during a surge

During a heat wave, the value of a 24/7 AI receptionist compounds. Here's specifically how to configure it for surge conditions:

Disclose wait times upfront

Nothing burns a customer relationship faster than promising "we'll be there soon" and showing up six hours later. The AI should state current estimated wait times during intake: "We're currently experiencing high demand — estimated arrival is 3–4 hours. Would you like to book at that window?" Most callers say yes. The ones who don't were never going to wait anyway.

Collect all dispatch info during the first call

During a surge, you don't have time for callbacks. Train the AI to collect everything during intake: address, access instructions, system age, symptom description, and a secondary contact number. A tech should be able to show up without any additional communication.

Offer callbacks to Tier 2 and 3 callers

Callers who aren't safety escalations but still need service should be offered a specific callback window from the AI, not a vague "we'll be in touch." "We can send a tech tomorrow morning between 8–10 AM — would that work?" converts a frustrated caller into a scheduled job.

After the surge

The day after a heat wave breaks, do two things: pull your missed call log and pull your Tier 2/3 backlog. The missed calls are revenue to pursue. The backlog tells you how much demand exceeded your capacity — and that number is your argument for the next piece of equipment, the next truck, or the next service area.

Surges are stressful. They're also the most profitable stretch of the year if you have the systems to handle them correctly. The businesses that come out of a heat wave ahead are the ones who triaged intelligently, priced appropriately, and didn't send a single call to voicemail.