---
sourceDocument: Zurich Field Service Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/field-service-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Field Service Management

ft:clusterId :

    - fsm

bundleId :

    - fsm

workflow :

    - Customer and Industry


---

# Accept or reject a WOT

# Accept or reject a work order task on a mobile device {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Accept or reject a work order task assigned to you through the Field Service Contractor for mobile application.

## Before you begin

Role required: wm_ext_agent or wm_ext_manager

## Procedure

1. Access your instance using the ServiceNow Agent mobile application.
2. On the My work navigation tab, tap All open tasks
3. Select the work order task from the list.
4. On the work order task form, either accept or reject the task.
   * To reject the task, tap Reject, select the reason
     for the rejection, and enter details.

     The following confirmation message appears at the top of the screen:
     Task rejected successfully. Click here to view open tasks.
   * To work on the task yourself, tap Accept.

   {#self-assign__choices_as5_q3h_bvb}  
   Note:  
   If the contractor agent or manager is unavailable, the following message is displayed: Warning: WOTXXXXXX has been scheduled for a time you may not be available.

## Result

The task is either accepted or rejected. If the task is rejected, it is reassigned
depending on the role of the person who accepted or rejected it.

* If a manager rejects the task, the state of the task changes to Pending
  dispatch or Pending assignment. The rejected task is assigned to the manager
  of next appropriate group. If the system cannot identify another qualified
  group, the task remains in the Pending dispatch state so the dispatcher can
  manually assign the task.

* If an agent rejects the task, it is reassigned to the agent's manager.
{#self-assign__ul_tdt_xw3_jvb}

