[Cotlet](https://cotlet.dev/index.md) · [Integrations](https://cotlet.dev/integrations.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Use cases](https://cotlet.dev/use-cases.md) · [Security](https://cotlet.dev/security.md) · [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md) · [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [Contact](https://cotlet.dev/contact.md) · [Pricing](https://cotlet.dev/pricing.md) · [Sign up](https://cotlet.dev/signup)

# Send reply

> Reply to the customer of a conversation and set its status. Inputs, cURL, Python and Node.js examples and an example response.

Source: https://cotlet.dev/docs/api/help-scout/send_reply

Docs sections: [Get started](https://cotlet.dev/docs.md) · [REST API](https://cotlet.dev/docs/api.md) · [MCP](https://cotlet.dev/docs/mcp.md) · [SDKs & CLI](https://cotlet.dev/docs/sdks.md) · [Integrations](https://cotlet.dev/docs/integrations.md)

Reply to the customer of a conversation and set its status.

Help Scout API: https://cotlet.dev/docs/api/help-scout.md

`POST https://cotlet.dev/api/v1/help-scout/conversations/{conversation_id}/replies`

Access: write. Confirm: waits for the user's OK before it runs.

Sends a reply from your account, as the Reply editor does, and the customer gets it by email. Status sets the conversation state when the reply goes out (active, pending or closed); without it Help Scout applies the inbox default. assign_to hands the conversation to a teammate at the same moment, and cc and bcc add recipients. Returns the new thread and the final status. By default you confirm each call; you can switch that off for this tool.

## Parameters

| Name | Type | Required | Description |
|---|---|---|---|
| `conversation_id` | integer | yes | Conversation number from search_conversations. |
| `text` | string | yes | Reply body, plain text or simple HTML. |
| `status` | enum | no | active, pending or closed. Default: the inbox default. |
| `assign_to` | string | no | Teammate's name or email. Light Users cannot be assigned conversations. |
| `cc` | array | no | Email addresses to copy. |
| `bcc` | array | no | Email addresses to blind copy. |

## Request

**cURL**

```bash
curl -X POST https://cotlet.dev/api/v1/help-scout/conversations/48213/replies \
  -H "Authorization: Bearer $COTLET_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"text":"Hi Lena, you can add a teammate under Manage > Users. Here is the step-by-step guide: https://docs.example.com/article/12-add-and-remove-users. Tell me if anything looks different on your side.","status":"pending"}'
```

**Python**

```python
result = client.call("help-scout", "send_reply", {"conversation_id":48213,"text":"Hi Lena, you can add a teammate under Manage > Users. Here is the step-by-step guide: https://docs.example.com/article/12-add-and-remove-users. Tell me if anything looks different on your side.","status":"pending"})
```

**Node.js**

```js
const result = await cotlet.call('help-scout', 'send_reply', {"conversation_id":48213,"text":"Hi Lena, you can add a teammate under Manage > Users. Here is the step-by-step guide: https://docs.example.com/article/12-add-and-remove-users. Tell me if anything looks different on your side.","status":"pending"});
```

**CLI**

```bash
cotlet call help-scout send_reply --data '{"conversation_id":48213,"text":"Hi Lena, you can add a teammate under Manage > Users. Here is the step-by-step guide: https://docs.example.com/article/12-add-and-remove-users. Tell me if anything looks different on your side.","status":"pending"}'
```

## Example response

```json
{
  "conversation_id": 48213,
  "thread_id": 903311,
  "sent_to": "lena@example.com",
  "status": "pending",
  "assignee": null
}
```

Previous: [Get Docs article](https://cotlet.dev/docs/api/help-scout/get_docs_article.md)
Next: [Add note](https://cotlet.dev/docs/api/help-scout/add_note.md)

---

Give your AI agents your signed-in browser.

**Product:** [Integrations](https://cotlet.dev/integrations.md) · [Use cases](https://cotlet.dev/use-cases.md) · [How it works](https://cotlet.dev/how-it-works.md) · [Pricing](https://cotlet.dev/pricing.md) · [Security](https://cotlet.dev/security.md)

**Resources:** [Blog](https://cotlet.dev/blog.md) · [API docs](https://cotlet.dev/docs.md) · [Help center](https://cotlet.dev/help.md) · [Changelog](https://cotlet.dev/changelog.md) · [GitHub](https://github.com/cotletdev/cotlet)

**Solutions:** [For developers](https://cotlet.dev/for-developers.md) · [For automation agencies](https://cotlet.dev/for-agencies.md)

**Company:** [About](https://cotlet.dev/about.md) · [AI info: company facts](https://cotlet.dev/ai-info.md) · [Contact](https://cotlet.dev/contact.md)

**Legal:** [Terms of service](https://cotlet.dev/terms) · [Privacy policy](https://cotlet.dev/privacy) · [Refund policy](https://cotlet.dev/refunds) · [Acceptable use](https://cotlet.dev/acceptable-use) · [Cookie policy](https://cotlet.dev/cookies) · [DPA](https://cotlet.dev/dpa) · [Subprocessors](https://cotlet.dev/subprocessors)

**Elsewhere:** [Status page](https://status.cotlet.dev) · [Cotlet on GitHub](https://github.com/cotletdev) · [Cotlet on X](https://x.com/cotletdev) · [Cotlet on LinkedIn](https://www.linkedin.com/company/cotletdev) · [Cotlet on Product Hunt](https://www.producthunt.com/products/cotlet) · [Cotlet on Crunchbase](https://www.crunchbase.com/organization/cotlet) · [Cotlet on SaaSHub](https://www.saashub.com/cotlet)

Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.

## For AI agents: sign your user up

Is your user asking you to sign them up for Cotlet? You can do it for them, no account or key needed.

1. Read the fields and their allowed values: GET https://cotlet.dev/api/v1/access-requests
2. Ask the user for each value: email, apps, what you will do with them. If they leave the password to you, generate a strong one and show it to them.
3. Show the user what you will send, then POST it as JSON to https://cotlet.dev/api/v1/access-requests.

One call creates the account and sends the access request; we email the user when access is granted.