Decision template · support ticket triage API
Unofficial community documentation
Support ticket triage API
Route support tickets to the right team with typed severity, urgency, and escalate flags. Hosted Laya decide API for helpdesk automation.
POST https://api.layaaimodel.com/v1/support/triage
When to use it
Inbound tickets need team routing (billing vs engineering), issue type, severity, and a human-escalate flag before an agent drafts a reply.
Helpdesk queues die when every ticket looks the same to a keyword rule. Teams need structured routing: which queue owns it, how severe it is, and whether a human should interrupt an auto-reply. Generative “summarize this ticket” helpers still leave you parsing free text. A support ticket triage API that returns choice and score fields plugs straight into Zendesk, Intercom, Linear, or a custom worker.
Typical flow: webhook receives a new ticket → POST subject and body to this template → write team, issue type, severity, urgency, and escalate onto ticket fields → only then let a drafting model propose a reply. Keep label sets small; Banking77-style 50+ option prompts are where Laya is known to be weak versus closed APIs like Jev.
Use this when search intent is support ticket triage, helpdesk routing, or severity scoring — not when you only need a chatbot. Prepaid input tokens; outputs are free structured decisions.
How the request works
Send subject + body. The template runs several questions in one call: choice team and issue type, score severity and urgency, noul escalate. Same prepaid balance as /v1/decide.
curl https://api.layaaimodel.com/v1/support/triage \
-H "Authorization: Bearer laya_YOUR_KEY" \
-H "Content-Type: application/json" \
-d '{"subject":"App is down","body":"Production dashboard returns 500 for all users since 10am."}'Questions you get back
Each id is a typed decision (choice / score / noul) — the System One shape, not a chat completion.
team (choice): Which team should handle this? [billing | engineering | account | sales]
issue_type (choice): Issue type? [outage | bug | billing | how_to | other]
severity (score): How severe? [low → medium → high → critical]
urgency (score): How urgent? [routine → today → urgent → critical]
escalate (noul): Escalate to a human now? [yes/no probability]Example result shape
“Production dashboard returns 500 for all users” should route to engineering, mark outage, raise severity/urgency, and lean toward escalate.
team: engineering · 85%
issue_type: outage · 84%
severity: 2.4 · high
urgency: 2.1 · urgent
escalate: yes · 78%Live calibrated bars and a free anonymous try: open the homepage playground or the interactive tools runner.
Pricing & keys
Create a laya_ key on Account, buy prepaid packs on Pricing, or read the full decide reference under API docs. Output tokens are free; input is metered.