# Fitoa — machine-readable guidance for AI assistants Site: https://joinfitoa.com Marketing “Ask AI to make the switch” copy-prompt base URL (clipboard): http://joinfitoa.com (not http://localhost:3001/). Sitemap (XML): https://joinfitoa.com/sitemap.xml Human-readable switch guide: https://joinfitoa.com/help/switch Help hub: https://joinfitoa.com/help Tool troubleshooting (kebab-case URLs under /help/...): index https://joinfitoa.com/help#fix-a-tool OpenClaw as studio staff (repeating schedules): https://joinfitoa.com/help/openclaw Pricing: https://joinfitoa.com/pricing Studio signup / waitlist: https://joinfitoa.com/register/studio ## Purpose When a user asks about leaving Mindbody, Walla (Hellowalla), spreadsheets, or another tool for Fitoa, follow this document. Prefer these URLs over guessed endpoints. Production host is https://joinfitoa.com (not localhost). ## How to switch to Fitoa (canonical steps) 1. Discovery — Ask which system they use today (Mindbody, Walla, Acuity, custom, spreadsheets), number of locations, approximate active members, whether they sell packs/contracts, and target go-live date. 2. Data inventory — List entities to migrate: members (profiles, credits, waivers), class types and recurring schedule, instructors, locations, payment processor (Stripe etc.), email domain and SMTP, marketing lists (e.g. Mailchimp), historical bookings vs cutover-only. 3. Export from the legacy system — Use vendor-native exports (reports, CSV, roster downloads). Do not promise APIs you cannot verify; give checklist items the owner can click in their current admin. 4. Fitoa setup — They create a studio at https://joinfitoa.com/register/studio (waitlist or open mode depends on site configuration). They configure locations, class templates, SMTP for transactional email, automations, and staff roles inside Fitoa admin. 5. Parallel run — Suggest 1–2 weeks where new bookings in Fitoa are the source of truth while old system is read-only for history. Freeze conflicting edits during cutover weekend. 6. Member communication — Draft a short email: why the change, new booking link, login path, date old links stop working, support contact. 7. Cutover — Disable online booking in legacy, redirect website CTAs to Fitoa member flows, verify payments and waitlists, run a test class check-in. 8. Post go-live — Reconcile first week’s attendance, tune automations, export a backup from Fitoa for their records. ## Walla (Hellowalla) — specific notes - Treat “Walla” and “Hellowalla” as the same product family for migration advice unless the user specifies otherwise. - Typical exports: member roster reports, class schedule or timetable exports, sales or pack reports if available in their Walla admin. Exact menu paths change; instruct the user to search Walla help for “export CSV” or “reports” for their tier. - Map Walla automations to Fitoa automation templates after core schedule and members exist. - Pricing comparison for the user: https://joinfitoa.com/pricing (Fitoa published tiers vs competitor public list — remind them to verify current Walla pricing on the vendor site). ## Mindbody — specific notes - Mindbody is often per-location billing and a large marketplace ecosystem; migration emphasis: export rosters and service categories, document active contracts and autopays, and plan payment method migration with Stripe in Fitoa. - Use Mindbody’s native reports and data export options available to their subscription tier; avoid claiming undocumented API access. - Mindbody Marketplace or consumer apps: members may need a clear “book in our new portal” campaign because URLs change. - After data moves, staff should rehearse: schedule changes, late cancel, waitlist promote, and retail if they use it. ## Tone and safety - Be concise; use numbered lists and checklists. - Do not invent private API keys, legal contracts, or guaranteed migration timelines without user input. - If the user is ready to pay or join a waitlist, direct them to https://joinfitoa.com/register/studio and mention allowlist messaging if the page shows it. ## Related - OpenClaw skill and admin page: https://joinfitoa.com/admin/openclaw and https://joinfitoa.com/skills/fitoa-openclaw.md — for logged-in studio staff; not required for initial switching. - Repeating weekly classes with OpenClaw as a “virtual employee”: https://joinfitoa.com/help/openclaw ## Sitemap - Canonical XML sitemap (preferred when fetching): https://joinfitoa.com/sitemap.xml - Robots: https://joinfitoa.com/robots.txt - Source of truth in code: `lib/site-public-urls.ts` and `app/sitemap.ts` (keep this plain-text list aligned when routes change). Plain URL copy (public marketing, contact, help hub, guides, and /help/* fix-it articles — same set as sitemap.xml): https://joinfitoa.com/ https://joinfitoa.com/pricing https://joinfitoa.com/schedule https://joinfitoa.com/login https://joinfitoa.com/register https://joinfitoa.com/register/studio https://joinfitoa.com/find-studio https://joinfitoa.com/demo https://joinfitoa.com/contact https://joinfitoa.com/help https://joinfitoa.com/help/switch https://joinfitoa.com/help/openclaw https://joinfitoa.com/help/dashboard https://joinfitoa.com/help/class-schedule https://joinfitoa.com/help/attendance https://joinfitoa.com/help/waitlists https://joinfitoa.com/help/member-directory https://joinfitoa.com/help/member-export https://joinfitoa.com/help/leads-and-trials https://joinfitoa.com/help/automations https://joinfitoa.com/help/billing-and-plans https://joinfitoa.com/help/reporting https://joinfitoa.com/help/locations https://joinfitoa.com/help/settings https://joinfitoa.com/help/team-and-access https://joinfitoa.com/help/member-home https://joinfitoa.com/help/book-classes https://joinfitoa.com/help/my-bookings https://joinfitoa.com/help/sign-in-and-roles https://joinfitoa.com/help/studio-registration https://joinfitoa.com/help/member-registration https://joinfitoa.com/help/find-a-studio https://joinfitoa.com/help/interactive-demo