Skip to content
Techila Global Services
Techila/Insights/Agentforce for Field Service: A Practical Guide

Agentforce · 11 min read

Agentforce for Field Service: A Practical Guide

Category

Agentforce

Read time

11 min read

Author

Techila Agentforce Practice

Published

22 Nov 2026

Last updated

22 Nov 2026

What Agentforce adds to Salesforce Field Service and Operations for dispatchers, technicians and customers, which features Salesforce lists as generally available, the licenses and data you need, published pricing, first use cases, rollout steps, metrics and pitfalls.

Agentforce for Field Service adds AI agents and generative AI to Salesforce Field Service, which Salesforce now calls Field Service and Operations. Dispatchers get natural-language help with schedules and exceptions, technicians get pre-work briefs, on-site knowledge answers and post-work summaries in the mobile app, and customers can book, change or cancel appointments with a Scheduling Agent. It runs on your existing work orders, service appointments, resources, territories and assets.

This guide covers what Salesforce says the product does today, what you need in place, published pricing, and how to roll it out without disrupting the field. New to Agentforce? Start with what Agentforce is.

What is Agentforce for Field Service?

It is an add-on to Field Service and Operations. Salesforce's Agentforce for Field Service pricing page describes it as assistive AI for dispatchers and mobile workers, unmetered employee agent usage and an operations suite powered by Tableau Next. Trailhead's introduction to Agentforce Field Service groups the work into three areas: scheduling, mobile workers and dispatchers, plus monitoring tools to review agent conversations.

Names vary: the product page says "Agentforce for Field Service and Operations", Trailhead says "Agentforce Field Service" and older material says "Einstein for Field Service". Check which features a proposal means, not which label it uses.

What does Agentforce do for dispatchers, technicians and customers?

Agentforce capabilities in Field Service, as described on Salesforce pages read 22 November 2026
WhoWhat Salesforce describesRelease status Salesforce states
Technicians, before the jobPre-work brief: an AI summary of the work order, customer history and asset details, which can be played back as audio on the goGenerally available since 9 April 2025, as part of Einstein for Field Service
Technicians, on siteOn-site knowledge search and troubleshooting answers from knowledge sources; multimodal troubleshooting is in the add-on's feature listOnsite troubleshooting announced as generally available in June 2025
Technicians, after the jobPost-work summary (job wrap-up) and service notes summaryJob wrap-up generally available since 9 April 2025
DispatchersNatural-language help to find appointments that need attention, resolve conflicts, fill schedule gaps, reassign work and locate parts; schedule summaryResolving schedule gaps generally available since 9 April 2025
CustomersBook, reschedule and cancel appointments in their preferred channelScheduling appointments announced as generally available in May 2025
Customers and dispatchersScheduling Agent across web chat, SMS, iMessage, WhatsApp, email and voice; Autonomous Scheduling with Agentforce Voice in Winter '27Not stated on the pages we read; confirm for your org

The release dates come from Salesforce's 9 April 2025 announcement, which also advises basing buying decisions on released features only.

The Scheduling Agent

Salesforce previewed the Scheduling Agent in a blog post on 8 September 2026, ahead of Dreamforce. It books, reschedules and cancels appointments, including outside business hours; contacts customers to confirm a new time when a dispatcher fills a gap left by a no-show or cancellation; lets technicians book follow-up visits from the mobile app; and can start appointment requests from an asset's health or history. It queries the Field Service scheduling and optimization engine in real time, respecting work rules, skills and territories, and applies fixed rules such as warranty status with deterministic Agent Script logic.

The Winter '27 announcement adds Autonomous Scheduling with Agentforce Voice, and Trailhead's Winter '27 highlights list multilingual voice-to-form and Scheduling Console enhancements. The Winter '27 release became generally available on 12 October 2026, but the pages we read give no status for these items, so confirm them before you plan around them.

What do you need before you start?

Licenses

Salesforce's editions page sets the base rules. Field Service and Operations requires at least one Service Cloud user license. Technicians (mobile employees) and contractors require at least one Dispatcher. Existing Service Cloud customers need at least one Dispatcher license. Per-user products need an annual contract, and Dispatcher and Technician licenses may not be used for a contact center or call center.

