FS-Con-101 Salesforce Certified Agentforce Field Service and Operations Consultant Exam Topics and Questions

Resource management is the foundation everything else in Field Service sits on. Get this wrong and no amount of scheduling logic will save you. This topic covers the people, their capabilities, their time, and the licences that unlock their access. Expect the exam to press you on decisions you would make before a single work order exists: who can do what, when they are available, and which licence tier is appropriate for their role.

– Resource types, crews, and territories

Salesforce Field Service recognises several resource types, and the exam wants you to know which fits which situation. A technician working alone, a crew assembled for a complex job, and a contractor managed through an outside company all behave differently in the scheduler. You need to know when to create a crew versus keeping resources independent, and how crew membership affects availability and scheduling.

Service Territories are not just organisational labels. They carry operating hours, they determine which resources are candidates for a job, and they can be nested so that a broader territory delegates to a smaller one. The exam gives you a business scenario and asks which territory configuration fits. Think about where the resource lives relative to the work, and whether secondary or relocation membership applies.

– Skills, time sheets, and operating hours

Skills and skill levels control whether a resource is even a candidate for a service appointment. Time-based skills add an expiry dimension: a certification that lapses mid-year means the resource drops out of eligibility for jobs requiring it after that date. The exam tests this time-sensitivity specifically, so know how skill validity periods interact with appointment scheduling.

Time sheets and time sheet entries sit below the service resource and connect up to work orders. The relationship chain matters: a service resource logs entries against appointments that are tied to work orders, and that chain is how labour gets tracked and billed. Operating hours are reused across the data model in four places: the resource, the account, the work order, and the booking slot. Each layer can restrict availability, and the exam asks you to reason about which layer is causing a constraint in a given scenario.

– Licence types and deployment decisions

Field Service licence types are a practical decision point, not a trivia question. The exam frames this as a scenario: a dispatcher who never goes into the field, a mobile technician who needs offline access, a contractor who only needs limited visibility. Each profile maps to a licence type, and assigning the wrong one either over-spends the budget or denies the user the features they need.

Know the functional difference between the Field Service licence and the Salesforce licence in a Field Service context. Know what the mobile-specific licence unlocks. The exam will not ask you to recite a price list, but it will give you a workforce composition and ask which licence mix covers it correctly.

How Managing Resources is tested

At 16%, this topic appears often enough that a gap in one area will cost you points across multiple items. Most items are scenario-driven: you are given a workforce structure, a territory layout, or a scheduling constraint, and you must identify the root cause or the right configuration choice.

The traps are usually in the details of the data model. Candidates who treat service territories as simple groupings miss questions about primary versus secondary membership and how relocation membership extends a resource's reach. Candidates who know skills exist but have not studied time-based skills will lose marks on items where certification expiry is the deciding factor.

Operating hours items are another common loss point. The exam stacks multiple layers of operating hours and asks which one limits availability in a specific scenario. Work through each layer methodically rather than stopping at the first restriction you find. Licence-type items reward knowing the functional boundary, not the commercial tier name.

Work Orders are the operational core of Salesforce Field Service, and at 23% this is the heaviest topic after scheduling. Where the previous topic was about who does the work, this one is about what the work is, how it is structured, and how it connects to the people and appointments carrying it out. Misconfigure a work type or a milestone and you affect every order that inherits from it, so the exam tests configuration decisions at the template level as much as the individual record level.

– Work Order configuration and Work Types

Work Types are reusable templates that stamp defaults onto Work Orders at creation: estimated duration, required skills, service contracts, and more. The exam tests whether you know which settings belong on the Work Type versus which should be set directly on the Work Order. If a default applies to every job of a particular kind, it belongs on the Work Type. If it varies by customer or location, it belongs on the record.

Work Order processes and parameters include the status values that drive lifecycle progression, the auto-creation rules that generate service appointments, and the field-level settings that control what dispatchers and mobile workers can edit. Know how these interact. A misconfigured status transition can block a work order from closing even when all the field work is complete.

– Line Items, Resource Preferences, and Products

