Skip to content
anti sandbox.
Measurement and pilots

Calculate cost per resolved support case with review effort included

Compare platform, usage and human-review costs over the same period, using a consistent definition of a resolved case.

Choose a complete numerator

List platform fees, usage charges, relevant staff time and any integration or review costs included in the comparison. Document what is excluded. Allocate shared costs consistently rather than charging one workflow for the whole team and another for only AI usage. Keep one reporting currency and record the date and source of any conversion; a US-dollar budget and a Saudi-riyal invoice cannot be added directly.

Use an honest denominator

Count resolved cases under the same definition and time window for both workflows. Separate unresolved work and avoid counting one conversation several times because it crossed channels. Report quality and repeat-contact outcomes alongside cost. A lower cost per closed ticket can be misleading if premature closures create more work in the following period.

Fictional worked example

Fictional calculation: 1,000 reporting-currency units in platform and usage costs plus 2,000 in allocated review time, divided by 600 resolved cases, equals 5 units per case. If 100 cases are still unresolved, report them separately. This illustrates the formula; it is not Anti Sandbox pricing, a savings claim or a recommended staffing budget.

Action checklist

  1. Document included fees, usage, staff time and exclusions.
  2. Use one currency with an explicit conversion reference when needed.
  3. Apply the same resolution definition and reporting window.
  4. Show unresolved cases and quality measures beside the cost result.
Related pages
See it yourself

A workspace worth exploring.

Open the demo