> 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/online-client-scheduling/helping-clients-transition-from-ocs-to-olb.md).

# Helping Clients transition from OCS to OLB

## Change can be exciting, but for clients who are used to a familiar booking experience, even positive upgrades can feel overwhelming. When transitioning from Classic OCS to New OLB, we want to be sure you and your clients feel comfortable. Even with enhanced functionality and a modernized look, it is important to introduce this change intentionally.

This article is meant to provide practical recommendations or how to guide clients from a system they know and trust to an improved experience designed to work smarter, look better, and support our users’ needs. You know your clients better than anyone, so it is important to adapt this to how you feel will be best received by your demographic of clients! Some great ways to share this information with clients are through social media and mass email marketing.

Consider sharing pictures or videos of the new platform:

A quick walkthrough tutorial of how to navigate your new booking page or screenshots of the new features and modern appearance of your booking page may encourage clients to check it out! Previewing some of the enhancements should help the change feel more exciting and less intimidating for your clients.

![image-png-Mar-27-2026-01-53-34-9461-PM](/files/d6f38d75b6db5b85f4673245e4a3b269c0e9185c)

Consider sharing a message like this:

Hi there!

We’re excited to share that we’ve introduced an updated version of our online scheduling system. It has new exciting features such as the ability to see additional service information, add yourself to the waitlist, jump to the next available date, leave appointment notes for your stylist, and so much more!

We know that any change can raise questions, and we want to ensure this transition is as seamless as possible for you. While we begin rolling this out, we will have both the classic system and the new booking system available for you to use. If you are not yet ready to get started on the new platform, you can temporarily still log in and book with the scheduling system you are familiar with. However, we encourage you to try the new one. We think you’ll like it!

## FAQ

<details>

<summary>What is your new booking link?</summary>

You can find our new booking page at \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

</details>

<details>

<summary>Why didn't this link didn’t ask me to sign in?</summary>

Isn’t that great? Now, you can see appointment availability before getting signed in! You can always log in using the top menu. Otherwise, you’ll be prompted to sign in before finalizing your appointment or purchase.

</details>

<details>

<summary>Can I use the same password as your other page?</summary>

You are welcome to reuse your password! However, for security reasons, you will need to go through a password reset the first time you use the new platform. When prompted to login, you can either sign in with Google, Facebook, or click “reset your password” to get signed in.

</details>

<details>

<summary>What do I do if I get stuck?</summary>

As always, you can contact our team to assist with getting your appointment scheduled if you have any difficulties. You can reach us at XXX-XXX-XXXX or <email@email.com>

</details>


---

# 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/online-client-scheduling/helping-clients-transition-from-ocs-to-olb.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.
