Skip to main content
Known Participant
March 25, 2026
4. Future Consideration

Enable Conversation ID Mapping for Agent Studio Use Cases

Related products:Agent Studio
  • March 25, 2026
  • 5 replies
  • 234 views

I propose introducing a mechanism to pass the conversation ID to use cases created via Agent Studio. Since most ticket operations in our organization—such as ticket creation and notifications—are planned to be customized using Agent Studio, having the conversation ID available within these use cases would allow accurate mapping between bot interactions and downstream ticket actions. This would significantly improve tracking, reporting, and deflection analytics.

5 replies

Community Manager
March 26, 2026
Updated idea status 1. New4. Future Consideration
Ajay Merchia
Community Manager
March 26, 2026

Hi Kavi,

This is a good idea – I can see how it would be useful for your organization. We will take it under consideration for our future roadmap. Thanks for sharing.

JacekU
New Participant
June 18, 2026

This is a great idea, and I really believe this should be introduced. This could significantly improve investigations in terms of speed and accuracy saving time and improving documentation.

Jacek Uhryn
KaviAuthor
Known Participant
July 15, 2026

Hi ​@Ajay Merchia : Do we have this considered in the roadmap? 

KaviAuthor
Known Participant
August 21, 2026

Hi ​@Ajay Merchia :

This is becoming increasingly important as we aim to track end-to-end deflection. For example, we collect explicit user feedback during plugin execution, but the feedback is stored separately from the Plugins table. Since there is no unique key to link the two, we currently rely on a combination of user_email, plugin_name, and creation timestamp, which is a fragile workaround.

Could you share your thoughts on introducing a unique identifier conversation ID to be passed ?