The Storm Hit at 2am. By 7am Mike Had 47 Voicemails and Lost Half the Jobs

The Real Problem

Mike runs a five-person arborist crew out of Henderson. He has been climbing trees for nineteen years and now mostly drives the truck while his two younger climbers do the cutting. His phone rings every day, but on storm nights it does not stop.

Last May a southerly hit Auckland around 2am. By the time Mike's alarm went off at six, his voicemail had forty-seven new messages. By seven, it had sixty-three. He worked through them sitting in the truck cab in his driveway, still in the clothes he slept in, calling people back in the order they had rung. By the time he reached message number twenty, the customer had already booked another arborist who picked up faster.

The storm jobs are the highest-margin work Mike does. A typical scheduled job is three to six hundred dollars. A storm callout with a tree on a roof or across a driveway is fifteen hundred to four thousand, and the customer is not negotiating. Whoever quotes first wins. Whoever picks up the phone wins more.

Mike has tried hiring an after-hours answering service. They take a name and a number and tell the customer Mike will call back. Half the customers have already moved on by the time Mike does. The answering service cannot tell him whether the tree is on a power line, whether the property is accessible, whether it is a one-truck job or needs a crane and a traffic management plan. So even the messages that do convert mean Mike spends another fifteen minutes on the phone before he can quote.

The other problem is council consent. Probably twenty percent of the trees Mike gets called about are on Auckland Council's notable tree register or in a Significant Ecological Area. He cannot legally touch them without resource consent. Customers do not know that. They get angry when he tells them. By then he has already driven thirty minutes to the site.

Why Existing Tools Don't Solve This

Tradify, Fergus, AroFlo are the tools most NZ arborists actually use. They do scheduling, invoicing, and basic quoting. They do not pick up the phone. They do not screen jobs. They are good once Mike has decided to take the job and needs to schedule it.

ServiceM8 has a job intake form on its website but it is a passive form, not a conversation. The customer fills in three fields and then waits. Most storm-night customers do not visit your website. They ring.

ArborGold and Tree Plotter are the international software platforms. ArborGold is built for US contracts where the average job is much larger. Tree Plotter is more about asset management for councils than quoting for a small operator. Neither has any awareness of Auckland Council notable trees, the Resource Management Act consent rules, or how Vector contracts power-line clearance work.

An after-hours answering service can take a message but cannot ask the right questions. It also cannot send photos, cannot tell Mike how steep the property is, cannot check whether the address falls inside a notable tree zone, and cannot tell the customer that a tree on a power line means Vector first, arborist second.

ChatGPT in a browser can answer general arborist questions, but it has no connection to Mike's calendar, his suburb-by-suburb pricing, or the council's notable tree register. It also cannot send a quote to the customer or book the site visit.

Nobody has built a tool that knows Auckland Council's notable tree boundaries, can take a photo from a customer at 2am, and can give a real quote band before the climber's boots are on. That is the gap.

How AI Solves This

Mike's number now rolls to an AI assistant after three rings, and also picks up every voicemail and every text and every contact-form submission. The customer can talk normally, send a photo, send a video, or just text "tree on my roof, Greenhithe."

Here is what happened on the next storm night, two months after Mike installed it.

A customer in Albany rang at 3:42am.

"Yeah hi, I've got a massive pohutukawa down across my driveway, the kids can't get out for school in the morning."

The AI: "That sounds stressful. Can you send me a photo? I just need to see the size of the tree, whether it's touching power lines or just on the ground, and roughly where it is on the property. You can text it to this number."

The customer sent two photos.

The AI assessed: trunk roughly 600mm diameter, completely on the ground (not on a power line), driveway access via a sealed concrete drive, no overhead lines visible in either photo. It cross-checked the address against Auckland Council's notable tree schedule. The tree was not listed. It cross-checked against Vector's power-line clearance database. Not a Vector job.

"Looks like a one-truck job, no crane needed, and your power lines are clear. For a tree this size with good driveway access, our quote band is $1,800 to $2,400 plus GST, including stump grinding to 100mm below grade and full removal of all green waste. We can be there between 7:30 and 9am Saturday morning. If you want to confirm, I'll book you in and Mike will call you at 7am to introduce himself before the crew arrives."

The customer booked at 3:51am. By 4am the job was on Mike's calendar with the photos, the address, the quote band, and a note that the AI had checked notable-tree status. Mike slept till six.

That morning, the AI had handled fifty-eight enquiries overnight. Forty-one were quote-banded and booked or queued for site visits. Eleven were politely declined because they were council notable trees or in SEA zones, with a clear explanation of why and a link to the council's resource consent process. Six were referred to Vector first because they involved power lines. Mike's job was to drive the truck, not to triage.

What the AI Knows That a Generic Bot Doesn't

The AI is configured with the things that matter for Auckland arborists specifically:

