A tutor that asks the next question instead of giving the answer
ClassTablet can build a tutor that responds to a stuck student with the next question rather than the answer, walking them to it a step at a time. It is not part of the product. Which subjects, which year groups and how far it helps are agreed first, and the capability is then built for you.
The problem it addresses
A student stuck on a maths problem at nine at night has nobody to ask, so they either close the book or copy the answer from somewhere. The homework comes in looking done, nobody notices the understanding is missing, and the gap shows up for the first time in an exam.
What the build covers
- 1
Subjects and year groups
Which subjects it covers and which years it is turned on for. The way you question a student through a physics problem is not the way you question them through a history essay.
- 2
How far it is allowed to help
After how many steps it stops, when it hands the student back to a teacher, and what it will not simply answer. Those limits get written down rather than assumed.
- 3
What the teacher sees
Whether a teacher can see where a student keeps getting stuck, and in how much detail. You decide, and it is recorded in the scope.
- 4
Safeguarding and boundaries
Because this talks to students, what it steers away from, what is logged and what parents are told are settled before any of it is built.
What it would look like
There is no screenshot here because this has not been built. What it looks like for your institution is settled in the scoping conversation.
Who it suits
- Coaching centres
- Schools
- Colleges
Common questions
Is there a chat assistant in ClassTablet today?
No. There is no AI that talks to students in the product. A question-led tutor is separate work, built for an institution that commissions it.
Would it just give students the answer?
How much it will and will not say is the main thing the scoping conversation settles. A rule that it never hands over the answer can be written in from the start.
Could teachers see where students get stuck?
That is your decision. What a teacher can see, and in how much detail, is written into the scope rather than left to whatever the software happens to do.
How would student data be handled?
What is logged, how long it is kept and who can see it are part of the conversation, and they are written down before the build starts.