Support

Help

Use help to move to the correct Onyx path instead of guessing through blocked states.

Support topics

  • Quiet path

    Authentication

    Resume account entry or recover an expired session before continuing.

    Auth entrySession recovery

  • Quiet path

    Onboarding

    Resume or restart the canonical onboarding path through the backend-owned session.

    Get startedOnboarding recovery

  • Quiet path

    Service

    Inspect active service state, activation readiness, and usage from the authenticated surface.

    Open homeConnections

  • Quiet path

    Wallet and number context

    Use the narrow wallet and connection-number pages when those surfaces should already show contextual product state.

    WalletConnection numbers

 

When should I use support instead of continuing in the current route?
Use support when the current page cannot safely confirm the next step from backend truth or when recovery is being surfaced explicitly.
Why does help point me back into onboarding, checkout, or service routes?
Onyx keeps one controlled path for each flow. Help should return you to the correct surface rather than create a separate product flow.
Why do Wallet and number pages stay intentionally narrow?
Those pages only summarize what the current client-facing contracts expose. If wallet or number detail is not available there, help should route you back to the live onboarding, checkout, connection, or recovery surface instead of inventing missing data.
What should I do if I refreshed, switched devices, or came back later and the flow feels different?
Return to the current controlled route first. Help exists to send you back into the correct onboarding, checkout, service, or recovery surface rather than rebuild state from memory.