Support split

Direct help or suite gateway.

Support needs to triage direct-distribution customers away from legacy suite routes immediately, while still preserving the suite gateway as a legitimate existing-customer path.

Direct firstSuite support remains visibleNo support clutter

Support contract

The route exists to reduce confusion, not to become a generic knowledge base.

Direct buyers
Recovery, billing, download, device actions
Suite users
Reroute to suite gateway support
Fallback
Support email remains visible
Tone
Calm triage, not a ticket maze

Triage paths

The support page stays small on purpose so customers can self-sort without reading dense documentation.

Direct distribution path

Support actions that belong to this web app.

  • Manage link resend and sign-in recovery.
  • Billing portal re-entry for monthly purchases.
  • Download access, device actions, and entitlement questions.

Suite gateway path

Support actions that should stay outside the direct storefront.

  • Existing suite entitlements and gateway-managed sessions.
  • Legacy account issues unrelated to direct purchase fulfillment.
  • Cases where the buyer needs the dedicated suite support flow.

Support route states

Later support and customer lanes inherit the triage surface and slot in live support actions where each state expects them.

direct-help

Direct buyers see recovery-first help.

The route highlights manage links, sign-in recovery, download access, and direct billing/license guidance for direct purchasers.

suite-help

Suite users are rerouted immediately.

Existing suite customers are acknowledged cleanly and pointed to the suite gateway support path instead of the direct storefront flows.

generic-contact fallback

A support dead-end is avoided.

If the route cannot determine customer context, it still provides support email and the suite gateway link without hiding either path.