Best-effort support, with a public scope that stays explicit.

At the current stage, SN Assistant support is handled through:

• GitHub Issues for bugs and reproducible problems
• GitHub Discussions for questions, usage help, and product feedback

To get useful help quickly, include:

• ServiceNow UI context such as Classic UI or Polaris and the table or record type
• the action used, such as Explain, Ask, Document, or Document UpdateSet
• provider and model used
• whether RAG was enabled
• whether Update Set mode was List-first or Deep
• what happened and what you expected
• any execution trace details
• any relevant console or service worker errors

For script actions, include:

• detected record type
• whether the editor was visible
• whether the issue reproduces after reloading the extension and refreshing the tab

For Update Set documentation, include:

• last visible line in Execution Trace
• updateCount, deepFetched, outputChars, or other visible trace values

Priority support scope for the current build:

• verified script contexts
• Update Set documentation
• provider configuration
• RAG settings and grounding behavior
• language settings

Areas that should be treated as non-GA or evolving:

• UI Scripts and Transform Scripts passed the current Chrome validation pass, but they still need Edge validation before entering the public support promise
• Background Scripts remain outside the guaranteed scope because they are not currently detected reliably
• edge cases in unusual ServiceNow layouts or highly customized instances

Support is currently best-effort. There is no guaranteed SLA yet. If paid plans are introduced later, support tiers can be separated more clearly.

The initial public release is expected to remain self-serve:

• free extension distribution
• user-managed provider setup
• best-effort product support through the public channels above

Do not post sensitive customer data, production secrets, or confidential scripts in public issue threads. If a future private support inbox is introduced, sensitive reports should go there instead.