Hello Moveworks community,
We've improved how ambient agent notifications are represented in the Data API.
What's changing
Ambient agents that deliver plain-text notifications will now be correctly categorized in the Data API /conversations entity as CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION, with use-case details (usecase_id, usecase_name) populated.
Previously, these plain-text notifications were not classified under this type and instead appeared as CONVERSATION_TYPE_UNSPECIFIED_SYS_EVENT without use-case details — making it difficult to identify and report on them.
What you'll notice
- An increase in CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION volume.
- A corresponding decrease in CONVERSATION_TYPE_UNSPECIFIED_SYS_EVENT for the same records.
- Populated use-case details for these notifications going forward.
Things to keep in mind
- Forward-looking only — this applies from the release date onward. Historical data cannot be backfilled.
- If you have filters built on CONVERSATION_TYPE_UNSPECIFIED_SYS_EVENT or that count CONVERSATION_TYPE_AMBIENT_AGENT_NOTIFICATION, you'll see a one-time shift on the release date (starting today) . This is the intended correction, not an anomaly.
- Plain-text notifications contain no interactive elements, so only "notifications sent" counts are available — there is no click/interaction tracking for these conversations.