It's 4:40pm, heat index past 100, and you're standing in a Rockville driveway with a multimeter in one hand because a compressor that was running fine an hour ago just went silent. Your phone hasn't stopped buzzing in your pocket since about 4:15. You already know why, even before you check the time against anything: Pepco or Dominion just ended a cycling event, half the enrolled AC units in the neighborhood are trying to kick back on within the same ten minutes, and a chunk of them aren't going to make it cleanly.
This isn't a generic "it's hot, calls go up" post. Pepco's Energy Wise Rewards and Dominion's Smart Thermostat Rewards are real, named programs that a meaningful share of your customers are enrolled in, and they create a specific, predictable mechanical event — not just a hot day, a restart — that lands on your phone in a tight window. I want to walk through what these programs actually do, why the end of the event is the dangerous part, and what that means for whoever's answering your calls that afternoon. Fair warning: I sell one fix for the phone-answering part. I'll be straight about where it does and doesn't help.
What these programs actually do to a compressor
Pepco's Energy Wise Rewards program — available to residential customers in DC and Maryland — installs a switch or web-programmable thermostat and cycles a participating home's central AC or heat pump compressor off for up to 15 minutes out of every 30-minute block on "Peak Savings Days," typically hot weekday afternoons, June through October. A conservation period can run three to six hours. Dominion's current Virginia equivalent, Smart Thermostat Rewards, does something similar through a connected thermostat — raising the cooling setpoint a few degrees or briefly cycling the compressor during a called "energy event," usually a couple of hours on the hottest afternoons.
Both programs are opt-in, both pay the homeowner a bill credit for participating, and both are explicit that customers can override an event if the house gets uncomfortable. None of that is a secret or a guess — it's what the utilities themselves say the programs do, and it's worth reading the source pages once so you can explain it correctly when a customer asks why their neighbor's unit is cycling and theirs isn't.
The dangerous part isn't the cycling. It's the restart.
A compressor that cycles off for fifteen minutes and back on is normal — that's what a thermostat does anyway. The part that isn't normal is what happens when the event itself ends. Energy Wise Rewards and Smart Thermostat Rewards events are scheduled and area-wide, which means a large batch of enrolled compressors across the same service territory come off cycling restrictions within roughly the same window, often right as the afternoon is still near its hottest point and every non-participating unit nearby has also been running flat-out the whole time.
A compressor asks for its biggest single draw of current at the moment it starts — the "hard start" — and that load is carried by a run capacitor that's been sitting in a 130-degree attic or a sun-baked side yard all summer, quietly degrading. A capacitor that's been getting weaker since May can survive a normal thermostat cycle all day and still fail on the one restart that happens to land during a synchronized grid event, because that's the moment demand on the unit is highest and the capacitor has the least margin left to give. You're not looking at more failures because it's hot. You're looking at a cluster of failures that share a start time, because a cluster of restarts shares a start time — the same wear, just compressed into one restart instead of stretched across a whole season, which is also why an "AC's not working" call means something different by late August than it does in June.
What that looks like on your phone
Take a shop that normally fields something like 9 missed calls in a slow week — the missed-call math piece walks through where that number comes from and what it's worth at a 35% close rate and a $450 average job, which pencils out to real money over a full year even in an ordinary week. Now compress a meaningful slice of a whole week's worth of no-cool calls into the ninety minutes after a cycling event ends, because that's genuinely when they happen — not spread evenly across the afternoon. If even three or four of those calls land while you're mid-diagnosis on someone else's dead condenser and can't get to the phone, that's not a slow-week miss anymore. That's several hundred dollars each, concentrated into the exact hour you have zero spare attention, because you're standing in someone else's driveway solving the same problem for the previous caller.
The voicemail you get back to at 8pm that night isn't the call handled. It's the call rescheduled onto your evening — you listen, you call back, you catch someone who's now also dealing with a second unit that failed on the same restart, and you're quoting tomorrow's slot for a today problem.
Why per-minute pricing breaks down in exactly this hour
This is the same trap covered in the two weeks that decide your HVAC season, just compressed from a multi-day heat wave down to a ninety-minute restart window: a per-minute answering service prices by call volume, which means the bill spikes hardest in exactly the hour your calls spike hardest. The pricing model doesn't distinguish "a normal Tuesday" from "every enrolled compressor in the ZIP code restarting within the same ten minutes" — it just charges more for more calls, right when those calls are worth the most to you and cost the most to have answered.
Where a flat-rate AI receptionist actually fits
This is the category Dialkeep's in, so take the next part with that in mind. The pitch for this specific hour is straightforward: $199 a month, flat — the same bill for a quiet Tuesday morning as for the ten minutes after a Pepco or Dominion event ends and six no-cool calls land back to back. It's built to ask the same triage questions a good dispatcher would — no cool air at all versus just running warm, whether anyone in the house is heat-vulnerable — get the address and symptom, and quote your configured diagnostic fee exactly as you set it, with no improvising a number to a stranger in the worst ten minutes of your day.
To be straight about the limits: it doesn't diagnose a bad run capacitor or quote a repair over the phone, and it shouldn't — nothing should, at the phone-answering stage. Dialkeep isn't live yet, and booking isn't built either — nor is any route that carries what the caller said back to you once they hang up. The demo line is coming; when it's live, you'll be able to call it yourself, describe a compressor that won't restart, and judge the triage (and, later, booking) firsthand.
Match the fix to the actual event
If your service area has low Energy Wise Rewards or Smart Thermostat Rewards enrollment, or your customers mostly aren't on time-of-use programs at all, this specific restart-clustering effect matters less to you, and a per-minute service might be perfectly reasonable. But if you've noticed your no-cool calls seem to arrive in a wave on the exact afternoons Pepco or Dominion push a peak-savings notice, that's not a coincidence — and the fix for a clustered restart-window spike should be flat-rate by design, not despite the pricing model. For the shop-size math on missed calls the rest of the year, see the missed-call math piece; for the surge-week version of this same problem, see the two weeks that decide your HVAC season; and the flat number is on the HVAC page.
Built for hvac contractors
The AC dies on the hottest day of the year and the customer starts working down the list. This answers, gets the symptom, the address, and how urgent it is down on the call — and the price is the same in a heat wave as it is in October.
The first heat wave doesn't have to cost you jobs →