Universal Containers wants their Technicians to create an additional visit to Complete unfinished work within...

The correct configuration is a Quick Action that creates a Service Appointment. The unfinished work remains part of the existing Work Order; only a new visit is required. A mobile Quick Action can create another Service Appointment against that Work Order so the follow-up can be scheduled and tracked independently.

Mobile configuration should reduce technician data entry and expose only the actions and information needed at the point of service. The strongest designs reuse the Work Order and Service Appointment data model, launch guided actions from the appropriate parent record, and keep customer-facing outputs such as signatures and Service Reports within the native Field Service workflow.

The alternatives address different parts of the Field Service model. Creating a new Work Order would fragment the original service requirement, while Visualforce, custom buttons, or macros add unnecessary customization when a standard mobile action satisfies the requirement.

This approach keeps the implementation aligned with the standard Field Service data model and avoids unnecessary customization. Study Guide reference: Configuring Mobility — Field Service Mobile Quick Actions; follow-up Service Appointments.