Integrations
Ada adds role-based access for Amazon Connect chat handoffs
Vendor-reportedChecked: [release]
Editorial attribution: Gosia Madej
Prepared with AI assistance. Editorial attribution does not imply personal product testing or manual review of every story.
Published: · Event date:
What changes for users
Support teams should treat authentication and handoff visibility as separate acceptance checks. After configuring queue forwarding, send a test chat through a handoff and verify the queue ID and entry timestamp in Ada’s conversation variables before relying on those fields in reports.
Editorial assessmentChecked: [guide]

Ada’s October 7 update lets its Amazon Connect handoff assume an IAM role secured with an External ID. Ada recommends this path for new setups; existing IAM-user integrations continue to work.
Vendor-reportedChecked: [release]
The setup guide still requires an SNS topic for chat messages and Ada’s team to finish backend configuration. Queue metadata needs an additional EventBridge rule that forwards CHAT events of type QUEUED to that topic. Without it, handoffs work but queue fields stay empty.
Vendor-reportedChecked: [guide]
Checked against sources
AI-assisted source check
How this was checked
Source evidence
Original source excerpt. This shows what the source says; it does not establish product performance.
Without it, the handoff works normally and the queue fields are left empty.
Sources
- [release] Ada: Amazon Connect handoff supports IAM role accessVendor-reportedPublished: 7 October 2026 · Checked: 9 October 2026
- [guide] Ada: Initial Amazon Connect configurationVendor-reportedSource publication date not stated · Checked: 9 October 2026