> 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/customer-notifications-for-scheduled-visits.md). # Customer notifications for scheduled visits Scheduling can trigger customer-facing communication for visits, depending on your outreach settings and the contacts selected on the visit. ## Visit reminders Use visit reminders to notify contacts before scheduled work. A visit needs contacts with email or SMS enabled before reminders can go out. Admins set the reminder schedule — one or several reminders at different times ahead of the visit — plus the email and text messages under Settings > Scheduling > Visit Reminders. Every visit follows the same schedule; whether a contact gets email, text, or both stays a per-visit choice. A visit takes its place in that schedule when it's booked or rescheduled: the first reminder still ahead of it. Reminders it is already past are skipped rather than replayed, so booking tomorrow's visit on a seven-day / two-day / twelve-hour schedule sends the twelve-hour reminder, not all three at once. Booked closer still, the last reminder goes out right away rather than not at all. You can review visit reminder outreach from Automations > Automated Outreach by filtering the type to Visit Reminder. Use the status filters there to see which reminders are pending, sent, bounced, stopped, or otherwise need attention. ## On My Way and ETA When On My Way is enabled, a technician can send an en route signal from mobile. If the visit and contact setup are eligible, the customer receives the configured notification and the office can see en route status or ETA. ## Arrival windows If your business uses arrival windows, set the arrival window on the visit so the customer sees a clearer expected range instead of only the exact internal schedule time. > **Where to find it:** Scheduling page > visit contacts, reminders, and arrival window ## Related guides * [Send a visit reminder to a customer](/customers-and-work/scheduling/send-a-visit-reminder-to-a-customer.md) * [Configure visit reminders](/administration/settings/configure-visit-reminders.md) * [Set a visit's arrival window](/customers-and-work/scheduling/set-a-visits-arrival-window.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) --- # 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/customer-notifications-for-scheduled-visits.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.