Visitor Help Path

Campfire, Archive, And Payment Help

Coordinate Lock: Offline Help Path: Loading
Help Setup

Visitor Help Summary

This page keeps the visitor help path simple: who answers, how fast, what to say, and where the visitor returns next.

Visitor Help Path

Public Help Path

Public Path Only

Use this path to keep visitor questions tied to Campfire, Archive receipts, payment help, and public policy before any human help step.

Help compass Show the next public step.

Visitors can bring a question, policy page, Archive receipt, or forum thread here; the path shows where it belongs before it becomes a private help request.

  1. 01QuestionAsk Navigator what public context is missing.
  2. 02PolicyAnswer from public refund, tax, account, or Archive copy.
  3. 03Help NoteDraft a note only when route context is visible.
  4. 04Human helpHuman help stays separate from the public route.
Forum memory No Community thread selected. Ask Navigator first, then return to the public Community Bridge before shaping any help note.
Curious visitor Ask Navigator what the route still needs.

Navigator frames the public question before Campfire discussion or human help is needed.

Policy question Use the public legal/refund/tax pages.

Answers stay aligned to public copy and do not improvise legal, tax, refund, or access promises.

Archive receipt Keep the receipt and guide check attached.

The help path can check status context without publishing, refunding, or changing account access.

Needs help Prepare a help note only.

The next step keeps public context attached before a visitor chooses human help.

Help loop Help returns visitors to the discovery loop.

When a visitor arrives from Archive, Public Archive, Commerce, or Campfire, the help mirror should show what can be answered publicly and where the route returns next.

  1. Confirm Read the visible receipt. Use only public route, checkout/credit, source, and policy context already visible to the visitor.
  2. Separate Policy from gameplay. Refund, tax, legal, and account questions leave the expedition path for a human check.
  3. Return Send research back to the loop. Site questions return to Campfire, Navigator, Public Archive, or Archive review with the same route attached.
01 / Public Bridge Start from visible context.

Help begins from the same public route, Archive receipt, and guide check the visitor can see.

02 / Policy Copy Use public wording.

Refund, tax, account, and Archive answers stay aligned to public policy pages until legal approval changes them.

03 / Help Note Route to human help.

Help notes can carry the visitor's public context into a human review.

04 / Live Action Human help stays separate.

Account or payment issues go to human help while the discovery loop stays simple and public.

Submission Archive context

Keep the public claim, source posture, receipt, and guide check attached.

Review Archive Path
Policy Refund and payment questions

Use published policy copy for payment questions before any live decision.

Read Payment Help
Escalate Help notes keep context

Help work keeps the Campfire, Archive, and payment path attached for a human review.

Review Help Notes
Staffing

Owner Roster And Coverage

Response Windows

Team-Editable Response Windows

Public Copy

Policy Text And Launch Check

Public Help / FAQ

Refund, Archive, Account, Credits, And Coordinate Boundaries

Public Draft

This keeps payment, Archive, account, credit, and coordinate boundaries simple for visitors while human help remains a separate reviewed step.

Public Status Notice

Launch / Incident Communication Preview

Public Draft

This shapes public status wording for launch, payment, and Archive questions without turning the visitor path into a private support console.

Evidence

Exportable Help Snapshot