> 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/why-cant-i-schedule-a-visit-here-inactive-customer-or-property.md).

# Schedule a visit for an inactive customer or property

Inactive customers and properties appear in the visit form's property search with an **Inactive** label beside the property name. You can select them and reactivate them when saving the visit.

> **Where to find it:** Scheduling page, **Create Job / Visit**, or an existing visit's edit form.

1. Select the property and enter the visit details.
2. Review the inline notice below the property explaining which records will be reactivated.
3. Save the visit.

Saving activates the selected property and its customer when either is inactive. Other inactive properties under the same customer stay inactive. Closing the form without saving leaves their status unchanged.

Automation settings stay unchanged. Recurring-service outreach can resume under those settings, including email or SMS to eligible contacts. Normal holds for services covered by an open visit still apply. Previously canceled subscriptions are not restored.

The same inline notice appears when you edit a visit whose property or customer has since become inactive.

## Related guides

* [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md)
* [Making a customer active or inactive](/customers-and-work/customers/making-a-customer-active-or-inactive.md)
* [Making a property active or inactive](/customers-and-work/properties/making-a-property-active-or-inactive.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/why-cant-i-schedule-a-visit-here-inactive-customer-or-property.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.