What is Amazon Connect? It runs a contact center on AWS and bills for what gets used. Since April 2026, AWS has been selling that product as Amazon Connect Customer.
I checked every feature against AWS's current docs and pricing page, including Voice ID, which AWS stopped supporting in May 2026.
What Is Amazon Connect? The Short Answer
Amazon Connect is a cloud contact center service from AWS that handles voice, chat, SMS, email, and tasks, and it has no seat-based licensing. You pay for what you use, and your team builds the caller experience in a drag-and-drop flow designer.
Amazon's announcement of April 28, 2026 turned Amazon Connect into a portfolio of agentic AI solutions named Customer, Decisions (supply chain), Talent (hiring), and Health (health care).
Of those four, the original contact center is now Amazon Connect Customer, and this guide covers that one.
AWS describes Amazon Connect Customer as an agentic AI solution for customer experience, where AI agents handle a contact from start to finish and business teams design them on a no-code canvas.
That canvas, the agentic CX designer, reached general availability on September 2, 2026, in nine AWS regions. This guide walks through flows and the setup around them, which is what older explainers describe. The designer's region limit comes up again in the Skip list below.
Key Features
- Channels and numbers: Voice, chat, email, and tasks share a single interface for routing, queuing, analytics, and management, and WhatsApp Business messaging and Apple Messages for Business have native integrations.
DID and toll-free numbers are available across 158 countries, and national outbound numbers in 72.
-
Flows: A flow defines the customer experience from start to finish. Default flows come with an instance, so you can test a first contact center before building your own flows.
-
AI agents: Customer-facing agents resolve contacts on their own, and AI agents that support human agents deliver answers and recommend next steps during and after a conversation. AWS describes what it previously called Amazon Q in Connect as one of these AI agents.
-
Conversational analytics: Sentiment and emerging contact themes across voice and chat. It also tracks agent compliance risks and redacts sensitive data in transcripts, audio files, and email messages.
On naming, AWS's docs title it conversational analytics, and the page address still reads contact-lens.
- Workforce management: Forecasting predicts contact volume and average handling time, and capacity planning estimates how many full-time agents you need to meet service-level goals, with what-if analysis to refine the targets.
Scheduling then builds each agent's schedule from skills and forecasts, and intraday forecasts update every 15 minutes. A spike may not appear until the next refresh.
Older explainers still list Voice ID, but AWS closed it to new customers on May 20, 2025, and ended support on May 20, 2026. The end-of-support notice points to the DeleteDomain API for removing stored data, and to Pindrop or one-time-password authentication as replacements.
Amazon Connect Pricing in Short
Amazon Connect Customer is pay-as-you-go. Voice costs $0.038 per voice minute with standard telephony rates added, and the other channels are priced per message or email. AWS lists no minimums, long-term contracts, seat-based licensing, or token-based charges.
| Channel | Rate on AWS's pricing page |
|---|---|
| Voice | $0.038 per voice min (standard telephony rates apply) |
| Chat | $0.010 per message sent or received |
| SMS and 3P messaging | $0.014 per message sent or received |
| $0.080 per email sent or received |
AWS also offers a lower-rate Customer Basic mode (around $0.018 per voice minute and $0.004 per chat message) that bills AI features separately. The rates above are the all-in Customer rate.
Beyond that, AWS says pricing may vary by region and communication type, and that third-party providers have their own rates, so check the pricing page before you commit. I checked these rates against AWS's pricing page on October 8, 2026.
How Does Amazon Connect Work?
Everything runs inside your own AWS account, and you set up the contact center there. All of it is held in an instance, which AWS describes as a virtual contact center that holds all its resources and settings.
An instance serves 4 groups of users, according to the what-is page, which are customers, agents, managers and supervisors, and administrators. Administrators provision phone numbers and link Amazon Connect to other products, while managers monitor team metrics and coach agents.
Five building blocks make up a basic setup, and the step-by-step order comes in the getting-started section below.
- Create an instance. By default, AWS creates Amazon S3 buckets for call recordings, chat transcripts, exported reports, flow logs, and email messages, and encrypts that data with AWS Key Management Service.
Object Lock in compliance mode isn't supported on those buckets, which matters if your retention rules call for write-once storage.
-
Claim or port a number. For voice, you claim a number from AWS or port (transfer) your own number.
-
Add users and routing. Security profiles control what each user can open, and queues and routing profiles decide who receives each contact.
-
Build flows. Start from a default flow or draw your own. In a Get customer input block, you can connect an Amazon Lex bot, and a flow can run AWS Lambda functions to reach your own systems.
-
Give agents the Contact Control Panel. Human agents use it to handle contacts.
Here’s how the pieces fit together on a real call. A caller dials the number you claimed, the flow asks for an account number, a Lex bot captures the digits from the keypad, and a Lambda function looks up the account before the flow routes the contact to a billing queue.
If the account lookup takes longer than 8 seconds, the contact follows the Error branch.
Amazon Connect vs. AWS Direct Connect: What's the Difference?
Amazon Connect and AWS Direct Connect are two separate AWS services that happen to share a word. Amazon Connect is the contact center, while AWS Direct Connect is a network link that connects your own network to AWS over a dedicated cable.
| Detail | Amazon Connect | AWS Direct Connect |
|---|---|---|
| What it is | AWS's contact center, now Amazon Connect Customer | A cloud service that links your network directly to AWS |
| What you set up | An instance, phone numbers, queues, and flows | A fiber-optic Ethernet cable from your router to a Direct Connect location, plus virtual interfaces |
| What it carries | Calls, chats, SMS, email, and task contacts from your customers | Network traffic to public AWS services or Amazon VPC, bypassing internet service providers in your network path |
| Who it serves | Customers, agents, supervisors, and administrators | Teams that connect their own network to AWS |
Choose by job. Direct Connect moves your network traffic to AWS, and Amazon Connect answers your customers' calls.
What I Liked and Didn't Like About Amazon Connect
I read AWS’s docs and pricing pages for this and haven’t run a production contact center on Amazon Connect. Each point below comes from those sources.
Pros
-
Cost follows contact volume. A month with fewer contacts should produce a smaller bill because AWS charges per minute and per message, and a seasonal agent doesn't need a seat license. Telephony charges are added.
-
Numbers are available in 158 countries. AWS lists DID and toll-free numbers in 158 countries and national outbound numbers in 72, so check both against your own country list.
-
Flows can be tested natively. Native testing and simulation arrived on November 30, 2025. A test sends DTMF (keypad tone) or text inputs through a flow, and up to 5 can run at once, which covers flow logic before launch.
-
Flows connect to your own code. A flow can invoke Lambda functions to reach your systems and add a Lex bot to handle caller input.
Cons
-
Names and features changed in 2026. A runbook written before April 28, 2026 can still say Amazon Connect where AWS now says Amazon Connect Customer, and one written before May 20, 2026 can still plan around Voice ID.
-
Lambda calls have fixed time limits. An invocation waits up to 8 seconds before the contact follows the Error branch, and a sequence of functions is capped at 20 seconds. Customers hear silence while a function runs, so AWS recommends a Play prompt block between functions.
-
Native testing validates flow logic and self-service paths, but a full live call (audio quality, interruptions, and latency) needs a call placed on your number. Our breakdown of Amazon Connect and Lex testing makes the same point.
Should You Use Amazon Connect? My Assessment
Amazon Connect works for teams whose contact volume swings and who already work in AWS. In my read, the Lambda and Lex connections matter when someone on your team can write the custom code.
Large companies use it too. Toyota, American Airlines, TUI, and Cochlear appear on AWS’s customer page, and Amazon’s April 28, 2026 announcement names State Farm and Air Canada as users of the original product.
Who Amazon Connect Suits
-
Seasonal or uneven contact volume, because the bill tracks minutes and messages.
-
Engineering teams already working in AWS that want Lambda and Lex inside the flow, because the pieces are already in their account.
-
Global operations that need local numbers across the 158 countries AWS lists.
Who Should Skip Amazon Connect
-
Companies that budget by headcount. Genesys Cloud lists Cloud CX 1 at $75 USD per user/month billed annually (usage-based pricing may apply), and Twilio Flex quotes its User + usage plan at "Starting at $35 per monthly active user" plus metered charges.
-
Companies that need the agentic CX designer outside its 9 supported regions, which include US East (N. Virginia), Frankfurt, and London.
Five9 shows no prices on its homepage and sends buyers to "Get a Quote," so you'd need a sales call to compare it.
If you're comparing AI voice agent platforms for a narrower job, our review of 7 voice AI services for businesses includes Cognigy for enterprise contact centers.
How to Get Started With Amazon Connect in 5 Steps
AWS's setup guide starts with an instance and lists more tasks after it. These set up a working inbound line.
-
Create an instance. Choose where Amazon S3 stores your data, then try the voice and chat experiences to see how they behave.
-
Claim a phone number. Claim one from AWS or port an existing number. Claiming first, as AWS suggests, lets you build while the transfer finishes. If you plan to make outbound calls, also enable outbound calling and set an outbound caller ID.
-
Add agents and security profiles. Assign permissions so each role opens the parts of Connect it needs.
-
Set up routing. Define queues and routing profiles so each contact reaches the right agents.
-
Edit a default flow. Default flows come with Amazon Connect, so edit one before you write your own. Then give agents access to the Contact Control Panel.
The what-is page links first-time users to hands-on labs in the Getting Started with Connect Customer workshop.
Amazon Connect Best Practices to Know Before You Build
AWS publishes architecture guidance for Amazon Connect workloads. The first two habits below come from it and the docs above, and the other two come from how I'd test a flow before it takes calls.
-
Decide on one instance or several first. AWS's guidance has a section on that choice, alongside sections on reliability, security, and cost.
-
Set up the Error branch before launch. When a Lambda call times out or the function throws an exception, the contact follows that branch, so give it a message and a fallback queue to keep a slow lookup from stranding the caller.
-
Run test cases before a flow takes live calls. AWS's simulations send DTMF and text inputs, so a dialed test covers the part they skip.
-
Check the DTMF inputs. If a Lex bot takes digits for account numbers, send those inputs through IVR and DTMF testing too.
These three mistakes follow from AWS's docs and notices:
-
Planning around discontinued features. Voice ID is no longer supported, so a plan that includes it needs a replacement.
-
Treating the voice rate as the full cost. Telephony rates apply as well.
-
Mismatched languages on Lex V2. The language attribute in Connect must match the model behind your Lex bot.
Ready to Test Your Amazon Connect Flows?
Now that you know what Amazon Connect is and how it works, test the call itself before launch, because AWS’s native simulations cover flow logic and stop at 5 minutes.
Amazon Connect's native tests check flow logic. Cekura tests the call itself. It dials the number your Connect instance answers, plays a scripted caller with a defined personality, and scores each call.
Live calls also vary from run to run, so one passing test isn’t enough. On Cekura’s benchmarks, 8 voice agent configurations each ran 82 scenarios three times, and even the most reliable, Retell, passed all three runs on only 62 of them (75.6%).
Cekura organizes its testing in three areas:
-
Pre-production. Scripted callers send each scenario against your Connect number, and DTMF testing checks keypad menus.
-
Infrastructure. Cekura scores each call on latency in milliseconds and counts interruptions in both directions with the AI Interrupting User and User Interrupting AI metrics.
-
Observability. Send each completed call's transcript and recording to Cekura's observability API, and the metrics you set for that agent are evaluated in the background.
Native integrations work out of the box for Retell, VAPI, ElevenLabs, LiveKit, Pipecat, Bland, and more.
Amazon Connect isn't on that list. Cekura reaches it through the phone number your instance answers, so you add testing on top of what you already run.
Forwarding call recordings to a third party means customer data leaves your account, so the security details matter.
Cekura is SOC 2-, HIPAA-, and GDPR-compliant for transcript redaction, role-based access, and audit trails. Its docs describe role-based access with a read-only Viewer role, and sensitive data is redacted before storage.
Book a demo to see how Cekura tests your Amazon Connect setup before launch.
Frequently Asked Questions
What Is Amazon Connect?
It's AWS's usage-billed cloud contact center for voice and digital channels. AWS now sells the product as Amazon Connect Customer, and "Amazon Connect" names a portfolio of four agentic AI solutions.
Is Amazon Connect the Same as AWS?
No. AWS is Amazon's cloud platform, and Amazon Connect is one contact center service that runs on it. AWS Direct Connect, a network link to AWS, is a different service with a similar name.
How Much Does Amazon Connect Cost?
Voice costs $0.038 per voice min (standard telephony rates apply), chat $0.010 per message, SMS and 3P messaging $0.014 per message, and email $0.080 per email. Billing is usage-only, and the pricing page shows no minimums, contracts, or seat licensing.
Who Uses Amazon Connect?
Toyota, American Airlines, TUI, and Cochlear appear in AWS’s customer stories, and State Farm and Air Canada use the original product, per Amazon’s April 28, 2026 announcement.
What Is the Best Tool to Test Amazon Connect Flows and Calls?
For the call itself, I'd pick Cekura. It dials your Connect number and scores each call on latency, interruptions, and expected outcome. Use Amazon Connect's native testing for flow logic and Amazon Lex's Test Workbench for bot performance.