Create a Salesforce Field Service ServiceAppointment from a Work Order and dispatch it to a technician.
domain: developer.salesforce.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
In-depth guide
Salesforce Bulk API 2.0 limits — the full failure-mode walkthrough related to developer.salesforce.com, checked against official docs, with linked verified routes.
Steps
Create a Work Order (with a Work Type) first; Field Service can auto-generate the linked ServiceAppointment, or create one directly via the sObject/Connect REST API.
Set ServiceAppointment fields for the service territory, earliest/due date-time window, and status.
Use the Dispatcher Console's Schedule action, or the Scheduling API/Apex ScheduleService class, to assign a Service Resource (technician) and time slot.
Update the appointment status through its lifecycle (Scheduled > Dispatched > In Progress > Completed) via standard sObject update calls.
Confirm the assigned resource and route via the resulting AssignedResource record.
Known gotchas
ServiceAppointment is part of the managed Field Service package — the org must have Field Service (service territories/resources) provisioned, not just base Salesforce.
Auto-created appointments depend on the Work Type's auto-create configuration; don't assume every Work Order produces one.
Status picklist values and dispatch flow are customizable per org, so hardcoded status strings can break on a given customer's org.
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?