Send a human reply
POST /api/conversations/{id}/reply
Sends a reply to a conversation on behalf of a human agent. This bypasses the AI pipeline entirely — the message is delivered directly to the customer via the conversation’s channel (email, WhatsApp, etc.). The conversation must be in ‘human_managed’ status (use the take-over endpoint first). The reply is delivered via a Temporal workflow signal, so delivery is guaranteed even under transient failures.
Authorizations
Section titled “Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The unique identifier of the conversation to reply to.
Request Body
Section titled “Request Body ”object
The reply message text to send to the customer.
Example
Hi Jan, your order #4521 is currently in transit and should arrive by March 27. Here is your tracking link: https://tracking.dhl.de/1Z999AA10123456784Responses
Section titled “ Responses ”The reply was accepted and will be delivered to the customer.
Simple success acknowledgment returned by action endpoints (reply, resolve, take-over, etc.).
object
Always true on success.
Example
trueThe request body is invalid (e.g., empty content).
Standard error response returned by all endpoints on failure.
object
A human-readable error message describing what went wrong.
Example
Conversation not foundNo conversation exists with the given ID in the authenticated tenant.
Standard error response returned by all endpoints on failure.
object
A human-readable error message describing what went wrong.
Example
Conversation not found