# Updating a website or booking engine

{% hint style="warning" %}
Before you begin: site or booking engine updates may affect platform features like **Discovery**, **Story River,** **HPC**, or **Quotes List**. Stay in touch with your Customer Success Manager, and we’ll help lead the charge.
{% endhint %}

## For first-time Discovery implementations

### <mark style="color:$info;">Coincide with your new website or booking engine</mark>

{% stepper %}
{% step %} <mark style="color:$primary;">First, launch your new website or booking engine.</mark>

Take 1-2 days to sanity check and dial in the website and booking engine prior to launching your platform.
{% endstep %}

{% step %} <mark style="color:$primary;">After, deploy Discovery following this post-launch window.</mark>
{% endstep %}
{% endstepper %}

## For existing Discovery implementations

### <mark style="color:$info;">Minor enhancements</mark>

{% hint style="info" %}
Examples include changing colors, moving locations of booking buttons or booking bars, reorganizing site sections, or changing class names. For expansive design support, talk to Customer Success.
{% endhint %}

{% stepper %}
{% step %} <mark style="color:$primary;">Let your Customer Success Manager know about upcoming changes.</mark>

Aim to give [at least 7 days notice](#user-content-fn-1)[^1] prior to your scheduled launch date.
{% endstep %}

{% step %} <mark style="color:$primary;">Your Customer Success Manager audits and updates Discovery.</mark>

We’ll make any design and platform adjustments as needed, and test.
{% endstep %}

{% step %} <mark style="color:$primary;">Deploy your enhancements, and our team coordinates to switch on any platform updates at the same time.</mark>
{% endstep %}
{% endstepper %}

### <mark style="color:$info;">Major enhancements or a total relaunch</mark>

{% hint style="info" %}
Examples include migrating to a new booking engine, making significant structural changes to your website, or changing booking URLs. For expansive design support, talk to Customer Success.
{% endhint %}

{% stepper %}
{% step %} <mark style="color:$primary;">Let your Customer Success Manager know about upcoming changes.</mark>

Aim to give [at least 7 days notice](#user-content-fn-2)[^2] prior to your scheduled launch date.
{% endstep %}

{% step %} <mark style="color:$primary;">Flip.to pauses your platform during your launch window.</mark>

Two days prior to launch, and up to two days following, Flip.to will pause the platform. In that time, sanity check and dial in the website and booking engine prior to relaunching your platform.

{% hint style="info" %}
While paused, Discovery will continue to engage existing planners who return to your website, but will not engage new planners.
{% endhint %}
{% endstep %}

{% step %} <mark style="color:$primary;">After the sanity check, your Customer Success Manager redeploys your platform. 🎉</mark>
{% endstep %}
{% endstepper %}

## For staging sites

### <mark style="color:$info;">In some cases, a staging site can be used to bring your platform back on board even faster.</mark>

{% hint style="warning" %}
Before you begin: The staging site should represent the final version, or ready-to-launch state.

* Booking URLs and variations are final
* Booking buttons and booking bars, including class names or IDs are final
* Pages and page locations are complete

Should last minute changes to the staging site take place, let your Customer Success Manager know as soon as possible.<br>
{% endhint %}

{% stepper %}
{% step %} <mark style="color:$primary;">Share the link and any credentials to your Customer Success Manager.</mark>

We’ll access and review the staging site, confirming it contains our scripts.
{% endstep %}

{% step %} <mark style="color:$primary;">Our team does the lift to get your platform back on board.</mark>

Our Customer Success team configures every aspect of Discovery to get you started.\
\
You'll receive preview links to review and approve, and at any point you can tweak the configuration in your account.
{% endstep %}
{% endstepper %}

Have a great launch! 🚀

[^1]: And the more the better! :smile:

[^2]: Especially for major relaunches, more time is even better! :smile:


---

# Agent Instructions: 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:

```
GET https://docs.flip.to/docs/gameplans/updating-a-website-or-booking-engine.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.