diff --git a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/index.md b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/index.md
index f587027e40..9ded65bd80 100644
--- a/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/index.md
+++ b/src/connections/sources/catalog/libraries/mobile/kotlin-android/destination-plugins/index.md
@@ -85,6 +85,10 @@ plugins:
 
 Analytics Kotlin uses its timeline/plugin architecture to support sending data to bundled SDKs when a Cloud Mode connection is not possible. Destination Plugins are similar to traditional Device Mode integrations available in Analytics Android in that Segment makes calls directly to the destination tool’s API from the device. However, Destination Plugins are more customizable, giving you the ability to control and enrich your data at a much more granular level on the device itself. 
 
+> info "Choosing the right destination"
+> Segment built device mode destination [plugins](https://segment.com/docs/connections/sources/catalog/libraries/mobile/kotlin-android/kotlin-android-plugin-architecture/){:target='_blank’} to be used with the classic/legacy destinations, not Actions destinations. The exception to this is the Amplitude plugin. The Amplitude plugin is a session plugin meant to be used with Amplitude Actions. If a classic/legacy destinations is in maintenance mode, Segment continues to make updates pertaining to the mobile plugins, but not the server or web components.
+> If you run into any issues setting up your destination, reach out to support.
+
 ## Device-mode Vs. Cloud-Mode 
 Analytics Kotlin allows you to choose how you send data to Segment and your connected destinations from your app. There are two ways to send data: