Skip to main content
A long row of telephone operators in headsets plugging cords into a Bell System international switchboard labelled London, Paris and Bermuda

Amazon Connect consulting: Every call,routed right.

Amazon Connect consulting: voice, chat, email, Cases, Contact Lens and Q in Connect, designed and hardened in your own AWS account. A focused pilot often lands in 4 to 8 weeks.

Talk to an AWS Connect Expert

What a Connect build takes

  • 4–8weeks for a focused pilot: one channel, core flows, basic Cases
  • 8–16weeks for a multi-channel cutover with CRM and compliance
  • From $699a month for EngageX, the AI desk on Connect
  • 10AWS Regions where Amazon Connect Cases runs

How long is your contact-center build?

A pilot is one channel, core flows, agent profiles and basic Cases. Switch on what your launch needs.

Build timelineMulti-channel build

8–16 weeks

1 of 5 items sit outside pilot scope.

  1. CRM integrationcustomer context in the flow at connect time

Where you land inside the band depends on the number of queues and integrations. Discovery in week 1 fixes the plan.

Book a Connect assessment
Four telephone operators in white coats and headsets seated at a tall exchange switchboard with rows of jacks and dials

The agent sees the customer before saying hello

The flow looks the caller up in your CRM, Q in Connect suggests the answer from your approved knowledge, and the contact lands in Cases, Customer Profiles and Contact Lens.

  • Cases
  • Customer Profiles
  • Contact Lens
Customer Profiles
Source integrations from CRM and order systems, matching rules, and which fields flows and agents may read.
Contact Lens
Real-time supervisor alerts, category rules, redaction scope and links into evaluation forms.
Q in Connect
Knowledge base content and refresh cadence, which recommendations agents see, quality gates before launch.

Connect alone, hybrid, or stay where you are

If Genesys, Five9 or a CRM-native telephony stack is the better fit, we say so in the first week, before you migrate.

Current contact center
A legacy PBX to replace, or a second CCaaS bill to shrink
Phone features
Covered by Connect, checked against the current AWS feature matrix
AWS ownership
An owner for IAM, networking and logging
Current contact center
Deep investment in another CCaaS, with custom routing you cannot rewrite this quarter
Phone features
Complex premise PBX features Connect does not cover
AWS ownership
No AWS owner yet: Connect would become another shadow platform

Six building blocks, configured for your SLAs

Connect sits in your AWS account with IAM, CloudWatch and EventBridge, so every block shows up in the same controls and the same bill as the rest of your stack.

Building blockWhat we configure
ChannelsVoice, chat, email, and tasks with queues and hours of operation matched to SLAs
Contact flowsIVR/chat trees, modules, Lambda integrations, CRM lookups at connect time
Agent workspace / CCPAgent experience, security profiles, supervisor vs agent separation
CasesTemplates, fields, and assignments for multi-contact issues, plus merge and link as of November 12, 2026 (see below)
Contact LensConversation analytics and quality workflows where they pay for themselves
Q in ConnectReal-time agent assist grounded in your approved knowledge

Discovery, design, build, harden

A row of male telephone operators in shirtsleeves and bow ties at the New York police headquarters switchboard in 1909, an officer standing beside them
Discovery, week 1
Channels, volumes, CRM systems, compliance scope and Region choice; Cases needs one of 10 Regions.
Design
Queue taxonomy, flow map, security profiles, Cases templates and recording policy.
Build
Flows, integrations, agent workspace and Cases, with Contact Lens and Q in Connect if scoped.
Harden
Least privilege, export governance, test plans, runbooks and cutover, with every number on a flow alias.

Related contact-center work

The full Amazon Connect guide

What is Amazon Connect?

Amazon Connect is AWS’s cloud contact center. You own the instance in your account, pay for usage, and wire identity, networking, and analytics to the same AWS controls you already use for the rest of the stack.

FactualMinds designs and hardens Connect for mid-market and high-growth teams that want contact-center ops on AWS, without accepting a second opaque CCaaS platform they cannot attribute in Cost Explorer.

Core building blocks

