Per-user vs per-minute pricing models in cloud telephony: which is actually cheaper
Per-user looks predictable but penalises low-utilisation seats. Per-minute looks fair but punishes growth. Per-active-user is the third option that very few vendors offer. Here is the math.
Cloud telephony pricing in India clusters around three billing models — per-user, per-minute, and per-active-user — and most teams pick the wrong one because the vendor's pitch deck shows the favourable number, not the realistic total. This post is the taxonomy, the math, the hidden costs, and the questions to ask before signing.
A different lens than deployment mode
A companion post on this blog — [cloud dialer vs self-hosted dialer](/blog/cloud-dialer-vs-self-hosted-dialer) — compares the same platform along a different axis (who runs the servers) and answers a different buyer question (what does ops look like at 25 seats vs 200). If you already know your billing-model preference and are choosing between cloud-managed, self-hosted, and hybrid, that post is the better read. This post is upstream of that decision: it is about the invoice line-items, not the deployment mode.
The two axes are independent. You can run per-active-user pricing on a cloud-managed deployment, on a self-hosted deployment, or on a hybrid one. The math below is agnostic to where the servers live.
The three pricing models, side by side
Per-user (per-seat) pricing
₹1,500 – ₹3,000 per agent per month, regardless of how many calls they make. Common on platforms that bundle voice + IVR + recording + reporting into one SKU.
Best for: Teams with predictable, consistent utilisation across all seats — e.g. inbound support desks where every agent handles roughly the same call volume. Worst for: Teams where some agents make 50 calls a day and others make 5. You subsidise the low-utilisation seats.
Per-minute pricing
₹0.80 – ₹1.40 per minute of voice traffic, usually with a small monthly platform fee on top. The minute rate covers the platform, the carrier markup, and the vendor margin in one number.
Best for: Teams with bursty or seasonal call volume — a Diwali retail spike, an insurance renewal window, a one-quarter compliance sweep. You pay for what you burn. Worst for: High-volume steady operations. The per-minute rate compounds fast and forecasting becomes hard when volume swings.
Per-active-user pricing
A newer model, still uncommon in India: ₹1,000 – ₹1,500 per agent per month, but only for agents who actually logged in and placed at least one qualifying call that month. Inactive seats, agents on leave, churned hires, hiring waves that landed one week too early — not billed.
Best for: Teams with variable headcount (hiring waves, attrition cycles, seasonal scale-up, campaign-based hiring). Worst for: Almost no team. It is per-user pricing with the unfair edge cases removed. The only teams for whom it does not matter are those with zero seat churn — rare in Indian contact-centre reality.
The carrier layer sits underneath all three
Whatever the platform pricing model, carrier minutes are billed separately or bundled in. Three patterns you will see in RFP responses:
Bundled (no separate minute billing). The platform fee includes 'unlimited minutes' up to a fair-use cap. Looks attractive but the cap is usually low (around 200 minutes per agent per day) and overages are at a markup that ends up dominating the invoice.
Marked-up minutes. The platform charges per minute of voice (₹0.90 – ₹1.40 in India), of which ₹0.30 – ₹0.60 is the actual carrier cost. The 2-3x markup funds the platform. Vendors rarely disclose the split.
Passthrough minutes. The platform does not touch the carrier billing. You contract directly with the carrier (Vilpower, Tata Communications, Airtel Business), pay ₹0.30 – ₹0.60 per minute, and pay the platform a separate — typically smaller — per-user fee on top.
Most teams underestimate how much of their total telephony cost is minutes. For an outbound SDR team running 5 hours of talk-time per agent per day, minutes are 70-80% of the all-in cost. Choosing passthrough over marked-up minutes routinely saves more money than any platform-feature trade-off you can make.
Modelled cost across team sizes
Workload assumption: each agent does 5 hours of outbound talk-time per day, 22 working days per month — a mid-intensity SDR or collections floor. Carrier rate is ₹0.45 per minute if passthrough, ₹1.20 per minute if marked-up (both toward the middle of the market range).
15 agents, ~198,000 outbound minutes per month
| Model | Calculation | Total | |---|---|---| | Per-user, bundled + overage | 15 × ₹2,500 = ₹37,500 + overage on 132,000 min × ₹1.20 = ₹158,400 | ~₹195,900 | | Per-minute, marked-up | Platform ₹22,500 + 198,000 × ₹1.20 = ₹237,600 | ~₹260,100 | | Per-active-user, passthrough | 15 × ₹1,500 = ₹22,500 + 198,000 × ₹0.45 = ₹89,100 | ~₹111,600 |
At 15 agents, per-active-user with passthrough comes in ~57% cheaper than per-minute marked-up and roughly 43% cheaper than per-user bundled once overage kicks in.
45 agents, ~594,000 outbound minutes per month
| Model | Total | |---|---| | Per-user, bundled + heavy overage | ~₹6.0 lakh / month | | Per-minute, marked-up | ~₹7.8 lakh / month | | Per-active-user, passthrough | ~₹3.3 lakh / month |
At 45 agents, the model choice is worth roughly ₹3–4.5 lakh per month — enough to fund an additional team lead plus a QA analyst.
120 agents, ~1.58 million outbound minutes per month
| Model | Total | |---|---| | Per-user, bundled + overage | ~₹19 lakh / month | | Per-minute, marked-up | ~₹21 lakh / month | | Per-active-user, passthrough | ~₹8.9 lakh / month |
At 120 agents, the delta compounds into eight-figure annual differences. The pricing-model decision matters more than any feature decision at this scale.
Where each model breaks down
Per-user, with no utilisation enforcement
You hire 30 agents in March for a campaign. By June, 10 of them are on leave, underperforming, or parked on other tasks. You are still paying for 30 seats. The vendor has no incentive to make this visible — they invoice you for 30 seats regardless of who logged in.
Fix: insist on per-active-user pricing in the contract, or get a clause that lets you reduce seat count quarterly with 30-day notice.
Per-minute, when call volumes grow
A growing team feels per-minute pricing as a tax on success. Doubling team size doubles minutes doubles spend. Forecasting cuts both ways — you cannot project budget if your call volume varies 30% month over month.
Fix: re-negotiate at every renewal once volume is predictable, or migrate to per-active-user.
Per-active-user, when seats are continually rotating
The model assumes activity is binary (logged in + made a call vs not). If an agent logs in for one call by mistake, they count as active. Most vendors handle this with a minimum-activity threshold (e.g. 'must have made 5+ calls, totalling at least 10 minutes, in a month'). Verify the definition of 'active' in writing before signing.
Hidden costs the pitch deck does not show
1. Setup / onboarding fees
₹15,000-50,000 one-time, often only charged on annual contracts. Negotiable — most teams either get it waived or halved by the second round of contract redlines.
2. Number rental on top of platform fees
₹400-800 per DID per month. A team running 50 numbers is ₹20,000-40,000 per month before they place a single call. Almost never included in the headline 'per-user' price.
3. API access tier
Some platforms gate API features to higher plans. If you need webhooks, calendar integration, or custom call routing, confirm what tier you need up front — moving up mid-contract is priced to punish.
4. Recording storage
First 30-90 days usually included. After that, ₹2-10 per GB per month. A 10-agent team accumulates ~50 GB per month — small individually, but storage costs hit hard at retention horizons (3-7 years for BFSI, 5+ years for insurance).
5. Contract renewal mechanics
'6-month auto-renew' clauses are common and rarely caught at signing. Read the termination terms before, not during, the renewal window.
6. Currency / payment surcharges
Some platforms invoice in USD; small FX fluctuations cost lakhs per year for large customers. India-incorporated vendors invoicing in INR avoid this entirely.
7. Premium support tier
Default support is usually email + business hours. 24×7 phone + guaranteed response SLA is a separate paid tier. If you run overnight campaigns, factor this in — it is not optional at that operating shape.
The 10 questions to send in the procurement email
Send these before the first vendor demo. The answers tell you what model you are actually buying:
- Is the per-user fee for provisioned seats or active users? What is the exact definition of 'active'?
- Are voice minutes bundled, marked-up, or passthrough? At what rate per minute?
- What is the markup over the underlying carrier cost? (Most will not tell you this; the answer, or the refusal, is itself informative.)
- Can I bring my own carrier (BYOC)? At what platform-side fee?
- What is the recording storage policy? When does it become billable, and at what rate?
- What is the all-in cost for a representative month at my team's projected volume? Get it in writing.
- What is the contract term and the renewal mechanic (auto-renew, opt-in renew, notice window)?
- What are the early-termination fees, and are they capped?
- Are setup / training / integration fees one-time, in writing, capped?
- Is the API on the base plan or a paid tier? What are the rate limits?
Why most teams pick the wrong model
Three patterns we see repeatedly on discovery calls:
Pattern 1: optimising for the lowest sticker price. The '₹999 per user' plan looks cheaper than the '₹1,500 per user' plan. But the ₹999 plan has marked-up minutes (₹1.10 per minute) and the ₹1,500 plan has passthrough (₹0.45 per minute). The ₹1,500 plan is cheaper after a few thousand minutes of monthly usage — which is most teams.
Pattern 2: not modelling the team six months out. You sign at 10 agents. In nine months you are at 25. The plan that was cost-competitive at 10 is brutal at 25. Always model the team you are headed towards, not the team you are.
Pattern 3: ignoring the carrier cost entirely. Vendors love this pattern — they pitch 'all-inclusive ₹2,499 per user' precisely because the minute cost is hidden inside the number. Always separate the platform cost from the minute cost in your evaluation. If the vendor will not disclose the split, that itself is a signal.
What dialque does
For transparency on our own model: dialque bills per active user (₹1,500 per month per agent who logged in and placed at least one qualifying call that month) on the Starter tier, ₹2,000 on Growth, and ₹2,500 on Enterprise. Carrier minutes are passthrough — you pick your own SIP trunk and dialque does not mark up minutes. The intent is that the vendor incentive is aligned with your outcome: we want you to actually use the platform, not pay for inactive seats or inflated minute rates.
If your team is on a per-user or per-minute marked-up plan today and the renewal is approaching, the per-active-user + passthrough math typically saves 30-50% at 10+ agents on comparable feature scope. Do the sums against your last three months of invoices before the renewal conversation, not after.
Frequently asked questions
Where is the rough threshold at which per-minute becomes structurally too expensive?
Above ~50,000 outbound minutes per month, per-minute marked-up plans become structurally expensive. Switch to either per-user (with low or no markup on minutes) or per-active-user + passthrough.
Does per-active-user mean unlimited calls per active agent?
Per-active-user covers the platform fee. Minutes are billed separately — either bundled, marked-up, or passthrough. Verify what is included in the base fee before assuming.
How does WhatsApp / SMS pricing typically work on top of voice?
Almost always per-message, on top of voice pricing. WhatsApp via the Business Solution Provider is ₹0.50-1.10 per conversation (Meta + BSP markup layered). SMS is ₹0.15-0.25 per message in bulk on DLT-registered senders. Both are billed separately from voice and are usually not in the 'all-inclusive' quote.
What about pay-as-you-go (no commitment) pricing?
A few vendors offer it. Per-unit rates are 20-40% higher but there is no contract lock-in. Useful for short pilots or seasonal campaigns; expensive if it becomes your steady state.
Should I sign annual or month-to-month?
Annual usually gets a 15-25% discount but you are locked in. Negotiate a 'termination for material breach within 30 days notice' clause to give you an out if the platform underdelivers.
How is this different from choosing between cloud-managed and self-hosted?
Pricing model (this post) is about how the invoice is calculated. Deployment mode (see the [cloud vs self-hosted post](/blog/cloud-dialer-vs-self-hosted-dialer)) is about who runs the servers. You choose both, independently. A common shape for Indian BFSI teams: per-active-user + passthrough billing, on a self-hosted deployment for DPDP + RBI localisation. A common shape for D2C support teams: per-active-user + passthrough billing, on a cloud-managed deployment for zero-ops onboarding.
The pricing-model decision is more financially consequential than any single feature decision past 10 agents. Model the all-in cost — platform + minutes + DIDs + storage — at your projected team size before signing, and the right model usually picks itself.