Billing Ticket Router
ivy.agent.billing-ticket-router · v1.0.0
ivyx
Reads support tickets, classifies them as billing-related or not, emails billing tickets, and drafts replies for all.
Steps
In the order the agent's file lists them. A branch or a loop is a step too; the wiring between steps is in the file.
- 01Model turnread the incoming support ticket text
- 02Model turndecide if the ticket is about billing
- 03Branchonly email to billing team if it is a billing ticket
- 04Ivy NodeEmail Sendivy.node.email-send
- 05Model turndraft a short reply for the customer
Nodes it brings
Adding this agent in IVYX Studio adds these nodes with it. A node your workspace already has is kept as it is, even at another version.
What it touches
Collected from what each of its nodes declares, plus the model call when a step is a model turn. A declaration is the author's statement, and it is what policy rules select on.
Inputs
| Field | Type | Description |
|---|---|---|
| messagerequired | string | What the model reads. |
Outputs
| Field | Type | Description |
|---|---|---|
| ticket_text | string | the raw ticket content |
| is_billing | boolean | true if the ticket is about billing |
| sent | boolean | True once the server accepted the message. |
| recipients | array | The addresses it was accepted for. |
| subject | string | The subject sent. |
| reply | string | the drafted reply text |
Tests
2 of 2 test cases passed on Oct 1, 2026, in the publisher's own environment, before this version was published. The registry keeps that record; it does not run the cases again.
Requires: a local SMTP relay on port 1025, python:3.9
- billing-ticket
A double charge is billing: it is mailed to billing and a reply is drafted.
- product-ticket
A broken button is not billing: nothing is mailed and a reply is drafted.