Building blockWhat we configure
ChannelsVoice, chat, email, and tasks with queues and hours of operation matched to SLAs
Contact flowsIVR/chat trees, modules, Lambda integrations, CRM lookups at connect time
Agent workspace / CCPAgent experience, security profiles, supervisor vs agent separation
CasesTemplates, fields, and assignments for multi-contact issues, plus merge and link as of November 12, 2026 (see below)
Contact LensConversation analytics and quality workflows where they pay for themselves
Q in ConnectReal-time agent assist grounded in your approved knowledge

Related GenAI context: Generative AI on AWS covers Q in Connect as part of the broader Amazon Q family.

AWS documentation now names the service Amazon Connect Customer (formerly Amazon Connect) in many places. The console, APIs, and pricing are the same service.

Customer Profiles, Contact Lens, and Q in Connect

CapabilityWhat it doesWhat we design
Customer ProfilesUnified customer profile at contact time, with Identity Resolution that matches and merges duplicatesSource integrations (CRM, order system), matching rules, which fields flows and agents may read
Contact LensReal-time and post-contact analytics: transcripts, sentiment, categories, summaries, redactionReal-time supervisor alerts, category rules, redaction scope, links into evaluation forms
Amazon Q in ConnectGenerative AI agent assistance on voice and chat: recommended responses, actions, and knowledge linksKnowledge base content and refresh cadence, which recommendations agents see, quality gates before launch

We treat Q in Connect recommendations as a support tool for the agent, not an answer the agent must read out. The knowledge base is the product. If it is stale, the recommendations are stale.

Digital channels: WhatsApp and SMS

Connect takes WhatsApp and SMS through AWS End User Messaging:

  • WhatsApp: link the WhatsApp Business Account with AWS End User Messaging Social, import the number into Connect, route it with an inbound flow. Supports text, interactive messages, rich link previews, delivered and read receipts, and attachments. See WhatsApp Business API on AWS.
  • SMS: a number from AWS End User Messaging SMS with two-way SMS enabled and Connect as the destination.

For branded RCS outbound updates outside the contact center, see RCS Business Messaging on AWS.

For choosing a channel per job (OTP, order status, promotion, receipt), start with AWS Communication Developer Services.

Voice ID end of support

AWS ended support for Connect Voice ID on May 20, 2026. If your flows still reference Voice ID blocks, caller authentication needs a new path. AWS lists AWS Partner solutions on AWS Marketplace (such as Pindrop) or a do-it-yourself one-time passcode over AWS End User Messaging SMS. We map the replacement into your flows and test the fallback when authentication fails. Inventory script, replacement options and a data-deletion checklist: Voice ID end of support: what to migrate to.

Who Amazon Connect is for

  • Retail and eCommerce support orgs scaling peak chat/voice without permanent agent overhire (see AWS for retail)
  • Healthcare and regulated teams that need recording, retention, and profile controls under a BAA (see HIPAA architecture)
  • SaaS product support that wants Cases tied to customer identity already in AWS
  • Ops leaders replacing legacy PBX or shrinking a second CCaaS bill

Implementation shape

  1. Discovery (week 1): channels, volumes, CRM systems, compliance scope, Region choice (Cases needs one of 10 supported Regions; the October 9 evaluation-form check needs one of 8).
  2. Design: queue taxonomy, flow map, security profiles, Cases templates, recording policy.
  3. Build: flows, integrations, agent workspace, Cases, optional Contact Lens / Q in Connect.
  4. Harden: least privilege, export governance, test plans, runbooks, cutover. Production numbers and queues point at a flow alias; each release is a new version, tested before the alias moves.

Typical pilot: 4 to 8 weeks. Multi-channel plus compliance: 8 to 16 weeks.

Amazon Connect Cases

Cases track work that outlives a single phone call or chat, such as warranties, claims, and escalations. Agents create and update cases in the agent workspace alongside the contact.

CSV export (August 4, 2026)

AWS shipped CSV export from the agent workspace: filter and select cases, choose columns, download Cases-export-YYYY-MM-DD.csv. Access requires the Cases - Export (Cases.Export) security profile permission.

We recommend default deny on Export, an approved column allowlist for vendor/legal shares, and API/analytics for recurring reports. Field guide: Connect Cases CSV export (Aug 2026). Enablement checklist: cases-csv-export-checklist.md.

Performance evaluations

