Updating a website or booking engine

To ensure your Flip.to platform continues to drive impact, follow the best practices below. We'll take it from there to get you to a successful launch! 🚀

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.

For first-time Discovery implementations

Coincide with your new website or booking engine

1

First, launch your new website or booking engine.

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

2

After, deploy Discovery following this post-launch window.

For existing Discovery implementations

Minor enhancements

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.

1

Let your Customer Success Manager know about upcoming changes.

Aim to give at least 7 days notice prior to your scheduled launch date.

2

Your Customer Success Manager audits and updates Discovery.

We’ll make any design and platform adjustments as needed, and test.

3

Deploy your enhancements, and our team coordinates to switch on any platform updates at the same time.

Major enhancements or a total relaunch

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.

1

Let your Customer Success Manager know about upcoming changes.

Aim to give at least 7 days notice prior to your scheduled launch date.

2

Flip.to pauses your platform during your launch window.

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.

While paused, Discovery will continue to engage existing planners who return to your website, but will not engage new planners.

3

After the sanity check, your Customer Success Manager redeploys your platform. 🎉

For staging sites

In some cases, a staging site can be used to bring your platform back on board even faster.

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.

1

Share the link and any credentials to your Customer Success Manager.

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

2

Our team does the lift to get your platform back on board.

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.

Have a great launch! 🚀