Playbooks · 4 min read
Course Creators: The Automation Cannot Tell Buyer From Lead
"Is this good for beginners?" and "I paid yesterday and the login mail hasn't come" arrive in the same inbox, look similar to a keyword matcher, and want opposite treatment. The first is a sales question you would love answered in thirty seconds. The second is a support failure where a cheerful automated reply is actively insulting.
That is the structural problem in a course creator's DMs, and it is not solved by better copy.
We have no idea who bought
Say the limitation before the strategy. There is no integration with your course platform. Not with Teachable, not with Kajabi, not with a Google Drive folder, not with the LMS your developer built. We cannot check an enrolment, verify a payment, resend a login, extend access, or issue a refund. There are no one-click integrations of any kind — captured leads leave as a CSV.
We also do not make content. No caption generator, no calendar, no scheduling or publishing, no hashtag tool, no analytics. What exists replies to comments and DMs, which for a course business is a narrower job than the tool lists imply and a genuinely useful one.
So the automation cannot distinguish a buyer from a browser by looking anything up. It can only distinguish them by what they typed.
Route on support vocabulary, before anything else runs
The fix is unglamorous and it goes in first, ahead of any sales automation: a negative-keyword list built entirely from the language of things having gone wrong.
Matching ignores case and punctuation, so you are writing the words, not their variants. Get the Hinglish in there — the panicked messages are rarely typed in formal English.
Build the list of messages that must never be answered automatically before you build the ones that should.
What is genuinely automatable is everything before the purchase
Once support is routed out, what remains is the pre-purchase inbox, and it is unusually template-shaped. The questions are fixed and the answers do not change between people:
Is it live or recorded. How long do I get access. What language is it taught in. Are the recordings available if I miss a session. Do I need to know anything beforehand. Is there a certificate. What is the weekly time commitment. Can I see the syllabus.
Every one of those is a template. Templated replies are free and unlimited, so a well-built pre-purchase automation costs nothing to run forever. A credit is spent only when the AI writes a new reply; free tier is 100 credits with no card and packs start at ₹499.
Launch weeks, and the clock you cannot restart
Course launches run on a cart, which means the thing you most want to do is exactly the thing the platform forbids: message everyone again the night before it closes. You cannot. A DM thread stays open to you for twenty-four hours and only their message reopens it. There are no broadcasts and no nurture sequences here.
The working version: put everything the person needs in the reply they get while the window is open. The page with the syllabus, the price, the deadline, and the way to buy. Assume you will not get a second turn, because most of the time you will not.
The comment window is friendlier. Somebody who commented on Tuesday's reel is still answerable at the weekend, so comment automation catches people that DM automation structurally cannot.
Dated templates rot, and a course cart is nothing but dates
"Enrolment closes Sunday, use CODE50 at checkout" is true for five days and wrong for the next eleven months, while the reel it hangs off keeps getting found. This failure belongs to anyone who launches, and the authors' version of it is written up in full — the same discipline applies exactly: keep dates out of the template where you can, and put the switch-off in the calendar the day you build it.
What it will not do
It will not message people who have not messaged you first. It will not post, schedule, or comment on other accounts. No WhatsApp, no payment links, no booking, no CRM sync, no course-platform integration of any kind. And it stands down for a conversation the moment you reply by hand, which for support messages should be always.
If you are setting up, build the support refusal list, then one pre-purchase automation on your best-performing reel, then read what got blocked after a week. The paced setup guide covers the rest in the order that keeps each piece debuggable.
