---
title: "Tell the agent working on a ticket"
url: https://docs.gleap.ai/en/reference/rest-api/tell-agent
method: POST
path: "/hard-tickets/tickets/{ticketId}/tell"
api: "API Reference"
tag: "HardTickets"
operationId: "TellAgent"
updatedAt: "2026-11-03T17:10:00.738Z"
language: en
---

# Tell the agent working on a ticket

`POST https://api.gleap.io/v3/hard-tickets/tickets/{ticketId}/tell`

"Tell Kai Support…": the teammate's words go to the agent working the ticket (its running session's next turn, or its run resumes), booked to the person. Never a reply to the customer and never a stop. The same path and guards as the old `POST /agents/ticket/{id}/input` with `mode: 'send'` (the ticket's board, Kai Copilot-only roles, files on our storage only, 409 when nobody works on it), which stays for the app's installed bundles for one release.

## Authorization

- `Authorization` (header, required): `Bearer <token>`

## Path parameters

- `ticketId` (string, required)

## Headers

- `project` (string, required)

## Request body (`application/json`, required)

- `attachments` (object[])
  - `type` (string)
  - `url` (string, required)
  - `name` (string)
- `text` (string, required)

## Example request

```bash
curl --request POST \
  --url 'https://api.gleap.io/v3/hard-tickets/tickets/{ticketId}/tell' \
  --header 'Authorization: Bearer <token>' \
  --header 'project: <project>' \
  --header 'Content-Type: application/json' \
  --data '{
  "text": "<text>"
}'
```

## Responses

### 200 (`application/json`)

Ok

- `ok` (enum<boolean>, required): One of: `true`.

```json
{
  "ok": true
}
```