A clean Field Service data model

Every feature above reads the core Field Service objects; if they are thin or stale, so are the answers. Review these first:

  • Work orders and work order line items: clear descriptions, work types and statuses.
  • Service appointments: accurate windows, durations and statuses.
  • Service resources, skills and crews: current skills, which the scheduling engine matches on.
  • Service territories and operating hours: territories that match how you really dispatch, with current hours and holidays.
  • Assets and service history: installed assets linked to accounts and locations, with past work attached.
  • Knowledge articles: current, owned and searchable, since on-site answers depend on them.

Data 360 and the Trust Layer

Salesforce names Data 360 for some capabilities, such as Asset Service Prediction and the Tableau Next analytics, so it is a decision per use case, not a day-one requirement for every feature. The Einstein Trust Layer provides secure data retrieval, dynamic grounding, zero data retention, toxic language detection and an audit trail. Trailhead notes that data masking for LLMs is currently disabled for agents, so control what an agent can see through permissions and the fields you ground on. Our Agentforce readiness checklist covers data, permissions and success measures in more depth.

What does Salesforce publish about pricing?

On 22 November 2026, Salesforce's pages showed the following US list prices. Salesforce says prices are for information only and subject to change, so treat them as a starting point for a quote.

Field Service and Operations and Agentforce pricing, as published by Salesforce (read 22 November 2026, USD, Enterprise Edition)
ItemList priceAgentforce notes on the page
Agentforce for Field Service (add-on)$125 per user per monthAssistive AI for dispatchers and mobile workers; unmetered employee agent usage
Dispatcher$175 per user per month, billed annuallyScheduling Agent requires Flex Credits, none included
Technician$175 per user per month, billed annuallyAgentforce for Field Service available for purchase
Field Service+ Core$250 per user per month, billed annually500K Flex Credits per org included for Scheduling Agent
Field Service+ Advanced$450 per user per month, billed annually1M Flex Credits per org included for Scheduling Agent
Field Service Max$650 per user per month, billed annuallyIncludes Agentforce for Field Service and 2.75M Flex Credits per org per year

Unlimited Edition versions of Dispatcher and Technician are listed at $330 per user per month. For how Flex Credits work across Agentforce, see our Agentforce pricing guide, and use the Agentforce cost calculator to model your volumes.

Which use cases should you pick first?

Pick one or two use cases that save time, run on data you trust and that a person can check. In our experience these are the safest starts:

  1. Pre-work briefs for one job type. Low risk, because the technician reads the brief and still does the work. It also exposes gaps in work order and asset data quickly.
  2. Post-work summaries. Ask technicians to check each summary before it goes on the record; the output then feeds service reports and the next visit.
  3. Dispatcher assistance on one territory. Natural-language questions about late jobs and schedule gaps, with the dispatcher still making the call.
  4. Customer self-scheduling. A strong second phase. It is customer-facing, so it needs clean scheduling policies, territories and operating hours first, and a clear handoff to a person.

For manufacturers who also want supply chain or sales agents, see our Agentforce for manufacturing services. If your service desk is the starting point, the Agentforce Service Agent guide covers customer service agents.

How should you roll it out?

  1. Baseline the field. Record today's metrics (below) for the job types in scope.
  2. Fix the data the agent will read. Work orders, appointments, resources, territories, assets and knowledge for those job types, with named owners.
  3. Configure in a sandbox. Turn on features, adapt prompt templates and set permissions.
  4. Test with real jobs. Run a set of real work orders, including awkward ones, and have experienced technicians and dispatchers judge the output.
  5. Pilot with one crew or territory. Train them, collect feedback weekly and fix what they flag.
  6. Expand and monitor. Add territories and job types in stages, review agent conversations in the monitoring tools and re-test after each Salesforce release.

Our Agentforce pilot follows these steps, and our Field Service implementation services cover the data model and scheduling setup underneath.

Which metrics should you track?

