Answers from the documentation; checking which model is on duty
Hi - I answer from the OpenSmartRoute documentation: routing, the API, plans and quotas, self-hosting. Ask away, or open a support ticket if you need a person.
Grounded in the docs - follow a source before acting on it.
escalate-ticket - Prompt - OpenSmartRoute
Promptv1.0.0
escalate-ticket
Escalate a ticket to a human team with a given escalation reason.
Prompt file imported from maumarcastil/helpDeskPersonal (.claude/commands/escalate-ticket.md). Fill in {{arg1}} before use. Copyright stays with the author.
Escalate ticket $0 with escalation reason {{arg1}}. Read the ticket first, choose the right target team from its triage category and subcategory, then record the escalation.
Use it
Copy one of these into your project. Installing also returns the manifest and these snippets.
<!-- Generated by `npm run generate`. Do not edit by hand. -->
Escalate ticket $0with escalation reason {{arg1}}. Read the ticket first, choose the right target team from its triage category and subcategory, then record the escalation.
Manifest
The prompt text and its fill-in variables. Copy it or fetch it by URL from your own code.
{
"prompt": "<!-- Generated by `npm run generate`. Do not edit by hand. -->\n\nEscalate ticket $0 with escalation reason {{arg1}}. Read the ticket first, choose the right target team from its triage category and subcategory, then record the escalation.",
"variables": [
"arg1"
],
"notes": "Escalate a ticket to a human team with a given escalation reason. Arguments: <ticketId> <reason>.",
"metadata": {
"source": {
"provider": "github-claude-commands",
"repository": "https://github.com/maumarcastil/helpDeskPersonal",
"path": ".claude/commands/escalate-ticket.md",
"ref": "e598f4d2049fdd40d717f8e606276ab258b0f2e6",
"url": "https://github.com/maumarcastil/helpDeskPersonal/blob/e598f4d2049fdd40d717f8e606276ab258b0f2e6/.claude/commands/escalate-ticket.md",
"key": "maumarcastil/helpDeskPersonal/.claude/commands/escalate-ticket.md"
}
}
}
Installed into a catalogue, chosen by a router
Install escalate-ticket and it becomes one more candidate the router can pick - when it fits.
A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.