> For the complete documentation index, see [llms.txt](https://kb.logicerp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/configuration/cancellation-reasons.md). # Cancellation Reasons **Available on:** Desktop · Web · Phone The list of **reasons** offered when an appointment is cancelled — for example *Client unwell*, *Stylist on leave*, *Booked by mistake*. A reason is asked for when an appointment is set to **Canceled**, unless it already has one (see [Appointment Status and Cancellation](/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/appointments/appointment-status-and-cancellation.md)). In Setup Appointments, open the menu and double-click **Configuration › Cancellation Reasons**, or use the **Setup Cancellation Reason** button in **Configuration › Settings**. Only users who can see the **Configuration** menu can open it. In the **Setup Appointment Cancellation Reason** window, type each reason in **REASON NAME** and, if you like, **REASON DESCRIPTION**. Both are typed in capitals. A name is required, and each must be different (*"Reason Name '…' already exist"*). Then **Save** and answer *"Are you sure you want to save changes"*. To remove a reason, delete its row, confirm, and save. In the **Select Cancellation Reason** window the reasons are listed by name; picking one shows its description — or its name, if it has none — and that text is what is saved on the appointment. If no reasons are set up, only **Other ...** is offered, and the reason must be typed each time. > **Example.** Add *UNWELL* — *CLIENT UNWELL*, *STYLIST LEAVE* — *STYLIST ON LEAVE*, and *MISTAKE* — *BOOKED BY MISTAKE*. Next time an appointment is cancelled, pick one from the list instead of typing; its description is saved as the reason. ## On the web The screen works the same way on the web. --- # 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://kb.logicerp.com/logic-erp-learning-hub-tutorials-and-best-practices/billing/setup-appointments/configuration/cancellation-reasons.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.