Managers score human agents and self-service contacts on evaluation forms. Start from a template for customer service, inbound sales, or self-service, then customize. Contact categories, generative AI, and metrics can fill answers.

Templates (November 9, 2026)

On November 9, 2026, evaluation form templates shipped in the same 8 Regions as Save and validate. Each template scores human and AI-agent behavior, including questions such as whether the agent showed empathy, and includes outcome questions for customer satisfaction and attrition risk. Use a template as-is or customize it. Templates do not skip the October 9 checks.

Automated checks (October 9, 2026)

On October 9, 2026, Save and validate checks a form before activation in 8 Regions. Structural errors block activation. Gen AI warnings do not. The Gen AI stage allows 3 validations in parallel and 30 per hour per instance. Clear warnings before you activate. Field guide: Connect evaluation checks (Oct 2026). Checklist: evaluation-form-validation-checklist.md.

October 2026 updates

Five Connect Customer launches between October 26 and October 30, 2026. None lists a price.

LaunchWhat it doesRegions
Flow versions and aliases (Oct 30)Immutable, numbered flow versions. An alias points at one version; phone numbers, queues, and quick connects can reference the alias, so moving it moves every linked resourceAll Connect Customer Regions
Flow action validation (Oct 26)Testing and simulation checks the data an action returns: a Lambda response, a resolved Amazon Lex intent, or variables set by an Agentic CX blockPer the Region list
Metric segments (Oct 26)Metrics broken down by customer lifetime value and repeat-caller statusRegions with Customer Profiles
Attachment previews (Oct 27)PDFs, images, and text files open inline on email, chat, and cases. .svg and .html never preview. Download stays available10
Email draft auto-save (Oct 30)Drafts save every few seconds with body, recipients, subject, and attachment references, and come back after a dropped connection or closed browser9 (the 10 above minus Cape Town)

What this changes in our builds:

  • Flows. Every production phone number and queue points at an alias. A release is a new version; the test asserts what each Lambda and Lex action returns; then the alias moves. Rollback is moving it back.
  • Attachments. Preview needs attachments enabled on the instance. With attachment scanning on, a file previews only after scanning approves it. Preview keeps most files off agent laptops, but agents can still download, so it does not replace download controls.
  • Email drafts. Draft content is stored in the S3 bucket tied to your instance and deleted when the agent sends or discards it, or when the draft contact expires (14 days by default). Include that bucket in your encryption and retention scope.
  • Custom agent UIs. Draft auto-save and attachment preview work in the agent workspace (and drafts in the CCP). Neither works in a custom app built on the Streams API. See Connect agent UI options.

Outcome metrics and segments sit next to evaluation forms; the evaluation checks guide covers how to read them together.

November 3, 2026 updates

Two Connect Customer launches on November 3, 2026. Neither lists a price.

LaunchWhat it doesRegions
Email pause and resume (Nov 3)Agents pause from the workspace or CCP. The handling timer stops, Send is blocked, and the draft stays. Paused time is separate from active handling time. A flow can resume or transfer an email that stays paused. Cap is 10 pauses. A paused email still counts toward the active email contact limit10, including Cape Town. Not GovCloud or China
Email address on a new case thread (Nov 3)Starting a new email from a case fills the address from the linked customer profileThe 10 Cases Regions

What this changes in our builds:

  • Email concurrency. Size the email contact limit for emails sitting on an approval. A paused email still occupies an active email slot.
  • Pause ceiling. Put resume-or-transfer on Flow at contact pause. A paused email has no maximum duration, and the 11th pause is rejected.
  • Case email. The filled address is only as good as the linked profile. The November 3 post does not say which address is used when a profile has several, or what the composer shows when it has none. Check that on a sandbox profile before training. Field notes: Connect agent UI options and Connect Cases CSV export.

November 12, 2026 updates

One Connect Cases launch on November 12, 2026. It lists no price.

LaunchWhat it doesRegions
Merge and link cases (Nov 12)Agents merge related cases, such as the chat and email a customer opened about one delayed shipment, into one case with one history. They can also link related cases, including cases from different customers affected by the same issue, so the response stays consistentThe 10 Cases Regions

