# Support requests

> In short: A support request is one conversation between your workspace and Zynth about one problem. The record is built, but there is no form to open one yet. This page says what a request holds and how it moves from open to closed.

Applies to: v0.9 · Last reviewed: 2026-09-30 · Canonical: https://docs.zymcos.com/product/support-requests/

A support request is one conversation between your workspace and Zynth about one problem. This
page says what a request holds, how it moves from open to closed, and what you can and cannot do
with it today.

## Where things stand

The record of a request is built: a request can be opened, its thread read, replied to and
closed. What is **not built yet** is a form for doing any of that in the app or on this site.
Nothing on a docs page or in the workspace opens a request for you today. The *Getting help*
section of [Welcome to Zymcos](https://docs.zymcos.com/product/getting-started/#getting-help) is where the docs point you, and
this page says what a request is and how it moves, so that you know what to expect when you
have one.

Zynth's side of the conversation is not a screen yet either: there is no staff console for
replying to, resolving or assigning a request.

## What a request holds

- A **subject** and a first **message** saying what happened.
- A **priority**: low, normal, high or urgent. Normal is the default.
- Optionally, the **docs page** it is about, such as `product/getting-started.md`. It has to be a
  real page of these docs. Linking one tells us which pages fail people.
- The **thread**: every message from you and from Zynth, in order, with short notices between
  them when something changes, such as when the request is assigned, resolved or closed.

A request belongs to your **workspace**. Anyone who is a member of it can read it, reply to it and
close it; nobody outside it can see that it exists.

A thread holds up to 500 messages. If yours reaches that, open a new request.

## How a request moves

| Status | What it means | What moves it |
|---|---|---|
| **Open** | The next move is Zynth's. | Every new request; a reply from you to a request that was waiting for you or resolved. |
| **Waiting on you** | Zynth has replied and needs something back. | A reply from Zynth. |
| **Resolved** | Zynth believes it is fixed. You can still reply. | Zynth marking it resolved. A reply from you reopens it. |
| **Closed** | Final. Neither side can add a message. | You closing it. |

Closing is yours. Zynth resolves a request; you close it. A closed request stays readable, and
it cannot be reopened: if the problem comes back, open a new one and mention the old one in it.

## What is deliberately not in a request

The thread is only what you and Zynth said to each other. Zynth's internal discussion about a
request happens elsewhere and never appears in your thread. If you see a short line from the
system, such as *assigned*, both sides see it.

## What to put in a request

It helps to say what you were doing, what you expected, what happened instead, and the time. If a
card in Zymcos showed a short **code**, such as the one at the foot of a failed take, quote it:
it tells us which kind of failure it was. See [When a take fails](https://docs.zymcos.com/product/when-a-take-fails/).
