Your own signed-in account. Organisational issues such as changing a lesson time or a missing course should first be clarified with the school office.
Follow these steps
Check state after the error
If an error occurred during a save, refresh the relevant list and see whether the operation was already stored. Do not immediately repeat adding a person or booking.
Open the support form
After sign-in choose Help, then Report technical problem. The public help centre does not expose private tickets.
Choose category and subject
Select a category such as Schedule, Booking or Data not visible. Use a specific subject, e.g. No confirmation after refreshing a saved slot.
Describe the event
In What is happening? include role, screen, date/time, steps, expected result, actual result and exact message. For a phone add OS and app version.
Send and keep the number
Select Send ticket. Save the number only after confirmation and check My tickets. If the register is unavailable, send the description through the agreed support channel.
What to enter and what it means
- Ready-to-use description pattern
- Role: … | Screen: … | Date/time: … | Steps: 1… 2… | Expected: … | Actual: … | Message: … | After refresh: …
- Severity
- Choose according to operational impact. Urgent does not by itself create a guaranteed response time.
- Screenshot
- Hide passwords, full PKK, invitation links, medical data and unnecessary personal data. Keep the error message visible.
How to verify it worked
The ticket has a concrete description and number so the same issue can be continued without duplicates.
Do not send passwords, tokens, full connection headers or invitation links. Support does not need them in the ticket body.
No form response is not proof of submission. Check the ticket register and avoid creating many identical tickets.