/ticket-triage

Use only support, knowledge-base, and project-tracker sources that are actually available and authorized in the host. State clearly when a source was not checked.

Categorize, prioritize, and route an incoming support ticket or customer issue. Produces a structured triage assessment with a suggested initial response.

When checking public documentation or known-issue evidence, read the SandBase API map. Resolve the listed capability with sandbase_discover, inspect its returned name with sandbase_inspect, then follow execute_as to call sandbase_run(name: "<returned name>", arguments: { ... }) using only the current schema. For async results, poll sandbase_run_get with the returned run_id within the task budget; report pending or failed runs without automatically resubmitting them.

Usage

/ticket-triage <ticket text, customer message, or issue description>

Examples:

• /ticket-triage Customer says their dashboard has been showing a blank page since this morning
• /ticket-triage "I was charged twice for my subscription this month"
• /ticket-triage User can't connect their SSO — getting a 403 error on the callback URL
• /ticket-triage Feature request: they want to export reports as PDF