Migrating to Messaging
Overview
Move an existing integration to Messaging with your Ada team and developers. Record the transition date for each AI Agent.
Limitations
Messaging requires a generative AI Agent. Changing the integration package and enabling Messaging are separate parts of the transition.
A dashboard label does not prove that every installed mobile app or bundled package has been upgraded.
Capabilities & configuration
Identify how your current Chat integration loads before you choose a migration path.
Implementation & usage
Use the Messaging migration guides for the exact code changes.
To migrate an integration:
- Inventory the websites, apps, packages, and custom interfaces that connect to your AI Agent.
- Review the web migration guide or the mobile integration guides.
- Check the security requirements, including content security policy and custom app origins.
- Configure appearance, launch options, and persistence.
- Test anonymous users, identified users, account switching, and sign-out.
- Test human support, file handling, notifications, language selection, and surveys.
- Coordinate production enablement and rollback with your Ada team.
- Record the transition date and compare reporting differences.
Best practices
Validate Messaging on the actual host website or mobile app. Dashboard tests do not validate your site’s security policy or application lifecycle.
Review metadata limits and identity failures before production. An identity-token failure can continue the session anonymously.
Keep legacy installation details available while older applications remain in use. Confirm each integration separately before you retire its setup instructions.