Measure before and after on the same job types and territories. We do not quote benchmark gains; results depend on your data, work mix and adoption.

  • First-time fix rate: jobs completed on the first visit, the clearest sign that briefs and on-site answers help.
  • Travel time and jobs per technician per day: whether scheduling and gap-filling make better use of the day.
  • Schedule adherence: arrivals inside the promised window, and how quickly gaps from cancellations are filled.
  • Admin time per job: time spent on notes and service reports after the work is done.
  • Self-scheduling share and handoffs: for customer-facing scheduling, how many bookings finish without a person, and why the others were handed over.

Salesforce's 2025 announcement quotes AAA's VP of Automotive Services saying Agentforce for Field Service cut average response time by five minutes. Treat customer results like this as examples of what to measure, not targets.

What are the common pitfalls?

  • Agents on top of a weak data model. Missing skills, stale territories or thin work orders produce confident but wrong answers.
  • Starting with the customer. Self-scheduling before the scheduling policies are right exposes every gap to customers first.
  • Planning around previews. A blog preview or Dreamforce demo is not a release. Plan on features Salesforce lists as generally available.
  • Underestimating credits. Scheduling Agent uses Flex Credits; estimate volumes before choosing an edition.
  • Skipping the technicians. If crews were not part of testing, they will not trust or open the briefs.

Where does Techila fit?

Techila Global Services is a Salesforce Summit Partner and a member of the Agentforce Partner Network, headquartered in Frisco, Texas, with more than 700 projects delivered and more than 500 Salesforce certifications across our team. We implement Field Service and the Agentforce features on top of it, from data model to monitoring. See our Agentforce implementation services and Manufacturing Cloud services for related work.

Frequently asked questions

What is Agentforce for Field Service?

It is Salesforce's add-on that brings AI agents and generative AI into Field Service and Operations, the product formerly called Salesforce Field Service. Salesforce lists pre-work briefs, on-site knowledge search, post-work summaries, resolving schedule gaps and schedule summaries among its features, used by dispatchers and mobile workers inside the tools they already work in.

How much does Agentforce for Field Service cost?

On 22 November 2026, Salesforce's pricing page listed Agentforce for Field Service at $125 per user per month, and said prices are for information only and subject to change. Scheduling Agent is priced separately: it needs Flex Credits, and the Field Service+ Core, Advanced and Max editions include a pool of them per org. Confirm current terms with Salesforce.

Do we need Data 360 to use Agentforce in Field Service?

Not for every feature. Pre-work briefs and post-work summaries ground on the work order, asset and history records already in your org. Salesforce does name Data 360 for capabilities such as Asset Service Prediction and the Tableau Next analytics. Decide per use case, and start with the ones that run on the Field Service data you already keep.

Which Field Service licenses are required?

Salesforce's pricing page says Field Service and Operations requires at least one Service Cloud user license, that technicians and contractors require at least one Dispatcher, and that existing Service Cloud customers need at least one Dispatcher license. Per-user products need an annual contract. The Agentforce add-on is bought on top, unless your edition includes it.

What is the Scheduling Agent in Field Service?

Salesforce describes Scheduling Agent as an always-on agent that books, reschedules and cancels appointments across web chat, SMS, WhatsApp, email and voice, and that checks the Field Service scheduling and optimization engine for work rules, skills, availability and territories. The pages we read on 22 November 2026 did not state its release status, so confirm it for your org.

Which use case should a field service team start with?

Start with work done by hand today on data you trust: a pre-work brief for one job type, post-work summaries, or dispatcher help on one territory. Customer self-scheduling is a strong second step once scheduling policies and territories are clean.

Next steps

Pick one job type, baseline its metrics and check the data behind it against the list above. If you want help scoping the first use case or reviewing your Field Service setup, talk to a Field Service specialist.

Talk to an expert about Salesforce Field Service implementation

All fields are required unless marked optional.

We save these details on this device to fill them in next time.

Add project details (optional: clouds, users, start date, role)
Salesforce clouds (optional, choose any)Which Salesforce clouds are involved?
Salesforce users (optional)How many Salesforce users?
Start date (optional)When do you want to start?
Your role (optional)What is your role?

We reply within 1 business day.

By sending this form, you agree that Techila Global Services may contact you by email or phone about your request. We do not sell your personal information. See our Privacy Policy.

Working on something like this?

We reply within 1 business day · +1 617-777-9873

See case studies