Free OpenClaw Skill for Tree Service Companies: Dispatcher and Estimator Agent (Download)

What this skill does for your tree service companies

• Triages inbound storm calls by urgency (limb on house, blocking driveway, hazard tree near power) and routes to the on-call crew with ETA.
• Follows up on outstanding estimates with the 48-hour, 7-day, and 21-day cadence keyed to job dollar value and homeowner objection.
• Compiles the recurring trim recall list each season (deciduous late-winter, oaks summer-only for oak wilt regions) from your ArboStar or SingleOps customer history.
• Drafts the TCIA ANSI A300 work specification language for every proposal so estimators stop hand-writing the same boilerplate.
• Flags OSHA 1910.269 line-clearance jobs for utility coordination before the crew rolls out.

What's inside this OpenClaw skill

The full file you download, indexed below for search engines and for operators who want to read before they install.

---
name: tree-service-dispatcher-and-estimator
description: Storm dispatch triage, estimate follow-up, recurring trim recall, and TCIA ANSI A300 documentation for ISA Certified Arborist tree service companies. Integrates with ArboStar, SingleOps, Jobber.
version: 1.0.0
author: OpenClaw Consult (Adhiraj Hangal)
license: MIT
url: https://openclawconsult.com/skills/tree-service-companies
---

# OpenClaw Skill: Tree Service Dispatcher and Estimator

## Overview

This skill turns the OpenClaw agent into the dispatch-and-estimate layer for a
tree service company. It owns storm-call triage, outstanding estimate
follow-up, recurring trim recall, and the boilerplate ANSI A300 specification
language that estimators repeat on every proposal.

It is designed for ISA Certified Arborist crews running 1 to 8 trucks, with
600 to 4,000 active customers, on ArboStar, SingleOps, or Jobber. Single-yard
and multi-yard operations both work.

## What this skill does

1. Triages inbound storm calls and voicemails by hazard urgency
2. Follows up on outstanding estimates with cadence keyed to job dollar value
3. Compiles seasonal recurring trim recall lists from CRM customer history
4. Drafts ANSI A300 specification language for every proposal
5. Flags OSHA 1910.269 line-clearance jobs for utility coordination
6. Routes hazard-tree calls and oak wilt season conflicts to a human by default

## Triggers

```yaml
triggers:
  - type: heartbeat
    schedule: "0 6 * * *"           # Daily 6am
    action: triage_overnight_voicemails

  - type: heartbeat
    schedule: "0 8 * * 1"           # Mondays 8am
    action: compile_estimate_followup_queue

  - type: heartbeat
    schedule: "0 7 1 * *"           # 1st of month, 7am
    action: compile_seasonal_recurring_recall

  - type: on_event
    event: crm.lead_created
    action: route_to_estimate_or_emergent

  - type: on_event
    event: weather.severe_alert
    action: prep_storm_dispatch_queue

  - type: on_event
    event: crm.estimate_sent
    action: enter_estimate_followup_cadence
```

## Workflow: storm dispatch triage

When voicemails or web requests land in the queue after a storm, the agent:

1. Reads the call transcript or web form text
2. Classifies into one of four buckets: EMERGENT, URGENT, ROUTINE, ESTIMATE
3. EMERGENT: contact with a structure, blocking access, contact with overhead
   lines, hazard tree leaning over a play area or vehicle
4. Pulls the customer's address and checks proximity to utility lines via the
   stored notes from prior visits
5. Drafts an SMS reply with an ETA window for emergent and urgent calls
6. Routes EMERGENT for office manager sign-off before sending; URGENT through
   ROUTINE auto-reply once the manager approves the daily batch

The skill defaults to conservative triage. A borderline call always routes to
a human rather than under-triaging a hazard.

## Workflow: estimate follow-up

When an estimate is sent from the CRM, the agent enters the customer into the
follow-up cadence keyed to dollar value:

- Under $1,000: 48h text, 7-day email, then drop
- $1,000 to $5,000: 48h text, 7-day call reminder for the estimator, 14-day
  email, 21-day final nudge
- Over $5,000: 48h text, 7-day estimator call reminder, 14-day personal email
  from the owner, 30-day "still around if you want to revisit" email

The agent reads the estimator's notes on the customer's stated hesitation
(price, timing, second opinion, HOA approval needed) and tailors the message
copy to that objection.

## Workflow: seasonal recurring trim recall

On the first of each month the agent compiles the seasonal recall list:

