AI for tree service companies: a triage queue, not an arrival time.

A message saying a tree came down in last night's wind could mean a branch on the lawn, a trunk through a bedroom ceiling or a limb lying across the line into the house. The first two are jobs. The third is a matter for the utility and emergency services, and while that line might be live nobody at a tree company should be telling the customer when a crew will turn up. So the most useful output of an AI back office here is not a reply but a sorted queue the owner works through, and a briefing pack the crew lead reads before anyone climbs.

Supervised assistants can sort storm messages against rules the owner wrote, set out photo estimate sheets for the arborist to price, attach the protected-tree rules the owner has listed for a job's area, and assemble the job-briefing pack. They do not decide whether a tree is hazardous, whether it may be cut, how it comes down or when the crew arrives.

OSHA's hazard card for tree care work (publication 3752, dated 2014, as checked on 16 October 2026) names falls, electrocutions and being struck by trees as ways many workers are hurt or killed. Its pamphlet on electricity and tree care work goes further and calls contact with electricity one of the leading causes of death for tree care workers. Employers must provide a hard hat, climbing spurs and a harness, and train workers to recognize fall and electrical hazards.

Supervisors carry a second list. Check the worksite for hazards. Make sure the climbing gear suits the size of the tree. Have a trained professional check falling-tree hazards before work starts. Keep work at least ten feet from electric power lines, or call the power company to de-energize and ground the line, and assume that every power line is energized. Cone off a drop zone at least twice the height of the tree. Decide whether rigging is needed. Employers, for their part, must make sure ground and elevated workers can see and hear each other.

These are federal publications; OSHA's State Plans page lists twenty-two State Plans covering private employers, among them California, Oregon and Washington, each at least as effective as federal OSHA. The owner confirms which rules govern their crews.

Each item on that second list is a judgment made at the tree by a trained person, never by software. The office puts the facts in front of that person and makes sure nobody has promised something their judgment might overrule, starting with a time.

When wind or ice brings trees down across a service area, requests arrive faster than one owner can read them: web forms, emails, forwarded photos, the owner's own notes. A triage Bot can read them on a scheduled routine, run no closer than five minutes apart, from the folder or mailbox the owner gives it, and file each under one of three headings the owner fixed in advance: life-safety, structure-impact or routine. Anything that mentions wires goes to the top with the owner's approved wording, which sends the customer to the utility and to emergency services and never to the tree crew.

Those rules, the wire wording and the phrases an assistant must never use are worked through in the storm triage article in this series. The short version: the Bot sorts and drafts, the owner sends, and no draft says when anybody will arrive.

Based on the Grok Bot documentation at docs.x.ai as checked on 15 October 2026. Its statements on Bot rules, Bot-to-Bot messaging, routine triggers, connected apps, approval expiry and payments were rechecked against docs.x.ai and Cursor's help pages on 26 October 2026. The trade examples are Aevrion's illustrations, not documented Grok Bot use cases. Aevrion Ops is an independent consultancy. It is not affiliated with, endorsed by or a partner of xAI, SpaceXSI or Cursor. Grok Bot is named here only to describe it.

Each assistant below is a Bot the owner sets up in Grok Bot, following Aevrion's pattern. A Bot is a named, durable assistant with a job and its own conversation, and all of an owner's Bots work on one persistent cloud computer that has its own browser, files and command line. The four roles below are Aevrion's design for a tree company, not features of the product.

