Billable condition

A billable condition is the machine-checkable rule that decides when an outcome becomes billable. It is a boolean expression evaluated against the events your system emits. When the condition is satisfied, the outcome is provisionally successful. When it still holds at the end of the settlement period, the outcome confirms and becomes a charge.

How it works

A condition is built from leaves. Each leaf checks one fact about the event stream: an event was seen, an event was not seen, an event occurred at least N times, or the latest value carried by an event compares against a threshold. Leaves combine with boolean logic into a complete definition of success.

A support agent example: agent_replied is seen, escalated is not seen, reopened is not seen and csat is missing or above 3. All four must hold for the resolution to bill.

Why it matters

The billable condition is pricing as code. It forces the ambiguity out of "we charge per resolution" and replaces it with explicit criteria both sides can inspect. It is also what makes an invoice defensible: every line item can point at the condition it satisfied and the events that satisfied it, which is how disputes get prevented rather than argued.

The condition is evaluated from scratch on every accepted event, so late reversals like a reopen flip the result before it ever settles into a charge.

Related

• Billable conditions in the docs, including all operators
• Defining Concrete Billable Outcomes for AI Agents
• Outcome-based pricing