Support & Help
/support is public and combines searchable FAQ help with FAQ-matching support chat.
Date: 2026-09-30 Purpose and access /support is public and combines searchable FAQ help with FAQ-matching support chat. The routed chat uses local matching/fallback replies, not a verified live model or human connection. No paid plan is required. Signed-in and public shells differ; native iOS filters external-purchase FAQ entries. This does not establish native-app parity. Workflow Open Help/Support or /support. Select an FAQ category, enter a search term and expand a matching question. Clear the category/search if no items match. Switch to chat for a question the FAQ does not resolve. Include the feature, route and error text, but never passwords, API keys or payment-card details. If escalation is offered, review the support-ticket form's name, email and details, including any conversation copied into it. Submit the ticket explicitly and check its confirmation. The Custom plan Contact us entry opens the same kind of ticket flow; it does not purchase a plan. Results, limits and states FAQ results are filtered locally; zero matches means adjust the search, not that support is unavailable. The chat's short typing delay is not evidence of remote research. Ticket submission is a separate network operation; on failure retry only after checking whether submission succeeded. Automated guidance may need human review and does not itself change billing, execute trades or guarantee resolution. There is no guaranteed response-time promise here. Identity-provider recovery and Stripe/store payment flows remain outside support chat; use their official screens. Oscar can also explain product navigation, but an answer is not an account-action confirmation.