What this changes in our builds:

  • Merge. Use merge when it is the same customer and the same issue split across contacts or channels. The announcement’s example is a chat case and an email case about one delayed shipment.
  • Link. Use link when several customers share one incident and each still needs their own case. Linking coordinates one response. It is not a merge.
  • Sandbox first. The November 12 post does not name a security profile permission, an API, or whether the source case is closed or deleted after a merge. Confirm those on a sandbox before you train agents. Field notes: Connect Cases CSV export.

November 17, 2026: case and calculated template variables

On November 17, 2026, Connect Customer message templates can insert Cases fields, including custom fields an administrator defines, and Customer Profiles calculated attributes such as a customer’s most frequent contact channel. Connect fills the current value for each recipient when the message sends. Developers can pass the same values through RenderMessageTemplate. There is no extra price in the notice.

Regions: US East (N. Virginia), US West (Oregon), Africa (Cape Town), Asia Pacific (Seoul, Singapore, Sydney, Tokyo), Canada (Central), and Europe (Frankfurt, London).

Use one template for a claim-status email that pulls the case reference and status, or a loyalty email that pulls a calculated order count. Do not put a value in the template that the profile or case does not already store. A calculated attribute is only as current as the profile pipeline behind it.

When not to choose Connect alone

  • Deep investment in another CCaaS with custom routing you cannot rewrite this quarter
  • Requirements Connect does not meet (confirm against current AWS feature matrix before committing)
  • No AWS owner for IAM, networking, and logging (Connect without account hygiene becomes another shadow platform)

We will say “stay” or “hybrid” when that is the lower-risk path.

Commerce, ERP and industry guides

Connect is only as useful as the context the agent sees. These guides cover the integration work behind that context:

Next step

Book a Connect assessment: channels, Cases needs, and compliance scope in one working session.

Contact us, start from the evaluation-form check guide if score quality is the immediate pain, or the Cases CSV export guide if export governance is.

Questions contact-center leaders ask

What is Amazon Connect?

Amazon Connect is AWS’s cloud contact center service. You run voice and digital channels, design contact flows, staff agents in the CCP or agent workspace, and optionally add Cases, Contact Lens analytics, and Amazon Q in Connect for real-time agent assistance, all inside your AWS account with pay-as-you-go pricing.

When should we NOT choose Amazon Connect alone?

Skip a Connect-only program if you already have a deeply customized CCaaS with low switching cost, need complex premise PBX features Connect does not cover, or lack AWS ownership for identity and networking. Hybrid or CRM-native telephony may fit better. We assess fit in the first week.

What are Amazon Connect Cases?

Cases track customer issues that span multiple contacts, such as warranties, claims, and escalations. Agents create and update cases in the agent workspace. As of August 4, 2026, agents with the Cases.Export permission can export selected cases to CSV with a column picker for offline share with legal or vendors. As of November 4, 2026, contact records include the case ID and reference number, visible on Contact Details and available from DescribeContact and contact event streams, so you can count contacts per case. That record does not replace the Cases API or the CSV export. As of November 12, 2026, agents can merge related cases into one case with a single history, for example a chat and an email about the same delayed shipment, and they can link related cases, including cases from different customers about the same issue. The November 12 announcement does not name a security profile permission, an API, or whether a merge closes or deletes the source case. Cases is available in 10 AWS Regions. The November 4 and November 12 announcements list no price.

Source: Cases on contact records (Nov 2026)

Source: Merge and link cases (Nov 12, 2026)

How long does a typical Connect implementation take?

A focused pilot (one channel, core IVR/chat flows, agent profiles, basic Cases) often lands in 4 to 8 weeks. Multi-channel cutovers with CRM integration, Contact Lens, Q in Connect, and compliance controls typically take 8 to 16 weeks depending on number of queues and integrations.

Can Connect meet HIPAA or PCI requirements?

Amazon Connect is on AWS HIPAA-eligible and PCI-relevant service lists when configured under a BAA and scoped architecture. Eligibility is not automatic. Recording storage, encryption, least-privilege profiles, and data retention must be designed. We align Connect with your compliance program rather than treating the service badge as sufficient.

How does Q in Connect differ from a general chatbot?

Q in Connect assists live agents with recommended responses and knowledge during contacts. It is not a customer-facing chatbot replacement by itself. Customer self-service still needs Lex/flows or your digital channel design. We scope agent assist separately from deflection bots.

