Support Desk

Clear support for users. Clear operations for the team.

Use a tracked ticket when you need follow-up. Use quick chat when you want a fast answer from the support agent.

Submit a Ticket Quick Chat

Initial AI triage Human follow-up in one thread Private ticket links saved on this device

Use this desk for

Support work that benefits from structure and follow-up.

Wallet, transaction, bridge, exchange, mining, and explorer issues.
Kipper, Entropic, StratumX, and developer-tooling questions.
Partnership routing, security concerns, and escalation paths.

What to include

Public identifiers and reproducible context only.

What you tried, what you expected, and what happened instead.
Wallet addresses, tx hashes, worker names, screenshots, and environment details.
How to reproduce the issue if it happens consistently.

Covered products

Wallets, How to Get QUAI, Kipper, Entropic, Mining, Developer Docs & SDK, Network & Explorer, Community & Media, Something Else

Common questions

Will support ever ask for a seed phrase or private key?

No. Support should only ask for public addresses, transaction hashes, worker names, screenshots, and reproducible steps. Never share custody credentials.

What makes the AI support agent effective?

Choose the right product lane, include concrete identifiers, add exact error text, and describe the last action that worked. Structured tickets are easier to route and safer to handle.

Where do mining questions belong?

Use StratumX for pool, worker, and mining infrastructure behavior. If the issue is about chain visibility or transaction state, use Network & Explorer.

Can a person from the team step in?