Skip to content
Industries

Field Services

The tech should be on the job. Not calling the office to ask what’s open and who they saw last time.

How it runs now

  • Dispatch filled the day. The callback from Tuesday never got a truck.
  • The AM is hunting renewals. The tech already knows which site is a mess.
  • The work order closed. The notes are still in the van.

What Bruce does

  • The field

    Bruce has the stop: which job, why, what they found last visit. The tech runs it. They talk to Bruce on the way out. The notes aren’t still in the van.

  • Renewals

    The site that used you every month went quiet. Bruce puts that in front of the AM with the last job. The quote is still a person.

  • Support

    The callback and the “is anyone coming” call. Bruce already has the last ticket.

  • Collections

    The work order closed. The invoice is aging. Bruce works it. The write-off waits.

Bruce at work: Field Services

Bruce
Bruce
Field Services
FSM

The board

4402 Oak — callback
Tuesday job · no truck went back
Active
Customer called again at 7:10
Open window today 1–4
Last visit: failed capacitor
Riverside Packing
Monthly site · quiet 6 weeks
Hold
Last job was the chiller
AM has not called
Quote draft is ready
Job 8812
Closed yesterday
Done
Notes from the van are in the work order
Parts ticket closed

Dispatch

Who does Mike run first?

Dispatch•7:20 AM
Bruce

Oak. They called again. Capacitor failed Tuesday. Window is 1–4. I put the last ticket in his brief.

Riverside can wait. The quote is drafted. Don’t send it until the AM looks at it.

Oak on Mike’s board · Riverside hold

Bruce•7:21 AM
FSMInventoryWork ordersCustomer phone

Start with the function that hurts

Same agents as Solutions. These are the ones this week uses.

Out of the box

What Bruce brings

The difference is what Bruce brings out of the box: a context graph, an execution graph, a feedback and eval layer, built-in enterprise execution, and a control plane.

  1. 01

    Context graph

    The picture of the enterprise stays current — structured and unstructured. Context is added, updated, and dropped when it goes stale. It is not a database we sell. It is the thing that dies in a thread.

  2. 02

    Execution graph

    Intent, then the tools, then a check, then recover, then done. Learned on real workflows. A miss does not kill the run.

  3. 03

    Feedback and evals

    Production traces, human corrections, failures, edge cases. Execution gets sharper from that. We score completion on ESE-1.

  4. 04

    Built-in enterprise execution

    The agents are already built. Role and workflow patterns from real businesses — sales, purchasing, finance, operations. Bruce already knows how that work runs.

  5. 05

    Control plane

    Permissions, approvals, what you can see, the log, and policy. Required if it acts on its own.

Bruce executes the business across the systems you already run. Connect the systems you run. In most cases it is working in under an hour.

Manual

The field

Field Mode