A page or action fails when a user tries to continue
Examples include a button that does nothing, a page that cannot load, or a route that stops a learner from progressing.
Report an Issue
Help us identify and fix problems faster
This page gives users a clear way to report technical issues, broken flows, confusing behaviour, and platform blockers so problems can be documented with the right level of detail.
Technical Issues
Blocked Flows
Support Quality
Structured issue reporting
Better reports, faster review
Why this page matters
Good issue reports reduce confusion and improve support quality
A dedicated issue-reporting page helps separate real platform problems from general questions, making it easier to document what broke, where it happened, and how it affected the user.
Best for
Broken experiences
Use when something clearly is not working as expected.
Designed for
Clear documentation
Supports more actionable issue review later.
Before you report
Make sure this is the right route for your situation
Some issues are true technical problems, while others are better handled through support, legal, or feedback routes. Choose the best path for a faster resolution experience.
01
Technical Problems
Use this route when a feature is broken or behaving unexpectedly
Best for errors, missing actions, blocked flows, broken links, or behaviour that clearly does not match the intended user experience.
Open Help Centre
02
Access Issues
Use this route when you cannot enter or continue in the platform
Useful for sign-in problems, account access confusion, unexpected dashboard blockers, or platform-entry issues.
Contact Support
03
Policy or Billing Questions
Use this route if the issue is related to billing or account policy expectations
When the issue may actually be a refund, access, or policy question, the legal and support pages are often a better first stop.
View Refund Policy
04
General Feedback
Use feedback when the problem is more about improvement than breakage
If something is not broken but could be improved, a feedback route is often better than an issue report.
Leave Feedback
Common issue types
Examples of the kinds of problems users may report
Not every report looks the same. These examples show the kinds of problems that usually belong on a dedicated issue-reporting page.
A page shows confusing, outdated, or clearly incorrect information
Examples include wrong labels, mismatched links, missing details, or inaccurate public information that affects user understanding.
A user cannot reach the platform area they expect
Examples include account-entry issues, navigation confusion, or access blockers that interrupt learning continuity.
Issue report form
A structured report layout ready for your future backend workflow
This form is designed to improve the quality of issue reports by collecting the essential context. You can connect it later to your preferred ticketing system, inbox, admin panel, or support workflow.
Submit an issue report
Describe the problem clearly
The more specific the report, the easier it becomes to investigate. This UI is intentionally frontend-ready only for now so you can connect it to your real issue workflow later.
Helpful checklist
What makes an issue report more useful
Better reports make debugging easier. Encourage users to include specific details instead of a short message that says only “it is not working.”
1
Describe what you expected to happen.
2
Explain what actually happened instead.
3
Mention the page or route where the problem occurred.
4
Include steps to reproduce the issue if possible.
5
Share the approximate time the issue occurred.
6
Add any helpful context such as device, browser, or screenshots later when backend support is added.
What a strong issue-reporting flow should do
Make problems clear enough to investigate properly
A good issue-reporting experience should reduce ambiguity, improve triage quality, and help the support or product team understand impact more quickly.
1
Clear problem context
2
Better reproduction detail
3
Faster triage quality
4
Lower support confusion
Need a different route?
Continue through Help Centre, Contact, or Feedback
If your situation is not a technical issue, the right next step may be support guidance, direct contact, or a product feedback route instead.