CCaaS Pricing for a 20-Agent Team in India: Seats, Minutes and AI Costs

For a 20-agent contact centre in India, compare the full cost at your actual inbound and outbound workload—not just the price per seat. Your quote should separate human licences, billable call minutes, phone numbers, recordings, integrations, support, AI usage and one-time setup. Twenty staff accounts also do not automatically provide twenty simultaneous AI calls.

This guide uses two fictional offers to show the calculation. The assumed prices are not market benchmarks, supplier quotes or a promise of VaniAgent capacity. Public provider documentation was reviewed on 15 October 2026; obtain a current written quote for your location, call routes and configuration.

For the broader pricing models, start with our AI voice agent pricing guide for India. Here, the specific buying decision is how to compare a seat-based and a usage-based contact centre offer for the same 20-person team.

What should a 20-agent contact centre budget include?

Start with the billable unit. A named user, a concurrently logged-in human agent, a simultaneous telephone channel and an AI conversation are different things. Ask which one a quoted licence or capacity limit represents.

Human salaries, recruitment, computers and office expenses belong in the business case too. Keep them in a separate staffing-and-overhead section so a software-only comparison is not mistaken for the total cost of running a contact centre.

Define one workload before comparing quotes

Suppose your team has 20 licensed human agents and operates for 26 days each month. The following connected-call workload is an educational assumption, not a measured customer result.

For the arithmetic below, assume these connected durations equal billed minutes, with no rounding, chargeable ringing, extra transfer legs or bundled allowances. That assumption must be replaced with the supplier's billing definitions. The number of unsuccessful outbound attempts is not specified here; if attempts carry charges, the example is incomplete until you add them.

Export a representative month's call records before requesting quotes. Include direction, destination, connection status and billed duration, and examine the busiest intervals. Staff may also spend substantial time on administration, breaks, support tickets or longer calls outside this example. The workload above does not establish the staffing requirement or productivity of twenty people.

Worked comparison: per-agent vs pay-as-you-go CCaaS

Assume both fictional offers support the same required features and routing. Both have the same carrier rates: Rs 0.50 per inbound minute and Rs 1 per outbound minute. These rates are invented for the calculation.

Offer B is Rs 5,080 lower at this illustrative volume. That difference is not a recommendation to select usage billing: it depends on identical scope, the assumed fees and the absence of other minimums or exclusions. Replace each row with the actual quote before deciding.

If setup were Rs 15,000 for A and Rs 20,000 for B, the first-month totals would be Rs 69,000 and Rs 68,920 before tax. The recurring difference would almost disappear in month one. With unchanged volume, twelve months plus setup would be Rs 663,000 for A and Rs 607,040 for B before tax, excluding AI, staffing and other unquoted costs.

Do not automatically apply one tax percentage to every component. Use the tax treatment and currency shown on the supplier's invoice. Foreign-currency services also need a dated conversion assumption and any applicable payment costs.

Find the break-even volume

When carrier and optional costs are genuinely identical, they cancel out of this simplified comparison. Let M be monthly platform-billed minutes:

• Offer A software: Rs 24,000.
• Offer B software: Rs 8,000 + Rs 0.30 × M.
• Break-even: (24,000 − 8,000) ÷ 0.30 = 53,333.33 minutes.

Below that volume, B has the lower software charge. Above it, A has the lower software charge, assuming no tier changes or additional fees. If inbound/outbound rates differ between quotes, use the complete cost equation instead: direction mix matters and the simple threshold no longer applies.

This table excludes the carrier and other shared charges. Ask whether platform minutes include queues or holds: usage can exceed actual human conversation time.

What public provider pages establish—and what they do not

Exotel's business-phone pricing page describes plans with rental, usage credits and agent allowances. It explicitly excludes Voice Streaming (Agent Stream) from the listed plans. That page alone is insufficient to price this twenty-agent AI workload; request the required streaming and routing scope separately.

AWS's Amazon Connect pricing appendix distinguishes voice-service charges from communication charges and describes additional features and billing rules. Choose the relevant product tier, region and destinations before using its published rates. An advertised service rate alone is not the complete telephone bill.

