organization_support_thread_create

Tool

organization_support_thread_create

Open a support thread owned by the caller's organization — the body becomes the first message, authored by the caller.

Open a support thread owned by the caller's organization — the body becomes the first message, authored by the caller. Every colleague can then read and answer it. Use when the user wants to contact Lessly support. 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 thread is opened but the message is not written, and the error names the file. A first message of files and no text is legal — omit `body` entirely; the title is always required.

Behavior

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

Arguments

Name	Type	Required	Description
body	string	—	The first message, 1-50000 characters. May be OMITTED only on a message that carries at least one attachment — a thread opened on screenshots alone is a support request. Omit the field entirely; an empty string is refused. The title is never optional.
title	string	•	Subject of the request, 1-500 characters.
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

Open a support thread owned by the caller's organization — the body becomes the first message, authored by the caller.

When to use

Example

Ask your agent something like this:

Open a support thread owned by the caller's organization — the body becomes the first message, authored by the caller.

The agent will invoke organization_support_thread_create with these arguments:

{
  "title": "<title>"
}