Work Order Line Items let you break a single work order into distinct tasks, each with its own status, duration, and skill requirements. The exam asks when you should use line items versus keeping everything at the work order level. The answer depends on whether the sub-tasks need independent tracking, separate appointments, or different resource assignments.

Resource Preferences let an account or a work order express a preference for, or an exclusion of, a specific resource. The exam presents a scenario and asks which preference type applies. Excluded resources are never scheduled to that account; preferred resources are favoured but not guaranteed; required resources must be assigned. Products Required connect inventory to the work order before the job starts, ensuring the technician arrives with the right parts. Know how this differs from products consumed, which are recorded after the work is done.

– Milestones and the Appointment relationship model

Work Order Milestones track time-sensitive obligations, typically drawn from an entitlement or a service contract. The exam tests configuration: which milestone fields trigger warnings, how breach and warning actions fire, and what happens when a milestone is paused. Candidates who treat milestones as simple timestamps miss the conditional logic that drives automated actions.

The relationship between Service Appointments, Work Orders, and Work Order Line Items is the most architecturally important concept in this topic. A service appointment can be linked to the work order header or to an individual line item. When a complex job has multiple appointments tied to different line items, the scheduling and completion logic changes. The exam gives you a scenario and asks which relationship model supports the stated business requirement. Think about whether independent scheduling of sub-tasks is needed, and whether completion of one appointment should gate the next.

How Managing Work Orders is tested

At 23%, this topic places more items in front of you than any other except scheduling. Expect a mix of configuration questions and scenario-based relationship questions. The configuration questions are specific: they describe a business rule and ask which Work Order setting or Work Type parameter implements it. The relationship questions give you a field service operation and ask which object model connects the pieces correctly.

Candidates lose marks by conflating Work Order and Work Order Line Item behaviour. The exam will describe a situation where independent scheduling is required for sub-tasks and reward the answer that routes appointments to line items rather than the header. Milestone questions trap candidates who know what milestones are but have not studied the warning and breach action configuration. Resource Preference items reward precision: the three preference types are distinct, and choosing the wrong one changes the scheduler's behaviour in ways the scenario makes visible. Products Required versus products consumed is another reliable loss point for candidates who have not traced the full order lifecycle.

At 28%, this is the single largest topic on the exam. Scheduling and optimization in Salesforce Field Service is where configuration decisions have the widest operational impact, and the exam reflects that by testing across a broad range of settings, policies, and dispatch strategies. You will need to reason about what the scheduler does when constraints compete, what the optimizer does when the schedule is already running, and how DateTime fields track state throughout the appointment lifecycle.

– Field Service settings and the Dispatcher Console

The SFS Administrator settings control defaults that affect every scheduling action taken in the org. Knowing which settings govern automatic scheduling, which control travel time calculation, and which affect resource matching is essential before you can reason about any scenario question in this topic.

The Dispatcher Console is the operational surface where scheduling decisions play out in real time. The exam tests filtering: which filter options narrow the candidate list by territory, skill, or availability, and how combining filters changes which resources appear. Aerial versus street-level routing is a specific distinction the exam expects you to know. Aerial routing calculates straight-line distance and is faster to compute but less accurate for travel time. Street-level routing uses road networks and produces more realistic estimates. The choice affects schedule density and the accuracy of arrival windows given to customers.

– Service Appointment lifecycle and Complex Work

A Service Appointment moves through a defined set of statuses from creation to completion, and each transition carries implications for what the scheduler, the dispatcher, and the mobile worker can do. The exam gives you a lifecycle scenario and asks which action is appropriate at a given status. Know the difference between scheduling, dispatching, and completing an appointment, and know what happens when an appointment is cancelled or cannot be completed.

Complex Work covers scenarios where a single job requires multiple resources simultaneously, sequential appointments, or appointments spanning more than one day. Multi-day service appointments have their own configuration requirements and behave differently from chaining standard appointments. The exam tests when to use each approach. Think about whether the work genuinely cannot be interrupted versus whether it simply takes a long time: that distinction drives the configuration choice.

