Curtis Boyle looks at a quiet office chair and says, “One person can cover the phones. It's only forty hours a week.” For a four-truck shop that has always relied on family, another payroll line is a serious decision.
Those forty hours are already doing other jobs.
Curtis is our illustrative owner in Toledo, not a client case study. His wife, Marcy, answers calls, dispatches technicians, keeps the books and orders parts. Four jobs have been fitted into one person's day, with the phone expected to interrupt every one of them.
His thirty-day call log shows 206 inbound calls and fifty-three unanswered. The highlighted line is 2:14 on a Tuesday, when Marcy was helping a supplier and the second line rang out. Before Curtis asks her to answer faster, he needs to count the minutes he has already assigned.
Which work is competing with the next incoming call?
Spend a representative week recording work in short blocks. Include live calls, call notes, callbacks, dispatch changes, supplier conversations, parts ordering, invoicing, bookkeeping, breaks and meetings. Record when the activity occurs, not just its total duration.
Do not require somebody to narrate every keystroke. A simple sheet can contain start, finish, task type, interruption, and whether another person covered the phone. Use the record to design coverage with the employee, rather than to judge whether they looked busy enough.
Keep call talk time and after-call work together when estimating workload. A six-minute conversation followed by two minutes documenting the appointment consumes eight minutes. If documentation is already in that allowance, do not deduct it again under general administration.
The Bureau of Labor Statistics describes customer-service work as including customer contact, recordkeeping and handling questions or complaints. It supplies no universal HVAC calls-per-hour target. Your mix of scheduling, technical routing and other office duties needs its own measurement.
Curtis can see why the chair is a poor capacity measure. Marcy can be sitting beside the phone and still be fully occupied. The call handling checklist describes the conversation; this worksheet finds the time and cover needed to complete it.
How many call-handling minutes are actually available?
Start with paid time, then name the duties already assigned. Here is an explicitly assumed weekly model, not Marcy's measured schedule or an industry standard:
| Weekly time item | Minutes |
|---|---|
| Forty paid hours | 2,400 |
| Breaks within this paid-time model | -150 |
| Bookkeeping and invoicing | -360 |
| Parts and supplier work | -240 |
| Dispatch and other non-call duties | -450 |
| Remaining call and wrap-up time | 1,200 |
| Planning reserve, 20% of that remainder | -240 |
| Planned call and wrap-up capacity | 960 |
960 ÷ 8 minutes per handled call = 120 handled calls per week in this particular plan. The eight-minute average includes the notes. The reserve is an assumption for interruptions and variability, not an instruction to use precisely 20% in every office.
The table treats the deducted dispatch and supplier work as work outside the handled-call allowance. If your log classifies some of those conversations as handled calls, move the minutes into the right category rather than counting them twice. Exclude unpaid time from the paid starting total.
This is a workload ceiling under stated assumptions, not a guarantee that 120 incoming calls will be answered. Call arrival time, length, skills and simultaneous demand still matter. Replace the model with measured times before deciding how much coverage to purchase.
Marcy's forty-hour week has become sixteen planned hours for call and wrap-up work in this example. Curtis has not discovered sixteen idle hours. He has discovered what remains after the other assignments he gave the same person.
Why can a week with spare time still miss calls?
Weekly totals cannot place two conversations in the same minute. Mark arrivals in fifteen- or thirty-minute blocks and inspect repeat peaks. Include what the person was doing when the call arrived and whether a backup was available.
Use a separate peak-hour illustration. Assume eight calls arrive during one hour, averaging eight minutes each including wrap-up. They require 8 × 8 = 64 minutes. Suppose essential dispatch and parts tasks leave only thirty minutes for those calls. The workload exceeds that available time by 34 minutes.
Even sixty-four available minutes spread across a longer period would not solve two callers arriving together. The plan needs a way to receive the second call, an honest callback process, or both. A quiet hour later does not retroactively answer a caller who has left.
Curtis's call log gives 53 ÷ 206 = 25.7% unanswered, with 153 answered. It does not show that all fifty-three were qualified new-job inquiries, all were lost, or all arrived after hours. Deduplicate attempts and identify intent before valuing any opportunity.
At 2:14, Marcy was solving a real supplier problem. The calendar could show plenty of theoretical time later that afternoon and still fail that customer. Curtis needs to compare the arrival pattern with coverage, not divide thirty days of calls by thirty days of office hours.
What should the backup own when the line rings?
Write a small routing card before choosing another device or service. It should name the coverage window, the trigger for forwarding or pickup, the primary receiver, a backup, and the allowed next steps.
Use this reusable format:
- Trigger: The first handler is occupied, absent, or outside staffed hours under the configured routing rule.
- Receive: Identify the company and collect name, callback number, address, service intent and the customer's stated urgency.
- Authority: Offer only appointment types and windows the business has actually released.
- Handoff: Create or update one inquiry record with an owner and promised next action.
- Exception: Escalate under the business's approved instructions; do not diagnose equipment or promise unstaffed dispatch.
- Close: Mark who accepted the callback and when the customer was reached.
Choose a routing threshold that fits the phone system and test it. A missed-call acknowledgement can tell the caller the request arrived. It does not supply a live conversation or confirm an appointment.
Keep daytime overflow distinct from overnight service. The after-hours and overflow comparison helps specify those assignments, while call-handler training prepares the person who receives them.
Curtis can ask Marcy which details she needs from a backup. That uses fourteen years of knowledge without requiring fourteen more years of permanent availability. The handoff should reduce repeat explanations for both her and the customer.
When would moving work beat adding another person?
Match the intervention to the bottleneck. Predictable bookkeeping blocks might move into protected periods with trained call coverage. A supplier task might be reassigned. A recurring afternoon collision might justify scheduled overflow. Continuous independent workloads may support a separate position.
Do not simply move the work into Marcy's evening. Time shifted out of the call window still has a cost and an owner. Test whether the task can genuinely move without delaying a technician or missing a customer commitment.
Compare options against the same assignment: hours covered, work performed, booking authority, backup reliability and total internal supervision. A vendor offering message-taking is not equivalent to an employee authorized to resolve dispatch conflicts.
Use actual written quotes and loaded labor costs. Include training, schedule coverage, software access and the time someone spends repairing incomplete handoffs. If the proposal depends on more completed jobs, use incremental contribution after direct delivery costs and check field availability first.
The technician hiring decision should follow the actual bottleneck too. Another truck does not answer the office's second line. A front-office hire does not create technician hours you have already committed.
Curtis does not need to choose a permanent solution from one Tuesday. He can test one protected task block with a named backup, then inspect what happened. A smaller measured change is useful if it makes the work possible and exposes the next constraint.
What should Curtis check next Friday?
Review arrival blocks, live answers, callbacks accepted, customers reached, eligible inquiries, appointments offered, bookings and completed work. Keep the stages separate. An answered supplier call is useful work, but it is not a new-job booking opportunity.
Use the same definitions before and during the test. Record changes in weather, advertising and field availability. Avoid claiming that every recovered call was an additional job the old callback process would have lost.
Ask the employee about the work left behind. Did the phone improve while invoices accumulated? Did the backup need constant help? Were promised callbacks owned at the shift change? A better answer rate purchased with invisible overtime is an incomplete result.
The inquiry-to-invoice record can connect the customer outcome. The operational handoff guide can make the backup less dependent on memory. Neither replaces the simple question of who is available when the next call arrives.
Curtis takes the printout out of the drawer and puts the time sheet beside it. The fifty-three missed calls are no longer an accusation against Marcy. They are evidence of assignments that overlapped.
Before the next 2:14 call, they can name the work she is doing, the person receiving the second line, and the customer promise that person is able to keep. That is a front-office capacity plan Curtis can actually use.
