Per-call and per-minute prices cannot be compared by their headline numbers alone. The result depends on call length, included services, minimum fees, overages, and what each provider counts as billable.
Read current primary pricing and billing definitions for the actual providers. Smith.ai publishes per-call options, while Ruby discusses per-minute pricing. Verify current terms before making a purchasing decision.
Normalize the workload before calculating
Use a defined reporting period and traffic sample: answered calls, duration distribution, short spam calls, transfers, failed attempts, and follow-up tasks. Average duration alone can hide a mixture of very short and very long calls.
Record base fees, included allowances, unit rounding, exclusions, concurrency or coverage limits, integrations, human escalation, setup, and support. Two plans with the same apparent unit may include different operating work.
Calculate a fictional comparison
Suppose Plan A charges an illustrative two units per call and Plan B one unit per minute, with no other costs in this simplified example. At 100 calls averaging three billable minutes, A costs 200 units and B 300.
If the same 100 calls average one billable minute, B costs 100 while A remains 200. The simplified break-even duration is two minutes. Actual plans need their base fees, allowances, rounding, and exclusions added before this arithmetic becomes useful.
| Scenario input | Why it matters |
|---|---|
| Call count | Drives per-call consumption |
| Billable duration | Drives per-minute consumption |
| Short unwanted calls | May have provider-specific treatment |
| Transfers and follow-up | Can change included work or cost |
| Base and overage | Alter the real break-even point |
All amounts and traffic figures are fictional examples, not current provider rates.
Compare completed outcomes too
A cheaper plan that requires staff to recreate every request may cost more operationally. Review supported integrations, accepted handoffs, pending-work ownership, and recovery. Do not label booked value as revenue saved without evidence.
Run low, expected, and high traffic scenarios and state the assumptions. Keep provider charges, agency management, and shared infrastructure distinct. Review management versus usage costs for the full bill structure.
Questions about pricing units
Is per-call always more predictable?
It can be easier to model when call counts are stable, but allowances, exclusions, and added services still matter.
Should every spoken minute count as billable?
Use the provider's exact current definition and rounding rules rather than assuming talk time equals charged time.
What should a comparison table include?
Verified terms, traffic assumptions, full monthly arithmetic, sensitivity cases, included outcomes, setup, support, and known uncertainties.