AI Agents for Education

Connected Support Across the Student Journey

We engineer agents for admissions, student services, learning support, course guidance, administration, and institutional knowledge — built so academic decisions stay where they belong: with educators.

01

Operating Context

H
How This Industry Operates

A university or school runs on conversations at scale. Thousands of students ask about entry requirements, module choices, fee deadlines, and campus services — and behind each answer sits a staff member querying a student information system, an LMS, an admissions platform, and a shared drive that rarely agree with one another. The work is essential, repetitive, and growing faster than teams are.

Most of that volume is structured. An enquiry has an approved answer, an application has a checklist, a request has a policy. That makes education well suited to agents that read the right systems, resolve the routine share, and route everything else to staff with context already gathered — rather than leaving a queue of raw tickets.

Alpha Expansion builds these agents the way institutions need them built: permissions mirror existing staff roles, every action is logged, and admission, grading, and disciplinary decisions never leave human hands. Agents prepare, flag, and route. Educators decide.

02

Operational Challenges

Where the Work Slows Down

Repeated Programme Enquiries

Admissions and front-desk teams answer the same questions about entry requirements, fees, and deadlines all cycle long — most of them from information the institution has already published.

Incomplete Applications

Applications stall on missing transcripts, references, and test scores, and often nobody notices until a deadline has passed and a qualified applicant has drifted away.

Fragmented Student Support

One student question can span registry, finance, and housing, but each office sees only its own system — so students repeat themselves and issues fall between departments.

High Administrative Volume

Room bookings, standard letters, form processing, and scheduling consume staff hours that should be going to students and teaching.

Inaccessible Institutional Knowledge

Policies and procedures live in PDFs, intranet corners, and inboxes across departments; even experienced staff struggle to find the current version of a rule.

Delayed Intervention

The signals that a student is struggling — missed deadlines, absences, no LMS activity — sit in separate systems until a tutor happens to notice, often late.

03

Purpose-Built Agents

Six Agents Designed Around This Work

01

Admissions Agent

Guides applicants from first enquiry to a complete, decision-ready file — and hands that file to the admissions team, who make every call.

Responsibilities
Receives programme enquiries across web chat, email, and forms, and answers from the published prospectus, entry requirements, and fee schedules
Checks each submitted application against the document checklist for its programme, flagging missing transcripts, references, or language scores to the applicant
Prepares a structured applicant summary — qualifications, documents received, deadlines met — for admissions officers to review
Routes non-standard cases such as transfer credit, mature entry, or unrecognised qualifications to the admissions team with the relevant policy attached
Records every applicant interaction and status change in the admissions platform and CRM

admissions platform, CRM, document storage, messaging

Offers, rejections, and entry-requirement waivers come only from admissions staff; the agent never communicates or implies a decision.

02

Student Services Agent

Acts as one front door for enrolment, records, finance, and campus-life questions — resolving the routine and escalating the personal.

Responsibilities
Retrieves a student's enrolment status, fee balance, and registered modules from the student information system before answering, so every response matches their actual situation
Answers timetable, housing, fees, and campus-service questions from the institution's approved knowledge base, citing the source page
Prepares standard documents — enrolment confirmations, transcript requests, exemption letters — and queues any that need a signature for staff
Routes welfare, safeguarding, complaint, and appeal conversations to named staff immediately, carrying the full history so students never repeat themselves
Records each resolved request against the student's record for continuity across departments

student information system, CRM, knowledge base, messaging, document storage

Fee disputes, appeals, and anything touching wellbeing or safeguarding go straight to designated staff — the agent gathers context, not resolutions.

03

Learning Support Agent

Assists students in navigating course materials, deadlines, and study resources while grading and academic feedback remain entirely with educators.

Responsibilities
Retrieves module outlines, reading lists, and assessment briefs from the LMS when a student asks where to find or how to start something
Checks upcoming deadlines and submission status across a student's modules and sends reminders on the schedule the institution sets
Prepares revision summaries and practice questions drawn solely from the module's published materials, clearly labelled as study aids rather than assessed content
Flags patterns of missed deadlines or low engagement to the personal tutor, following thresholds the teaching team defines

LMS, student information system, calendar, messaging

It never marks work, gives feedback that counts toward a grade, or judges academic integrity — those questions route to the module tutor.

04

Course Guidance Agent

Helps students build a valid module selection against programme rules, leaving requirement interpretation to registry and the final choice to the student.

