A short story
Jonas leads customer support and is admin for the support team. He is setting up a triage agent that sorts incoming tickets and drafts first answers.
Before it goes live, he opens the agent’s Settings → Value tab.
- He writes the value statement in one sentence: "Saves the support team about eight hours a week on sorting tickets." The agent sees it too, so it knows what it is for.
- He rates its criticality as High. The whole team depends on it.
- He clicks Ask the agent to suggest. The agent reads its own instructions and proposes outcomes it can actually count. Jonas keeps two key metrics: tickets triaged and answers drafted.
Then the agent goes to work. Every time it triages a ticket, it records it with the ticket number. If the same ticket comes back, it is still counted once.
Three months later, at the quarterly review, finance asks: "What are we actually getting for this?"
Jonas opens the agent’s Usage tab. The value statement is at the top. Below it, the two key metrics with their trends for the period he picks. Further down: how many credits the agent has used.
Then they look at Agent usage, the list of all the team’s agents. An old reporting agent has no value statement and no activity for a month. Jonas switches it off.
The answer was ready before finance asked, because Jonas set it up on day one.



