A Universal Containers (UC) Technician arrived onsite for an appointment, but the customer was unavailable...

The requirement is best implemented with Cannot Complete plus a new Service Appointment on the same Work Order. The technician made the visit but could not perform the work because the customer was unavailable. Marking the original appointment Cannot Complete preserves the failed-visit history, and a new appointment records the follow-up visit under the same underlying Work Order.

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. In Progress would misstate the final outcome, Complete would imply successful service, and a new Work Order is unnecessary because the service requirement itself has not changed.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Managing Work Orders — Service Appointment lifecycle; Cannot Complete; follow-up visits.