Platform
One platform. Every role on campus.
Merzal AI covers the full institutional surface — students, faculty, departments and management — under a single administration and security model.
How it works
What happens between a question and an answer
Most of the platform's value is in the four steps a reader never sees. Each one is a control the institution can inspect.
The question arrives with a role attached
Nobody queries the platform anonymously. A request carries who is asking, which department they belong to and what their role permits them to read. That context is applied before retrieval runs, not filtered out afterwards.
Retrieval runs inside that scope
The platform searches your circulars, syllabi, regulations and records — only the ones this person is allowed to see. A confidential document in another department is not ranked lower; it is not in the search space at all.
The answer cites what it used
Every response points back to the institutional source it came from, down to the page. A reader can open the circular and check. An answer that cannot be traced to a document is an answer you should not act on.
The exchange is logged
User, role, timestamp, query and source documents are written to an audit log that management and IT can review. When someone asks why a decision was made, the trail exists.
The same four steps run whether the platform sits on campus hardware or in a private tenancy — see deployment models for where each layer physically lives, and the security model for how the boundaries are enforced.
Modules
Eleven capabilities, one administration model
Every module below shares the same index, the same roles and the same audit trail. IT administers one platform, not eleven separate subscriptions.
Student AI
A grounded assistant for coursework, revision, regulations and placement preparation — answering from your syllabus and past papers, with citations students can open.
Staff Automation
Agents that take on repetitive administrative work: drafting circulars, compiling department reports, preparing accreditation evidence and turning notes into action lists.
AI Agents
Task agents scoped to a role and a permission set. They prepare and propose; a human approves anything that leaves the institution.
Institution Knowledge Base
One versioned index of circulars, syllabi, regulations and records. Superseded documents lose authority the moment they are replaced.
Department AI
Each department gets its own scope. Retrieval respects department boundaries so confidential material never surfaces through a helpful answer.
OCR Ingestion
Printed circulars, scanned records and handwritten registers are digitised, structured and made answerable.
Voice AI
Hands-free queries and dictation for faculty and office staff, in the languages your campus actually speaks.
Analytics
Adoption, query themes and workload signals for management review — evidence you can take into a governing council meeting.
Document Intelligence
Ask questions across hundred-page documents — regulations, tender files, accreditation manuals — and get answers with the source page cited.
Temporary Knowledge
Time-bound material such as exam schedules or event circulars expires automatically instead of misleading someone next term.
Role-Based Access
Chairman, secretary, principal, dean, HoD, faculty and student roles, each with a defined view and a defined limit.
Because the fee is institution-wide rather than per seat, switching a module on for another department does not change the bill. See how pricing works, or what each role gets.
Boundaries
What the platform deliberately does not do
A system that claims to do everything is a system nobody can evaluate. These are the limits worth knowing before a demo, not after.
It is not a better general assistant
For open-ended general knowledge, a consumer assistant is excellent and Merzal AI is not trying to beat it. The platform is built for the work where the answer has to come from your institution's own records and stand up to scrutiny.
It cannot answer what you have not given it
Grounding cuts both ways. A regulation that was never ingested is a regulation the platform will not quote. Ingestion is the first phase of every deployment for exactly this reason.
Agents propose; people approve
A drafted circular is a draft. Agents prepare and compile, then hand the work back for a human decision. Nothing leaves the institution on an agent's judgement alone.
Old documents lose their authority
Superseded circulars stop carrying weight the moment they are replaced, and time-bound material expires on its own. The platform is designed to forget on purpose, because a confidently quoted stale rule is worse than no answer.
Platform questions
What committees ask when the demo ends
The four that come up in almost every evaluation.
Do students and faculty use the same system?
They use the same platform through different roles. A student sees what is published to them — syllabus, regulations, past papers, placement material. Faculty see their teaching and administrative surface, HoDs see department knowledge, and management sees institution-wide analytics. One administration model, one security model, different views.
What happens to our printed and handwritten records?
OCR ingestion digitises printed circulars, scanned records and handwritten registers, structures them and makes them answerable alongside everything born digital. Institutional memory that currently lives in a filing cabinet becomes searchable.
How is this different from a chatbot on our website?
A website chatbot answers from a scripted FAQ and owns nothing. Merzal AI retrieves from a versioned index of your real documents, respects department and role boundaries on every request, cites its sources, logs every exchange, and leaves the institution owning the index and the documents.
Does every module have to be switched on at once?
No. A pilot is normally scoped to one department and the modules that department will actually use daily. The rest of the platform is already there under the same administration model when you widen the rollout.
See the platform running against your own documents.
We ingest a sample of your circulars and syllabus before the demo, so you evaluate it on your institution — not a generic script.