Contact Us

Providing an accessible in-app contact channel directly supports the platform's commitment to users with varying digital skills, including those with cognitive or sensory challenges. Without a visible support path, frustrated users abandon the app rather than escalating issues, leading to underreporting and churn. From an organizational perspective, routing support requests through a structured form reduces ad-hoc email noise and ensures requests reach the right person. This feature also contributes to trust-building during the early rollout phase when organizations are running parallel systems and user confidence in the app is still forming. A reachable support channel signals that users are not alone in the transition, directly addressing the "introduce as an offer, not a mandate" principle stated in the source documentation.

The screen is a simple Flutter form widget using AppTextField and AppButton from the shared widget library, submitted via the REST API to a support-request endpoint. Organization-specific contact details (email address, phone number) are fetched from the organization settings response returned at bootstrap, ensuring the correct contact is shown per tenant without hardcoding. The SupportRequestService handles form submission with network retry logic. WCAG 2.2 AA compliance requires semantic labels on all fields, minimum 24x24 touch targets, and a visible focus indicator. On successful submission the screen shows a confirmation message with an accessible announcement for screen readers. No complex state management is required; a simple Riverpod StateNotifier covering loading/success/error states is sufficient.