Amazon Connect adds persistent chat across linked AWS Regions

AWS announced on October 23, 2026, that Amazon Connect Customer Global Resiliency supports persistent chat across linked AWS Regions. According to the announcement, returning users can resume previous conversations with context, metadata and transcripts carried across Regions, allowing agents to access the earlier conversation history.

What carries across Regions

AWS illustrates the capability with a customer who starts a chat in US East (N. Virginia), then returns to it in the linked US West (Oregon) Region. In that example, the agent has access to the full conversation history and a chat attachment.

For engineers, the useful distinction is between regional reachability and conversation continuity. A deployment test should establish not only that a customer can reach an agent, but also that the agent can retrieve the expected context from the earlier exchange.

Availability and adoption requirements

AWS says the feature is available in all Regions where Amazon Connect Customer Global Resiliency is supported—not across AWS Regions generally. Adoption requires onboarding to Global routing, according to the announcement.

The stated scope is persistent chat across linked Regions. Teams should confirm that their intended regional setup falls within that scope before planning adoption.

What engineers should validate

Test the returning-customer workflow separately from basic regional reachability: whether the intended conversation resumes, whether expected metadata and transcripts are available, and whether the agent can retrieve the attachment used in the test.

The announcement does not specify recovery timing or replication guarantees, nor does it establish that an active chat connection can move between Regions without interruption. Treat those as separate deployment questions rather than promises of this release. Include cross-Region transcript and attachment handling in the data-residency review.