What is actually changing in field service technology

Four shifts are reshaping field operations: scheduling by policy rather than by person, agentic first-line service, asset data driving preventive work, and customers expecting portal-level visibility as standard.

Scheduling moves from a person to a policy

Dispatch by whiteboard or spreadsheet caps daily job capacity at whatever one coordinator can hold in their head. Scheduling policies with skills, certifications, travel time and SLA weighting raise capacity without adding vans — and make emergency insertion safe rather than disruptive.

First-line service becomes agentic

Routine status and rescheduling contacts no longer need a person. Agentforce answers from the live work order, writes changes back, and escalates with the history attached. It runs inside your Salesforce org, so sharing rules and audit hold — which is what makes it approvable in regulated operations.

Asset data turns reactive work preventive

Asset hierarchies, service history and readings captured on the job make preventive maintenance schedulable from the contract rather than from memory. First-time fix improves because parts and history are on the work order before the engineer arrives.

Customers expect visibility

Housing authorities, facilities managers and consumers all now expect to see job status without phoning. An Experience Cloud portal removes the calls that only ever asked where the engineer is — the pattern Ignyto built for Bridge Heating.

What to do about it

• Baseline jobs per engineer per day, first-time fix and travel time before changing anything.
• Move scheduling into policy before adding AI — an agent cannot fix a schedule nobody trusts.
• Get asset and parts data into the work order; it is the precondition for both prevention and deflection.
• Give customers the portal before they ask for it.

Common questions