> 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/customers/manage-customer-follow-ups.md). # Manage customer follow-ups Choose whether a customer receives automatic invoice reminders, quote follow-ups, and job approval follow-ups. > **Where to find it:** Settings → Company → Customer Follow-ups, then Customers → open a customer → Edit → Follow-ups. ## Enable customer opt-outs A user with the Business Profile setup permission can turn on **Allow customer opt-outs** and click **Save changes**. This setting starts off for every business. Enabling it leaves all customers' follow-ups on until staff change a customer's preferences. ## Choose a customer's follow-ups 1. Open the customer and click **Edit** to open the Edit Customer window. 2. Under **Follow-ups**, check individual follow-up types, or check **Turn off follow-ups** to select all. 3. Click **Save**. Cancel discards your changes. When any follow-ups are off, the customer page shows a **Follow-ups off** or **Some follow-ups off** pill beside the customer's other status pills. Hover over it to see which types are off. There is no pill while every follow-up is on. To turn them back on, open Edit, uncheck those choices, and save. Initial sends, manual messages, visit reminders, and en-route texts are unaffected. Queued follow-ups are skipped when they become due. Skipped messages are not replayed if you turn follow-ups back on; future messages use the saved schedule. Turning **Allow customer opt-outs** off hides the Follow-ups section and pill and ignores saved opt-outs. The choices are kept and apply again when the business turns the setting back on. Related: [What the customer page shows](/customers-and-work/customers/what-the-customer-page-shows.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/customers/manage-customer-follow-ups.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.