Grok Bot's documentation says to tell a Bot rules that should stay true, such as never sending an external message without approval, and to ask it to remember them. A tree company's lasting rules would include never stating an arrival time, never describing a tree as safe and never naming a price. A remembered rule is guidance the Bot follows rather than a lock, so the owner also sets approval rules for anything that sends, books or deletes. Approving a step does not undo work a Bot has already finished. A request for approval that appears while the owner is in the chat simply waits; one produced by an unattended routine, such as an overnight storm run, expires after roughly ten minutes (Cursor's help pages say thirty) without its action running, so that run is written to finish in email drafts for the morning.

Telephony is absent from the documentation, so these Bots do not answer calls or send texts; they start from what whoever took the call wrote down, or from forms and emails passed to them. Reading the company's job software is a custom integration or supervised browser use where the vendor permits it, subject to testing, since no connector for tree-care software or crane hire bookings is documented. Prices, crew schedules and permit status come from the source system on every run, never from a Bot's memory.

Only the arborist can say whether photos are enough to price a job. Consider, as an illustration, a homeowner who emails four photos of a silver maple split at its main fork and leaning toward a neighbor's fence, and asks what removal would cost. The owner attaches the photos to the Estimate Prep Bot's conversation; Grok Bot accepts images of up to 25 MB, six at a time from the desktop app. The Bot builds a sheet in Aevrion's pattern, a design rather than a product feature:

• PHOTOS, LABELED

  Each picture named by what it shows (whole tree, trunk base, fork, ground beneath) and dated. A missing whole-tree view is flagged, not guessed at.

• WHAT LIES BELOW

  The fence, shed, car or roof the customer mentioned, in the customer's words. It is a record of what was said, not an assessment of risk.

• ACCESS AND OVERHEAD

  Gate width and distance from the drive if the customer gave them, and a mark on any photo where wires appear, for the arborist to check in person.

• THE ARBORIST'S LINES

  Climbing, bucket truck or crane; rigging; haul-off or wood left on site; stump grinding; clean-up. Every line is blank until the arborist fills it.

• QUESTIONS BACK

  An email draft asking the customer for the views the arborist will want, waiting for the owner to edit, send or discard.

A guessed number would sit on the sheet looking like a measurement, and someone might price a job or plan a drop zone around it. So measurements come from the arborist, or from the customer when the arborist asks, labeled with their source, and rates come from the owner's own price file. The arborist chooses the method and sets the price; only then does the sheet become an estimate the owner sends.

Whether a tree may be cut at all depends on where it stands, and the rules differ in kind. In England a Tree Preservation Order means a consent application, and a conservation area without one means six weeks' notice unless an exception applies (government guidance, as checked on 16 October 2026); Austin, Texas regulates residential trees from nineteen inches in diameter measured four and a half feet up, dead or alive. The owner-arborist article in this series works through both. Portland, Oregon asks for an Urban Forestry permit for a private tree of twelve inches or more at breast height, once its Heritage Tree, development, land-use review and overlay checks are cleared.

A Tree Check Bot can hold the owner's list of jurisdictions and their rule pages, match a job's address to the right one, and attach the summary and links to the job for the owner to confirm. Searching a council map or city permit site is supervised browser use where the site allows it, and any sign-in, code or fee is a step the owner completes by taking over the computer. An unclear result reaches the owner as unclear; the Bot never declares a tree unprotected and never files anything.

OSHA's supervisor list makes a good spine for the briefing, because each line is a question the pack shows as answered or open. In Aevrion's pattern the Crew Briefing Bot assembles it the evening before from the job file and the arborist's notes, for a job such as a bucket-truck reduction of a roadside sycamore. The crew lead signs it, and the check at the tree outranks anything on it; how a pack is versioned and re-signed through a storm week is followed in the owner-arborist article.

• METHOD AND RIGGING

  The arborist's chosen method and the rigging decision, copied from the job file with the arborist's name beside them.

• LINES

  The distance to overhead lines the arborist recorded, or the utility's reference for de-energizing and grounding the line.

• DROP ZONE

  The zone the arborist set, which OSHA says must be at least twice the height of the tree, and where the cones go.

• EQUIPMENT

  What is booked, with the confirmation attached. A booking still waiting on the owner is shown as unconfirmed.

• PERMISSION

  The protected-tree finding the owner confirmed, or the open question if there is one.

• ON SITE

  Customer notes such as cars to move, dogs and gate codes, kept in the owner's system and pulled fresh for the pack.

The Federal Trade Commission's advice on avoiding scams after weather emergencies (updated September 2025, as checked on 16 October 2026) asks homeowners to get written estimates and a written contract and read it before signing. It expects the contract to state start and completion dates and a payment schedule and to put any verbal promise in writing, and it tells people to walk away from anyone who wants cash up front. It also suggests confirming a contractor's license with the state or county and asking for proof of insurance.

That makes a fair template for a tree company's own drafts: every estimate goes out in writing once the arborist has priced it, and no draft asks for cash up front or pushes for a same-day signature. If a customer asks about the arborist's ISA credential, the draft can point to ISA's public Find an Arborist directory, which ISA offers for verifying holders; listing is voluntary, so the owner checks the entry shows first. The Bots draft nothing about insurance coverage, and whether a contract meets a state's rules is a question for the owner's lawyer.

Grok Bot's documentation suggests starting with read-and-prepare work and the smallest roster that covers it. Estimate Prep fits: it only lays out sheets. Storm Triage carries the most at stake, which is why its rules must be on paper before any Bot runs them.

A sensible first step is the workflow automation readiness assessment. It is ungated and rates a single workflow on twelve fixed dimensions, among them repeatability, rule clarity, ownership clarity and security and compliance readiness, then gives an immediate verdict (not ready yet, standardize first, good automation candidate or high-leverage candidate) naming its blockers and a next step. Score the photo-estimate workflow, from a customer's pictures to a priced sheet. Expect data availability to suffer if photos arrive by email, web form and the owner's own phone, and manual re-entry to show if the arborist's lines are retyped into the job software; storm triage is scored in the storm triage article.

One point belongs in that scoring. All of an owner's Bots share one computer and its sign-ins, and separate Bots are not a security boundary, so the bank and payroll stay off it or move to a separate user account, and the owner signs out of any city permit site after each search. Once the result is in, Aevrion Ops can scope the chosen workflow on a call booked through the contact page, including how the job software would be connected, so far as the vendor's API and terms permit and once tested.

1. OSHA names falls, electrocutions and being struck by trees as leading hazards; the ten-foot line distance, the drop zone and the rigging decision are judgments made at the tree.
2. A triage Bot sorts storm requests into life-safety, structure-impact and routine under the owner's rules, and wire cases go to the utility and emergency services.
3. Photo estimate sheets label the pictures and leave every method and price line blank for the arborist; the Bot never estimates a tree's size from a photo.
4. Protected-tree rules are local: England's Tree Preservation Orders, Austin's nineteen-inch line, Portland's twelve-inch line. The owner confirms them for each job.
5. Post-storm drafts follow the FTC's advice to homeowners, with written estimates and contracts and no request for cash up front, and no draft gives an arrival time.