The situation
A software company put an assistant in front of its help centre. Deflection went up. The support queue got shorter. Everyone agrees it is working.
Nobody can say what it returns. The model bill arrives monthly as one number. Deflection lives in the support tool. Agent salaries live in payroll. The three have never been in the same sentence, so the renewal conversation is a debate about feelings.
Meanwhile three teams have quietly built their own assistants on the same account, and their calls are inside that same monthly number.
What runs where
API gateway
Every metered call routed through your gateway arrives attributed, per request, so the support assistant separates from the three side projects.
Vendor account
The seats your engineers and product managers use directly, including chat in the browser.
Developer machines
Coding sessions on engineer laptops, including subscription seats the API bill never sees.
What Oabo shows in the first 30 days
- Cost per assistant, split out of the single monthly bill.
- Tickets answered without a human, tied to the model calls that answered them.
- The support hours those answers absorbed, held in the capacity register on their own.
- A cash figure only where it reaches your ledger — a contractor invoice that shrank, a seat you stopped buying.
What to expect
Two units, two blocks. Cash is money your ledger moved. Capacity is time your people got back. Oabo never adds them together.