Support

Support should reduce ambiguity.

Support exists for technical issues, operator questions, and route clarification when docs or product pages are not enough.

Support

Support pages should map users to the correct help path.

The route should distinguish support, docs, and enterprise escalation clearly.

Support

Where support fits

Support is for operational questions and technical help, not for every commercial or policy conversation.

Utility surface

Operator help

Route CLI, platform, or workflow questions to support or docs.

Issue escalation

Bug reports should preserve a traceable path through support or GitHub.

Commercial boundaries

Deployment and contract scope should move to enterprise or Contact Sales.

Reference routes

Useful routes before opening support

Support works better when docs and product routes are still visible.

Docs

Operator guidance and reference material.

Contact

General human route.

GitHub

Public issues and source repository.

Open docs first when the issue is best solved by command or workflow reference.