These observations explain why we use a normalized quote worksheet rather than declare a cheapest provider from headline prices. They do not establish feature parity between suppliers.

Add AI as a separate, scoped scenario

Do not apply AI pricing to every human-handled minute unless every minute actually uses the service. Suppose an approved pilot processes 2,000 calls with an average of three AI-billed minutes: that is 6,000 AI minutes. Multiply those minutes by the verified AI rate, then add only excluded charges.

Separate AI-contained calls from calls later transferred to people. A transferred conversation can consume AI time, human time and more than one carrier leg. Read the provider's transfer rules and compare cost per qualified lead or verified completed task, rather than claim savings from automation percentage alone.

Check current VaniAgent pricing for the published plan terms, then request a scope for this workload. A single-channel plan is not an automatic substitute for a twenty-agent contact centre. Extra concurrency, specific integrations and carrier routing need confirmation. Monthly credits and minute usage must also be reconciled so the same prepaid consumption is not counted twice.

Size simultaneous call capacity separately

At the example's monthly average, call volume may look manageable. A burst of callers after an advertisement or service incident changes the requirement. Use peak arrival intervals, connected duration, abandonment, permitted waiting time and an overflow path to size capacity.

Twenty human licences do not establish twenty active AI sessions, and unlimited usage does not establish unlimited parallel calls. Model an outage and a busy period before purchasing. Our simultaneous receptionist calls guide explains the capacity distinction.

Send every supplier the same quote request

Copy these requirements into your procurement brief:

1. Twenty human users: identify which require simultaneous login, supervision or administration.
2. The same monthly inbound/outbound minutes, destination mix and peak intervals.
3. The required phone numbers, transfers, recordings and retention period.
4. CRM workflow, language requirements and the exact AI pilot scope.
5. Separate recurring fees, usage, included allowances, minimum spend and first-month setup.
6. Written billing rules for unsuccessful attempts, ringing, queues, rounding and transferred legs.
7. Commitments, cancellation terms, service support and an export/exit process.

Ask for a sample invoice calculated from that brief. Run the same permitted pilot with each shortlisted supplier, and reconcile completed outcomes against the invoice using the voice-agent billing audit guide. Use the vendor RFP template to record scope and supporting evidence.

Choose the offer that meets your service requirement at a verified total cost. If a supplier cannot explain an exclusion or billable unit, keep that item marked unquoted rather than entering zero.

Frequently asked questions

How much does contact centre software cost for 20 agents in India?

There is no reliable single price without a workload and written quote. In this fictional comparison, the recurring technology budget is Rs 54,000 for a seat-based offer and Rs 48,920 for a usage-based offer before tax. These are arithmetic examples, not market rates; salaries, AI usage and setup are excluded from those recurring totals.

Is pay-as-you-go CCaaS cheaper than per-agent pricing?

It depends on the fixed fees, billable minutes, rate differences, included services and minimum commitments. In the worked example, software charges break even at approximately 53,333 monthly billed minutes. Below that volume the usage offer has the lower software charge; different quotes or carrier rates change the result.

Do 20 contact centre agents require 20 AI calling channels?

No. Human seats and simultaneous AI calls measure different capacity. Size AI channels using peak arrival patterns, call duration, permitted queue time and overflow requirements; a monthly average cannot prove adequate capacity.

Are inbound and outbound minutes included in CCaaS pricing?

Some offers include a defined allowance; others charge separately by direction, destination or call leg. Ask about connected time, ringing, queue time, minimum duration, rounding, transfers and unused allowances before comparing totals.

Does an unlimited-agent telephony plan include unlimited AI calls?

No such inclusion should be assumed. A human-user licence allowance does not establish AI usage, streaming access, simultaneous call capacity or carrier charges. Confirm each component in the written offer.

Should monthly prepaid credits be added to minute charges?

Not if the same credits pay for those minutes. Track usage value and cash payment separately, including minimum top-ups, expiry and unused balances, to avoid counting the same cost twice.

Plan a scoped comparison

Bring your monthly call records and peak concurrency requirements to a scoped VaniAgent demonstration. Confirm written pricing and deployment capacity before replacing an existing route.