Design and Implementation of an Intelligent Chatbot for University Information Services

A student help desk, campus directory, and information front door in one interface.

MWECAU Smart Assistant is designed to answer common public questions across admissions, fees, student systems, programmes, accommodation, and university support contacts without sending every user to an office.

Admin Login
English and Swahili prompts Knowledge-base answers with source hints Admin-managed updates for dynamic information

Service Hub

Official portals, support routes, and scope guardrails

The public experience stays simple while the system still points users to the correct official university channel.

Support Channels

Human contacts behind the chatbot

Admissions Desk admissions@mwecau.ac.tz Application support and joining guidance.
General Enquiries info@mwecau.ac.tz Public university information and redirection.
ICT Support admin@mwecau.ac.tz UMS, LMS, and institutional platform access issues.

Scope Guardrails

How the system stays realistic and safe

  • Chatbot replies are limited to public university information.
  • Personal records such as grades, transcripts, or balances stay outside the chatbot.
  • Dynamic items like fees and deadlines should be maintained from official notices in the admin dashboard.

Live Chat Experience

A smarter launcher with a real conversation workspace

The assistant stays compact until needed, then opens into a proper chat panel where a visitor can type freely, follow quick prompts, and continue the conversation naturally.

How It Opens

Tap the floating message

A small assistant prompt stays at the lower corner of the page. Once a visitor taps it, the chat window slides open and the first response appears.

Conversation Model

What users should expect

  • Answers are grounded in curated knowledge entries with flexible intent reasoning, not random internet responses.
  • Each reply can include a source label or an official link when available.
  • When confidence is low, the chatbot suggests supported topics instead of inventing an answer.

Admin Workflow

How content stays current

  • Authorized admin users log in before editing the knowledge base.
  • Entries can be enabled, disabled, or updated without changing code.
  • High-change items like fees and deadlines should be reviewed before each semester or intake.

Knowledge Zones

Core university information areas covered by the chatbot

The MVP matches the proposal scope and gives room to extend the knowledge base as the university adds more services.

01

Admissions

Applications, joining instructions, and official admissions contacts.

02

Programmes

Courses, faculties, and academic pathways across the university.

03

Fees

Fee structure guidance, payment direction, and finance-related FAQs.

04

Registration

UMS, LMS, course registration, and student-system support.

05

Academic Dates

Almanac guidance, exams, results scope, and public academic notices.

06

Support

Contacts, location, ICT, library, and student support channels.

07

Accommodation

Residence guidance and where to confirm hostel or housing updates.

Seeded Knowledge

Initial answers loaded into the system