Help and support
Help center
Use the help center for onboarding, billing, portfolio imports, and product understanding in one public support layer.
Help center and support content
Help articles, onboarding guides, billing explanations, and portfolio troubleshooting should become a reusable support layer instead of staying hidden across product pages.
Issue triage queues
Portfolio mismatches, billing confusion, login issues, and source-data complaints should later route into structured support queues with clear ownership.
Subscriber success interventions
Incomplete onboarding, unused premium features, and failed imports should trigger guided recovery or success workflows before churn sets in.
Operator-facing support rules
Support operations should live behind clear policies for escalation, rollback, customer messaging, and auditability rather than informal fixes.
Next routes
Signed-in supportProtected route for subscriber support posture, recovery, and configured contact channels.Billing recoveryReview renewal, failed-charge, and fallback-access expectations in one place.Contact routeFallback public route when a user needs a visible help destination before sign-in works cleanly.