For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Login
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
HomeDocsAPI ReferenceMCP ServerChat SDKsRelease Notes
Login
LogoLogo

Release notes

Welcome to Ada’s release notes. Scroll down to see a list of recent releases, or subscribe to get notified about updates.

Subscribe via email

Receive a weekly email summary of releases every Friday at 11 a.m. Eastern, provided there has been at least one release that week.

Subscribe via RSS

Copy the following URL into your RSS reader to get notified about new releases:

https://docs.ada.cx/release-notes.rss
March 24, 2026
March 24, 2026
Was this page helpful?
Previous

Connect Zendesk with Global OAuth

Next
Built with

Amazon Connect Voice integration improvements

The Amazon Connect voice integration now supports two new capabilities:

  • Pass metadata from Amazon Connect to Ada — The Ada-Get-Call-ID Lambda can now be used to send metadata from Amazon Connect to Ada at the beginning of a conversation. Values sent will be available in Ada as purple metavariables.

  • More clearly identify if a call should continue in Amazon Connect — The Ada-Get-Transfer-Data Lambda response now includes a should_continue field. If the value of this field is true, that means that Ada escalated the call to a human agent and the call should continue in Amazon Connect. If the value of this field is false, that means that either Ada or the end user ended the call without escalation and the call should be ended in Amazon Connect.

Both changes are backwards compatible. Existing Lambda implementations using GET requests continue to work without modification.

To learn more, see Integrate Voice with Amazon Connect.