Short answer
For per-call rounding, add each connection’s blocks rather than rounding total seconds once. Check minimum, block size and the provider’s duration basis. The exercise does not apply to different rules or convert minutes into cost without a rate.
Key verification: The total reconstructs from each call under declared minimum and billing unit.
Sources and limitationsFour short calls may consume more blocks than one conversation of equal total duration. Separate measured time from billing units to understand why. This guide solves a fictional example without estimating your invoice or claiming every carrier rounds alike.
Contractual rule before formula
CallHippo describes full-minute increments and per-call rounding in its terms, with additional traffic and plan conditions. Check the applicable contract: inbound, outbound and unconnected calls may be treated differently. Avoid deriving units from an agent’s visual timer.
Example: a 60-second block
| Fictional call | Duration in seconds | Billable minutes |
|---|---|---|
| A | 10 | 1 |
| B | 50 | 1 |
| C | 61 | 2 |
| D | 119 | 2 |
| Total | 240 | 6 |
The assumption is a one-minute minimum with each connected call rounded upward. For positive duration, blocks equal seconds divided by 60 rounded up to an integer. The 240 seconds equal four measured minutes but six billable minutes here. Rounding only the total produces the wrong basis.
Duration, legs and additional charges
Check whether a record represents one call or multiple forwarded legs and which basis the provider uses. Keep fixed charges, destination rates and surcharges separate. Avoid adding legs already included in a total. Failed calls need their own rule rather than automatic treatment as an example minute.
Check a sample before budgeting
Retain identifier, duration basis and expected blocks, then reconcile against provider evidence. Investigate discrepancies before extrapolating. CallsIQ has not tested CallHippo billing: this original table can be used in a worksheet without buying additional software.
Sources and limitations
Documentary review: . Content type: Documentation-based guide with original exercise.
Sources describe terms and capabilities stated by their owners. Proposed protocols and fictional examples do not establish product tests performed by CallsIQ.
- full-minute increments and per-call rounding in its termshelp.callhippo.com
Check current terms
Consider these options if they solve the problem described. Confirm features, limits and availability in your country.
CallHippoAffiliate linkThe labelled commercial links may earn CallsIQ a commission or referral reward. Our commercial policy.
Official sources, explained calculations and clearly labelled examples. Read about our methodology and use of AI in writing.