Features

The design principle you'll be asked about in adoption meetings: the tutor guides students step-by-step without revealing answers. Prompts probe reasoning rather than the final result.

Concretely: the tutor escalates through five levels of hints — from "look here" to a worked example with different numbers — but never states the final answer, even asked directly. Every help request is logged and rolls up into a per-problem support level teachers see on their dashboards, which is how "who needed help" becomes instructional data instead of a secret.

That matters for two reasons. Academically, students do the thinking. Practically, it means teachers should grade Thinkverse on completion rather than accuracy — worth saying out loud during training, because it's the single most common misunderstanding. See how to grade Thinkverse and support levels.

What's built in today:

• Voice both ways — students can speak to the tutor instead of typing, and the tutor reads aloud. An "Always read to me" mode reads every message and can read the problems too; younger grades default to it.
• 100+ conversation languages, chosen per student and switchable mid-problem — explanations, voice, and interface follow.
• Touch and stylus support throughout the whiteboard (iPad-friendly).
• Reduced-motion preferences respected, alt text on question images, dark mode.

We don't currently ship dedicated dyslexia modes, font-size controls, or captioning of tutor speech — if a review or IEP requires those, say so before rollout rather than after.

For a specific accommodation requirement, email support@thinkverse.co with the actual IEP language — it's better to confirm against that than against a feature list.