The schedule on the site should be the one on the floor.

Outdoor classes cancel. A studio closes early. Members trust the timetable on the site, and it is usually yesterday's. Otto keeps the public pages aligned with what is actually running.

The scheduleWhat members trust

A class that moved, a coach who left, and a closure that only made it into a story. People still drive over.

Otto updates class times and closure notes, in both languages when both pages exist. Memberships stay in the system you already use.

  • Class times include weather cancellations
  • Closure notes go up before the drive
  • Trials end when the dates say they do

The week the front desk already knows.

Otto does not run the studio. It stops the website from describing a schedule the weather already cancelled.

  • Classes and coaches

    Times, rooms, and who is teaching stay matched to the floor, including the class that moved indoors.

  • Closures

    An early close or a dark studio goes on the public page before members leave home.

  • Trials that end

    A challenge or an intro offer comes down when the dates say it does, not when someone remembers the site.

  • A read on what filled

    Which class pages are getting visits, which offers expired, and what is worth featuring next.

Memberships stay in your system.

Otto edits the public site. Billing, waivers, and the member login stay where they are.

  • Public pages only

    No member accounts and no billing. Otto never opens that system.

  • Offers expire on purpose

    A trial has an end date. It does not linger because no one filed a ticket.

  • Every schedule change is logged

    You can see what the public timetable said, including the closure note.

Members were booking a class the storm had cancelled.

An outdoor session can be pulled for the week while the homepage still lists it, in English. The Spanish schedule can already have the indoor replacement. Coach pages can still name people who have left.

Otto can put both languages on the same timetable and retire the bios, then wait for approval. The member system stays untouched.

Example: how a neighborhood studio could use Otto

Otto would stop the site from selling a class that is no longer on the schedule, and leave the change in draft until someone approved it.

  • 2Languages on the same timetable
  • 2Coach pages retired
  • 1Cancelled class taken off the homepage
  • 0Changes inside the member system