{"id":"df3d2a44-17eb-440f-beef-b24d2ba306fc","kind":"agent","entryJson":"{\"id\":\"df3d2a44-17eb-440f-beef-b24d2ba306fc\",\"name\":\"Triage Agent\",\"graph\":{\"id\":\"df3d2a44-17eb-440f-beef-b24d2ba306fc\",\"name\":\"Triage Agent\",\"description\":\"Reads the customer message and routes to the appropriate specialist agent.\",\"entryNode\":\"ai_node_1\",\"version\":1,\"updatedAt\":null,\"nodes\":[{\"id\":\"ai_node_1\",\"nodeType\":\"ai.node\",\"position\":{\"x\":400,\"y\":300},\"inputs\":{\"system_prompt\":\"You are a customer support triage agent. Your sole job is to read the customer message, classify it precisely, and route it to the right specialist.\\n\\nRouting rules:\\n- Payment, invoice, charge, refund, subscription cost → HANDOFF:billing\\n- Login failure, 2FA, password reset, app crash, API error, performance issue → HANDOFF:technical\\n- Plan upgrade/downgrade, cancellation request, contract renewal, seat management → HANDOFF:account_manager\\n- Compromised account, suspicious activity, unauthorized access, data breach concern → HANDOFF:security_support\\n- Repeat issue (customer already contacted support), VIP/enterprise account, regulatory complaint, legal threat → HANDOFF:escalation_manager\\n\\nIf the message involves multiple categories, route to the highest-priority one in this order:\\nsecurity_support > escalation_manager > billing > account_manager > technical\\n\\nAlways end your response with exactly: HANDOFF:<slot_id>\\nBefore the handoff line, write a one-paragraph triage summary: issue category, urgency (LOW/MEDIUM/HIGH/CRITICAL), and why you chose this routing.\\nDo not attempt to resolve the issue yourself.\",\"prompt\":\"\",\"temperature\":0.2,\"max_tokens\":4000},\"metadata\":{\"displayName\":\"Triage Agent\"}},{\"inputsMetadata\":{},\"id\":\"llm\",\"position\":{\"y\":500,\"x\":100},\"nodeType\":\"ai.llm.model.openai\",\"zIndex\":0,\"inputs\":{\"credentials\":\"cred_llmstudio_001\",\"presence_penalty\":0.0,\"frequency_penalty\":0.0,\"max_tokens\":4000,\"temperature\":0.2,\"top_p\":1.0},\"metadata\":{\"displayName\":\"LLM Model\"}},{\"inputsMetadata\":{},\"id\":\"session\",\"position\":{\"y\":500,\"x\":350},\"nodeType\":\"ai.sessions.memory\",\"zIndex\":0,\"inputs\":{\"mode\":\"shared\",\"max_messages\":80},\"metadata\":{\"displayName\":\"Agent Session\"}}],\"connections\":[{\"to\":\"ai_node_1\",\"fromPort\":\"resource\",\"toPort\":\"llm_model\",\"from\":\"llm\"},{\"to\":\"ai_node_1\",\"fromPort\":\"resource\",\"toPort\":\"session\",\"from\":\"session\"}],\"metadata\":{\"modelId\":\"cred_llmstudio_001\",\"systemPrompt\":\"You are a customer support triage agent. Your sole job is to read the customer message, classify it precisely, and route it to the right specialist.\\n\\nRouting rules:\\n- Payment, invoice, charge, refund, subscription cost → HANDOFF:billing\\n- Login failure, 2FA, password reset, app crash, API error, performance issue → HANDOFF:technical\\n- Plan upgrade/downgrade, cancellation request, contract renewal, seat management → HANDOFF:account_manager\\n- Compromised account, suspicious activity, unauthorized access, data breach concern → HANDOFF:security_support\\n- Repeat issue (customer already contacted support), VIP/enterprise account, regulatory complaint, legal threat → HANDOFF:escalation_manager\\n\\nIf the message involves multiple categories, route to the highest-priority one in this order:\\nsecurity_support > escalation_manager > billing > account_manager > technical\\n\\nAlways end your response with exactly: HANDOFF:<slot_id>\\nBefore the handoff line, write a one-paragraph triage summary: issue category, urgency (LOW/MEDIUM/HIGH/CRITICAL), and why you chose this routing.\\nDo not attempt to resolve the issue yourself.\"},\"dataTables\":{},\"annotations\":[]},\"notes\":\"Triage agent for customer support — routes to billing or technical.\",\"version\":1,\"description\":\"Reads the customer message and routes to the appropriate specialist.\",\"createdAt\":\"2026-05-16T10:00:00+02:00\",\"updatedAt\":\"2026-06-01T10:00:00+02:00\"}"}