Why do generic helpdesks struggle with online course support?
A generic helpdesk knows an email address. Course support depends on what sits behind it: which courses that person owns, which cohort they joined, whether their last installment cleared and how far through the lessons they are. Without those details, every reply starts with a hunt through two or three other tools.
- Buyers often write from a different address. Work accounts, PayPal logins and a partner's card all produce "I paid but there's nothing in my dashboard", and a tool that matches on email alone shows a stranger.
- Volume follows your launch calendar. Cart close, a cohort's first week and the first installment date after a launch each bring a wave about one product, while ordinary weeks stay quiet. Monthly averages hide it.
- Refund calls depend on data the helpdesk lacks. The purchase date, lessons completed, which version of the guarantee applied at checkout and the buyer's country decide the answer.
- The people who can answer content questions aren't on the support team. Instructors and TAs need to read a thread and leave a note without being handed a full seat and a queue of their own.
- Support leaks into community spaces. Learners post billing and login problems in Discord, a Facebook group or your community platform, where account details should never be discussed in public.
- Several kinds of customer share one address. Individual learners, companies buying staff seats, affiliates chasing commissions and guest instructors all email support@, and each needs a different owner.
How should an online academy set up its support inbox?
Create queues around what the learner needs and who is allowed to decide it, and attach course, cohort and payment-plan fields to every conversation. The layout below fits an academy that sells a handful of self-paced courses alongside two to four live cohorts a year.
| Queue | What lands there | SLA target (example) | Owner |
|---|---|---|---|
| Access and login | Missing courses, login links, purchases under another email, community invites | 2 business hours; 30 minutes during a cohort's first week | Support lead |
| Billing and payment plans | Failed installments, pay-in-full requests, receipts, plan changes | 1 business day | Billing specialist |
| Refunds and disputes | Requests outside the guarantee, refunds that cite promised results, chargebacks | 1 business day; dispute evidence well before the processor's deadline | Founder or finance lead |
| Live sessions | Joining links, rescheduled sessions, recordings, time-zone mix-ups | 15 minutes, from an hour before each session until it ends | Cohort coordinator |
| Course content | Questions about lessons and assignments, requests for feedback | 2 business days | Instructors and TAs; support sends the reply |
| Accessibility | Captions, transcripts, alternative formats, extra time on assessments | 1 business day | Named accessibility owner |
| Certificates and records | Disputed completion, name corrections, verification requests from employers | 2 business days | Program manager |
| Teams and partners | Company seat assignments, invoices, purchase orders, affiliate commissions | 1 business day | Partnerships or account manager |
SLA targets are examples. Set yours from your own volumes and from what your course terms promise.
Routing rules worth setting up
- Bring course, cohort, payment-plan status and lesson progress in from your course platform through the Aftersales API or webhooks, and use them as columns and filters. Confirm the connector for your platform on a call.
- Move any thread that mentions "chargeback", "dispute", "my bank" or "scam" into Refunds and disputes at high priority, whichever queue it started in.
- Shorten the Access and login SLA automatically for learners whose cohort opens within seven days.
- Turn on round-robin assignment (Growth and up) in Access and Billing so launch week doesn't fall on one person.
- Tag reports of a dead video or a broken quiz as a content bug. A workflow then alerts your production team in Slack and files a Jira issue, so one fix can close every matching thread.
- Route company accounts by custom fields such as seat count and region, and give your biggest corporate clients a Slack Connect channel that lands in Teams and partners.
What reply templates should an online course support team keep?
Write templates for the conversations where one careless line costs you a refund, a chargeback or a public review. Have whoever owns your guarantee approve them before the next launch. Placeholders are in braces.
Refund request after the guarantee has closed
Hi {first_name}, thanks for explaining why {course_name} isn't working for you. You enrolled on {purchase_date}, and the {guarantee_days}-day guarantee ended on {guarantee_end}, so a refund isn't something I can offer. What I can do is {alternative}, for example a place in the {next_cohort} cohort or a switch to {other_course} at no extra cost. Reply with the one you'd prefer and I'll set it up today.
Refund request that cites promised results
Hi {first_name}, I'm sorry the course hasn't delivered what you hoped for. I want this reviewed properly, so I've passed your message to {owner_name}, who handles refund reviews, and you'll hear back by {date}. If a page, email or video led you to expect a particular result, please send me the link or a screenshot so it's part of the review.
Never debate in writing what a sales page meant; escalate instead. The FTC has said that certain practices in the education marketplace are deceptive or unfair, which is one more reason a lead should review every reply that touches outcomes.
Learner has filed a chargeback
Hi {first_name}, your bank has told us you disputed the {amount} payment for {course_name}. While the bank reviews it, those funds are already back with you, so we can't send a separate refund on top. If you would rather settle this with us, withdraw the dispute with your bank and we'll {resolution_offer}. Otherwise we'll send the bank your purchase record, the terms accepted at checkout and your course activity. Course access stays paused until the dispute closes.
For digital goods, Stripe's evidence guidance suggests including an IP address or system log showing the customer used the product, so export lesson activity before you respond.
Missed installments and financial hardship
Hi {first_name}, thank you for telling me what's happening. Your {plan_name} has {remaining_installments} payments left, and the {failed_amount} due on {failed_date} didn't go through, which is why your access is paused. I can {hardship_option}, for example spreading the balance over {new_count} smaller payments or pausing the plan until {pause_end}. Your progress is saved whichever you choose. Let me know and I'll reopen your access as soon as the new plan is in place.
Deferral after illness or bereavement
Hi {first_name}, I'm so sorry to hear about {circumstance_summary}. Please don't worry about the course right now. I've held a place for you in the {next_cohort} cohort starting {start_date}, and you keep the recordings from this one. There's nothing you need to send us. Whenever you're ready, reply here and I'll confirm the details.
Accessibility request
Hi {first_name}, thanks for letting us know what would help. I've shared your request for {accommodation} with {owner_name}, who coordinates accessibility for {course_name}, and they'll confirm what we can provide by {date}. Meanwhile, {interim_option}. Share only as much detail as you're comfortable with.
How should a course business staff support around launches and cohorts?
Staff for your own calendar rather than for an even week. Most academies need a small core team, instructors on call for content questions and extra cover on a handful of dates you can see coming months ahead.
Who does what
- Support reps own access, billing and certificates, and send the reply on content questions once an instructor has left a note.
- A cohort coordinator owns joining links, recordings and schedule changes, and keeps the inbox open during every live session.
- Instructors and TAs answer through internal comments and @mentions on free Lite seats (20 on Growth, 50 on Scale). Anyone who writes to learners directly needs a full seat.
- The founder or a finance lead approves refund exceptions and payment-plan changes, also from a Lite seat.
- A solo creator can run all of it from the one seat on the Free plan and add queues once a second person joins.
Hours
People take online courses around jobs and families, so messages arrive in the evening and at weekends. Cover the hour before each live session and the hour after it, when link and recording questions come in. When a cohort spans several continents, stagger shifts so overnight messages aren't left for the morning.
Peaks to plan for
- Cart open and cart close. Prospects ask about payment plans, start dates and refund terms, and a checkout error on the final day needs a person fast. Put your most experienced rep on sales-page chat.
- A cohort's first week. Access, onboarding and community invites peak in the first few days. Hold the 30-minute access target and keep leave off the calendar.
- The first installment after a launch. With monthly plans, failed payments arrive about a month after cart close. Have payment-update links and the hardship template ready.
- The last days of the guarantee. Refund requests tend to bunch up just before the window shuts, so make sure whoever approves exceptions is around.
- Promotions. Black Friday or New Year sales add coupon and presale questions on top of normal volume.
Forecasting in Insights helps you size each of these weeks from your own history instead of guesswork.
Where does AI help an online course support team?
Let AI draft, summarize and translate, and let Agent close routine requests. People keep refunds outside policy, disputes, accommodations and anything about a learner's own work.
- Drafts that cite their sources. Copilot writes a reply from your refund terms, syllabus and certificate rules and shows which document it drew on, so a rep can check the guarantee version before sending. By Aftersales' own figure, teams using Copilot on every conversation reply 2.4× faster at the median.
- Summaries of long threads, such as a refund argument that has moved between email and Instagram DMs, before the founder decides.
- Translation in 31 languages, right-to-left scripts included, for international cohorts and for instructors who teach in one language to learners who write in another.
- Agent for the routine share: lost logins, failed-installment questions, session times and refunds inside your guarantee. Its procedures and limits are set out in AI customer service for online courses.
Every plan includes 10 Copilot and 10 translation conversations per rep each month, and the Copilot add-on costs $29 per rep per month on annual billing ($35 monthly).
Which metrics should an online course support team track?
Report by course and by cohort as well as overall, because one rough launch can hide inside a healthy monthly average.
| Metric | Formula | Target guidance |
|---|---|---|
| Contacts per 100 enrollments | Conversations ÷ new enrollments × 100, per course and cohort | Compare launches; a jump points at onboarding or checkout |
| Refund request rate | Refund requests ÷ purchases, per course and per launch | Read alongside the sales page and guarantee wording used for that launch |
| Dispute rate | Disputes ÷ successful payments, per month | Stay well clear of your payment processor's monitoring thresholds |
| Installment recovery | Failed installments later paid ÷ failed installments | Track by plan length; a falling rate means reminders need work |
| First response time by queue | Median time to first human reply, per queue, with cohort first weeks reported separately | Measure against the SLA table above |
| Accessibility turnaround | Days from request to accommodation in place | Agree a target with the accessibility owner and review every miss |
| CSAT by queue and course | Satisfied responses ÷ all responses | Look for courses or cohorts that trail the rest |
| Cost per conversation | Seats, resolutions and channel costs ÷ conversations, in Insights | Compare launch months with ordinary months |
Formulas are suggestions. Set targets from your own baseline across two or three launches.
How do you move a course business off its current support tools?
Most creators answer learners from a mix of places: a shared Gmail or Outlook address, messages inside the course platform, social DMs, a community space and sometimes a general-purpose helpdesk. Keep the course platform as the record of who owns what, and bring the conversations into one inbox.
- Pick a gap between launches, not a cohort's opening week or the days before cart close.
- List every way learners reach you, including old launch addresses, the reply-to address on payment reminders, and each community and social account.
- Connect course and payment data through the Aftersales API or webhooks, with Stripe connected natively, so enrollments and payment plans appear beside each thread.
- Rebuild saved replies from the templates above, and add course and cohort fields to every view.
- Move channels in order: email first, then chat on sales pages and the dashboard, then WhatsApp and social. Pin a note in your community pointing account problems to support.
- Invite instructors, TAs and finance on Lite seats and show them how @mentions and approvals work.
Most teams finish migration in an afternoon, and on Growth and Scale we run the migration with you. If you already use Zendesk or Freshdesk and want to keep it, Agent can run inside it with no seats and no migration at $0.99 per resolution, with a minimum monthly commitment. Plans are compared on pricing.