- Deciduous structural pruning: late winter (January to early March) for
  oaks-excluded customers in temperate zones
- Oak pruning: winter dormancy only in oak wilt regions, otherwise general
  dormancy window
- Crown thinning and elevation: spring through early summer for general care
- Hazardous deadwood removal: any season, prioritized by years-since-last-visit
- Fertilization and soil care: late fall

The skill pulls every customer with a recurring service flag in the CRM, finds
the customers due this month based on years-since-last-service, and drafts a
recall message referencing the specific tree species and the work last done.

## Workflow: ANSI A300 specification drafting

For every proposal, the agent drafts the ANSI A300 specification language:

- Part 1 pruning: Class I (fine pruning), Class II (medium pruning), Class III
  (hazard reduction), Class IV (crown reduction) with the percentage removal
  cap stated
- Part 9 hazard tree risk assessment: target zone, probability of failure,
  probability of impact, consequences
- Part 7 lightning protection: when installed, the conductor specifications

Every drafted spec is reviewed by the ISA Certified Arborist or TRAQ-qualified
estimator before the proposal goes out. The skill is a drafting assistant, not
a substitute for the credentialed arborist's judgment.

## Workflow: OSHA 1910.269 utility coordination

When a job is flagged within 10 feet of an energized conductor, the agent:

1. Pulls the customer's utility provider from the address lookup
2. Drafts the utility coordination request for the office
3. Holds the job in the queue until utility coordination is confirmed
4. Will not auto-schedule the crew to that job until a human signs off

If the company runs a separate line-clearance qualified crew, the skill can
route those jobs to a different queue with separate dispatch logic.

## Memory keys

```yaml
memory:
  - key: tree.estimate_followup[{customer_id}]
    description: Current cadence stage for an outstanding estimate
    values: [pending, day_2_sent, day_7_sent, day_14_sent, day_21_sent, won, lost]

  - key: tree.recurring_schedule[{customer_id}]
    description: Next seasonal recall and last service done
    schema: { service_type: string, last_service: date, next_recall: date, tree_species: string }

  - key: tree.storm_call_log[{call_id}]
    description: Storm call triage record
    schema: { urgency: enum, address: string, hazard_type: string, eta_quoted: datetime, dispatched_crew: string }

  - key: tree.line_clearance_queue[{job_id}]
    description: Jobs pending utility coordination
    schema: { utility_provider: string, coordination_requested: date, coordination_confirmed: date }
```

## Message templates

```yaml
templates:
  storm_emergent_dispatch:
    channel: sms
    body: |
      Hi {customer_first_name}, this is {company_name}. We got your call about
      {hazard_summary}. We have a crew coming to you between {eta_start} and
      {eta_end} today. Stay clear of the tree and any wires until we arrive.
      Call back at this number if anything changes.

  estimate_followup_48h_under_5k:
    channel: sms
    body: |
      Hi {customer_first_name}, this is {estimator_first_name} from
      {company_name}. Wanted to make sure the proposal I sent for
      {job_short_description} came through. Any questions on the work scope or
      the timing? Happy to walk through it.

  estimate_followup_owner_personal_over_5k:
    channel: email
    subject: "Following up on the {job_short_description} proposal"
    body: |
      Hi {customer_first_name},

      {estimator_first_name} mentioned the proposal we sent over for your
      {tree_species} work. Wanted to follow up personally because the job has
      a couple of moving parts (the {specific_complexity_factor}) that are
      worth talking through.

      If you have ten minutes this week, I am happy to come by myself to walk
      the property and answer anything. Otherwise, no pressure and we will
      circle back next month.

      {owner_first_name}
      {company_name}

  recurring_trim_recall:
    channel: email
    subject: "Time for your {tree_species} structural prune?"
    body: |
      Hi {customer_first_name},

      Last time we were at your property in {last_visit_month_year} we did
      {last_service_description} on your {tree_species}. Best practice is to
      come back every {recommended_interval_years} years for structural
      pruning, and you are due.

      Open windows that fit the dormancy schedule for your {tree_species}:
      {available_windows}

      Want me to put you on the calendar?

      {office_first_name}
      {company_name}

  ansi_a300_proposal_block:
    channel: proposal_pdf
    body: |
      Work specification (ANSI A300 Part 1, Class {pruning_class}):
      {pruning_class_definition}

      Percentage removal cap: not to exceed {percent_cap}% of live foliage on
      any single specimen, consistent with ANSI A300 best practice.

      Branch collar treatment: cuts made at the branch collar without flush
      cuts or stub cuts, per ANSI A300 Part 1.

      Crew credentials: ISA Certified Arborist on-site, TCIA Accredited
      company, OSHA 1910.269 line-clearance qualified personnel as required.

      Insurance: General liability and workers compensation coverage
      certificates available on request.
```

