> 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/send-a-visit-reminder-to-a-customer.md). # Send a visit reminder to a customer You can let a customer know about an upcoming visit by sending a reminder from the visit's details on the Scheduling page. Open the visit and use Send reminder next to a contact; it goes to that contact by email or text, depending on how they're set to be notified. Reminders can also go out automatically as part of scheduled outreach, and the visit keeps track of whether one has already been sent so you don't double up. Sending one yourself is a manual nudge on top of any automated reminders: it delivers a single reminder on each channel the contact is set up for and then stops, leaving your scheduled reminders to run as normal. It's most useful when the visit is further out than your first scheduled reminder and you want to tell the customer now. Changing your reminder schedule in Settings never re-dates a reminder you sent by hand. > **Where to find it:** Scheduling page, open a visit's details, then Send reminder next to a contact ## Related guides * [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) * [Create a new visit](/customers-and-work/scheduling/create-a-new-visit.md) * [Deleting a scheduled visit is permanent](/customers-and-work/scheduling/deleting-a-scheduled-visit-is-permanent.md) * [Draft visits and releasing them to the team](/customers-and-work/scheduling/draft-visits-and-releasing-them-to-the-team.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/send-a-visit-reminder-to-a-customer.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.