Schools need a clear support channel when a workflow does not behave as expected. SkoolPro support conversations let users describe an issue and follow replies, while school and role associations provide the context for account access.
Before you begin
Write down the affected screen, action and approximate time. Use a relevant screenshot if needed, but remove unrelated private information before sharing it through support.
How the workflow works
1. Describe the issue
Choose the relevant support category and explain the action that caused the problem.
2. Add useful context
Attach a relevant screenshot when appropriate, without including authentication secrets.
3. Follow the conversation
Read the support response and provide additional information in the same thread.
4. Confirm the outcome
Check the affected workflow and close or reopen the ticket according to the result.
A practical school example
A teacher cannot open an expected result card. They describe the class, assessment and error in a ticket rather than sending their password. Support replies in the thread, and the school checks whether the issue is resolved.
What to check before relying on the result
Never include passwords, PINs or one-time codes in a ticket. School data isolation is a security design that requires continuing verification; a support feature is not a guarantee that no security issue can occur.
Try the workflow with your school team
Use the animated example on this page to walk through support & school data isolation with the staff or family members who will use it. The illustration uses sample data; it does not log into a school or change any records. When reviewing the real workflow, check the intended school, person and date before saving or sharing information.
Feature access follows your school plan and assigned role. Contact our support team about your plan, browse the school feature catalog, or book a guided demo to review the workflow with the SkoolPro team.