These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Wellness Retreat Management
- Implementation and migration
How a Wellness Retreat Management rollout works
Start with one season's rooms, rates and bookings, then add programs.
Agree the operating boundary
The system holds stays, units, programs, sessions, service tasks, folios and payments. Card processing, accounting and booking channels stay in connected systems. The retreat decides rates, programs and refunds.
Map the source data
Agree unit numbers and types, the season's rate plans, guest records and booking numbers. Load upcoming bookings and open folios.
Configure a bounded pilot
Run one month of stays live: confirmation, check-in, service tasks, folios and checkout.
Rehearse the exceptions
Two guests cannot hold the same unit on the same night. A draft charge is never treated as paid, checkout uses confirmed payments only, and a unit is not available again until inspection passes.
Reconcile and release
Compare bookings and balances with the old system, get sign-off from the retreat manager and agree the rollback window before cut-over.
What the customer provides
- Unit list with numbers, types and capacities, and seasonal rate plans.
- Upcoming bookings with guest details.
- Program calendar with leads, sessions and facilitators.
- Open folios, payments and the people who will use the system.
Changing it afterwards
Use Proto to prepare changes on a branch. Review changed fields, permissions and reports with the retreat manager and replay the pilot’s exception cases before release. Past stays keep the rates and charges that applied at the time.
Set up Wellness Retreat Management your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.