Responsibilities
Retrieves programme regulations, prerequisite chains, and module availability for the student's specific cohort and year
Checks any proposed selection for credit shortfalls, timetable clashes, and unmet prerequisites, naming exactly which rule each conflict breaks
Prepares side-by-side comparisons of elective options — assessment mix, schedule, workload profile — from the published catalogue
Updates the student's module registration in the student information system only after the student confirms and every rule check passes
Routes waiver, overload, and late-change requests to the programme director with the student's academic history summarised

student information system, LMS, calendar, knowledge base

Prerequisite waivers, credit overloads, and regulation interpretation belong to academic staff; the agent enforces published rules but never bends them.

05

Administrative Workflow Agent

Executes the approved, rule-bound administrative tasks that consume staff hours — bookings, forms, scheduling — and queues everything else for people.

Responsibilities
Receives routine requests such as room bookings, event scheduling, and standard form submissions from staff and students through existing channels
Checks requests against availability calendars, capacity limits, and written policy before acting on any of them
Executes tasks that pass every check — confirming a booking, issuing a standard form, scheduling a meeting — within limits administrators set
Updates calendars, booking records, and shared trackers as each task completes, so no one reconciles systems by hand
Records what was requested, what was executed, and what was escalated in an audit trail administrators can inspect

calendar, document storage, messaging, student information system

Requests involving money, staffing, policy exceptions, or anything ambiguous wait for an administrator's explicit sign-off.

06

Institutional Knowledge Agent

Turns scattered policies, handbooks, and procedures into cited, current answers for staff and students — without ever interpreting policy itself.

Responsibilities
Retrieves answers from versioned, approved sources — academic regulations, staff handbooks, quality manuals — and cites the exact document and section
Checks that every passage it quotes is the current version, flagging superseded or contradictory pages to the content owner
Prepares draft corrections when staff report outdated policy text, routing each draft to the responsible owner for review
Records questions no approved source can answer as documented gaps for the knowledge team to close

knowledge base, document storage, messaging

It answers only from approved sources; interpreting policy and changing official documents remain with the document owner every time.

04

Example Workflow

One Request, End to End

1
Question Received
A student asks in their own words through chat, email, or the portal — no forms, no menu trees.
2
Identity and Context
The agent verifies who is asking and loads their programme, year, and enrolment status from the student information system.
Approved RetrievalHuman approval
It draws only on sanctioned sources: the knowledge base, the published catalogue, and the student's own records.
4
Task or Application Guidance
The student receives a cited answer, a step-by-step walkthrough, or a prepared form ready to review and submit.
5
Staff Review Where Required
Anything touching a decision, an exception, or a wellbeing concern routes to the responsible staff member with full context attached.
6
Record Updated
The interaction, its outcome, and any escalation are written back to the student's record so the next conversation starts informed.

05

Systems Landscape

Connected to the Systems That Run the Work

Student information systems
Ellucian Banner
PeopleSoft Campus Solutions
Tribal SITS
or a custom SIS
Learning management systems
Canvas
Moodle
Blackboard
or Brightspace
Admissions and CRM platforms
Slate
Salesforce
HubSpot
or a purpose-built admissions system
Messaging and student portals
Microsoft Teams
Slack
institutional email
or an existing student portal
Calendars and scheduling
Google Workspace
Microsoft 365
or a dedicated timetabling system
Document and knowledge stores
SharePoint
Google Drive
Notion
or an institutional repository

06

Human Control & Governance

Governance Built for Academic Institutions

Education agents work with the records of young people and data that shapes academic futures, so control is the architecture, not an add-on. No agent we build makes an admission, grading, disciplinary, or other high-impact academic decision — those sit with educators, backed by checkpoints, scoped permissions, and a complete audit trail.

Controls Built Into the Architecture
Role-based permissions mirroring existing staff data access
Approval checkpoints before record changes and outbound messages
No autonomous admission, grading, or disciplinary decisions
Educator oversight of all learning-support content
Age-appropriate privacy controls and guardian-consent handling
Data boundaries aligned to FERPA, GDPR, and local student-record law
Audit trail covering every retrieval, answer, and escalation
Evaluation suites run on real enquiry samples before each release
Safe fallback to a named staff member on uncertainty

07

Questions

Frequently Asked Questions

Map One Workflow With Us

Pick the process that eats the most staff time — programme enquiries, application chasing, enrolment questions — and we will map it with you end to end: the systems it touches, the rules it follows, where staff review sits, and what an agent could responsibly carry. You leave with a concrete design either way.