# Service appointment statuses, categories and transitions

*Agentforce Field Service and Operations Consultant Study Guide · Managing Scheduling and Optimization · Last updated October 29, 2026 · https://www.certifyforce.com/study-guide/agentforce-field-service-consultant/managing-scheduling-and-optimization/service-appointment-statuses-categories-and-transitions*

The service appointment lifecycle: the seven default statuses, why custom statuses need a status category, how status transitions and profile limits are configured and where they are enforced, and which date and time fields the lifecycle fills in.

- Certification: Salesforce Agentforce Field Service and Operations Consultant
- Exam section: Managing Scheduling and Optimization
- Study guide: https://www.certifyforce.com/study-guide/agentforce-field-service-consultant

**Official exam objective:**

> Given a scenario, apply the appropriate lifecycle of a Service Appointment required to execute a Work Order.

## What the exam expects

- Name the default service appointment statuses and what each means as a work order is executed.
- Add a custom status and map it to the right status category so field service processes treat it correctly.
- Configure status transitions and profile limits, and predict where they are enforced and which actions bypass them.
- Say which date and time fields the lifecycle fills in (Scheduled, Actual) and which ones an admin sets up front (Earliest Start Permitted, Due Date, arrival window).

Key terms:
- **Status:** the customizable picklist that records the appointment's stage.
- **Status Category:** the fixed classification each Status value maps to; processes read it instead of Status.
- **Status transition:** an allowed move from one status to another, defined in the Service Appointment Workflow settings.
- **Parent Record Status Category:** read-only appointment field holding the work order or line item parent's status category.
- **Actual Duration:** minutes between Actual Start and Actual End, filled in automatically once.

## Key facts

| Fact | Detail | Source |
|---|---|---|
| Default statuses | None, Scheduled, Dispatched, In Progress, Completed, Cannot Complete, Canceled | [Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5) |
| Custom Status value | Must be assigned a status category | [Status Categories](https://help.salesforce.com/s/articleView?id=service.fs_status_categories.htm&language=en_US&type=5) |
| Processes read | Status Category, not Status | [Status Categories](https://help.salesforce.com/s/articleView?id=service.fs_status_categories.htm&language=en_US&type=5) |
| Unscheduled appointment | Status changes to None | [Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5) |
| Renaming a status | Doesn't change its automatic transition behavior | [Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5) |
| Transition name limit | 40 characters for "Status 1 - Status 2" | [Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5) |
| Profile limits on transitions | Feed tab status change action only, not the Gantt | [Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5) |
| Emergency to Dispatched category | Ignores status transitions | [Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5) |
| Status Scheduled after optimization | Requires an assigned resource | [Field Service Limits](https://help.salesforce.com/s/articleView?id=service.fs_limits.htm&language=en_US&type=5) |
| Actual Duration | Set when actual times are first added; not recalculated later | [Service Appointment Fields](https://help.salesforce.com/s/articleView?id=sf.fs_appointment_fields.htm&language=en_US&type=5) |
| SLA window | Earliest Start Permitted and Due Date | [Service Appointment Fields](https://help.salesforce.com/s/articleView?id=sf.fs_appointment_fields.htm&language=en_US&type=5) |

## Check yourself

- Which seven statuses does a service appointment come with?
- Why do field service processes reference Status Category instead of Status?
- Why would a transition you added not be saved?
- When does optimization leave an appointment's status unchanged even though it set Scheduled Start and End?
- Why can't the status flow diagram show who may make a change?

## Sources

- [Customize the Service Appointment Workflow](https://help.salesforce.com/s/articleView?id=sf.pfs_lifecycle.htm&language=en_US&type=5)
- [How are Status Categories Used?](https://help.salesforce.com/s/articleView?id=service.fs_status_categories.htm&language=en_US&type=5)
- [Service Appointment Fields for Field Service](https://help.salesforce.com/s/articleView?id=sf.fs_appointment_fields.htm&language=en_US&type=5)
- [Schedule Service Appointments for Field Service](https://help.salesforce.com/s/articleView?id=sf.pfs_scheduling_appointments.htm&language=en_US&type=5)
- [Create Service Appointments for Field Service](https://help.salesforce.com/s/articleView?id=service.fs_create_appointments.htm&language=en_US&type=5)
- [Field Service Limits and Limitations](https://help.salesforce.com/s/articleView?id=service.fs_limits.htm&language=en_US&type=5)
- [Guidelines for Creating Service Appointments for Field Service](https://help.salesforce.com/s/articleView?id=fs_appointment_guidelines.htm&language=en_US&type=5)

## About the full unit

The "Core concepts", "Exam traps" and "Worked scenario" sections of this unit, its 7 linked practice questions, and unlimited timed mock exams are included with the Agentforce Field Service and Operations Consultant pack (USD $19): https://www.certifyforce.com/practice-exams