> 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/map-services-to-visit-types-service-visit-types-page.md).

# Map services to visit types (Service Visit Types page)

The Service Visit Types page maps each service to the visit type(s) that can complete it. The mapping controls service completions from inspection reports and, when you opt in, from submitting a Job Summary without a report.

Each service has an "All visit types" checkbox: leave it on to apply the service to every visit type (including ones you add later), or turn it off to pick specific visit types with the two-step picker - choose an asset group type, then a visit type - adding each as a removable pill.

Each service also has a **Create *****service name***** completions on Job Summary submission** switch. It is off by default, which keeps the inspection-report behavior unchanged. Enable the switch on every service that a matching visit should complete without an inspection report. Before the first submission, the technician sees one Next Due Dates choice per enabled service, selected by default, and can turn off a service that was not completed. When one service has several recurring schedules, the technician sees the earliest date and a note that multiple schedules are affected. The row shows the number of affected assets, or identifies a schedule-only update when its asset group is empty. Turning the service off skips every automatic completion and empty-group fallback update for that service on that submission; it does not remove a completion created by an inspection report.

For a populated asset group, Essential records one completion for each applicable asset. If the group has no assets, Essential cannot create an asset-level completion, so it advances the recurring schedule from the visit date instead. Either path clears Awaiting Service Completion and advances the next due date. A populated group whose assets do not apply to the service is left unchanged. Clocking out alone does not trigger this automation; if no Job Summary is submitted, the service does not advance.

Changes aren't applied until you use Save. This page sets the mapping and the per-service visit-submission behavior; for how those settings drive service completions and the recurring-service cycle, see how visit types affect service completions.

This page maps existing services to existing visit types. To add, rename, or disable the visit types that appear in scheduling and recurring-service pickers, use Settings -> Scheduling -> Visit Types. If your business needs a new asset type or inspection report type, open the Essential Assistant and choose the Talk to a human tab.

![Service visit types settings](/files/Lq2zkhVNhyrFTTenCof2)

> **Where to find it:** Settings -> Service Visit Types

## Related guides

* [Add or edit a pricebook item](/administration/settings/add-or-edit-a-pricebook-item.md)
* [Add, edit, or disable visit types](/administration/settings/add-edit-or-disable-visit-types.md)
* [Contact Essential for setup changes](/getting-started/getting-started/contact-essential-for-setup-changes.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)


---

# 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://learn.withessential.com/administration/settings/map-services-to-visit-types-service-visit-types-page.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.