Those who sell courses invest almost all their energy in acquisition and disappear after payment. The student is thrown into a platform and expected to manage on their own — and most do not manage. This guide covers the less glamorous part of the education business: the sequence that gets the student started, the follow-up that helps rather than embarrasses, the design of the question channel, and the refund reduction that determines whether there will be a second cohort.
In this article
- Why online courses sell but don’t deliver
- The four moments that define the outcome
- The doubt that blocks course purchase
- The welcome sequence that decides everything
- Following up without seeming like surveillance
- Course with cohort, date, and live sessions
- Where to ask questions: group, community, or chat
- Refunds and the guarantee window
- Official API, messages, and what is allowed
- What to automate and what not to
- What to record for each student
- The accounting of a cohort
- The most common mistakes
- Where to start
- Frequently asked questions
Why online courses sell but don’t deliver
Those who sell online courses face two uncomfortable numbers. The first is the completion rate, which in most self-paced courses is much lower than the producer imagines. The second is the refund rate, which rises when the student buys, doesn’t start, forgets, and asks for their money back on the eve of the guarantee period.
Both numbers have the same cause: the course platform does not communicate with the student. It hosts the video and records access, but does not notice when someone stopped at lesson three, does not ask why, and does not pull anyone back. WhatsApp does exactly that — and that is why it stopped being just a sales channel to become the delivery and retention channel.
The calculation that changes priorities: a student who completes gives testimonials, refers others, and buys the next product. A student who doesn’t start requests a refund. The difference between the two is usually decided within the first seven days.
Those who sell courses usually invest almost all their energy in the acquisition phase: ads, sales page, launch, offer. After payment, the operation disappears. The student is thrown into a platform and expected to manage on their own — and most do not manage.
This guide covers the part after "payment approved": the sequence that gets the student started, the follow-up that doesn’t feel like surveillance, the design of the question channel, refund reduction, and what the official API allows in this context. It’s the less glamorous part of the education business and the one that decides if there will be a second cohort.
Continue reading for free
Fill out once and unlock this and all other blog articles. We don’t charge anything — we just want to know who we’re writing for.
It takes 20 seconds. Prefer to talk directly on WhatsApp?
The four moments that define the outcome
- Before purchase. Questions about content, level, required time, access, and guarantee. Responding quickly here closes the sale.
- First 48 hours. The most decisive moment of all: those who enter and watch the first lesson within the first 48 hours have a much higher chance of completion.
- During the course. Blockages, doubts, and silent dropout, which is the most common form of abandonment.
- Afterwards. Certificate, testimonial, referral, and next purchase.
Most operations work well on the first moment and abandon the other three, which are precisely the ones that determine if the business sustains itself the following year.
The doubt that blocks course purchase
Before talking about delivery, it’s worth addressing the moment that precedes everything, because it’s quick and decisive. Those evaluating an online course almost never hesitate because of the content, which is described on the page. They hesitate for five specific reasons, all of which can be answered with objective information.
- "Is it for my level?" The person fears buying something too basic or too advanced. Answering what they need to know before starting solves it immediately.
- "Will I have time?" Total duration, lesson length, and suggested pace. The effective answer is concrete: how much time per week, for how many weeks.
- "How long do I have access?" Access period, whether there is renewal, and what happens afterward.
- "What if it doesn’t work for me?" The guarantee policy, stated clearly and without fine print.
- "Is there support?" Who answers questions, through which channel, and in what time frame.
Having these five answers written and ready to send changes two numbers simultaneously. It increases conversion because the person decides with their doubt resolved in minutes instead of postponing. And it reduces refunds because those who buy knowing the level, time, and format have expectations aligned with what they will receive — and misaligned expectations are the source of many refund requests.
The welcome sequence that decides everything
The message sent after purchase is usually an operational notice: "payment approved, access via platform." It’s a wasted opportunity because this message has the highest read rate of the entire operation.
The version that works has three parts and is sent at different times. At confirmation, access and a single instruction: where to start. The next day, a simple question about whether they managed to log in, which has two functions — solving access problems, which is the silent cause of much abandonment, and opening the conversation window. On the third day, a message related to the first lesson’s content, serving as a practical invitation for those who haven’t started yet.
None of these messages demand anything. All offer something — access, help, a starting point. Demanding at this stage produces silence and often refunds.
Following up without seeming like surveillance
There is a line between following up and bothering, and it’s simpler than it seems: the message should be about the content, not the student’s behavior.
Saying the student hasn’t accessed for twelve days sounds like surveillance and embarrasses. Sending a practical tip related to the module where they stopped sounds like help and reopens the conversation. Both messages come from the same information and produce opposite reactions.
The same applies to pace. Weekly contact with useful content is well received; daily contact asking if they’ve watched yet leads to blocking. In longer courses, it’s worth agreeing on the pace with the student at the start, asking how often they want to be reminded — those who choose the frequency rarely complain about it.
Course with cohort, date, and live sessions
When the course has a cohort, scheduled meetings, or group mentoring, the operation changes nature: it depends on attendance, and attendance depends on reminders. The effective design combines enrollment confirmation, a reminder the day before each meeting, a message at the moment the room opens with the direct link, and afterward, a notice of recording availability.
Two details make a practical difference. The link needs to be resent on the day, always, even to those who already received it, because it gets lost in the conversation history. And those who missed need to receive the recording with a message that doesn’t embarrass — the goal is to bring the person back the following week, not make them feel behind and give up entirely.
Where to ask questions: group, community, or chat
This decision defines the course’s operational cost and is almost always made without analysis. Each format has predictable behavior.
The group creates a sense of cohort and reduces individual support volume but concentrates complaints, allows one dissatisfied person to influence all others, and requires constant moderation. The community within the platform better organizes knowledge and creates a searchable archive but depends on the student logging in, which greatly reduces participation. The individual chat offers the best experience and highest cost and is the only one that allows noticing when someone stopped.
The most efficient arrangement is usually hybrid: individual chat for access, payment, problems, and re-engagement; group or community for content questions and peer exchange; and live Q&A sessions at defined intervals, which greatly reduce ad hoc demand.
Refunds and the guarantee window
Most refund requests in online courses don’t come from dissatisfaction with content. They come from someone who didn’t start, remembered the expense, and decided to ask for their money back before the guarantee period ended. This means refunds are largely an initial engagement problem, not a quality issue.
Three measures consistently reduce refunds: ensuring the student can access within the first 48 hours, delivering a small concrete result in the first week, and making a useful contact a few days before the guarantee period ends — not to discourage the request, but to resolve what blocked the student. When the request comes anyway, respond quickly and without friction: fulfilling promises protects reputation in a market where it spreads fast.
Official API, messages, and what is allowed
Online courses are a comfortable case for WhatsApp’s official platform because much of the messaging is utility-based: enrollment confirmation, access release, meeting reminders, recording notices, and certificate issuance. Three points deserve attention.
Starting a conversation outside the 24-hour window requires an approved template, and the category must correspond to the actual message content. Permission from the recipient remains mandatory, including for students — enrollment is not automatic consent for promotional messages. And within 24 hours after a student’s message, the conversation is free, covering almost all question support and is an argument for encouraging students to write first.
What to automate and what not to
- Automatic: purchase confirmation, access release, welcome sequence, meeting reminders, recording notice, certificate message, and inactivity trigger.
- Human or AI consulting the material: content questions, extension requests, specific technical problems, refund requests, and any upset student.
One caution applies to both sides: an automatic message that doesn’t recognize the student’s stage destroys trust. Sending "great you started" to someone who never accessed, or offering the course to someone who already bought it, are small errors that make the student conclude no one is paying attention.
What to record for each student
The history that supports the operation is short: purchase source, enrollment date, whether accessed within the first 48 hours, module where they stopped, participation in live meetings, completion status, satisfaction rating, and refund request. With these fields, after two cohorts useful patterns emerge — for example, which channel brings students who complete and which brings those who disappear, which is much more actionable information than which channel brings more sales.
The accounting of a cohort
A course costing R$ 697 with 140 enrolled students:
- Gross revenue: R$ 97,580.
- Without follow-up: 41% access within the first 48 hours, 19% complete, 11% request refunds. Refunds total R$ 10,734, 27 possible testimonials.
- With welcome sequence and follow-up: 78% access within the first 48 hours, 37% complete, 4% request refunds. Refunds total R$ 3,904.
- Direct difference: R$ 6,830 more in the same cohort.
- Indirect difference: 25 more completing students, who provide testimonials, referrals, and audience for the next launch.
The second difference is larger than the first and appears in the next quarter’s revenue, when the base of satisfied students supports the next cohort without needing as much advertising.
The most common mistakes
- Disappearing after the sale, treating delivery as the platform’s sole responsibility.
- Sending messages about student behavior instead of content.
- Using group as the only channel, mixing questions, complaints, and technical support.
- Not resending the link on the day of each live session.
- Ignoring the guarantee period and discovering the problem when the request arrives.
- Not recording who completed, losing the best list for the next launch.
Where to start
Build the welcome sequence in three messages and link it to payment confirmation. Define the question channel and communicate it clearly on day one. Create meeting reminders calculated by lesson date, with link resending on the day. Establish a useful contact before the guarantee period ends. And record, in this cohort, who accessed within the first 48 hours — because this single number will indicate, before any other, the completion and refund rates.
Frequently asked questions
How to reduce refunds in online courses?
Most refund requests don’t come from dissatisfaction with content but from someone who bought, didn’t start, remembered the expense, and decided to ask for their money back before the guarantee period ended. This makes refunds largely an initial engagement problem. Three measures consistently reduce refunds: ensuring the student can access within the first forty-eight hours, quickly resolving login problems; delivering a small concrete result in the first week; and making a useful contact a few days before the guarantee ends, aiming to unblock what prevented the student from starting. When the request comes anyway, respond quickly and without friction.
How to follow up with the student without seeming like surveillance?
The rule is simple: the message should address content, never behavior. Telling someone they haven’t accessed the course for twelve days sounds like surveillance and embarrasses, while sending a practical tip related to the module where they stopped sounds like help and reopens the conversation. Both messages come from the same information and produce opposite reactions. Pace also matters: weekly contact with something useful is well received; daily contact asking if they’ve watched leads to blocking. In longer courses, it’s worth agreeing on frequency with the student at the start, because those who choose the pace rarely complain about it.
What is the best question channel: group, community, or individual chat?
Each format has predictable behavior, and the best arrangement is usually hybrid. The group creates a sense of cohort and reduces individual support volume but concentrates complaints, allows one dissatisfied person to influence all others, and requires constant moderation. The community within the platform better organizes knowledge and creates a searchable archive but depends on the student logging in, which reduces participation. The individual chat offers the best experience and highest cost and is the only one where you notice if someone stopped. In practice, it works well to use individual chat for access, payment, and re-engagement, and group or community for content questions.
Course delivery is also a conversation.
VeyloCRM triggers the welcome sequence, reminds of meetings by lesson date, keeps each student’s history, and shows who accessed in the first days — before refund requests arrive.