Which reasons can field agents provide when rejecting tasks that were assigned to them? (Choose two.)

In ServiceNow Field Service Management, when a field service agent rejects an assigned work order task, they must provide a reason. The system is configured with a set of default rejection reasons to ensure that rejections are based on valid operational constraints rather than personal preferences. "Skills mismatch" is a valid reason, indicating the agent lacks the necessary expertise. "Parts unavailable" is another valid reason, as the task cannot be completed without the required components. These reasons provide dispatchers with actionable information to reassign the task appropriately.

A. Type of work not preferred: This is based on personal preference, not an operational inability to perform the task, and is not a standard rejection reason.
C. Not a preferred customer: Rejecting work based on customer identity is unprofessional and would not be a system-sanctioned reason for task rejection.

1. ServiceNow Product Documentation - Reject a work order task: The official documentation for the Washington DC release explicitly lists the default reasons an agent can provide for rejecting a task. It states, "By default, the following reasons are available: Skills mismatch, Parts unavailable, Schedule conflict." This directly supports the correctness of options B and D.

Source: ServiceNow Product Documentation, Field Service Management, "Reject a work order task", Washington DC release.

2. ServiceNow Product Documentation - Configure rejection reasons for work order tasks: This document explains how administrators can add or modify rejection reasons. It confirms that "Skills mismatch" and "Parts unavailable" are part of the base system configuration, stored in the Rejection Reason [fsmrejectionreason] table.

Source: ServiceNow Product Documentation, Field Service Management, "Configure rejection reasons for work order tasks", Washington DC release.