All Services

Business Apps

Amazon Connect

Amazon Connect—whose legacy contact-center product is now documented as Amazon Connect Customer—provides managed omnichannel customer service across voice, chat, SMS, web calling or video, email and tasks, with flows, queues, routing, agent workspaces, analytics, recording and AI integrations.

Explore pricing models, common use cases, infrastructure support, and the AWS services that commonly work with Amazon Connect.

Amazon Connect pricing and cost programs

Pricing model: Contact-center channel and feature usage

On-Demand
Available
Reserved Instances or reserved capacity
Not applicable
Savings Plans
Not applicable
Spot
Not applicable

Billing dimensions: Voice minutes · Messages · Tasks · Profiles, analytics, and AI features

Programs and modes: Voice · Chat and messaging · Tasks · Contact Lens and Customer Profiles

Telephony rates, Regions, channels, and optional Connect features are priced separately.

Free Tier: Available — verify current offers

Pricing reviewed 2026-07-25. Reviewed against the linked official AWS pricing page. Recheck regional rates and program terms before purchase.

Official AWS pricing

Official AWS sources reviewed 2026-07-21.

Why implement Amazon Connect?

  • Replaces much contact-center telephony, routing and agent-desktop infrastructure with usage-based managed services.
  • Unifies voice, chat, SMS, web calling or video, email and tasks with queues, routing profiles, flows, agent workspaces, cases, campaigns and analytics.
  • Integrates Lex, Lambda, Contact Lens, EventBridge, streams, S3, KMS and workforce-management capabilities for automation and insight.

How to implement Amazon Connect

  1. Define countries and channels, phone-number porting, hours, service levels, queues, concurrency, agent locations and network quality, identity and MFA, roles, PCI or privacy scope, recording and transcript retention, encryption, fraud, emergency calling and recovery.
  2. Create the instance and storage, claim test numbers while porting, establish queues and routing profiles, build small reusable flows with explicit error and timeout branches, integrate only approved Lambda and bot actions, and create least-privilege security profiles.
  3. Pilot end-to-end customer and agent journeys, load and fail flows, verify recording consent and sensitive-data handling, train agents and supervisors, monitor real-time and historical metrics and CloudWatch logs, and rehearse telephony, dependency and Region disruption.

Amazon Connect best practices

  • Make flows small and modular with consistent attribute names, explicit default, timeout and error paths, version control and regression tests before publishing.
  • Restrict security profiles—especially user create or edit and administrator permissions—require MFA through the identity provider, protect participant bearer tokens, and never log tokens or put them in URLs.
  • Minimize contact attributes and recordings, encrypt and restrict S3 and KMS access, define legal retention and consent, avoid PII in Voice ID speaker identifiers, and monitor fraud, quality, quotas and downstream integrations.

Amazon Connect use cases and server impact

  • Customer service contact centers
  • Automated IVR, chatbots, and skills-based routing
  • Omnichannel sales, support, and case workflows

Replaces much PBX, IVR, call-routing, recording and agent-desktop infrastructure, while staffing, telephony policy, flow correctness, identity, privacy, compliance, fraud, integrations, training and business continuity remain yours.

Official implementation resources

Commonly paired AWS services