Field services · GuardenerAI Automation

Automation for field service businesses.

Field service businesses use GuardenerAI Automation to lay down the same follow-up tasks after every job with action plans, keep customer and site contact records clean with validation and duplicate rules, and run routine steps from a chat command with workflows.

The work on site is only half the job. The follow-up call, the review request and the next maintenance visit are where repeat business comes from, and they are exactly what slips in a busy week.

Start free → Book a walkthrough

Action plans for every kind of job

An action plan is a list of tasks with subjects, priorities and timing. Apply it to the customer and every task lands with a due date.

  • An installation plan: welcome call on day one, check-in after a week, maintenance reminder at six months.
  • A repair plan: follow-up call the next day, then a review request two days after that.
  • Timing counts from the plan start or from an earlier task in the plan.
  • Apply plans to the customer company or the opportunity, so the tasks sit where the relationship lives.

Clean customer and site records

Rules check built-in records every time they are saved.

  • A validation rule can require a phone number on every person before they are saved.
  • An enrichment rule can set a region on a company from its state, using a decision table you write.
  • Duplicate rules flag a new person or company that matches an existing one by name or normalised phone, for review in the queue.
  • Rules run on built-in objects only, not on the Work Orders object the template adds.

Routines from a chat command

A workflow chains an AI agent step with actions such as creating a task or a note, and runs when someone starts it.

  • Start a workflow from the chat slash menu, or ask the assistant to run it on a record.
  • Every run is listed under Workflow executions with the status of each step.
  • Workflows do not fire on their own from record changes or a schedule.

How to set it up

  1. Apply the Field Services starter template for Work Orders, task types and outcomes.
  2. Build an action plan per job type, with tasks, priorities and day offsets.
  3. Add validation and duplicate rules for persons and companies.
  4. Apply the right action plan to the customer after each job.
  5. Build a workflow for any routine you repeat, and run it from chat.

Worth knowing

  • Validation and enrichment rules do not run on custom objects such as Work Orders.
  • Workflows start from a chat command or the assistant; there are no record-change, schedule or webhook triggers.
  • Action plan tasks carry a subject, priority and timing, but not a task type.
FAQ

Fair questions.

Can a plan start automatically when a work order is completed?
No. Action plans are applied by a person, and workflows start from chat. Make applying the plan part of closing the job.
Can rules check work order fields?
No. Rules run on built-in objects such as persons, companies, opportunities, tasks and invoices, not on custom objects.
Does it dispatch technicians?
No. There is no dispatch or route planning. The template adds Technician and Scheduled fields to Work Orders and views such as Urgent dispatch.