Help and support must stay reachable from every page without entering the main tree

What it is

Stuck people need help or support immediately, and they are often already outside the “right” class—otherwise they would not be stuck. Reachable on every page, without entering the main structure: the help entrance lives in the utility cluster or a stable floating position, and does not require a correct content-tree click first. Making “Help centre” a primary nav section asks lost people to walk the right road in order to ask for directions. The entrance may deep-link to an article about the current page; the entrance itself must be on the current page.

Reachable is not an auto-popup. It is that when someone decides to ask, they need not first complete a successful classification.

Why it happens

Help-seeking starts after the main task has failed. The classification model is then unavailable or falsified; putting help back inside that tree uses the failed tool to fetch rescue. Working memory is full of the failure; extra wayfinding steps are dropped. A cross-page stable help entrance lifts rescue out of the classification decision, so failure and asking can coexist.

If help lives only on home or only under About, people in deep pages and mid-flow must leave the current state to ask, which may dump unsaved work, so they choose not to ask. Reachability protects “ask while still in the bind,” not “ask, then come back.”

Studying it

Create a failure mid-task and see whether help is found without destroying current state.

• Paradigms: halfway through a flow, an obstacle that cannot be solved alone; help in the utility cluster versus only a primary “Help” section versus only on home. Search allowed.
• Independent variables: entrance location, whether a contextual deep link opens a relevant article, whether opening help covers and dumps the form.
• Dependent variables: time from obstacle to help open, whether the current page was left, whether main-task state is still there after help opens.
• Methodological note: lab participants click Help more readily. Watch whether they pay with task-leaving. Score contextual deep-link accuracy separately: a wrong article is a second falsification, worse than no context.

Where it stops holding

Expert tools may summon help with a function key or command palette and need no persistent button, but the summon must be consistent app-wide. Where compliance forbids chat (exams, trade confirmation), a static help-doc entrance should remain rather than the whole block vanishing. People outside the login wall often need help most; putting the entrance only in the post-login utility cluster makes it unreachable when signed out. In some industries a phone emergency must outrank in-app help and does not follow the usual “below primary weight” rule.

Applying it

• Keep a help entrance in the same place on every page (utility text or a stable icon), not in the content-class row.
• Open help in a side sheet or layer that keeps task state underneath. Do not whole-page-jump unless the person explicitly opens a standalone help centre.
• When the current page has a matching article, land there by default and offer an exit to all help.
• Verify by blocking a half-filled form and timing until help opens. If the person must go home or into a content section first, or the draft is gone after open, the entrance is still nested in the main structure, or rescue itself is causing a second failure.

Related

• Within the group: G2.09.1 Utility navigation holds function entries that are not part of the content tree · G2.09.2 Utility entries need less visual weight than primary nav so they do not compete · G2.09.3 A sitemap is the exhaustive fallback when primary nav fails · G2.09.4 Footer nav holds secondary and exhaustive links; it does not replace primary nav
• Adjacent: T3.02 Organizing and retrieving help · H3.02 Three elements of an error message · G2.07 Navigation consistency
• Search terms: persistent help · support entrance · contextual help