public sealed class ConversationSuccess : IMessage<ResponseMessage.Types.ConversationSuccess>, IEquatable<ResponseMessage.Types.ConversationSuccess>, IDeepCloneable<ResponseMessage.Types.ConversationSuccess>, IBufferMessage, IMessage
Indicates that the conversation succeeded, i.e., the bot handled the issue
that the customer talked to it about.
Dialogflow only uses this to determine which conversations should be
counted as successful and doesn't process the metadata in this message in
any way. Note that Dialogflow also considers conversations that get to the
conversation end page as successful even if they don't return
[ConversationSuccess][google.cloud.dialogflow.cx.v3.ResponseMessage.ConversationSuccess].
You may set this, for example:
In the [entry_fulfillment][google.cloud.dialogflow.cx.v3.Page.entry_fulfillment] of a [Page][google.cloud.dialogflow.cx.v3.Page] if
entering the page indicates that the conversation succeeded.
In a webhook response when you determine that you handled the customer
issue.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-07 UTC."],[[["\u003cp\u003eThe provided content outlines the different versions of \u003ccode\u003eConversationSuccess\u003c/code\u003e within the \u003ccode\u003eGoogle.Cloud.Dialogflow.Cx.V3\u003c/code\u003e library, ranging from the latest version 2.23.0 down to 1.0.0.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eConversationSuccess\u003c/code\u003e is a class that indicates a successful conversation, signifying the bot has addressed the customer's issue within the Dialogflow system.\u003c/p\u003e\n"],["\u003cp\u003eDialogflow uses \u003ccode\u003eConversationSuccess\u003c/code\u003e to track successful interactions, but it does not process the message's metadata, and reaching the conversation end page can also be considered successful.\u003c/p\u003e\n"],["\u003cp\u003eThe class \u003ccode\u003eConversationSuccess\u003c/code\u003e can be set in a page's \u003ccode\u003eentry_fulfillment\u003c/code\u003e or in a webhook response when a customer issue is resolved, and it implements interfaces like \u003ccode\u003eIMessage\u003c/code\u003e, \u003ccode\u003eIEquatable\u003c/code\u003e, \u003ccode\u003eIDeepCloneable\u003c/code\u003e, and \u003ccode\u003eIBufferMessage\u003c/code\u003e.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eConversationSuccess\u003c/code\u003e class includes a \u003ccode\u003eMetadata\u003c/code\u003e property, allowing for custom metadata to be added without any structure imposed by Dialogflow.\u003c/p\u003e\n"]]],[],null,[]]
