Helixdesk

Product

A support desk that knows which wallet it is talking to

Helixdesk is built around one idea: a ticket from a crypto-native user should arrive with the context an agent would otherwise ask for.

Wallet-signed intake

  • Connect Phantom or Solflare, or use the simulated demo wallet.
  • Sign a message containing a timestamp and a random nonce. The signature is checked with ed25519 before the ticket is created.
  • Signing a message is not a transaction and cannot move funds.

Automatic on-chain enrichment

  • SOL balance via Solana RPC getBalance.
  • Token account summary via getParsedTokenAccountsByOwner, showing accounts with a non-zero balance.
  • The five most recent signatures via getSignaturesForAddress.
  • Status for every transaction signature you paste, plus a Solscan link.
  • If the public RPC rate limits, the ticket is still created with a clear "using cached enrichment" notice.

Agent dashboard

  • Ticket list with status badges, search across subject, wallet, and signature, plus status and category filters.
  • Ticket detail with a threaded conversation and a permanent enrichment sidebar.
  • Status workflow: open, in progress, resolved.
  • A simple help-article admin to add or remove articles shown in the help center.

Where your data lives

  • In this build, tickets, replies, and the agent session are stored in your browser with localStorage.
  • We never ask for a seed phrase or private key.
Try the ticket flowRead the help articles
Agent sign inOpen ticket