This is an illustrative scenario, not a client result. The business, people and numbers are examples chosen to show how the math works. Replace them with your own.
Imagine a three-truck HVAC company in peak season that still can’t keep up. The owner has a good problem — more demand than the team can handle during business hours. But there is a hidden problem too: when the office closes at 5pm, the calls keep coming, and none of them get answered.
In this example, we assume that after the first month with AI intake, the company captures 31 after-hours leads that would otherwise have gone to voicemail, and 22 of them become booked jobs.
Here is how that could work.
The Setup: A Busy Company With a Quiet Blind Spot
Suppose the company was built on referrals and repeat customers that keep three technicians busy most of the year. By summer, the phone rings constantly.
The problem isn’t lack of demand. It’s timing.
For this example, assume a review of three months of call logs shows that a large share of inbound calls (say about 40%) arrive between 5pm and 9pm, when the office is closed. There is voicemail, but few callers leave a message. Many simply call the next company in the search results.
Picture the owner arriving Monday to 12 or 15 missed weekend calls, with no way of telling which were real jobs.
The Before Numbers (Assumptions)
| Assumption | Value |
|---|---|
| Office hours | 8am–5pm, Monday–Friday |
| After-hours coverage | Voicemail only |
| Missed calls per week (peak season) | 28–35 (use 30) |
| Share of missed calls that are distinct new inquiries | About 24% |
| Distinct new inquiries missed per month | About 31 (30 × 4.33 × 24%) |
| Share of inquiries that become booked jobs when handled | About 70% |
| Average job value | $285 |
Not every missed call is a new lead. Repeat callers, existing customers, vendors and spam are why this example counts only about a quarter as new inquiries.
Running the math: 31 inquiries × about 70% ≈ 22 jobs × $285 = about $6,270 a month in potential revenue going to voicemail during peak season.
What the Build Could Look Like
A sensible first step is a two-week diagnostic: how calls come in, what qualifies a job, and the scheduling constraints.
Decisions that process would likely produce:
- Qualification criteria: Emergency vs. non-emergency, service area (zip code check), AC vs. heating, equipment age
- Booking integration: Connect directly to the company’s scheduling software so the AI can offer real available windows
- CRM routing: Tag leads by job type (emergency, tune-up, replacement estimate) and route them to the owner’s phone and the shared job board
- Escalation logic: Genuine emergencies (for example, no AC with an elderly resident) trigger an immediate text alert to the owner’s personal phone. Safety situations such as a gas smell are handled differently: the assistant tells the caller to leave the building and call the gas utility or 911 first, then alerts the owner.
For this example, assume build and integration take about three weeks from kickoff to live.
Month One: What the Numbers Could Look Like
Assume the system goes live at the start of peak AC season.
Assumed 30-day numbers:
| Assumption | Example value |
|---|---|
| After-hours inquiries captured | 31 |
| Leads qualified (met criteria) | 27 |
| Jobs booked | 22 |
| Emergency escalations (text alerts) | 4 |
| Typical response time | Seconds |
Revenue from captured leads:
22 jobs × $285 average = $6,270 in month one from leads that would otherwise have gone to voicemail.
The emergency escalations could be the most valuable part. The burst pipe scenario shows the same idea for plumbing. A no-AC call from an elderly resident during a heat wave is where a same-night response builds a reputation.
What Could Change Day-to-Day
Three operational shifts are likely when intake runs after hours:
1. Monday mornings change. The owner arrives to a CRM already holding qualified leads, job types, and booked appointments.
2. The office admin can shift focus. Rather than triaging voicemails and doing callback rounds, that time can move to customer follow-up and review requests.
3. Peak season feels different. A busy Saturday no longer means a pile of unsorted messages on Monday. The owner looks at what is already booked and spends attention only on the calls that need a person. For more on dispatcher workload, see three HVAC automations for dispatchers.
The Investment and Payback
Prices for AI intake vary widely. Off-the-shelf AI receptionist products are inexpensive: as of October 2026, Goodcall lists plans from $79 to $299 a month and Smith.ai lists paid AI receptionist plans from $150 to $500 a month base, before add-ons. Managed systems with custom scheduling and CRM integration cost more.
For this example, assume a managed AI intake system costs $10,000 to set up and $1,500 a month.
| Assumption | Amount |
|---|---|
| Setup | $10,000 |
| Monthly cost | $1,500 |
| Year 1 total | $28,000 |
| Year 2 and beyond | $18,000 |
Month one revenue from captured leads: $6,270. After the $1,500 monthly cost, $4,770 goes toward the setup fee.
- On revenue: $10,000 ÷ $4,770 ≈ 2.1 months, so the setup is recovered during month three, if peak-season volume holds.
- On gross profit: revenue is not profit. If the company keeps about 50% of each job after parts and labor, month one contributes $3,135 − $1,500 = $1,635 toward setup, and payback takes about 6 months ($10,000 ÷ $1,635 ≈ 6.1).
Off-season volume will be lower, so use your own month-by-month call data. For a longer view, see the 90-day after-hours worked example.
Is This Relevant for Your Service Business?
The HVAC scenario isn’t unique. Any local service business with consistent inbound volume, after-hours inquiry gaps, and a qualifying process that follows the same pattern every time could see a similar pattern.
The first step isn’t committing to a build — it’s understanding where your leads are actually dropping. Our AI Readiness Audit is a two-week diagnostic that maps your workflow, identifies your highest-ROI automation, and delivers a written plan. The 2-week AI Readiness Audit starts at $2,500, and the fee credits toward the setup of a build started within 90 days (up to 40% of the setup price).