The average conversation on one landscaping line ran 76 seconds. That is the real cost of answering every call.
Not a salary. Not a shift. 76 seconds, averaged across a full peak season.
Owners talk about answering the phone as though it were a staffing decision. On one landscaping line it was a 76-second decision. That is the average conversation length across all 80 calls of a full 15-week peak season, long enough to take the job, the property and the callback details properly, and short enough that the total time commitment is smaller than almost anyone guesses before they measure it.
What fits inside a 76-second call?
More than it sounds. A quote request needs the job, the property, and a way to reach the caller back, and that is a conversation of about a minute when nobody is being kept waiting or transferred.
- 76saverage conversationacross all 80 calls
- 80calls in the window15 weeks
- 100%answerednone went to voicemail
- 86%first-time callers69 ÷ 80
The number is unremarkable on its own and useful in context. A call of this length is not a consultation, and it was never trying to be; it is an intake. The judgement is captured, the details are taken, and the actual work of quoting happens later, in person, where it belongs.
It also sets a ceiling on what automation can save. If the average call ran twelve minutes, shortening it would be the prize. At about a minute, there is nothing meaningful to shave, and the entire value sits in whether the call was answered at all.
What does that add up to across a week?
Almost nothing. 80 calls over 15 weeks is 80 ÷ 15 = 5.3 calls a week. At 76 seconds each, that is roughly 6.8 minutes of talking per week, across the busiest season of the year.
That figure is the one worth sitting with. The business was not failing to answer its phone because answering it was a burden; 6.8 minutes a week is not a burden. It was failing because those minutes were scattered unpredictably across hours when everyone was on a site.
Which is why framing the phone as a workload problem leads to the wrong solutions. Nobody needs to be freed from six minutes a week. They need those six minutes to be covered at moments they cannot choose.
So why were these calls going unanswered before?
Timing, not length. Landscaping crews are on site with equipment running and the owner is in a truck, and the calls arrive during exactly those hours. A 76-second call is trivial to handle and impossible to take when both hands are occupied.
This is the shape of the problem in most trades, and it is why "just answer the phone" is unhelpful advice. The constraint is not willingness or time in aggregate; it is simultaneity. The call arrives while the work is happening, and the work is what the call is about.
It also explains why the fix has to cover moments rather than hours. Something that answers between 9 and 5 on weekdays does not solve a problem that occurs at 11:40 on a Tuesday while a crew is mid-install.
The reason these calls went unanswered was never that they were long; the average ran 76 seconds, about 6.8 minutes of talking a week. It was that they arrived while the crew was on a site and the owner was in a truck.
The time cost of answering every call is almost always smaller than the owner assumes. The arithmetic is on this page.
Start free pilotWhat this figure does not tell you
One business, one trade, one season. The number is real and its scope is narrow.
- Not an industry average. This is Lammer Enterprises's measured average across one season. A cross-industry figure would flatten exactly the variation that matters, so none is published here.
- Call type drives length. A quote request and a booking confirmation are different conversations. This window was dominated by quote requests from first-time callers.
- Averages hide the tail. We publish the mean because that is what the reporting gives us. The distribution behind it is not something we currently break out.
Questions this raises
- How long is an average business phone call?
- On this line it was 76 seconds, across all 80 calls of a full 15-week season. That is one landscaping business, and it is not offered as an industry benchmark.
- Is a minute long enough to capture a lead properly?
- For an intake, yes. The job, the property and the callback details fit comfortably. What does not fit is quoting the work, which happens after a site visit anyway.
- Does answering every call take a lot of time?
- On this line, roughly 6.8 minutes of conversation a week during peak season. The difficulty was never the total; it was that the minutes arrived at unpredictable moments.
- Would a longer average be better?
- Not necessarily. Longer calls in an intake context often mean repetition, hold time or re-explaining, none of which the caller wanted.
- Will this number change?
- Yes. It is read from the underlying call records at build time, so when the reporting is refreshed this page moves with it rather than needing a rewrite.
Sources
- Sucré Body Sugaring & Medical: call reporting, one month, 1 locationAnswerAI first-party data, published with permission2026-08-09
- Lammer Enterprises: call reporting, April 21 - August 6, 2026AnswerAI first-party data, published with permission2026-08-06
Want your own version of this number?
We build a working receptionist on your calls and your booking rules, you run it for about 14 days, and at the end you have your own data instead of somebody else's.
Start free pilot
