> For the complete documentation index, see [llms.txt](https://sonic-ai-works.gitbook.io/sonic-networks-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sonic-ai-works.gitbook.io/sonic-networks-docs/help-center/sonic-support-assistant-and-helpers.md). # SONIC Support Assistant & Helpers Support-assistant character, helper registry, security boundaries, escalation logic and safe account/token-sale support behavior. **Version `1.0.0` · Status: Preview** The SONIC Support Assistant is a **support-specific assistant surface** backed by restricted helper functions. It may use a friendly character presentation, but its authority comes from the authenticated user context and helper policy—not from the character/persona. ## Role The assistant is optimized for: * product/documentation questions; * onboarding and account guidance; * Studio/project troubleshooting; * generation-status explanation; * AI Credit and billing-state explanation; * wallet-connection diagnostics; * transaction-state explanation without signing; * Tokenomics/token-sale status and disclosure lookup; * API/debug guidance; and * support escalation. ## Support character vs authority ``` Character / visual persona ↓ presentation only Support Assistant ↓ intent + dialogue Helper Registry ↓ scoped functions SONIC APIs / Docs / Status ↓ authoritative data Response / Escalation ``` A support character can express tone, accessibility and continuity. It does not receive elevated permissions, wallet authority or hidden account access. ## Helper registry Recommended safe helper contracts: | Helper | Purpose | Auth requirement | | ---------------------- | --------------------------------------------------------------- | -------------------------------------------- | | `docs.search` | Search canonical docs/FAQ | Public | | `status.read` | Read service/provider status | Public or authenticated | | `account.context.read` | Read normalized account/workspace context | Authenticated | | `generation.read` | Read generation operation/status | Authenticated + ownership | | `credits.read` | Read available/reserved/used credits | Authenticated | | `billing.read` | Read plan/invoice/payment status | Authenticated + billing scope | | `wallet.diagnostics` | Check wallet provider/network/linking state | Authenticated where account data is used | | `transaction.read` | Explain existing TransactionIntent/attempt state | Authenticated + resource ownership | | `token.sale.read` | Read canonical pre-sale status, provider, dates and disclosures | Public sanitized projection | | `token.market.read` | Read verified market/pool/routing status | Public sanitized projection | | `support.case.prepare` | Build a redacted escalation packet | Authenticated where account data is included | | `support.case.create` | Create a support case after explicit user action | Authenticated | Helper names are logical contracts. Runtime implementation may map them to internal service/tool identifiers. ## Helper response contract Each helper should return normalized provenance: ```ts type SupportHelperResult = { ok: boolean; data?: T; status: "LIVE" | "VERIFIED" | "CONFIGURED" | "PLANNED" | "PAUSED" | "UNAVAILABLE"; source: string; observedAt?: string; requestId?: string; errorCode?: string; }; ``` The assistant must preserve `UNAVAILABLE` instead of inventing a value. ## Token-sale helper behavior `token.sale.read` may surface the current published planning state, including: ``` stage PRE-SALE / planned targetWindow Q4 2026 provider PinkSale | Smithii.io | TBA allocationEnvelope ~3–5B SONIC (planning; source allocations TBA) presaleReference ~$0.000002 initialDexReference ~$0.0000025 binance TBA binanceAlpha TBA ``` The helper must also return the risk/disclosure state. It must never turn a planning price into a recommendation, target return or guaranteed launch value. ## Transaction safety The support assistant can **explain** a transaction and link to the product's explicit authorization flow. It cannot: * access private keys; * sign or auto-approve transactions; * bypass re-authentication/AAL requirements; * fabricate wallet ownership; * alter recipient/amount/program after the user preview; or * treat a transaction signature as settlement. ## Sensitive-data boundary Do not place the following in assistant prompts, logs, analytics or escalation packets: ``` seed phrase private key wallet secret password MFA secret / recovery code raw auth token raw provider API secret ZK witness full payment credential ``` Support cases should include only the minimum diagnostic context: request IDs, operation IDs, normalized error codes, timestamps, resource IDs, safe provider/job correlation IDs and redacted environment metadata. ## Escalation logic ``` assistant can answer from canonical source → answer with source/status helper reports recoverable user action → provide exact safe steps helper reports requires-review / policy / security issue → prepare escalation packet → ask user to submit/escalate possible account compromise / suspicious signing → stop risky workflow → direct to Security/Support escalation ``` ## Non-goals The Support Assistant is not: * a financial or investment adviser; * an exchange/listing representative; * a private-key recovery mechanism; * a substitute for legal/compliance eligibility checks; * a source of deployment truth independent of the registry/RPC; or * an unrestricted autonomous Agent. ## Quality invariant ``` canonical source + least-privilege helper + authenticated ownership where needed + no secrets + explicit status/provenance + safe escalation = valid SONIC support response ``` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://sonic-ai-works.gitbook.io/sonic-networks-docs/help-center/sonic-support-assistant-and-helpers.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.