– Schedule Policies and dispatch strategies

Schedule Policies are rule sets that tell the scheduler which objectives to optimise for: minimising travel, respecting skills, prioritising high-value customers, or some weighted combination. The exam asks you to read a business requirement and identify which policy configuration achieves it. A policy that minimises travel time will produce a different schedule from one that prioritises customer priority scores, and the exam wants you to reason about that trade-off.

Dispatch strategies determine how appointments are pushed to field workers. An organisation that wants dispatchers to retain control uses a different strategy from one that automates dispatch on scheduling completion. The exam frames this as a scenario: given the org's operational model, which dispatch strategy fits? Know the implications of each option for dispatcher workload and for the mobile worker's experience.

– Scheduling and optimization services, and DateTime tracking

The exam distinguishes between the types of scheduling service (manual, assisted, and automated) and the types of optimization service (in-day, overnight, and global). Each has a different trigger, a different scope, and a different cost in terms of processing time. Choosing the wrong optimization type for a scenario wastes capacity or fails to meet the business's responsiveness requirement.

DateTime tracking fields in Salesforce Field Service record when appointments are scheduled, dispatched, in progress, and completed. The exam tests what each field captures and which field to query when you need to answer an operational question about timing. Candidates who treat these as interchangeable lose marks on items where the distinction between when something was scheduled and when it was actually started is the point of the question.

How Managing Scheduling and Optimization is tested

With 28% of the exam drawn from this topic, the item count alone means you cannot afford broad gaps here. Items range from direct configuration knowledge to multi-constraint scenario reasoning. The scenario items are the hardest: they describe an operational situation with several plausible actions and reward the one that fits the stated business requirement most precisely.

Candidates lose marks most often by conflating scheduling and optimization services. Knowing that optimization exists is not enough; the exam rewards knowing which type of optimization applies to which operational window. Schedule Policy items trap candidates who know the policy names but have not reasoned through what each objective does to the resulting schedule.

The DateTime tracking field items are a reliable loss point for candidates who have not worked with the data model directly. Items in this area reward knowing which field is populated at which lifecycle stage. Complex Work items reward understanding the architectural difference between multi-day appointments and chained standard appointments. Read the scenario constraints carefully before choosing between them.

After the depth of scheduling, mobility is a focused topic: 10% of the exam, four sub-topics, and a clear boundary between what the Field Service mobile app does and what the standard Salesforce mobile app does. The exam tests whether you can configure the mobile experience to match a business process, not whether you can describe the app in general terms. Configuration choices here affect what field workers see, what they can do offline, and how customer sign-off is captured.

How Configuring Mobility is tested

Items in this topic are largely scenario-based. You are given a business process, such as capturing a customer signature at job completion or restricting which records a technician can edit in the field, and asked which configuration achieves it. The trap is confusing Field Service Mobile capabilities with those of the standard Salesforce mobile app. The two apps share some surface area but diverge on offline behaviour, available actions, and the settings that control them.

The customer sign-off process has specific requirements and a specific set of tools in the Field Service app. Candidates who know the sign-off exists but have not studied the configuration steps lose marks on items that ask which setting or component enables it.

SFS Mobile settings items reward knowing which settings are available and what each one controls. The exam does not ask you to recall a settings menu from memory; it describes an outcome and asks which setting produces it. Read the scenario requirement precisely, because several settings are adjacent and the distinction between them is the point of the item.

Inventory sits at the intersection of field operations and financial accuracy. At 8%, this topic is narrower than the ones before it, but the exam tests it with precision. The three sub-topics cover how products are priced when consumed on a job, how the inventory model is structured to reflect where parts live and move, and what happens when something needs to come back. A candidate who has studied the scheduling and work order topics but skipped inventory will lose marks that are straightforward to recover.

How Managing Inventory is tested

Inventory items tend to be more model-focused than the scenario-heavy questions in scheduling. The exam describes a business requirement around product consumption or returns and asks which object, configuration, or process supports it.

