What do online course students contact you about?
Most student messages are about getting in, paying and keeping up with the schedule. Far fewer are about the material itself. The table shows where Agent can finish the job and where a person should take over.
| Conversation type | Can Agent resolve it? | Hand off when | Data Agent needs |
|---|---|---|---|
| Can't log in, or the course is missing from the dashboard | Yes: finds the enrollment, resends your platform's login or password-reset link, and moves a purchase made under another email once the student proves it's theirs | No purchase turns up after two lookups, or the student says someone else is using the account | Enrollments by email, purchase records, login method |
| Access removed after a missed installment | Yes: names the installment that failed, sends the payment-update link and re-enrolls once the payment clears | The charge is under dispute, or the student asks to change the plan's terms | Payment-plan schedule, failed charge, unenrollment event |
| Refund request | Yes inside your guarantee terms, up to your cap, including cancelling installments still to come | Outside the window, above the cap, or the student says the course promised results | Purchase date, guarantee terms, share of lessons completed, payment method |
| Payment-plan questions: what's left, paying off early, switching plans | Yes: gives the balance and dates and sends a pay-in-full link | Hardship requests or a new installment schedule | Plan schedule, payments made, checkout links |
| Live session times, joining links and recordings | Yes: converts the time to the student's time zone and shares the link or recording | The link is broken for the whole cohort, or the session was cancelled without notice | Cohort calendar, joining links, recording library |
| Defer or transfer to a later cohort | Yes, once, within your policy (for example, requested before week two and seats remain) | A second deferral, or a request tied to illness, bereavement or a disability | Cohort dates, seats left, deferral rules, attendance |
| "Where is module 4?" and questions about the material | Answers from your syllabus, drip schedule and lesson notes | Feedback on the student's own work, grading, or anything needing the instructor's judgment | Syllabus, release dates, lesson notes, course FAQ |
| Certificate missing, misspelled or needed again | Checks the completion rules, resends the certificate, and fixes a name typo where your platform allows | The student disputes the completion record, asks about professional credit, or a third party wants it verified | Completion status, quiz scores, certificate rules |
| Receipts, invoices and team seats | Resends receipts and explains how a manager assigns seats | An invoice reissued with different tax details, or contract and volume terms | Orders, billing details, seat allocation |
| Community invite never arrived | Resends the invite through your community platform's API | The student was removed from the community for conduct | Community membership status, enrollment |
Example scope for an academy that sells self-paced courses and live cohort programs. Set every limit to match your own terms.
Degree-granting schools work around registrars, financial aid and accreditation, which changes the picture; AI customer service for universities covers that setting.
What does an AI procedure for course access problems look like?
"I can't get into my course" usually comes down to one of five causes: the student checked out with a different email, the login link expired, an installment failed, the content isn't released yet, or access has run out. One procedure should test them in order before anyone touches the account. Agent turns each line below into steps against your course platform and payment processor.
Example procedure: a student can't reach a course they paid for
- Find the purchase. Search enrollments by the address the student is writing from. If nothing matches, ask for the receipt number or the email used at checkout, such as a work address or the one tied to their PayPal account. Never ask for a password or card number.
- Prove ownership before moving anything. If the purchase sits under another address, the student replies from that address or quotes the receipt number. Only then does Agent enroll the login they actually use.
- Read the enrollment status: active, cohort not open yet, module locked until its release date, access period ended, or removed after a failed payment.
- Active but locked out: send your platform's password-reset or login link and say which address it went to. If one resend doesn't work, hand off with the student's browser and device.
- Not open yet: give the opening date and time in the student's own time zone.
- Removed after a failed installment: name the installment and amount, send the payment-update link, and re-enroll as soon as your platform reports the payment. A promise to pay is not enough.
- Access period ended: offer one free extension of up to 30 days per student per course, if your policy allows it. Longer extensions go to a person.
- Hand off when no purchase turns up after two lookups, the payment is under dispute, the student reports someone else in their account, or the seat belongs to an employer's team plan.
Example conversation (web chat, names invented)
Student: Hi, I paid for the spring cohort of the UX research course last week, but my dashboard says I have no courses.
Agent: Sorry about that, Priya. I can't find a purchase under the address you're writing from. Did you check out with another email, maybe a work one? If so, send me the receipt number from your confirmation email.
Student: Oh, probably my work email. It's R-48213.
Agent: Found it: UX Research, spring cohort, paid in full on March 3. I've added the course to the account you're signed in to, so refresh your dashboard and it will be there. The cohort opens on March 18, and the first live session is Tuesday, March 19 at 6:00 pm Lisbon time. The joining link appears in your dashboard on the 18th.
What guardrails does an AI agent need for student refunds, outcomes and records?
Cap what Agent can refund, keep it away from promises about outcomes, and never let it edit academic records. Agent should not give medical, legal or financial advice: in a trading, health or law course, any question about what the student personally should do goes to a person.
What Agent must never do
- Promise results. No claims about income, job offers or exam passes, and no repeating them from old sales pages. The FTC has put businesses on notice that certain practices used to attract people to money-making opportunities are unfair or deceptive. A student who asks "will this get me to $10k a month?" gets your published course description and an offer to talk to someone.
- Touch academic records. Grades, completion percentages and quiz results stay as recorded, and no certificate goes out before the criteria are met.
- Refund a disputed payment. Stripe's documentation notes that once a payment is formally disputed, the issuing bank has already refunded the cardholder, so a second refund would pay the student twice.
- Share a student's progress with an employer, parent or classmate unless your team or family terms allow it.
- Take card numbers or passwords in any channel.
Refund rules differ by country
Your guarantee is a promise you've published, and local law can add to it. UK guidance says sellers of downloads and streamed content must get the customer to confirm they will lose their 14-day right to cancel before access starts; skip that step and the customer keeps the right. The EU's consumer rules treat online digital content in a similar way. Load each region's refund terms into Knowledge so Agent applies the right version, and have counsel review them. Aftersales gives you the controls; compliance stays with your business.
Children and school records
If you teach children, the FTC's COPPA Rule sets requirements for online services directed to under-13s. Keep parents as the account contacts and route anything a child writes to a person. Academies that partner with schools or colleges should ask counsel whether FERPA reaches the student records they hold.
What triggers a handoff
Words such as "chargeback", "my bank", "scam", "lawyer", "FTC", "Trading Standards" and "attorney general"; refund requests that mention promised results; accessibility requests such as captions, transcripts or extra time on an assessment; any mention of a personal crisis; negative sentiment after Agent's first answer; and team or enterprise accounts. The person who picks it up sees the thread, the enrollment and payment data Agent looked up, and every step it already tried.
Data handling
Each connector step carries explicit permissions you can revoke. A common start: Agent reads enrollments and payment status from day one, and gets refund and re-enrollment rights after your team has reviewed its first two weeks. Card data stays with your payment processor. The security page covers US hosting and the GDPR DPA; all student data is hosted in the United States, so academies with strict residency rules should check that first.
Which channels should an online course business automate first?
Start with email and chat on your school's site, where access and billing questions arrive. Messaging teachers is part of studying online: Eurostat reports that in 2025, 16% of people aged 16 to 74 in the EU had done an online course and 17% had interacted online with educators or fellow learners.
- Email. Receipts, welcome emails and payment-plan reminders all invite replies, and Agent checks which message the student is answering.
- Chat on sales pages and the student dashboard. Launch-week questions about fit and start dates come from the sales page; "where's the workbook?" comes from inside the course, if your platform lets you add a chat widget there.
- WhatsApp. If your cohorts already gather there, a separate support number keeps billing and login problems out of the class group.
- Social DMs. Followers ask about price, payment plans and start dates before they buy, and Agent answers from the course page and your refund terms.
- Slack Connect. Companies that buy seats for their staff can reach you in a shared channel.
- Phone. Bootcamps with admissions advisors take calls; on Growth and Scale those calls sit in the same Inbox, with warm and cold transfers and recording consent.
Agent reads and replies in 31 languages, which helps when one cohort spans several countries.
What systems does an online course AI agent connect to?
Agent needs three things: your course platform for enrollments and progress, your payment processor for charges and refunds, and your teaching calendar for live sessions.
- Course platform or LMS. Connects through the Aftersales API or webhooks; confirm specific connectors on a call. Hosted platforms expose what Agent needs. Teachable's webhooks report new enrollments, completions, refunded transactions and unenrollments, including those caused by failed payments or expired access, and Kajabi's API can grant and revoke offers and read purchases. With those events flowing in, Agent knows a student lost access before they write.
- Stripe. A native connection, so Agent can refund inside your cap.
- Other checkout and payment-plan tools. Through the API or webhooks, so failed installments and pay-in-full links reach Agent.
- Live session tools and your community platform. Session times, joining links, recordings and invite status come in through the API or webhooks, or you keep the cohort calendar in Knowledge.
- Knowledge. Syllabus, release schedule, refund terms by region, certificate criteria, accessibility options and the course FAQ in one Knowledge source that Agent, your team and the help center all use.
- Slack and Jira. A workflow can post a broken-lesson report to your production channel in Slack and open a Jira issue for whoever maintains the site.
How much does AI customer service cost for an online academy?
For the example academy below, a normal month costs $838.62 and a launch month $1,699.92 on annual billing. Seats stay fixed while resolutions rise and fall with enrollment.
Assumptions (Example):
- 5,000 active students across six self-paced courses and two cohort programs.
- 1,100 written conversations in a normal month, and 2,600 in a month with a launch and a cohort start.
- Agent resolves 58% (638 normally, 1,508 in the launch month). That sits below Agent's 71% median after 90 days because refund exceptions, assignment feedback and accessibility requests always go to people.
- Three support reps on Growth seats with annual billing; four instructors and six TAs on free Lite seats.
| Item | Normal month | Launch month |
|---|---|---|
| Growth seats | 3 × $69 = $207.00 | 3 × $69 = $207.00 |
| Agent resolutions | 638 × $0.99 = $631.62 | 1,508 × $0.99 = $1,492.92 |
| Lite seats for instructors and TAs | $0.00 (20 included on Growth) | $0.00 |
| Conversations handed to people | $0.00 | $0.00 |
| Total | $838.62 | $1,699.92 |
List prices checked October 2026. Monthly billing adds 20% to seat prices. Copilot is optional at $29 per rep per month on annual billing.
A resolution is counted once per conversation, however many questions the student asked in it. A solo creator can start on the Free plan, which includes one seat, live chat and email, and the first 50 Agent resolutions. Every plan is on pricing.
How do you roll out an AI agent for online courses in 30 days?
Start between launches, so Agent learns on ordinary weeks before a cohort start tests it.
- Days 1 to 7: connect Stripe and your course platform, load the syllabus, release schedule, cohort calendar, refund terms and certificate rules into Knowledge, and agree refund caps with whoever owns the guarantee.
- Days 8 to 14: replay conversations from your last launch with personal details removed, fix what Agent gets wrong, then go live on chat for access and schedule questions.
- Days 15 to 21: add payment-plan questions and refunds inside the guarantee on email. Refunds start as prepare-and-hand-off; grant the refund permission once your team has checked 50 of them. Turn on Monitors (Growth) to score every conversation.
- Days 22 to 30: let Agent take the first reply through a cohort's opening week or a cart close, read the handoff reasons each morning, and follow resolution rate and cost per conversation in Insights.
If you plan to compare Agent with your old helpdesk, the resolution rate guide shows how to decide when a conversation counts as resolved.