> 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/deleting-a-scheduled-visit-is-permanent.md).

# Deleting a scheduled visit is permanent

Deleting a visit removes it for good, and a deleted visit does not drop back into the Backlog. If you only want to take a visit off a technician's day without losing it, drag it back to the Backlog instead of deleting; that clears its time but keeps the visit.

Right after you delete a visit, an Undo button appears at the bottom of the screen for a few seconds - click it to recreate the visit with the same property, technicians, duration, contacts, and notes. Once the Undo button disappears or you navigate away, the deletion is final and there is no trash to recover it from.

If you missed the Undo window and can't remember which customer a deleted visit was for, the only trace is on the related Job: open that job and look in its Timeline for a "visit deleted" entry, which records the work type (like "Backflow - Annual") but not the customer or property name - there is no list of deleted visits to browse.

Because it is permanent once the Undo window passes, treat Delete as different from rescheduling or moving a visit to the Backlog, which are always reversible.

## When the visit was covering a recurring service

If the visit you're deleting or moving to the Backlog covers a recurring service that shows "Awaiting Service Completion", Essential asks what should happen to that service's automation before removing its scheduled coverage:

* **Keep Awaiting Service Completion** — nothing changes; the service stays paused until a completion is recorded (or you clear the status from the asset group page later).
* **Start the automation again** — the status clears and automation resumes. The dialog shows when the next outreach would send (or when the Custom Task would be created); if the due date already passed, that can be as soon as the next send window.
* **Resume automation using a future date** — the status clears. For automated outreach, the date you select becomes the service due date, and outreach may begin earlier based on your configured schedule. For Custom Tasks, the task is created on the selected date.

When another scheduled visit also covers the service, the dialog adds that note under the service — you still choose what happens; nothing is decided for you. The extra note is omitted when the deleted visit is the only one covering it.

Each affected service is labeled as **Asset group type (asset group name): Visit type / Service**. The asset group name is omitted when that group has no name.

> **Where to find it:** Scheduling page -> open a visit -> the trash icon deletes it, with an Undo option appearing briefly after. To only clear its time instead of deleting, drag it from the calendar or map to the Backlog; the same automation choices appear when needed.

## Related guides

* [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)
* [Work with the scheduling backlog](/customers-and-work/scheduling/work-with-the-scheduling-backlog.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)
* [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.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/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.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.