AI Chatbot for Sakai

Most Student Questions Are Not About Learning

Teaching staff expect to answer questions about the subject and instead answer questions about logistics: which file format, whether the deadline is midnight or 9am, where last week’s recording went, why a link does not work.

None of that needs academic expertise, and all of it is documented somewhere. Automating it returns the most expensive hours in the institution to the work those hours were funded for.

Students Work When Support Is Closed

Coursework happens late at night, at weekends and in the days before a deadline. Institutional support runs on office hours, so the gap between question and answer is often longer than the time left to submit.

Round-the-clock answering removes that mismatch. It also reduces the panic escalations that arrive at 8am on a submission day.

Consistency Is a Fairness Issue

When policy is explained by different people it gets explained differently, and in an educational context that is not merely inefficient — it can be unfair. One student is told late submission costs a grade; another is told it is fine.

A single source answering from published policy treats every student identically, which is easier to defend and easier to audit.

Access Confusion Generates Most Tickets

A large share of helpdesk volume is visibility: a module not appearing, a resource released later than expected, group membership not applied. Students interpret these as faults and report them.

Explaining the release rules at the moment of confusion resolves most of those before they become tickets, without anyone having to check a configuration.

International Cohorts Carry Extra Load

Students studying in a second language spend more effort on administrative comprehension than domestic students, which is an equity problem rather than a preference.

Answering in the student’s own language reduces that load directly, and costs nothing additional once the assistant is running.