Public Batch Registration & Paid Demo Booking for Tuition Centres (2026)

A parent searches “Class 10 Maths tuition near me”, opens your page, likes the timing — and still cannot join. Fee is “contact us”. Demo is “message on WhatsApp”. At 9pm on a Sunday they are comparing three centres; whoever answers first with a clear next step usually gets the child.

Tutors keep asking for two things: a public batch list parents can act on, and a way to take a small demo fee so tyre-kickers stop wasting Sunday slots. Those are operating problems, not a reason to name or copy another company’s product. You can run both with a public page, WhatsApp, UPI, and one fee register.

This guide is for Indian home tutors and small coaching centres who want parents to see batches, raise a hand, pay a token if you want, and land in your fee register — without pretending you run a 500-seat academy. It covers the operating system, when a paid demo is worth it, and where a free public page plus WhatsApp is enough versus when you actually need self-serve Razorpay enrolment.

The real problem is not “no website”. It is the gap after interest

Parents already decide in three screens: Google / Maps, WhatsApp, and one public page that answers which batch, which fee, which next step. If your public page only says “Best faculty, limited seats, contact us”, you have given them nothing to act on.

The drop-off looks like this:

1. They found you. Maps, Instagram, a neighbour’s forward.
2. They liked the subject and area. Still not enrolled.
3. They had to message you to know the fee and the next demo date. You replied after class. They had already booked a demo somewhere else.

Public batch listing and a clear demo offer close that middle step. Online payment is optional. Speed and clarity are not.

Public batch registration: make the seat requestable

A public batch is not a pretty timetable graphic. It is a page a parent can screenshot and send to a spouse. Minimum information that converts:

• Batch name + class/board — “Grade 10 CBSE Maths — Mon/Wed/Fri 5–6:30”, not “Batch A”.
• Monthly fee in ₹ — hiding the number does not make you premium; it makes you look like a phone-tag business.
• One next action — enquiry form, WhatsApp, or “book Sunday demo”. Not all three fighting each other.
• Capacity as a human sentence — “12 seats, 3 left” if true. Fake urgency destroys trust faster than no number at all.

Some large institutes collect a one-time joining / registration fee online and auto-create the student in accounts. If you already run that volume, fine. For most independent tutors the same outcome is simpler: list the batch, take the enquiry, confirm the seat on WhatsApp, collect joining fee via UPI, then add the student to your fee tracker the same evening.

The operational rule that matters: the person who paid a joining fee must exist in the same ledger as monthly fees. If registration lives in a Google Form and monthly fees live in a notebook, you will argue about “I already paid admission” by month two. That is why the public page and the fee register have to be one story — even if payment is still UPI + screenshot.

A simple public-registration flow that actually gets used

1. Publish batches and monthly fees on one public page (your TutorPe profile at tutorpe.in/p/yourname works for this — batches, fee, address, enquiry form).
2. Parent submits name + phone + class. You get the lead without them hunting for your personal number in a bio.
3. You reply on WhatsApp within a few hours with: next demo / start date, joining fee if any, monthly fee, and UPI.
4. On payment, you send a dated PDF receipt and add them as a student in the same app you use for monthly collection.

That is public batch registration for a small centre. The parent self-served the interest. You still confirm the seat. You did not need a second admissions CRM.

Paid demo booking: when a token fee filters, and when it scares people off

Free demos fill rooms with tyre-kickers. Paid demos filter for seriousness — and can also empty the room if your centre is new and has no reviews. Use the fee as a filter, not as a revenue line.

Two rules that keep paid demos from becoming a mess:

• Let the parent suggest a time; you confirm it. Small centres do not run a public slot grid like a clinic. WhatsApp confirmation is enough and avoids double-booking.
• Say in writing whether the token adjusts against fees. “₹300 demo, adjusted in first month if you join” converts better than a silent charge.

How to collect without a gateway: one WhatsApp message, one UPI, one screenshot, one receipt titled “Demo class — [date]”. Put it in payment history so it is not a random PhonePe entry you forget. If they enrol, the next record is month-1 fee, not a second mystery payment.

Need copy-paste messages? Use fee and follow-up WhatsApp templates and keep a separate 4-line demo invite: dates, subject, token amount, UPI.

What parents should see in 15 seconds

Whether you use TutorPe’s public profile, Instagram highlights, or a Google Business post, the page has one job: make the next step obvious.

• Who you are (tuition name + teacher name + area)
• What you teach (batches with class names, not internal codes)
• What it costs per month
• How to ask for a seat or a demo (form + WhatsApp)

TutorPe’s public profile is built exactly for that stack: live batch + fee list, enquiry form (student name, parent phone, class, message), and WhatsApp/call links. It is not a Razorpay checkout that auto-enrols the child and decrements capacity in real time. We don’t pretend it is. For a tutor with 20–150 students, the bottleneck is almost never “parent couldn’t click Pay” — it is “parent couldn’t see the batch, or you lost the enquiry in chat.”

After they pay: one student, one ledger

This is where brochure tools fail and ops tools win. A public form that dumps rows into a spreadsheet is still a second system. The enrolment is only done when:

• The student exists in your batch
• Joining / demo / first-month fee is logged with date and mode (cash / UPI)
• The parent has a receipt they can forward
• Next month’s due is visible so you are not chasing from memory

That is the job TutorPe is actually built for: fee tracking, partial payments, WhatsApp reminders, PDF receipts, attendance. Public profile + enquiry is the front door. The dashboard is the house. A shiny join form that still leaves monthly fees in a notebook is not a finished system.

When you do need full self-serve payment (and when you don’t)

If your front desk already takes online payments all day, and confirming UPI screenshots is slower than teaching, you may want gateway auto-enrol and hard seat limits. That is a different product category than a free fee tracker. TutorPe is the tracker + public enquiry page, not a full checkout that enrols the child without you.

If you are a home tutor or a 2-room centre, start with public listing + enquiry + WhatsApp + UPI + one ledger. Add a payment gateway later if screenshot-confirming becomes the bottleneck. A same-evening WhatsApp reply still converts more parents than an unpaid form you ignore.

7-day setup you can finish after class

For filling empty benches beyond the form, use the same playbook as how coaching centres actually attract students and local SEO + retention — Maps, reviews, and keeping the students you already have.

Bottom line

Public batch registration means parents can see a real class and ask for a seat without hunting you. Paid demo booking means you can charge a token so only serious families book time. Both are about shortening the distance between “interested” and “enrolled.”

You do not need an ERP demo to start. You need a public batch list, a form that captures phone numbers, a WhatsApp reply with dates and UPI, and one fee ledger so joining money and monthly fees are not two different stories.

List your batches on a free TutorPe public page, take enquiries, and track fees in the same app →