Guide • School admins • District admins

How to monitor teacher activity and submit support requests

School admins need more than a roster. They need to see who is active, who needs help, and when to escalate with school context attached.

What this guide helps you do

Use teacher activity patterns and institution support workflows to guide onboarding, follow-up, and escalation.

Expected outcome

Admins can distinguish between teachers who need training, issues that can be solved locally, and issues that should be escalated to Classwise.

For

School admins • District admins

Before you begin

Open the institution admin area with enough context to know whether the issue is about rollout coaching or true product support.

What you will need

Teacher names, course context, or rollout notes so the support conversation stays specific.

Last verified: 2026-03-25

Teacher activity should answer a practical question: who is using Classwise well, who is stuck, and who needs follow-up?

Step by step

  1. Open Team Management and select a teacher.
  2. Review the member activity drawer for the teacher you selected.
  3. Compare activity patterns across the roster to spot champions, inactive users, and likely support needs.
  4. Use those signals to decide where to train, follow up, or escalate.

You should see

Teacher activity becomes a rollout coaching signal rather than a raw score.

Keep in mind

  • Treat teacher activity as a rollout aid, not a performance score.

Common blockers

  • Low activity does not always mean resistance; it can also mean a teacher is still waiting on seats, credits, LMS setup, or training.

Use the institution support request flow when the issue affects the school context rather than one teacher’s local workflow.

Step by step

  1. Open Support & Settings from the Institution Admin Center.
  2. Start a support request from the institution context.
  3. Describe the rollout or account issue clearly and paste the relevant teacher, class, or license details into the request.
  4. Submit the request and keep the school context together in one thread.

You should see

School-level support requests keep the right context together instead of fragmenting the issue across teachers.

Keep in mind

  • The in-product support form is text-based, so screenshot sharing has to happen outside the form if needed.

Common blockers

  • The institution support flow is better for school-scoped issues than opening separate teacher-level tickets.

Not every issue needs escalation. Separate local rollout fixes from problems that need Classwise support.

Step by step

  1. Use the product docs first when the issue is really a workflow misunderstanding.
  2. Document local rollout expectations and internal training notes for issues the school can solve itself.
  3. Escalate to Classwise support only when the blocker is tied to accounts, licenses, integrations, or institution-scoped behavior.

You should see

Admins know what to document internally and what to escalate externally.

Keep in mind

  • Local rollout notes should stay aligned with what teachers actually see in the product.