Field work orders that dispatch, schedule, and close themselves.

The whole configuration surface: work types and templates, per-agent limits like travel radius and working hours, the dynamic scheduling and skills-matching setup, dispatch and appointment booking, and the dispatcher workspace. She sets up the machinery that runs the field operation.

What she doesn't do is invent your live jobs. Actual work orders and their tasks are generated day to day by your platform and dispatchers — she reads them to understand your estate, then configures around them.

A field agent isn't one magic record — it's a real person, their group membership, their limits, and the certified skills matched for assignment. Phyllis assembles the agent from those genuine pieces. She also keeps equipment and scheduling assets distinct from people, so a piece of gear never gets dispatched as though it were an agent.

Yes. Advanced capabilities like crew operations, territory planning, capacity and multi-day scheduling are Professional-only and licence-gated. Before using any Pro-tier feature, Phyllis confirms it's actually active on your instance and gives a clear message instead of a raw error — so a plan never assumes something your edition can't run.

No. Phyllis explores, proposes a plan, and builds only after you approve. Everything lands in one scoped, reviewable change set, and nothing is applied — including any fixes after the post-build check — until you approve it.

Every finding is cited back to the exact record it came from in your own instance — your dispatch method, your work types, your scheduling and matching setup. She reads your live instance first, so the plan reflects how your field operation actually runs, not a generic template.