Coding classes for kids booking is seat inventory, not a calendar
An after-school institute sells something a plain date picker cannot express: a seat at a laptop with an instructor beside it, tied to a curriculum week. Publish a generic calendar and the 4 pm Saturday Scratch batch double-sells inside a month. Coding classes for kids booking stops failing when seats become inventory with states instead of appointment rows. SWIQ runs this model for Scratch, Python and robotics studios in India, where one booking holds a seat, an instructor and a batch week together.
The grid: age bands crossed with real capacity
Capacity is the least glamorous part of coding classes for kids booking, and the first thing that breaks. Build rows from age bands and columns from the slots you can actually staff: 6–8 ScratchJr at 60 minutes with eight seats, 9–11 Scratch at 75 minutes with ten, 12–14 Python at 90 minutes. Then intersect with hardware, because hardware is what people forget: a robotics batch is capped by robots, roughly one shared robot per two kids. Real capacity is the minimum of machines, robots and instructor load, so publish that number and let the booking page refuse the eleventh seat instead of improvising on Saturday. The form should also ask age and prior experience: a seven-year-old in the Python batch is a trial that ends badly.
Trial to enrolled: a six-state flow with one owner per transition
Model the conversion explicitly: requested → trial_scheduled → trial_attended → enrolled → paused → churned. Each transition gets exactly one owner — the desk schedules within a working day, the instructor marks attendance at the laptop, the owner flips enrolled only once the batch fee is recorded. Most of the money lost in coding classes for kids booking sits in these transitions. A no-show trial returns to requested with a retry message, not to churned. A sibling joining is one family, two seats and one payment record. A child entering in week four takes a level test first; the curriculum does not reset for one student. And never transition on a promise: "I'll pay tomorrow" leaves the seat in trial_attended — the standard route to a full calendar and an empty bank account.
The perishable seat: make-ups, holds and a waitlist with positions
A seat nobody occupies at 4 pm on Tuesday is gone; it cannot be banked for Thursday — the fact coding classes for kids booking must be designed around. So make-ups need hard rules: two credits a month, claimable only into genuinely open seats, requested at least 12 hours ahead. Hold one or two seats per batch until 48 hours before the first class for late siblings and converted trials, then release them: a buffer without an expiry becomes an empty seat you never sell. Waitlists should carry a visible position: when a seat opens, the first family in line gets a short claim window, then it passes to the next. Those numbers are sensible practice rather than law; every hold just needs a clock.
WhatsApp confirmations, reminders and the crowded lobby
Parents read WhatsApp. Four messages cover almost everything: booking confirmed with batch, time, address and instructor name; a reminder 24 hours before the first class; a "class starts in two hours" nudge on the day; and one line afterwards so the parent sees value without calling. Put the cancellation window inside the first message — free until 12 hours before, a credit consumed after — because a policy nobody reads becomes a policy you enforce angrily.
The lobby needs the same discipline: early-arriving parents crowd the desk while the previous batch runs, so a queue display turns them into a number on a screen and staff finish what they are doing. For the wider shift off Google Forms and spreadsheets, this guide to appointment booking apps in India for 2027 covers what small operators should expect.
Copy-ready: the parent-facing booking policy
Paste this onto the booking page or into your WhatsApp auto-reply:
Batch booking policy — please read
- A booking holds one seat in one batch for the full eight-session cycle. Seats are confirmed on payment, not on enquiry.
- Free cancellation with full refund until 48 hours before the first class; after that one credit is consumed.
- Each student gets two make-up credits a month, claimable into open seats with 12 hours' notice.
- Siblings hold separate seats and one combined payment record.
- Trial classes occupy one seat for 45 minutes. Two no-shows close the trial until the parent re-requests it.
- Students joining after week two take a level test first.
- Missed classes without notice are marked absent; the seat stays reserved.
- Batch fees are non-transferable but may move once to the next batch with seven days' notice.
Four numbers worth a weekly look
Fill rate per batch (seats sold ÷ seats available), trial-to-enrolled conversion, make-up credits redeemed, and no-shows per slot. Fill rate under roughly 70% two weeks into enrolment is a follow-up problem rather than a pricing problem — the trial happened and nobody asked for the fee. Trial conversion under 40% usually means the child enjoyed it and the parent never received the next message. Double-booking should be a hard zero; if your system tolerates it, every other number above becomes unreliable. Group these per batch in basic analytics, so a Saturday Scratch batch and a Wednesday Python batch are never averaged into one comfortable percentage.
Where this leaves you
Treat the batch as the product, the seat as inventory with an expiry, and every parental promise as unconfirmed until it is recorded. That covers most of what goes wrong in coding classes for kids booking, and none of it needs extra instructors. SWIQ holds batch calendars, seats, waitlists and WhatsApp reminders in one place — the landing page walks through the flow — while the shared-resource slot logic is written up in the clinic booking system post, where rooms and staff are held the same way. Plans start at ₹777 a month, first 300 bookings are free, setup takes two minutes with no card; questions go to WhatsApp on +91 79002 60076 in Jodhpur.
Top comments (0)