> For the complete documentation index, see [llms.txt](https://navixy.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://navixy.com/docs/navixy-api/user-api/guides/field-service-management.md).

# Field service management

Worked examples of assigning work to field employees and collecting what they report back.

Field service work follows a cycle: a task is created and assigned, an employee's status changes as they work it, and information comes back from site as a form or a check-in. These guides walk that cycle with the calls in order.

* [How to create and assign tasks](/docs/navixy-api/user-api/guides/field-service-management/manage-tasks.md): the starting point, and what the other three build on.
* [Changing employee statuses](/docs/navixy-api/user-api/guides/field-service-management/change-task-statuses.md): recording what an employee is currently doing.
* [Using task forms](/docs/navixy-api/user-api/guides/field-service-management/create-forms.md): collecting structured information when a task is completed.
* [Working with check-ins](/docs/navixy-api/user-api/guides/field-service-management/check-ins.md): recording what an employee reported from a location.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://navixy.com/docs/navixy-api/user-api/guides/field-service-management.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.