Request a chapter. Report an error. Tell us what to fix.
Every message here goes to a subject teacher, not a support queue. The more specific you are about where the problem is, the faster it gets fixed.
What happens after you send it
Messages are read in the order they arrive, and content corrections take priority over new requests — a student who is being taught something wrong right now loses more than one waiting a week for a chapter. Most reports are resolved within a few days.
If your report turns out to be right, the correction goes into the next update and you will see it on the page without any version note. We do not keep a public changelog, because a student checking a worked answer does not need the editorial history.
Missing a chapter, or a topic inside one you already read? Ask for it by name. Requests are worked through in syllabus order, and the most-requested chapters get written first.
If a model answer or solution reaches a different conclusion than your teacher does, tell us the subject, year and question number. Include the working you were given — a disagreement we can check is fixed; one we cannot reproduce is not.
A wrong formula, a missing step, a definition that no longer matches the syllabus. These are the fastest reports to act on, because they are checkable against the source.
A chapter you could not follow, a question bank you wanted, or a mock test that felt too easy. All of it shapes what gets built next.
Response time
Replies go to the email address you give in the form, so put one you actually read. Reports about an answer being wrong are usually answered within 48 hours; chapter requests are batched, since writing a chapter takes longer than checking one.
Lost your login or need your password changed? Write to support@seesathi.com from the address on your account and say so in the subject line.