The requirement is best implemented with Case # Work Order # Service Appointment # Dispatch. The Case captures the inbound customer issue, the Work Order represents the onsite work, and the Service Appointment is the schedulable visit assigned and dispatched to a Service Resource. This is the standard service-to-field execution sequence.
The Field Service data model separates the service requirement from its individual tasks and visits. A Work Order represents the overall job, Work Order Line Items represent component-level or task-level work, and Service Appointments represent the scheduled field visits used to execute that work. Choosing the correct level preserves accurate history, pricing, inventory, and scheduling.
The alternatives address different parts of the Field Service model. Dispatching a Work Order directly or creating an appointment before the underlying work reverses the Field Service data model and does not provide the intended parent-child structure.
This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders - Cases; Work Orders; Service Appointments; dispatch lifecycle.