What changed
AWS extended persistent chat to Amazon Connect Customer Global Resiliency. An end user who starts a chat in one linked Region, such as N. Virginia, can later continue it in the paired Region, such as Oregon, with the full transcript, contact metadata and chat attachments carried over for the agent. Adopting it requires onboarding to Global routing.
Vendor documentation (opens in a new tab)Why it matters
Without it, a Region switch or cross-Region routing breaks long-running chat threads and forces customers to start again. Continuity now depends on Global routing being in place, so chat should be part of failover design and testing alongside voice.
CxCave practical context
Who should care
- Cloud architects
- Administrators
- Business continuity teams
Implementation considerations
REVIEWIf you run Global Resiliency with persistent chat, confirm Global routing onboarding and add a cross-Region chat-resumption test to your next failover exercise.
CxCave recommendation, not a vendor mandate unless explicitly stated.