StudyIQ

A mentorship layer, built into an exam platform serving millions

Comments piled up, nobody answered them

Aspirants posted their doubts in the comment feed and waited. Nothing trackable there to assign a mentor to actually resolve them, the questions just sat there, unanswered.

Live classes kept getting interrupted

Doubt sessions never had enough time to get through everyone’s questions. And some students weren’t comfortable asking out loud in front of the whole class, so they typed their doubts into the comments instead, right in the middle of the lecture later, pulling the teacher’s attention away from what they were teaching.

Doubts got lost inside mentor WhatsApp groups

Hundreds of messages piled into one thread. A question could get answered, buried under the next fifty messages, or simply missed, nobody could tell which.

Support tickets became a doubt-solving channel

A queue meant for billing and account issues started filling up with the doubts because there was nowhere better to ask.

Nobody could see what mentors were actually doing

There was no way to track how many questions came in, whether the answers followed the rules, how much effort a mentor was putting in, or how many doubts actually got resolved. No numbers, no record.

A 1:1 chat between one student and one assigned mentor

Not a group thread, not a pooled inbox, each student gets a single mentor for their course, and the chat had to be built around that one relationship, not a queue of many mentors serving many students.

Scheduled sessions on Google Meet, instant call marked coming soon

1:1 sessions had to route through Google Meet rather than a built-in call layer in version 1, booking, confirmation, and the meet link all had to work around an external tool. Instant call wasn’t ready yet, so it had to be shown honestly as coming soon, not hidden or faked.

Mentors can end a session

Ending a running session was a mentor-only action. The design had to make that asymmetry clear, a student needed to know a session was over because the mentor ended it, not wonder if something broke.

Entry point placed inside My Content

Rather than adding a new destination in the app, mentorship opens from inside the course a student’s already enrolled in. One mentor, tied to that course, reachable from a place they already visit daily.

Mentor status shown honestly, not optimistically

Online, active, or offline. The status had to tell the truth. A student needed to calibrate their expectation of a reply, not assume a mentor was always one message away.

Ending a session is visible, not silent

When a mentor closes a chat, the thread shows it plainly, a clear “session ended” state, so a student never wonders whether they’ve been left on read or the conversation genuinely wrapped up.

Feedback required, not optional

Asking for feedback immediately after a session, before the next one could start, made it a natural part of the flow instead of an afterthought nobody returns to complete.

Instant Call for urgent doubts.

Quick-call access for time-sensitive doubts, so students don’t have to wait for a scheduled slot when the question can’t sit until then.

Embedded video calling.

Calls that happen inside the app itself, removing the redirect to Google Meet and closing the one gap between chat and conversation.

Rich attachments in chat.

Support for images, audio, and PDFs, so a doubt can be shown, not just described, cutting down the back-and-forth needed to explain it in words.

Auto-timeout for idle chats.

Sessions that go quiet get closed automatically, keeping both sides working within a structured window instead of an open-ended thread nobody formally ends.

Built-in credits and payments.

A native payment and recharge layer, so booking a session doesn’t depend on credits managed somewhere else in the platform.