Price book items reward knowing that different price books can apply to different contexts in Field Service, and that the choice of price book affects what a technician can record as consumed on a work order. Candidates who treat price books as a standard Sales Cloud concept without considering how Field Service uses them will choose configurations that look right but break the consumption workflow.

The Return Order object model is specific to Field Service and is not something candidates typically encounter in a general Salesforce background. Know the object relationships: what a return order connects to, what a return order line item represents, and how the process closes out. Items here reward tracing the return from the field back to the warehouse. Candidates lose marks by applying general case or order management logic where Field Service-specific Return Order behaviour applies.

Assets represent the installed equipment that field service exists to maintain and repair. At 5%, this topic has one published sub-topic and a tight scope, but the exam expects you to know how assets are maintained over time, how they relate to each other when equipment is part of a larger system, and how those relationships affect the work orders and service history tied to them. A technician servicing one component of a multi-part installation needs the asset hierarchy to be correct, or the service record will be wrong.

How Managing Assets is tested

At 5%, this topic contributes a small number of items, but those items tend to be procedural and specific. The exam describes an asset maintenance or update scenario and asks which steps or configurations apply. The sub-topic is explicit about procedural concepts, which means the exam is testing process knowledge rather than conceptual understanding.

Asset relationships are the detail most candidates underestimate. An asset can be a component of a parent asset, and it can have a location that differs from the account it belongs to. Items reward knowing how to update these relationships correctly and what downstream effects a change produces on service history or open work orders.

Candidates lose marks here by applying general Salesforce object knowledge without accounting for Field Service-specific asset behaviour. The asset's relationship to product, to location, and to the work order is distinct from how accounts and products relate in other Salesforce clouds. Work from the Field Service data model, not from general CRM intuition.

Maintenance Plans automate the generation of work orders for recurring service: scheduled inspections, periodic replacements, contract-driven visits. At 5%, this is one of the smaller topics, but it is one where candidates either know the configuration model or they do not. There is limited middle ground. The exam gives you a business scenario describing a recurring service requirement and asks which maintenance plan configuration meets it.

How Configuring Maintenance Plans is tested

With one published sub-topic, items here are tightly scoped. The exam describes a recurring service obligation and asks which maintenance plan settings satisfy it. The variables that matter are the generation horizon, the frequency, the work type that gets stamped on the generated work orders, and whether the plan is tied to an asset, a location, or an account.

Candidates lose marks by treating maintenance plans as simple calendar entries. The generation horizon controls how far in advance work orders are created, and setting it incorrectly either floods the dispatcher with future work or leaves gaps. The relationship between the maintenance plan and the work type is also tested: the work type determines what skills, duration, and products are expected on every generated work order, so a misconfigured work type propagates errors across every recurring job.

Items reward knowing the full configuration path, not just that maintenance plans exist. If you have only read about this feature rather than traced the settings, spend time on the generation and work type linkage before exam day.

Permissions and sharing is the final topic and, at 5%, a contained one. It sits at the boundary between Field Service configuration and the broader Salesforce security model. The exam tests whether you know which permission sets belong to which Field Service roles, how scheduled appointments become visible to the resources who need to act on them, and where user territories and service territories diverge in purpose and effect.

How Permissions and Sharing is tested

Items here are precise. The exam describes a user role or an access problem and asks which permission set or sharing mechanism resolves it. The trap is applying general Salesforce sharing knowledge without accounting for Field Service-specific constructs.

SFS permission sets have defined names and defined scopes. The exam expects you to know which permission set is appropriate for a dispatcher, a mobile technician, and an administrator, and what each one unlocks. Assigning the wrong set either over-privileges the user or blocks a workflow the business depends on.

The sharing of scheduled service appointments with resources is a Field Service-specific mechanism. It does not follow standard manual sharing or OWD logic in the way candidates expect from their general Salesforce experience. Items reward knowing how this sharing is triggered and what controls it.

User territories and service territories sound similar but serve different purposes. User territories are part of Enterprise Territory Management and affect opportunity and account visibility. Service territories in Field Service govern scheduling eligibility and resource assignment. Conflating the two is the most common loss point in this topic.