Appearance
Knowledge base & AI assistant
Help articles your schools can read themselves — and the source the in-product chatbot answers from.
Sidebar → Knowledge Base
What it is for
Every question a school asks you is a question they could not answer themselves. The knowledge base is where the answer goes so the next school finds it without writing to you.
It has two audiences:
- School staff, reading help articles inside the panel
- The chatbot, which answers from these articles
This is not the same as these docs
The documentation you are reading is for you — installing, configuring and running the platform.
The knowledge base is for schools — how to mark attendance, how to collect a fee. Different readers, different content. Do not mix them.
Structure
Categories hold articles. Keep categories few and obvious — schools scan, they do not search well.
A workable starting set:
| Category | Articles about |
|---|---|
| Getting started | First login, setting up the year, adding classes |
| Students | Admissions, records, promotion |
| Fees | Collecting, receipts, dues, reminders |
| Attendance | Marking, reports, biometric machines |
| Exams | Setting up, entering marks, publishing results |
| Staff | Adding staff, leave, payroll |
| Apps | Getting parents onto the app, notifications |
Writing articles that work
- Title it as the question the school would ask — "Why can't I add a student?" beats "Student module troubleshooting"
- One task per article
- Short numbered steps, exactly like these docs
- Say what they should see after each step
- Add the error message verbatim if there is one — that is what people search for
Write the article while answering the ticket
The moment you type an answer into a support ticket, you have written the article. Paste it into the knowledge base before you close the ticket, and it is done.
An article written later, from memory, never gets written.
The AI assistant
Sidebar → AI Management
| Screen | What it does |
|---|---|
| AI Settings | How the assistant behaves and what it may answer from |
| AI Analytics | What people asked, and whether it could answer |
AI Analytics is a list of your missing articles
The questions the assistant failed to answer are precisely the pages that do not exist yet. It is the cheapest content plan you will ever get — the schools wrote it for you.
The assistant is only as good as what it reads
It answers from your knowledge base. With five thin articles it will be vague and schools will stop trusting it, then keep asking you directly.
Build the articles first, then turn the assistant on.
What to write first
Take the categories from your support tickets and start with whichever is largest. That is, by definition, what your schools most need answered.
If you have no tickets yet, start with these five — they are the same everywhere:
- Setting up the academic year
- Adding students in bulk
- Collecting a fee and printing the receipt
- Marking attendance
- Getting parents onto the mobile app