> 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/customers-and-work/scheduling/add-work-orders-visit-types-and-contacts-with-reminders-to-a-visit.md). # Add work orders (visit types) and contacts with reminders to a visit A visit needs at least one work order before you can move on. In the visit form, click the field with the wrench icon, which reads Select visit category and type. You first pick a category (an asset group type such as your fire or sprinkler categories, or Miscellaneous), then pick the specific visit type within it. The chosen type appears as a removable pill, and you can add several types to the same visit by repeating this. Each one shows as the type name with its category. Click the small x on a pill to remove it. You cannot add the same visit type twice. When you add a work order to a scheduled visit, Essential immediately marks any matching recurring service as Awaiting Service Completion. Its automation pauses until the visit is completed or that status is cleared. When removing a work order means a scheduled visit will no longer cover a recurring service that is already Awaiting Service Completion, Essential asks what should happen to its automation before saving. You can keep it waiting, start the automation again, or resume it using a future date. No prompt appears when another work order remaining on the visit still covers the service. Visit types are either property-based or no-property. Once you pick one kind, the picker only offers matching types so the visit cannot mix property-based work with no-property blocks such as Tech Unavailable. Below that, the contact field lets you attach people to the visit. Contacts are listed for the property's customer and sorted so the most relevant scheduling contacts appear first. Add one or more. If the person is not listed, open the contact dropdown and choose **+ Add contact**. The contact fields expand inside the visit form, so you can create the person without opening another modal. Essential selects the new contact on the visit after it saves. To correct a selected contact's name, email, phone numbers, notes, or roles, click the edit icon beside their name; the same inline editor opens below the contact dropdown and refreshes the visit when you save. For each contact you attach, you can turn on an Email checkbox and a Text checkbox, shown only when that contact actually has a valid email address or a textable phone number on file. These control whether that person receives the automated visit reminder. When creating a visit, changing either checkbox remembers your Email and Text choices for the next new visit. These choices are personal to your sign-in and business in this browser. You can still choose different reminders for each contact, and opening an existing visit keeps its saved choices. Before you have saved a preference, a newly created contact starts with Email on when an email address is available. For a phone-only contact whose number can receive texts, it turns on Text instead. If neither channel is usable, both reminders stay off. You can change either available reminder before saving the visit. If the contact field says Configure Visit Reminder Template, you can still choose **+ Add contact**, but an admin needs to save the starter reminder settings under Settings > Scheduling > Visit Reminders before reminders can be attached normally. No-property visit types do not have a property or customer contact list, so the contact and reminder fields are hidden for those visits. > **Where to find it:** On step 1 (Add Details) of the visit form, the wrench field is where you choose what work the visit is for, and the contact field is just below it. ## Related guides * [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md) * [Exact time vs. estimated, duration, technician count, and due date](/customers-and-work/scheduling/exact-time-vs-estimated-duration-technician-count-and-due-date.md) * [Filter and sort the backlog](/customers-and-work/scheduling/filter-and-sort-the-backlog.md) * [Reserve inventory, flag expected asset group inspections, and two kinds of notes](/customers-and-work/scheduling/reserve-inventory-flag-expected-asset-inspections-and-two-kinds-of-notes.md) * [Set a visit's arrival window](/customers-and-work/scheduling/set-a-visits-arrival-window.md) * [Add, edit, or disable visit types](/administration/settings/add-edit-or-disable-visit-types.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/customers-and-work/scheduling/add-work-orders-visit-types-and-contacts-with-reminders-to-a-visit.md?ask=&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.