General enquiries
- Marketing and partnership requests
- Public championship questions
- Editorial and celebration submissions
Client operations
Contact routes should separate enquiries from school onboarding
The rebuild keeps general contact, school registration, and password-recovery flows distinct so operational requests land in the right queue from the start.
Primary contact lanes
The public site should not force every enquiry through the same generic form.
School onboarding
- Registration approval
- Band setup and seat planning
- Coordinator and band leader provisioning
Support
- Login and password issues
- Quest access incidents
- Reporting and payment follow-up
Implementation note
In NestJS this should become a queue-backed contact module with explicit submission types, spam controls, and admin review state.
For this scaffold, the page documents the route structure and the form intent. A later iteration should connect it to a persisted contact submission entity and notification workflow.