Help · Classly.software
This is one thick reference, not eight thin stubs. Each section below composes from the same material the rest of the site draws on — the capacity-N booking law, the capabilities list, the FAQ — nothing here is written twice.
Read the pill on any capability before the headline: built means a shared-engine mechanic that exists right now; planned means designed and not built. Onboarding today is a guided conversation, not a self-serve wizard.
The checklist for a new studio.
Who runs what once the console lands.
The four-step capacity-N flow, built vs. planned.
Branding at the Studio tier — not paywalled to the top.
Common questions, answered once.
The two conflict reasons, and why over-booking can’t happen.
Getting started
mailto:[email protected].Admin & instructor setup
An instructor or studio-owner console — publishing a session and its seat count, toggling which session types are open, seeing the roster — is designed on the same shared engine the rest of the schedule.software family is built on, and it is not built on a classly.software surface today. When a K-12 after-school module ships, roster identity is stripped at the server through the family’s consent chokepoint, never a client-side filter — the same guarantee every sibling in the family holds.
How booking works
Reused verbatim from the workflow this page teaches elsewhere on the site, so this section and the home page can never quietly disagree about what the flow is.
Step 1 — An instructor publishes a session and a seat count (surface in development)
An instructor sets up a session — a class, a workshop, a recurring weekly meetup — and publishes how many seats it holds. This is part of the classly.software roster page, which is in development and not live today.
Step 2 — People book into the same session, not a private slot (surface in development)
A client sees a session's real remaining seats and books into it — sharing the session with everyone else who books, unlike a 1:1 appointment link. If the session is full, they're offered the waitlist instead of a dead end. Also part of the surface in development.
Step 3 — The server guarantees the seat count in one transaction (built)
This step is the built part. The shared capacity-N decision core counts live bookings under a lock in the same transaction that books, rejecting a booking that would push a session over its published seat count before any write lands, and preventing the same person from double-booking the same session with a partial-unique index. A conflict returns a clean, retryable machine reason — never a silent over-fill.
Step 4 — An instructor sees the roster and marks attendance (planned)
After bookings close, an instructor's dashboard shows the roster who actually booked in, with a place to mark attendance for the session that ran. This dashboard is designed and planned; it is not built today.
White-label
Your logo, your colors, and the “Powered by Classly” badge gone — a Studio-tier commitment, one plan step up from Starter. The sending domain and the consent/legal footer stay the platform’s at every tier; that floor does not move. This is a planned pricing-tier feature, not a live self-serve screen today.
Custom domain
Most class-booking tools reserve a custom domain for a paid, often higher, tier. The plan here puts it on Starter instead. The planned mechanism is a DNS-TXT ownership proof on the same shared platform the family is built on — you prove you control the hostname, no invented CNAME/ACME dance; the classly.software-branded screen for claiming a domain yourself is in development, and no custom domain is served on this brand today.
FAQ
An appointment slot has a capacity of exactly one — one person claims it and it's gone. A classly.software session has a capacity of N — many people book into the same session up to a published seat count, with a waitlist once it fills. Both run on the same shared fixed-slot / identity-keyed capacity decision core; capacity-N is simply that core's other mode, not a different, retrofitted product. This is a genuinely different booking mechanism, not a re-skin of a 1:1 tool with classes bolted on afterward.
No. The capacity-N booking law itself is built in the shared engine. The branded classly.software surfaces around it — the public roster page a student would open, the waitlist queue, and the instructor's attendance dashboard — are in development or planned; none of them is built today. We say this plainly rather than imply a console exists.
No commission skim on any booking, at any tier — a stated pricing commitment for the planned Starter and Studio tiers below. classly.software does not process live payments today; this is a claim about how pricing is planned to work, not about a live checkout running now.
No. classly.software is a separate product with no association, affiliation, or shared ownership with any other product operating under a similar mark, in any market or vertical. This page does not name, link to, or reference any such product, and does not borrow its positioning or copy.
classly.software is the single-session sibling: one class, one seat count, drop-in or recurring bookings into the same session. cohort.software is the planned companion for recurring fixed-roster series enrollment — a multi-week program where the same group of people stays enrolled across sessions. Both are designed to run on the same capacity-N booking law; neither is live as a standalone product surface today, and neither is a feature of the other.
No, it is not an application-code check. Per-session capacity is counted under a SELECT … FOR UPDATE inside the same transaction that books, and a partial-unique index prevents the same person from double-booking the same session. A booking that would exceed the published seat count is rejected at the database before any write lands, with a clean, retryable machine reason — not a form-level check a race condition could slip past.
No, and nothing here will try to charge you. The tiers are a published intention; there is no live checkout, no card is charged, and the Stripe seam behind those numbers is switched off. Reserving early access puts you in a conversation about what your studio needs — billing is a later conversation that starts only once there is something to bill for.
The capacity-N booking law — per-session seat counting under a lock, no-double-book at the database — is built in the shared engine this whole family is assembled on. The standalone classly.software product surface (the public roster page, the waitlist queue, the instructor dashboard, self-serve onboarding) is in development or planned. So the honest answer is: nothing on this brand, yet. Book a conversation and we will show you the seat law running and name a date for the roster page rather than a demo of one.
Not for the domain, as planned: a custom domain sits on the entry Starter tier, not locked behind an enterprise conversation the way it is on some sign-up tools. Removing our badge and applying your logo and colors is Studio, one plan step up. Both are planned pricing-tier commitments today, not a live self-serve screen — the classly.software-branded setup screen for a domain or a brand is in development, the same status as the roster page and the waitlist queue above, and classly.software sets no custom domain and removes no branding today.
No, and we say that plainly rather than let it be assumed. A white-labeled account would carry your display name and reply-to on any notification; the actual sending domain and the consent/legal footer stay the platform’s at every tier — that floor does not move, even at the top plan. This is a planned pricing-tier shape; classly.software sends no notification email today.
Troubleshooting
Per-session capacity is counted under a SELECT … FOR UPDATE inside the same transaction that books, and a partial-unique index stops the same person from double-booking the same session. A conflict — a full session, a duplicate booking attempt — returns a clean, retryable response with a machine reason, never a silent over-fill and never a 500.
Data & privacy
There is no public roster to browse and no open sign-up sheet on this brand today. When a K-12 after-school surface ships, every identity field on a roster route passes through a consent chokepoint: a suppressed student’s name and grade are stripped at the server — not hidden by a UI filter a client request could disable — and the row still counts toward capacity. A guardian would see only their own child.
classly.software does not hold FERPA, COPPA, SOC2, or VPAT certification, and holds no student data of any kind today — there is no branded roster surface live yet.