How it works, in one sentence
Capturing and enrolling is, at heart, moving the right person from “I have a question” all the way to the classroom without losing anyone on the way. The agent decides nobody’s admission and touches nobody’s academic record — it removes the friction from the journey so your team handles the judgment only people can make.Concrete flows
1. Answer the prospect and capture interest in the CRM
Trigger: someone asks about a course — through the site, over WhatsApp, or via an inquiry form. Athena, the organization’s operator, pulls from the Company Brain what that course offers — syllabus, dates, prerequisites, format, the questions the registrar answers every week. She opens the chat and replies with the information that already exists: “that cohort starts in March, it’s fully online, and has three live sessions a week.” Each conversation becomes a lead in the CRM with the course of interest, the channel, and the stage — and nothing is lost when the prospect disappears for a week and comes back. If the person asks about a scholarship amount, whether a diploma is valid, or a policy exception, the agent searches the Brain; if it can’t find it, it doesn’t invent: it logs the question and escalates to coordination. Answering the catalog is routine work; promising a commercial condition is not.2. Guide enrollment document collection
Trigger: a prospect decides to enroll and the lead advances in the pipeline. The agent pulls the checklist for that enrollment from the Brain — school transcript, ID, proof of address, whatever each course requires — and guides the person one document at a time, over the chat or WhatsApp: “got the ID, now I need the high-school transcript as a PDF.” Each file becomes a document organized in that student’s folder, and the CRM activity records what has arrived and what’s still missing.The agent organizes and checks completeness — it doesn’t validate whether
the student meets the prerequisite, doesn’t approve the enrollment, and posts
nothing to the academic record. It hands a complete folder to the registrar
to review; the admissions decision begins exactly where collection ends.
3. The follow-up that recovers a stalled applicant
Trigger: a routine the agent schedules for itself — every morning, it sweeps applicants with an enrollment started and a document pending for more than X days. On fire, the agent pulls from the CRM who stopped halfway, drafts a gentle reminder of what’s missing, and sends it on each person’s channel (email or WhatsApp) — with human approval before sending if you want to keep a hand on the communication. Anyone who doesn’t respond after a few attempts becomes a task for the enrollment advisor, and a proactive notification raises the bell for whoever owns that cohort.Why this matters: an enrollment that stalls on a missing document is the
biggest source of seats leaking away in an enrollment cycle — not because the
person quit, but because nobody chased on the right day. A routine has no
cohort-closing crunch: it chases every time, on time, and turns the silent
queue into an actionable signal.
4. Student support from the Brain — with human escalation
Trigger: an enrolled student sends a question — “how do I join tomorrow’s class?”, “where do I download the week-3 material?”, “when is the assignment due?”. The agent answers from the Company Brain: access guides, cohort calendar, submission rules, the process answers the registrar repeats all the time. The reply goes out in the chat or over WhatsApp, right away — outside business hours too. When the question touches the student’s record — a grade review, attendance, a fee negotiation, a leave request — the agent doesn’t resolve it: it assembles the case summary and opens a task assigned to the right person, with all the context already organized.5. Track a cohort’s milestones
Trigger: a routine tied to the cohort calendar — start, deadlines, live sessions, wrap-up. The agent tracks the milestones on the cohort board and flags them proactively: it reminds coordination about Thursday’s session, signals when a submission date approaches, and raises the bell when something slipped. The indicators you track — attendance, cohort progress, milestones met — live in a running document, assembled from what’s already recorded, not from a spreadsheet someone updates on Friday. Whoever opens the panel sees today’s truth.| Cohort milestone | What the agent does | What stays human |
|---|---|---|
| Start | Confirms complete enrollments, flags gaps | Granting access to who enters |
| In progress | Reminds sessions and deadlines, flags absences | Posting attendance and grades |
| Submissions | Warns who’s near the deadline | Evaluating and grading the work |
| Wrap-up | Assembles the cohort summary for coordination | Approving completion and issuing the certificate |
What stays human
Where to start
Teach the catalog and processes to the Brain
Upload to the Company Brain your syllabi, dates,
prerequisites, access guides, and the answers the registrar repeats every
week. That’s where the agent pulls what to answer, what to request, and what
to check.
Schedule the enrollment follow-up
Create a routine that sweeps stalled enrollments and
chases what’s missing. One agent, one cadence, one channel — and autonomy
grows like a ratchet, never a leap.
Next steps
Sales & commercial
Capture and qualification up front — how the prospect enters the funnel.
Native CRM
Where the pipeline of prospects and enrollments lives — stages, activities,
and history always current.
Routines
The daemon that chases documents, reminds deadlines, and tracks cohort
milestones.
People & HR
The same onboarding and support pattern applied to your own team.