PixelClear is currently designed for controlled beta, design partners, and guided rollout. This support surface explains what kind of help exists, what we expect from onboarding and plugin continuity, and where a team should go next when something feels blocked.
This preview exists so the future public support lane can be reviewed as part of one coherent launch surface before pixelclear.io is finalized.
Right now PixelClear support is optimized for fast, high-context help: onboarding questions, scan interpretation, plugin continuity, and beta rollout recovery. The goal is not to simulate a huge help center. The goal is to make the real support lane credible and usable.
Use the support lane when one of these is true:
A storefront cannot complete onboarding cleanly, a plugin handoff looks pending or conflicted, a scan result seems questionable, or your team needs help deciding whether an issue is real proof, noise, or rollout risk.
Before opening a human support conversation, check these first:
`Scans` for runtime and plugin alerts, `Settings` for connected storefront posture, `Website detail` for storefront continuity, and `Reports` when the question is really about proof packaging rather than scan execution.
Shopify and WooCommerce handoffs are now supported as real MVP lanes, but support should still treat reconnect, conflict, and pending continuity as rollout-sensitive states. If a storefront looks uninstalled, disconnected, pending, or owned by the wrong workspace, route the team through the plugin connect lane and workspace connection review before treating it as a scan bug.
The most helpful requests include the storefront domain, workspace name, whether the issue came from manual onboarding or plugin flow, what page or scan was being viewed, and whether the problem looks like runtime failure, continuity mismatch, or proof disagreement.
During controlled beta, support is intentionally human and high-context. Expect guided resolution, not anonymous ticket deflection. That is a feature of the current rollout posture, not a missing piece of the product.
If your team is still evaluating PixelClear, the best route is to review pricing posture, then enter the app through sign-up or sign-in and test the first storefront path deliberately.