> For the complete documentation index, see [llms.txt](https://support.rosysalonsoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.rosysalonsoftware.com/advanced-settings/cancellation-policy.md).

# Cancellation Policy

The Cancellation Policy Setup allows you to edit the time ranges in which clients can cancel their appointments online. This is also where you set up the policy message clients see when they attempt to cancel an appointment.

There are two ways to access the Cancellation Policy Setup:

{% stepper %}
{% step %}

## First setup option

Proceed to: **Manage** > **Advanced Settings** > [Manage Custom Messages](/advanced-settings/custom-messages.md) (located under **Custom Messages**) > Select Cancellation Policy
{% endstep %}

{% step %}

## Second setup option

Proceed to: **Manage** > **Advanced Settings** > Configure how Clients can cancel appointments (located under **Cancellation Policy**)
{% endstep %}
{% endstepper %}

## Completing Cancellation Policy Setup

![Cancellation Policy Setup](/files/f1e2775d3ef5374cfe81f0a5f9cdf0ceb9e945ad)

**Allow Clients to Cancel Online:** If you would like clients to be able to cancel their appointments *themselves*, you can set this to "Yes".

**Minimum Days in advance to cancel an appointment:** If you allow clients to cancel their own appointments online, this controls how soon in advance they are able to do so.

**Require Credit Card online:** If this is set to "Yes", every time a client who *does not* have a credit card on file tries to schedule online, it will require them to enter a valid credit card before proceeding to schedule.

*This option will be grayed out if you do not have a credit card processing account set up with* [*Integrated Card Processing*](https://www.rosysalonsoftware.com/salonrunnerpay)*.*

**Require Credit Card in Manager App:** If this is set to "Yes", every time a client who *does not* have a credit card on file tries to schedule in the salon, it will require the employee scheduling them to enter the client's valid credit card information before proceeding to schedule. This *can* be skipped while scheduling once it is turned on!

*This option will be grayed out if you do not have a credit card processing account set up with* [*Integrated Card Processing*](https://www.rosysalonsoftware.com/salonrunnerpay)*.*

**Charge if cancelled within:** This controls when a client's cancelled/no-show appointment will go to the Pending Cancellation Charges page within the Tickets List.

For example: If this is set to 2 days, and I cancel my appointment only 1 day before I am supposed to come in, my appointment will go to the Pending Cancellation Charges page for you to decide to proceed with charging my card on file, or waiving my fee.

*This option will be grayed out if you do not have a credit card processing account set up with* [*Integrated Card Processing*](https://www.rosysalonsoftware.com/salonrunnerpay)*.*

**Percent of service charged:** Decide what percentage of each service scheduled you would like to charge the client if their appointment is not cancelled before your set "Charge if cancelled within" days.

*This option will be grayed out if you do not have a credit card processing account set up with* [*Integrated Card Processing*](https://www.rosysalonsoftware.com/salonrunnerpay)*.*

**Your Cancellation Policy Message will appear to clients who attempt to cancel online!**

*This is an example of how it will look to clients who attempt to schedule an appointment online without a credit card:*\
*Classic OCS:*\
![](/files/FooW3gVhGQhn6nhlFktY)

*New OLB:*

<figure><img src="/files/OuJsKLhAxq1VIaudQ7jU" alt=""><figcaption></figcaption></figure>

Cancellation Charge

If the business is integrated with Credit Card processing through RosyPay, you have the ability to charge clients for a cancelled or no-show appointment.

## Applying Cancellation Charges to Client

{% stepper %}
{% step %}

## Open pending cancellation charges

Proceed to: **Tickets** > **Pending Cancellation Charges** > **Charge Card** option next to the client.

![Pending cancellation charge](/files/34499a887cab31f8bc085ca45a29eb91b09d7210)
{% endstep %}

{% step %}

## Finalize payment

Adjust the **Cancellation Fee** if necessary.

Click **Finalize Payment**.

![Finalize cancellation payment](/files/f93e72bf8651beef75af5225eeaca874b45941d8)
{% endstep %}

{% step %}

## Confirm successful payment

You will receive this message at the top of your screen if the payment goes through successfully.

![Cancellation message](/files/6828bd0fc01096c01ef593106733f8a808fed8e0)
{% endstep %}
{% endstepper %}

You also have the option of waiving the charge by clicking "Do Not Charge".

![Waive cancellation charge](/files/d32ce7169fa110f451c6633513530a98a2f3cb2b)

You will alternatively receive this message at the top of your screen if you've chosen not to charge the client.

![Waived cancellation message](/files/a5a8db1d20fe7034ec2f3bb69107be920c4ef159)


---

# 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://support.rosysalonsoftware.com/advanced-settings/cancellation-policy.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.
