Improve Support Accessibility – Add No-Login Contact Options for Users
Dear Meta Community Team and Support,
I would like to provide constructive feedback regarding the current support contact process for Meta Quest and Horizon accounts, as it presents significant challenges for many users, including myself.
The primary difficulties include:
- The requirement to log in to the community forums or other Meta services in order to access private messaging, chat, or detailed support options.
- Reliance on the Meta Horizon app or authenticated channels (such as WhatsApp or linked social accounts) for many recovery and troubleshooting flows.
- Absence of a straightforward, no-login-required method—such as a dedicated public email address or phone support line—for submitting general feedback, reporting process issues, or handling basic account recovery scenarios.
In my recent experience, a phone change and device reset led to loss of app access and 2FA recovery codes, making it impossible to log in without first navigating these authenticated support paths. This creates a circular problem: users locked out of their accounts cannot easily reach assistance without creating additional accounts or using services they may not have (e.g., WhatsApp or Facebook).
These barriers can frustrate legitimate users, reduce trust in the platform, and potentially impact customer satisfaction and retention—factors that are important for business success.
Proposed Improvements:
- Introduce a no-login feedback form or public email channel specifically for support process suggestions and non-sensitive issues.
- Offer limited phone support options (even if queued or callback-based) for account verification and recovery.
- Provide clearer, upfront guidance on alternative contact methods for users without app or social account access.
I believe these changes would make support more accessible and user-friendly, benefiting a broader range of customers.
Thank you for considering this feedback. I appreciate the efforts of the support team and look forward to any improvements that may address these concerns.
Best regards, Daniel