Help documentation is accessible from within the onboarding flow
Why it matters
Users who get stuck during onboarding and cannot find help in-context either email support (expensive for you, slow for them) or give up entirely. The user-experience taxon treats contextual help access as onboarding-tier support, not a polish item: a "Need help?" link in the corner of the signup screen, a tooltip on a confusing step, or an embedded chat widget deflects support load and rescues conversions that would otherwise be lost to silent abandonment. The cheapest support ticket is the one the user answers themselves by clicking a link.
Severity rationale
Low because most users complete onboarding without needing help, but the absence amplifies churn and support cost for the subset that gets stuck.
Remediation
Add a persistent help affordance to the onboarding layout. Edit src/app/(app)/onboarding/layout.tsx to render a fixed-position "Need help?" button linking to the getting-started docs in a new tab, or embed a chat widget so users can ask questions without leaving the flow.
<div className="fixed bottom-4 right-4">
<Button variant="outline" size="sm" asChild>
<Link href="/docs/getting-started" target="_blank">Need help?</Link>
</Button>
</div>
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the Onboarding UX Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
Taxons
History
- 2026-04-18·v1.0.0·Initial import from saas-onboarding·automated