organization_support_thread_reply

Tool

organization_support_thread_reply

Reply in any support thread of the caller's organization, as the caller.

Reply in any support thread of the caller's organization, as the caller. A thread of another organization is reported as not found. Attach screenshots or logs by passing them in `attachments` as base64 — up to 10 files, each up to 25 MiB decoded; they travel in this same call and need no upload step of their own. If any file is refused the reply is not posted at all, and the error names the file and what went wrong with it. A reply of files and no text is legal — omit `body` entirely.

Behavior

HTTP: POST /governance/api/v1/support/threads/:id/messages

Arguments

Name	Type	Required	Description
id	string	•	Thread uuid to reply in.
body	string	—	The reply text, 1-50000 characters. May be OMITTED only on a message that carries at least one attachment — a reply of files alone is a reply. Omit the field entirely; an empty string is refused.
attachments	array	—	Files to attach, base64-encoded. Up to 10 per message, each up to 26214400 bytes (25 MiB) decoded, and at most 26214400 bytes decoded across all of them in one call. Screenshots and logs are the intended use; the whole call travels as one request.

Response

Field	Type	Always	Description
id	string	•	Thread uuid.
title	string	•	Subject of the request, e.g. "Billing export fails".
legacy	boolean	•	True for a PERSONAL thread opened before support became organization-owned. Such threads stay visible to their own author alone and cannot be migrated.
status	string	•	The status NAME the product chose, e.g. "In progress" — display text, not an id.
category	string	•	The lifecycle bucket behind that status.
messages	array	•	The whole conversation, oldest message first.
createdAt	string	•	When the thread was opened, ISO 8601 UTC.
openedByName	string	•	Name of the colleague who opened the thread. Never null — an unresolvable opener falls back to a placeholder.
lastMessageAt	string	•	When the thread last moved, ISO 8601 UTC. A thread with no replies reports its own creation.
lastMessagePreview	string	•	First 140 characters of the last message, or null when the thread has none.

Try it

Reply in any support thread of the caller's organization, as the caller.

When to use

Example

Ask your agent something like this:

Reply in any support thread of the caller's organization, as the caller.

The agent will invoke organization_support_thread_reply with these arguments:

{
  "id": "<id>"
}