Contact
This environment currently relies on direct support rather than a ticket queue.
The contact page holds the active feedback path, support boundaries, and response expectations instead of repeating them across the homepage or pricing flow.
Feedback path: issues are routed through direct support and developer troubleshooting rather than an in-product ticket system.
Scope: account access, billing questions, analysis failures, and context handoff issues should all enter through this page first.
Response expectation: support is handled manually on working days and is suitable for the current MVP stage rather than a formal SLA-backed queue.