Pay for the outcomes that happened.
Outcome-priced vendor invoices, verified against your systems of record. Monthly statements, invoice reconciliation, dispute packages. A billed outcome is an agent action like any other: CommitLayer verifies it against your helpdesk, CRM and billing systems, not against the vendor's report.
Statements from the Starter plan. Read-only connectors. Paid by you, never by the vendor.
Outcome-priced vendors, each cited to its public definition.
Definitions are transcribed from the vendor's own documentation and carry the retrieval date. Where the documentation does not say, the field is marked unknown rather than guessed.
- Intercom Fin
- Zendesk AI
- Sierra
- Decagon
- Salesforce Agentforce
Decagon states you pay only when the AI resolves a conversation from start to finish and that there is no charge when the case is passed to a human. The vendor notes that defining a resolution 'can be tricky'. No public operational definition exists, so the vendor lens below is a conservative placeholder to be replaced with the criteria in your Decagon order form.
Retrieved 2026-09-11 · 6 unknown fields
Template for vendors without a built-in connector. Claims come from a CSV/XLSX export mapped in the Connections screen. Replace the vendor lens with the definition in your contract and cite it.
Retrieved 2026-09-11 · 3 unknown fields
HubSpot charges 50 credits (USD 0.50) per resolved conversation on text-based channels. The Knowledge Base defines a resolution as a conversation with at least one customer-agent reply that shares a content source or performs an action, and no qualifying (visitor-initiated) handoff to a human within 72 hours of the last visitor response.
Retrieved 2026-09-11 · 2 unknown fields
A Procedure handoff is counted when Fin successfully executes a Procedure configured to end in a handoff to a human or a workflow. Verified when the handoff (escalation/assignment) is observed in the conversation record.
Retrieved 2026-09-11 · 1 unknown field
Two lenses on every billed outcome.
The vendor lens follows the vendor's published definition. The strict lens applies longer windows and additional checks. The gap between them is your definition delta.
| Reason code | Label | In plain language |
|---|---|---|
| reopened_within | Reopened after claim | The record was reopened inside the contract's reopen window, so the resolution did not hold. |
| no_customer_reply_within | No customer reply in window | The customer did not write again within the window after the claimed outcome. |
| escalated_to_human_within | Escalated to a human | The conversation was escalated or assigned to a human agent inside the window. |
| refund_or_credit_within | Refund or credit issued | A refund or credit was issued to the customer inside the window after the claim. |
| duplicate_claim_for_subject | Duplicate claim for subject | Another claim for the same subject exists in the same billing period; only the earliest counts. |
| verified_condition_not_met | Verified condition not met | None of the conditions that would verify the claim were satisfied. |
| no_structured_signal | No structured signal | The subject exists in the fact sources but none of the record types the definition depends on were observed. |
| missing_fact_source | Required fact source not connected | A fact source the definition depends on is not connected, so there are no facts to verify against. |
| identity_unmatched | Subject not found in fact sources | The claim's subject could not be found in any connected fact source, so nothing can be verified either way. |
| outside_billing_period | Outside billed period | The claimed outcome occurred outside the billing period on the invoice. |
From statements to disputes.
Every billed outcome in the period, verified under the vendor's own definition and under a strict lens, with the delta between them.
Line-by-line comparison of the invoice or usage export against the verified count, with reason codes for every gap.
A hashed, exportable bundle of the claims, the facts and the verdicts behind a disputed line, ready for the vendor.
What the vendor counts, what a stricter reading counts, and how far apart they are month over month.
Each vendor's outcome definition transcribed from its public documentation with the retrieval date; unknown fields stay unknown.
Every statement and dispute package carries a hash that anyone can check without an account.
Monthly statements from Starter; invoice reconciliation and dispute packages from Growth. Each billed outcome verified is one verified action against the same allowance. Pricing.
How large might your definition delta be?
Enter what you are billed and an assumed strict-lens rate. The output is a range, labeled as an estimate; the real number comes from your facts and your contract.