> 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/set-a-visits-arrival-window.md).

# Set a visit's arrival window

If your business uses arrival windows, you can give a visit a customer-facing arrival window so the customer knows roughly when the technician will show up. Arrival Windows must be enabled in Settings > Scheduling > Features before the field appears.

Set it in the visit form using the Arrival Window field, picking a start time and an end time. The window is broader than the visit's exact scheduled start: it's the range you commit to the customer. When you choose an exact start time outside that window, the start-time step shows an alert before you schedule the visit. When a visit has an arrival window, visit details add a separate section at the top with a truck icon, **Arrive between**, and **Est. duration**. Detailed calendar cards show primary-color compact **Arrive 9AM-1PM** plus shorthand **Duration 3 hr** wording when the card is tall enough. If only one timing row fits, **Arrive** takes priority over the internal scheduled time; opening the visit still shows both. The scheduled-time row stays below with a neutral clock when there is room because the arrival promise makes an exact-time target misleading. If that scheduled start is outside the arrival window, both the card and visit details show a warning. Visits without an arrival window do not get that arrival section or neutral-clock override. Day (Schedule) rows show the arrival window above the scheduled time. In the technician mobile app, the window appears as a bold **Arrive between** line, and exact arrival-window visits use the same neutral timing icon and text as the other windowed visits. If the window ends before the technician clocks in, mobile marks it **Missed** in red until the technician arrives.

If the window ends and an assigned technician has not clocked in, the Arrival Window banner at the top of Scheduling flags the missed visit. If you save a same-day visit whose window has already ended, the missed warning is created as soon as the visit is saved instead of waiting for the next scheduled check. This missed-window warning works even when Technician GPS is off. With Technician GPS on, the banner can also warn earlier when a technician's ETA puts the visit at risk or shows that they will miss the window.

If you don't see an Arrival Window field, the feature isn't turned on for your business or your role cannot use it. If you need arrival windows for your work, contact your business's administrator to review your role.

> **Where to find it:** In the visit form (create or edit a visit), the Arrival Window field

## Related guides

* [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)
* [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)
* [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)
* [Send a visit reminder to a customer](/customers-and-work/scheduling/send-a-visit-reminder-to-a-customer.md)
* [Turn scheduling and GPS features on or off](/administration/settings/turn-scheduling-and-gps-features-on-or-off.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/set-a-visits-arrival-window.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.