Case Study

The Course Was Already Unlocked. Nobody Had Told the Students.

How a missing purchase confirmation turned into a paid-acquisition problem for a spoken-English brand — and the second account where low-ticket direct sales hit the same ceiling.

Role
Marketing Consultant (external, ongoing)
Period
August 2024 – present
Market
India and UAE

The short answer

Students were buying the course and hearing nothing back. No confirmation, no next step, no indication anything had happened.

So they went to the brand's social accounts and said publicly that they had paid and been given nothing. They were wrong — access had already been granted in the backend. The only thing that had failed was the message telling them so.

The damage didn't stay in the support inbox. Those comments landed on the ads themselves, which meant cold prospects were reading accusations of fraud before they ever reached the landing page. A fulfilment-notification gap was quietly suppressing conversion rate on paid.

We closed it with WhatsApp automation — payment triggers confirmation and next steps immediately, with the operations and sales teams notified in parallel. The comments stopped, and the paid channel started converting on its own merits.
The transferable principle

On paid social, post-purchase communication is an acquisition channel. Your angriest customers are commenting on the ads your coldest prospects are reading.

The situation

Serene Paathshala is a creator-led spoken-English brand selling into India and the UAE, with a premium sub-brand, Speak Perfecto, used for the paid funnel — the name reads better to an English-learning audience than the parent brand does.

When I came in as a marketing consultant in August 2024, there was nothing running on paid at all. Everything was organic, and the problem with organic was consistency: revenue moved with whatever happened to perform that month, which makes planning impossible.

But the brief wasn't only "run ads." There were several problems tangled together, and the interesting part of this account is that the acquisition problem and the fulfilment problem turned out to be the same problem.

What was actually broken

A student would purchase the course. In the backend, their access was unlocked immediately — the product worked exactly as intended. What didn't happen was anyone telling them.

No timely confirmation. No next step. No "here's where to log in." From the student's side, they had paid money into a void.

What they did next was entirely reasonable from where they were standing: they went to the brand's Instagram and Facebook and said so, publicly and angrily, accusing the business of taking payment and withholding access they had in fact already been given. The support team spent its days replying to the same accusation across comments, posts and DMs, without ever fixing the thing generating it.

Then we turned on Meta ads, and the cost of it changed completely.

Comments attach to the ad. A cold prospect who has never heard of the brand clicks through, or simply scrolls, and reads a queue of people saying they were defrauded. That is the most damaging social proof available, sitting on the exact asset we were paying to distribute — and it was suppressing conversion rate on a product that was, in fact, being delivered correctly the whole time.

It would have been easy to file this as customer service and keep optimising creative. It was a media problem.

Closing the gap

The fix was unglamorous: make the payment event trigger a message, immediately, on the channel the audience actually uses.

A successful payment now writes to the database and fires a WhatsApp confirmation with access details and next steps, while the operations team is notified in parallel so a human knows a student has arrived. Failed payments route to the sales team instead — a different problem needing a different response, and previously invisible to everyone.
Trigger
Course purchasePayment success or failure
Orchestration
Automation workflowRoutes on payment outcomen8n + Claude via MCP
Student recordAccess stateSupabase
Lead + order logGoogle Sheets
To the student
Instant confirmationAccess details and next stepsWhatsApp Cloud API
To the team
Payment success → operationsA student has arrivedSlack
Payment failure → salesRecoverable, previously invisibleSlack
Built with n8n and the WhatsApp Cloud API, assembled using Claude through the n8n MCP. The engineering here is ordinary — the leverage was in noticing that this was an advertising fix, not a support one.

Why it worked

Two things happened at once, and they reinforced each other.

The complaints stopped at the source. Not moderated, not out-argued — eliminated, because the thing causing them no longer happened. That cleaned the ads as an asset: a prospect landing on a post now reads the offer rather than a queue of accusations. The support team stopped spending its day on a problem that regenerated itself every morning.

Paid gave the existing demand somewhere to go. This is the honest qualifier on the whole account: the client already had a real audience across YouTube, Instagram and Facebook. The demand existed. Organic simply couldn't reach all of it reliably, and couldn't be scheduled. Paid didn't manufacture interest here — it reached people who were already inclined and gave revenue a consistent floor.

That distinction matters if you're trying to apply this. Paid social on top of a genuine creator audience behaves very differently from paid social trying to build demand from nothing, and the results here shouldn't be read as the latter.

The same ceiling, again

The direct funnel worked. Landing page, low-ticket course, buy on the page — it held 2.5–3x ROAS and then stopped responding.

Not a creative problem and not a targeting problem. The same structural wall I had run into at Entri four years earlier, on a different product, in a different category, for a different client: the pool of people willing to complete an unassisted purchase decision for a course is finite, and you exhaust it well before you exhaust the market.

The resolution was the same shape too, but this time with the qualification step automated. The landing page still sells directly to people ready to buy. Everyone else gets routed to WhatsApp — where an AI agent asks a short set of questions, places the student at beginner, intermediate or advanced, and hands them to the person best placed to sell the right thing. That triage is what makes premium courses sellable at all: you can't pitch an advanced programme to someone who needs the fundamentals, and you can't discover which they are from a landing page.
Direct onlyObjective: Purchases
Meta ad
Landing pagespeakperfecto.com
Buy low-ticket course

Held 2.5–3x ROAS, then stopped responding — the same ceiling as the Entri account, four years and one category apart.

Direct + AI-qualified assistedObjective: Purchases and conversations
Meta ad
Landing page
Ready to buy
Buy on page
Has questions
WhatsApp conversation
AI agent qualifiesBeginner / intermediate / advanced
Routed to matched agent
Premium course pitchedLevel-appropriate

Assisted path makes premium tiers sellable — level is something you discover in conversation, not on a landing page.

The second principle

Low-ticket direct-response course selling has a structural ceiling, not a creative one. Past it you scale by adding qualification and raising order value — I have now hit this in two unrelated accounts.

How to apply this

What transfers out of this account into any similar one:

  1. Before you scale paid, read the comments on your existing posts. If your own customers are angry in public, you are paying to distribute that anger to people who have never heard of you.
  2. Treat post-purchase messaging as acquisition infrastructure, not support hygiene. It sits upstream of conversion rate on paid social, which is not where most teams look for it.
  3. Check whether the product is actually broken before you rebuild it. Here it never was. The entire crisis was an information gap, and the fix was a message rather than an engineering project.
  4. Notify the team, not just the customer. Payment success to operations, payment failure to sales. Failed payments are recoverable revenue that is invisible unless someone is told.
  5. Expect the low-ticket direct funnel to cap. Plan the assisted path and the premium tier before you need them.
  6. Automate the qualification, not the selling. An AI agent placing someone at beginner or advanced is fast and consistent. The pitch that follows still lands better from a human.
  7. Be honest with yourself about whether paid is creating demand or reaching it. On top of a real creator audience it is doing the second, and that changes what you should expect elsewhere.

Evidence and limits

I have worked on this as an external marketing consultant since August 2024, and the engagement is ongoing.

The one performance figure here is 2.5–3x ROAS on the direct funnel before it hit its ceiling. Spend, revenue and student volumes are not mine to publish, so they aren't here — and I would rather show one number I can stand behind than pad the page with figures I can't. There is no before-and-after conversion rate for the comment problem, because we didn't instrument it as an experiment; the comments stopped because the cause was removed, which is observable but not a measurement.

What is directly checkable is the brand, the funnel and the audience the account was built on.

What can be independently checked:

Piyush Sachdeva

By Piyush Sachdeva

Founder of Social Masla and Pulse. Author of The Growth Engine.