Your ₹99 workshop is a funnel, not a payment link

Where the funnel actually leaks

A ₹99 payment tells you very little. What tells you who will buy the main course is what happened next, and that is exactly the data most setups throw away:

• the payment page knows who paid, but not who joined the session
• Zoom knows who joined, but nobody matches it back to the payer
• questions asked in chat sit in a Zoom export nobody opens
• the main-course offer goes to everyone at once, or to nobody, because there is no list of who stayed till the pitch
• a payer who missed the session gets the same message as someone who sat through all 90 minutes

So the team ends up either spamming the whole list or chasing a handful of names someone remembers. Both waste the ad money that paid for the workshop.

This is the same continuity problem I wrote about for sales teams: Stop running the pipeline in Excel and WhatsApp. For a course business the "pipeline" is just shorter and faster. A lead goes from ad to payer to attendee to buyer in a few days, so every gap shows up quickly.

One record per person, from ad to enrolment

Before automating anything, I want one row per person that carries the whole path:

1. Source — which ad, post, or referral brought them in
2. Workshop payment — paid, failed, or refunded, with the payment reference
3. Attendance — joined or not, and roughly how long they stayed
4. Signal — did they ask a question, reply to a poll, or click the offer link
5. Offer status — offered, paid in full, on instalments, or not interested
6. Owner and next step — who calls or messages them, and when

If those six things are not on the same record, you cannot tell your hot leads from your cold ones. And if you cannot tell them apart, every follow-up becomes a broadcast.

The order we wire it

When a course business asks for "automation" around a workshop, this is the order that holds up:

1. Payment writes the record. The ₹99 payment creates or updates the person. Not a screenshot, not a sheet someone fills in later. GST invoice details are captured here too, so you are not chasing billing details after the sale.

2. Joining details come from the record. The Zoom link and reminders go out from the same system that knows they paid. A failed payment does not get the link; a refund removes access.

3. Attendance comes back to the record. After the session, attendance is matched to the payer. This is the step most setups skip, and it is the most useful one.

4. Follow-up splits by what actually happened. Attended and stayed for the offer: a direct, personal follow-up from a named owner. Paid but missed it: a recording and a second chance, not a sales push. Did not pay: nothing, or a light nudge for the next batch.

5. The main-course payment closes the loop. When they enrol, the same record moves from workshop attendee to student, and course access unlocks from there.

Only after this runs cleanly for one or two batches does it make sense to add smarter pieces, like scoring who is most likely to buy or drafting follow-ups with AI. Automating before the record exists only sends the wrong message faster. Same rule I follow for any SME: wire AI into the operating system, do not bolt it on. And for the WhatsApp side specifically, the basics are in how to automate lead follow-up on WhatsApp.

What not to build first

It is tempting to start with a fancy landing page, a countdown timer, or a full LMS for a course that does not have its first ten paid students yet. None of those fix the leak above.

A plain landing page, a payment that writes a record, a session, and a follow-up list split by attendance will beat a beautiful funnel that forgets who showed up.

A test for your next workshop

After your next session, try answering these without opening WhatsApp:

• How many people paid, and how many of them actually joined?
• Who stayed until the offer?
• Who asked a question during the session?
• Who owns the follow-up for each of them, and by when?
• How many main-course enrolments came from this batch, and from which ad?

If any of these needs a manual export and an evening with a spreadsheet, the workshop is working and the system around it is not.