## Required integrations

| Integration            | Purpose                                       | Read | Write    |
|------------------------|-----------------------------------------------|------|----------|
| ArboStar               | Jobs, customers, proposals, scheduling        | yes  | optional |
| SingleOps              | Jobs, customers, proposals                    | yes  | optional |
| Jobber                 | Jobs, customers, quotes                       | yes  | optional |
| Answering service      | Voicemail intake (Twilio, CallRail, etc)      | yes  | no       |
| Twilio (or similar)    | Outbound SMS                                  | no   | yes      |
| Email provider         | Outbound email (SendGrid, Postmark, etc)      | no   | yes      |
| Weather alert feed     | NWS severe storm alerts for the service area  | yes  | no       |
| OpenClaw Memory        | Cross-run state                               | yes  | yes      |
| OpenClaw Heartbeat     | Scheduled cadence and recall triggers         | yes  | yes      |

Write-back to the CRM is optional. Most companies start with read-only and
have the office manager commit any CRM changes manually. Once trust is built,
flip write access on for low-risk fields (note appends, recall date updates).

## Safety notes

The skill respects OSHA 1910.269 line-clearance rules: no job within 10 feet
of an energized conductor goes to a non-line-clearance qualified crew. The
skill respects state-level oak wilt restrictions where active (Texas A&M
Forest Service guidance for Texas, Minnesota Department of Natural Resources
for the upper Midwest). Editable in the config block.

The skill will not draft a proposal that promises a specific tree's recovery
from a disease, structural defect, or pest infestation. Those judgments stay
with the ISA Certified Arborist on the ground.

## Configuration

```yaml
config:
  company_name: "Your Tree Service"
  isa_certified_arborists:
    - name: "Arborist Name"
      isa_credential: "WE-XXXXA"
      traq_qualified: true
  approval_mode: manager_approves_all   # or "autonomous_after_2_weeks"
  storm_dispatch_buckets: [EMERGENT, URGENT, ROUTINE, ESTIMATE]
  line_clearance_qualified_crews:
    - crew_name: "Crew 3"
  oak_wilt_region: false                # set true for Texas, MN, IA, etc.
  estimate_followup_brackets:
    under_1k: [48h, 7d]
    one_to_five_k: [48h, 7d, 14d, 21d]
    over_5k: [48h, 7d, 14d, 30d]
  recurring_recall_seasons:
    deciduous_structural: ["January", "February", "March"]
    oak_pruning_dormancy: ["December", "January", "February"]
    fertilization: ["October", "November"]
```

## Quick install

```bash
mkdir -p ~/.claude/skills
mv tree-service-companies.md ~/.claude/skills/tree-service-dispatcher-and-estimator.md
# Edit the config block to match your company
```

Launch OpenClaw and the skill is live. Run `triage overnight voicemails` or
`compile estimate followup queue` to invoke it on demand, or wait for
Heartbeat to fire it on the configured schedule.

## Want it wired to your stack?

This SKILL.md is the starting point. If you want it plugged into your specific
CRM, your answering service, your utility-coordination process, and your crew
dispatch on a fixed-price two-week clock, with the founder writing every line
of the build, the door is at https://www.adhirajhangal.com/work

Install in 60 seconds

1. 1

   Drop the file into your OpenClaw skills directory

   Save the downloaded tree-service-companies.md as ~/.claude/skills/tree-service-dispatcher-and-estimator.md (or scope it per crew in your project-level .claude/skills/). OpenClaw picks up new skill files on next agent launch, no restart command required.

2. 2

   Connect your ArboStar, SingleOps, or Jobber instance

   Edit the integrations block to point at your ArboStar API, SingleOps export, or Jobber feed. Read access to jobs, customers, and proposals is enough to start. The skill ships prompts that translate each CRM's job export into the agent's working memory.

3. 3

   Launch in approval mode, then move to autonomous on safe templates

   Start with the office manager approving every outbound text and email for two weeks. The skill's defaults route anything that touches a hazard-tree call, a quote over $5,000, or a utility-line job to a human. After two weeks of validation, flip the recurring-trim and standard estimate-follow-up templates to autonomous.

Example conversation

Common questions

Related free skills