Resolve a conversation
POST /api/conversations/{id}/resolve
Marks a conversation as resolved, ending the active conversation lifecycle. This sends a signal to the conversation’s Temporal workflow, which triggers post-resolution processing including the learning loop (which may propose new KB entries and policies based on the conversation). Optionally include an outcome description summarizing how the issue was resolved.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the conversation to resolve.
Request Body
Section titled “Request Body ”object
A short description of how the conversation was resolved. Stored on the conversation record for reporting and audit.
Example
Delivery timeline confirmed, customer satisfied.Responses
Section titled “ Responses ”The conversation was resolved successfully. Post-resolution workflows (learning loop, CSAT follow-up) have been triggered.
Simple success acknowledgment returned by action endpoints (reply, resolve, take-over, etc.).
object
Always true on success.
Example
trueThe conversation cannot be resolved in its current state (e.g., already resolved).
Standard error response returned by all endpoints on failure.
object
A human-readable error message describing what went wrong.
Example
Conversation not found