> 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/add-edit-or-disable-visit-types.md).

# Add, edit, or disable visit types

Visit types label the kind of work on a job, a recurring service, or an internal schedule block—for example, Inspection or Repair. Users with Settings access can view the page. Adding, editing, disabling, and creating an inline group type require **Manage GPS & Scheduling Settings**.

Use **Add visit type** and enter one name, or enter several names separated by commas. Choose one or more Asset group types. Essential creates every requested name for every selected group type and skips an identical active pair that already exists. **Miscellaneous** creates a general visit type that is not tied to an asset group type.

If the group type you need is missing, choose **+ New group type**, name it, and select **Create**. The new group type is selected immediately.

Most visit types should leave Requires a property to schedule turned on. Turn it off only for blocks like Tech Unavailable, where you are scheduling technician time with no customer, property, or job. No-property visit types hide property-scoped fields such as contacts, reminders, expected asset group inspections, and job inventory, and technicians cannot clock into them on mobile.

You can rename a visit type later. If a visit type is already used by scheduled visits or recurring services, its asset group type and property requirement are locked. To change either one, disable the old visit type and create a new one.

Disabling a visit type removes it from scheduling and recurring-service pickers. Existing visits and recurring services that already use it keep working, and disabled visit types remain visible in a read-only Disabled visit types section.

This page defines the visit types themselves. The Service Visit Types page is separate: it maps services to existing visit types so inspection reports and recurring services know which service completions match.

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

## Related guides

* [Map services to visit types (Service Visit Types page)](/administration/settings/map-services-to-visit-types-service-visit-types-page.md)
* [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md)
* [Add work orders (visit types) and contacts with reminders to a visit](/customers-and-work/scheduling/add-work-orders-visit-types-and-contacts-with-reminders-to-a-visit.md)
* [Visit types: which services an inspection report can complete and reset](/administration/how-recurring-service-automation-works-the-full-cycle/visit-types-which-services-an-inspection-report-can-complete-and-reset.md)
* [Recurring service templates and template groups](/field-operations/assets/recurring-service-templates-and-template-groups.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/add-edit-or-disable-visit-types.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.