Contact
Reach Hero through clear, accountable channels.
Contact should feel like part of the product system, not an afterthought. Until structured support forms are wired, the web should offer direct and honest contact paths.
Contact principles
The public site should never imply a support workflow that does not exist. Direct channels are acceptable when they are explicit and reliable.
- Use direct contact paths until support workflows are connected
- Keep support, legal, and help routes easy to discover
- Prefer clarity over simulated form success states
Current contact paths
These routes are intentionally direct. Structured request handling will be added when the support domain is integrated into the backend ecosystem.
Structured web forms will be connected once the support domain is wired to the real backend. Until then, these contact paths remain honest and direct.