Here's the trap. Amazon Connect charges 3.8 cents a voice minute, which sounds unbeatable against a $119 seat licence, so you model it and it wins comfortably. The pricing page carries four words in brackets that change the answer.
"Voice $0.038 per voice min (standard telephony rates apply)". The headline is the platform. The phone call itself is extra, and almost nobody quoting this figure includes it.
It is the same shape as every advertised rate in the voice category: a number that is genuinely what the vendor charges, for a subset of what you will actually be billed.
What does Amazon Connect actually charge?
| Channel | Published rate | Unit |
|---|---|---|
| Voice | $0.038 | per voice minute, telephony extra |
| Chat | $0.010 | per message sent or received |
| SMS and third-party messaging | $0.014 | per message sent or received |
| $0.080 | per email sent or received |
Read from AWS's own pricing page on 22 August 2026. AWS notes that pricing varies by region and communication type, so check your own region before modelling.
The oddity worth noticing is email. At 8 cents a message it is the most expensive interaction on the page: one email costs the same as 2.1 voice minutes, eight chat messages or nearly six SMS. If you are choosing which channels to open, that ordering is the opposite of most people's intuition, and it is charged both on send and on receipt.
What does a ten-agent centre cost?
Talk time drives everything, so here it is at three levels, across 21.7 working days.
| Talk time per agent per day | Voice minutes | Platform cost | With illustrative telephony |
|---|---|---|---|
| 2 hours | 26,040 | $989.52 | $1,354.08 |
| 4 hours | 52,080 | $1,979.04 | $2,708.16 |
| 6 hours | 78,120 | $2,968.56 | $4,062.24 |
At four hours a day the platform alone works out at $198 per agent per month, and around $271 with telephony on the illustrative rate. Both are above every published seat licence in the category, including Five9's $119.
So where does Connect actually win?
Below the crossover, and we published that threshold two days ago using the headline rate. This is the correction: adding telephony moves it.
| Seat licence | Crossover, platform only | Crossover with telephony |
|---|---|---|
| Five9, $119 | 2.4 hrs/day | 1.8 hrs/day |
| NICE CXone, $110 | 2.2 hrs/day | 1.6 hrs/day |
| Talkdesk, $85 | 1.7 hrs/day | 1.3 hrs/day |
| Dialpad, $27 | 0.5 hrs/day | 0.4 hrs/day |
Including telephony pulls the Five9 threshold from 2.4 hours a day down to about 1.8, a reduction of roughly a quarter, and it moves in the seat vendors' favour at every price point. Our census of who publishes a CCaaS rate flagged that the comparison was tilted toward Connect; this is how much by.
Connect still wins clearly for genuinely low-utilisation operations: overflow lines, seasonal peaks, out-of-hours cover, anything where agents are available rather than talking. That is a real and common shape, and it is the one the per-minute model was built for.
How do you keep the bill down?
Three levers, and they are unusually direct because consumption pricing means every saving is immediate rather than waiting for a renewal.
- Channel mix is the biggest single lever and nobody talks about it. Moving an interaction from email to chat takes it from 8 cents to 1 cent, an 87 percent reduction on that contact. If your support flow defaults to email because it always has, that default now has a price attached.
- Handle time is the second. On a per-minute platform, thirty seconds shaved off an average call is a straight-line saving across every call, which is not true on a seat licence where you have already paid for the agent's month regardless.
- Turn off what you are not reading. The separately-metered components accumulate quietly, and analytics nobody opens is the classic example. This is the same discipline as auditing any usage meter, and we set out what happens when one runs out in the credit overage post.
The inverse is also worth stating: on a per-minute platform there is no saving from an idle agent, because you were not paying for them. That is the actual argument for consumption pricing and it is a good one for the right shape of operation.
What is not in these numbers?
The AI layer, and it is the reason most people are looking at Connect in 2026. Contact Lens for conversation analytics, Lex for the conversational front end, Voice ID, Customer Profiles and storage are all separately metered and none appeared on the channel table we read.
We are not going to estimate them. What we will say is that the modelled figures above are a floor, that the components you are most likely to want are the ones not counted, and that the difference between a floor and an invoice in this category is usually large. Ask for a quote with every component you intend to switch on, and compare that against a seat licence rather than comparing the headline rate.
The answer to the question people actually have is that Amazon Connect is genuinely cheap for a contact centre that does not talk very much, genuinely expensive for one that does, and that the line between those falls at roughly two hours of talk time per agent per day rather than at the figure the headline rate suggests.
