> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getnexor.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Send a message in a test conversation

> Send the simulated lead's next message in a test conversation and get the agent's answer, with the tools it called and the lead's stage.

Continues a test conversation you started by API or in Playground. You send what the lead writes next, and you get the agent's answer for that turn.

## Before you start

* It runs on the channel you chose when you started the conversation.
* Same rules as starting a conversation: secret API key only, `workflows:write` on MCP keys, always simulated.
* Send one message at a time. While a turn is running, another message to the same conversation returns `turn_in_progress`. Wait for the answer, then send the next one.
* If the agent refuses the turn on purpose, for example because the lead was escalated to a person or the AI is off for it, you get 409 `turn_refused` with the cause in `reason`, such as `lead_in_support`, `human_takeover`, or `ai_not_enabled`. Sending the same message again gets the same answer. A real failure returns `turn_failed` instead.
* Only test conversations of your account are accepted. A real lead, or a conversation from another account, returns `conversation_not_found`.

## What you send

| Field | Detail |
| - | - |
| `conversation_id` | In the path. The ID you got when you started the conversation. |
| `message` | What the simulated lead writes. Up to 4000 characters. |

## What you get back

The same fields as when you start a conversation: `conversation_id`, `channel`, `reply`, `messages`, `tool_calls`, `status`, and `no_reply_reason` when the agent stayed silent on purpose.

## Read a turn in detail

With the Nexor MCP, pass `conversation_id` as the lead ID to `list_lead_turns` and `get_lead_turn` to see the full reasoning of a turn.

## Limits

* 30 turns per minute per API key, shared with starting conversations.
* A turn that takes more than 90 seconds returns `turn_failed` with reason `timeout`.


## API Specification

The full API specification for this endpoint is available in the [documentation index](https://docs.getnexor.ai/llms.txt).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.