MB-240 study materials
MB-240 study resources

MB-240: Configure Field Service applications

MB-240 · Work through your exam, one topic at a time.

All guide sections

Configure Field Service applications

Configure Field Service applications

This domain tests your ability to shape a Field Service environment before work orders flow: settings, security, reference data, and scheduling configuration.

Core rules and concepts

  • Field Service settings control work order and booking behavior, agreement defaults, dispatch options, and resource scheduling parameters.
  • Out-of-box security roles such as Field Service Administrator, Dispatcher, and Resource should be scoped to business units; avoid granting broad access just to make the schedule board work.
  • Bookable resource categories and characteristics drive requirement matching. Territories and organizational units narrow which resources are eligible.
  • Work order types classify work; incident types act as templates that add service tasks, products, and services to a work order.
  • Booking statuses track the scheduling lifecycle and are separate from work order system statuses.
  • Price lists, products, and services support estimates and billing.

Worked example

Contoso has HVAC and electrical crews. You create bookable resource categories for each trade, characteristics for certifications such as EPA, and territories for North and South. An incident type called Annual HVAC Inspection adds tasks for filter check, refrigerant check, and customer sign-off. A dispatcher can then match a North territory HVAC requirement to a certified technician without manual searching. The reasoning is to configure reusable classification and matching data first, then let scheduling rules use it.

Traps that cost marks

  • Confusing booking status with work order status; closing a booking does not necessarily close the work order.
  • Adding characteristics but forgetting to attach them to resources or requirements, so matching never occurs.
  • Changing scheduling settings after live data exists without testing existing bookings.
  • Assuming an incident type applies automatically; it must be associated with the work order.
  • Forgetting to publish app customizations before testing in the Field Service mobile app.