> For the complete documentation index, see [llms.txt](https://learn.withessential.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.withessential.com/administration/settings/turn-scheduling-and-gps-features-on-or-off.md).

# Turn scheduling and GPS features on or off

The Features tab on the Scheduling settings page is where you enable scheduling and location features, with some depending on others. Draft Visits lets schedulers stage visits before releasing them to technicians - turning it off releases every existing draft to the team (and any automated reminders for them get sent) and can't be undone.

Technician GPS tracks technician location on the map. After enabling it, technicians should restart the mobile app and allow location access. On My Way requires Technician GPS and lets technicians broadcast that they're en route. Arrival Windows lets you schedule a customer-facing arrival window.

Expected Asset Group Inspections lets schedulers mark which asset groups a visit should inspect. Automatic Customer Notifications requires Technician GPS, On My Way, Arrival Windows, and a configured Tech En Route outreach template; if the template is missing, Essential warns you before the toggle can be used. When Automatic Customer Notifications is on, the page shows a live preview of the en-route message your customers will receive. Use **ETA available**, **No ETA**, and **Access details** above the preview to check each message condition. These tabs only change the sample preview; they do not change the feature switches or save settings.

A toggle stays disabled until its requirements are on, and changes aren't applied until you Save.

![Scheduling features and GPS settings toggles](https://3838208579-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Flu1pgNH0CrkCPslG8suQ%2Fuploads%2Fgit-blob-ee6ba5c86dbde2f268dab2249a1611406a6b7dfb%2Fsettings-scheduling-gps.png?alt=media)

> **Where to find it:** Settings > Scheduling > Features

## Related guides

* [Add or edit a pricebook item](/administration/settings/add-or-edit-a-pricebook-item.md)
* [Add the intake form to your website](/administration/settings/add-the-intake-form-to-your-website.md)
* [Automate task statuses with Task Automations](/administration/settings/automate-task-statuses-with-task-automations.md)
* [Build your intake form](/administration/settings/build-your-intake-form.md)
* [Bulk upload pricebook items from a spreadsheet](/administration/settings/bulk-upload-pricebook-items-from-a-spreadsheet.md)
* [Feature availability and setup](/getting-started/getting-started/feature-availability-and-setup.md)
* [Configure visit reminders](/administration/settings/configure-visit-reminders.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.withessential.com/administration/settings/turn-scheduling-and-gps-features-on-or-off.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.