Customer Support Agent
Bill when the problem is solved.
Not when the ticket closes. When the customer doesn't reopen it.
Support agents send replies, close tickets and move on. Whether the customer's problem is solved is a different question. Charging per interaction means you get paid either way. Outcome-based billing means you only charge when the ticket stays closed.
Billing logic
Conditions
How it works
From signal to settled charge
Agent handles a support ticket
Customer rates or closes the chat
Settlement period starts
Charge fires if the ticket stays closed
Live demo
See it run
Support Chat
Acme CorpNo active chat
A customer ticket will appear here
Conditions
Outcomes
No active outcomes
A ticket will appear here when started
Include in next invoice
Nothing to bill yet
Settled outcomes will be queued here
More use cases
For teams charging when work gets done
Charge when the code ships.
Not when CI passes. When the code lands and sticks.
See how it works →Earn when the system is back.
Not when the runbook runs. When the incident stays closed.
See how it works →Launch outcome billing without rebuilding your stack
Book a 30-minute walkthrough of how it works