Questions, answered

Click Get started, then use Proto to configure Wellness Retreat Management for your business. Start with one season’s units, rate plans and bookings, and run a month of stays live before adding program capture.

No. Confirming a stay reserves every night from arrival up to departure at once, and a second booking for the same unit and nights cannot be confirmed.

Programs and sessions run on their own calendar beside the stays. The front desk sees both, so arrivals and sessions line up.

Add the replacement as a correction. The original assignment stays in the record, so you can see who was planned and who led the session.

After checkout the room goes to cleaning, and it becomes available only when the cleaning task is completed and the inspection passes.

Payments are recorded against the stay and confirmed by the accounts clerk. Checkout reconciles posted charges against confirmed payments only. Card processing stays with your provider.

Yes. Rate plans set the nightly rate and minimum nights for each unit type over a season.

Yes. Service staff see their assigned tasks and facilitators see their sessions; roles control who confirms stays and payments.

Ordinary manual use has no per-user charge under the platform policy. Imports, integrations, agent execution and other machine work use prepaid credits; implementation is scoped separately. The pricing page lists current rates.