Estimate demand
- •Average handle time × total calls = projected minutes.
- •Add a buffer for seasonality and promo spikes.
- •Map projected minutes to the included minutes on each plan.
AI coverage cost per call divides plan cost by calls handled. Project minutes from average handle time, then add metered usage and the add-ons you need.
This KPI keeps stakeholders honest about AI pricing. It divides your projected AI minutes by the monthly platform fee to show how predictable coverage compares to staffing curves.
Expressed as dollars per call at your own average handle time.
Your number
Plan cost ÷ calls handled
Varies by plan and languages enabled. See current plans on our pricing page.
Billing driver
Minutes · concurrency
Not tied to headcount, overtime, or temp agencies.
Cost breakdown
| Line item | Annual spend | Per-unit | Notes |
|---|---|---|---|
| Platform fee | Monthly plan fee × 12 | Annual ÷ expected calls | Depends on the plan you choose. See current plans on our pricing page. |
| Usage minutes | Overage minutes × rate | Annual ÷ expected calls | Metered minutes above the base tier. |
| Optional add-ons | Add-ons you enable | Annual ÷ expected calls | Languages, custom EMR hooks, specialty QA. |
Assumptions
Your own minutes per call once AI collects intent, verification, and disposition tags.
Plot your own simultaneous-call peaks; single-site clinics and multi-specialty groups differ.
Supporting proofs
We’ll plug your call logs into our usage estimator and produce a finance-ready projection.