• Auckland Council notable tree register: the address-level boundaries are loaded so the AI checks every job before quoting
• Significant Ecological Areas: same approach, the SEA overlays from the Auckland Unitary Plan are checked
• Vector power-line zones: anything within four metres of a line goes to Vector first, no exceptions
• Mike's pricing bands by suburb and tree type: pohutukawa removal in Albany is a different number than a sycamore in Henderson, and the AI knows
• Crane vs no crane heuristics: based on tree size, lean direction, and access, the AI flags whether a crane callout is likely needed (which adds $1,500-$2,500 to the job)
• NZ Arb minimum standards: the AI does not quote work that the NZ Arboricultural Association considers two-climber minimum as a single-climber job

The Council Consent Side

The Auckland Council notable tree process is one of the things customers most often get wrong. They want a 120-year-old kauri removed because it is dropping branches on their roof. The AI has been trained to handle that conversation:

"I've checked the address and that tree is on Auckland Council's notable tree schedule. That means we can't legally remove or significantly prune it without a resource consent from the council. The good news is, if the tree is genuinely a danger to your house, the consent application has a 'health and safety' pathway that often gets approved within a few weeks. I can have Mike come out and do a written arborist's report for the application. That's usually $400-$600 and is the document the council will require. Want me to book that?"

That conversation alone has saved Mike from multiple wasted site visits and turned what used to be a frustrated customer into a paying job for the report and (often) the consent-approved work.

How We Set This Up

None of this works if the AI is just a chatbot on a website. That's why BestAI builds a custom integration program that connects the AI to all the moving parts of an arborist's actual workflow.

For Mike, that meant:

• Connecting the AI to his Spark business number so it picks up calls, voicemails, and texts
• Loading Auckland Council's notable tree schedule and SEA zones into the AI's reference data, with a quarterly refresh job to keep it current
• Pulling Vector's power-line zone data so the AI can check power-line proximity before quoting
• Connecting the AI to Mike's Tradify account so booked jobs land on the calendar with photos, address, and quote band attached
• Building a simple morning dashboard where Mike sees overnight enquiries, AI decisions, and any flagged jobs that need his judgement before quoting
• Setting up an SMS handover so Mike or his climbers can take over a conversation any time with a single tap

Here's our process:

1. We review the call log: how many calls per week? How many storm nights per year? What percentage convert today?
2. We build the council and Vector data layer: loading the notable tree schedule, SEA boundaries, and Vector power-line zones for the suburbs the operator works in.
3. We configure the pricing bands: working with the operator's actual quote history to set realistic bands by suburb, tree type, and access type.
4. We test against past callouts: we replay the last six months of calls through the AI to see how it would have handled them. The operator reviews and adjusts.
5. We maintain it: council schedules update, pricing changes, new suburbs get added. We handle the upkeep.

You don't need to be technical. We handle all the development. Mike still climbs trees and drives the truck. The AI handles the phone.

The Result

• Zero missed storm callouts: every call, voicemail, and text is answered within seconds, day or night
• Quote bands sent within 10 minutes: customers know the price before they decide whether to ring three more arborists
• Council notable trees flagged before any site visit: no more wasted drives to jobs Mike legally cannot do
• Vector jobs handed off cleanly: power-line work routed where it belongs, with a referral note that does not lose the customer for follow-up cleanup
• Mike sleeps through storms: overnight enquiries are triaged, booked, or politely declined, with a morning dashboard showing exactly what happened

For an operator running five climbers and averaging twelve to fifteen storm callouts per major weather event, capturing even half of the jobs that previously went to whoever answered first means $8,000 to $20,000 in additional revenue per storm event. Auckland gets four to six of these per year. The AI pays for itself inside the first season.

What AI Can't Do Here

• AI won't climb a tree, swing a saw, or operate a crane. The actual work is still Mike's crew.
• AI won't quote definitively. It gives bands, flags anything outside its bands, and hands those to Mike for a human quote.
• AI won't sign off on hazardous tree assessments. NZ Arb best practice requires a qualified arborist's site report for any work that needs a consent, and the AI knows to defer those to Mike.
• AI won't argue with a customer who insists the tree is not on the notable register. It explains the rules, links to the council page, and books a site visit if the customer still wants to discuss.
• AI won't replace the relationship. Mike still rings every job before the crew arrives. The AI just makes sure he is ringing customers who are already booked, not chasing voicemails.

Who This Is For

• Arborists with two or more climbers who lose storm-night work because they cannot answer the phone fast enough
• Operators who routinely drive thirty minutes to a site only to find the tree is on the council notable register
• Tree-service businesses where after-hours enquiries are most of the high-margin work
• Crews working across Auckland, Wellington, or Christchurch where notable tree schedules and SEA overlays make council compliance complicated
• Family-run arborist businesses where the owner is also the climber, the quoter, the dispatcher, and the after-hours phone