What could go wrong in a Connect rollout?

Common failures include over-granting security profiles (including Cases.Export to all agents), recording retention with no legal hold policy, flows that hardcode phone trees without Lambda/CRM context, flow edits published straight to live numbers with no version to roll back to, and launching Q in Connect without knowledge-base quality gates. We put least privilege and flow test plans in the critical path before go-live.

How do we roll back a Connect flow change?

Since October 30, 2026, Connect Customer supports flow versions and aliases. A version is an immutable snapshot with a sequential number. An alias points at one version, and queues, quick connects, phone numbers, task templates, email, outbound campaigns, views, and rules can reference the alias. To release, publish a new version, test it, and repoint the alias. To roll back, repoint the alias to the previous version. Every resource on that alias follows in one update. A resource that references the flow with no alias or version gets the latest published content.

Source: Flow versioning and aliasing

What happened to Amazon Connect Voice ID?

AWS ended support for Voice ID on May 20, 2026. It stopped accepting new customers on May 20, 2025, and after May 20, 2026 the Voice ID console, agent features, and resources are no longer available. AWS points to alternatives such as AWS Partner solutions on AWS Marketplace (for example Pindrop) or a do-it-yourself one-time-passcode check with AWS End User Messaging SMS. We help teams move caller authentication to one of those paths.

Source: Voice ID end of support

What do Customer Profiles add to Amazon Connect?

Customer Profiles gives agents and flows a unified profile at contact time, built from your CRM, ecommerce, and other sources. Identity Resolution detects similar profiles (by name, email, phone, date of birth, and address) with rule-based and ML matching, and can merge them under consolidation rules. Flows read the profile through the Customer Profiles block.

Source: Enable Identity Resolution for Customer Profiles

Does Contact Lens work in real time?

Yes. Contact Lens provides both real-time and post-contact analytics: transcription, sentiment, issue detection, automatic contact categories, summaries, and sensitive data redaction. Real-time rules can alert supervisors during a live contact. Post-contact analytics feed search, categories, and evaluation forms.

Source: Amazon Connect Contact Lens API

Can customers reach our Connect agents on WhatsApp or SMS?

Yes. For WhatsApp, you link a WhatsApp Business Account and number with AWS End User Messaging Social and import the number into your Connect instance. For SMS, you get a number from AWS End User Messaging SMS, enable two-way SMS with Connect as the destination, and import it. Both channels then route through contact flows like chat.

Source: Set up WhatsApp Business messaging

Source: Set up SMS messaging

Can we keep a third-party dialer or add-on such as Acqueon?

Often, yes. Third-party products integrate with Connect through flows, Lambda, and the Connect APIs, and the right answer depends on the product and your contract. Before keeping or adding an outbound dialer, we compare it with native Amazon Connect outbound campaigns. FactualMinds has no partnership with Acqueon; we assess fit on the merits.

Source: Set up outbound campaigns

Can agents pause an email in Amazon Connect?

As of November 3, 2026, yes, from the agent workspace or the Contact Control Panel. The handling timer for that email stops, Send is blocked, and an in-progress draft is kept. Paused time is tracked separately from active handling time. The same email can be paused 10 times, and a paused email still counts toward the active email contact limit. There is no maximum pause duration. A flow on Flow at contact pause can resume or transfer it. Available in 10 Regions, including Cape Town, and not in AWS GovCloud (US) or the China Regions. The announcement lists no price. The same day, starting a new email thread from a case fills the address from the linked customer profile, in the 10 Cases Regions.

Source: Pause and resume emails

Source: Email address on a new case thread

Further reading

Also looking at AI agents for support or operations? See where production agents fit.

Ask AI:ChatGPTClaudePerplexityGemini

Ready to Design Your Contact Center on AWS?

Tell us about channels, agent count, Cases needs, and compliance scope, and we will map a Connect assessment in 30 minutes.

Photographs, public domain, via Wikimedia Commons: Bell System switchboard (U.S. National Archives); telephone exchange, Jerusalem (Matson Collection) and New York police switchboard, 1909 (Bain Collection), Library of Congress. Cropped; hero darkened.