FS agent cannot complete work, adds the reason in the 'Work notes' field, clicks 'Close Incomplete'. The parent WO is then set to the same state.

FS agent cannot complete work, adds the reason in the 'Work notes' field, clicks 'Close Incomplete'. The parent WO is then set to the same state.

• A. Closed Incomplete (wo task)
• B. Canceled (work order)
• C. Pending Dispatch (wo task)
• D. Assigned (wo task)

Answer: (A)

When a field service task can’t be finished, signaling that outcome with a Close Incomplete action is the explicit way to mark both the task and the overall job as not fully completed. The work notes capture why it couldn’t be done, and closing the task as incomplete tells the system this particular work item didn’t reach a successful close. Propagating that same status to the parent Work Order reflects the real situation: the entire job, as represented by the Work Order, is not completed. Other options don’t fit this scenario. Canceled would imply removing the work order entirely, while Pending Dispatch and Assigned indicate not-yet-started or active work, not an incomplete closure.

When a field service task can’t be finished, signaling that outcome with a Close Incomplete action is the explicit way to mark both the task and the overall job as not fully completed. The work notes capture why it couldn’t be done, and closing the task as incomplete tells the system this particular work item didn’t reach a successful close. Propagating that same status to the parent Work Order reflects the real situation: the entire job, as represented by the Work Order, is not completed.

Other options don’t fit this scenario. Canceled would imply removing the work order entirely, while Pending Dispatch and Assigned indicate not-yet-started or active work, not an incomplete closure.