The pain
Enquiries, booking, student intake, and tutor preparation live in separate chats and files.
Enquiries, booking, student intake, and tutor preparation live in separate chats and files.
One student record connects the first question to a prepared tutor.

English on-screen text. Fictional demonstration, not a live customer system. Music and sound effects. Starts muted.
Parents keep using the familiar channel while booking, intake and lesson context become one controlled journey. The tutor receives the student’s level, goal, weak areas and agreed preparation before the first call.
A parent books an assessment in WhatsApp. The intake answers stay in another form. Ten minutes before the lesson, the tutor still does not know the student’s level or goal.
The team repeats the same service answers, moves booking details by hand and prepares tutors from incomplete message history. The first lesson starts with discovery that should already be complete.
The workflow is configured around the school’s real booking, intake and safeguarding rules. The public demo uses fictional data.
Best fit: Tutoring · Language schools · Training providers · Education teams
Reference: interactive education operations prototype developed for Archimede. The public walkthrough uses fictional student data.
The enquiry becomes a student profile, a booking and a ready tutor brief.
Try the interactive demoChoose a parent’s enquiry, prepare the intake, then open the tutor brief.
Choose a parent enquiry. Move it through intake to see what the team and tutor actually receive.
“My daughter is 13 and needs help with algebra before her October exam.”
The tutor may see only a time slot — not the student’s goal or uncertainty.
One structured record connects the parent’s message to intake.
No copy-paste or second enquiry form for the team.
Local scripted example. No WhatsApp connection, real student data, booking or message is created.
Tell us about your current process. We’ll map the right setup around your tools and agree on a focused pilot.