> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Contact support

> Reach Sazabi support from the dashboard or the CLI through a conversation with the agent, and know where the reply arrives.

Support at Sazabi starts as a conversation with the agent. You describe the problem once, the agent answers from the documentation when it can, and when a human needs to look it drafts a support ticket with you and files it only after you say yes. Support replies in the dashboard's support chat, and by email when you are not there to see it.

## Start a support conversation

> [tab] Dashboard
>
> 1. Select the **Help** button in the top bar and choose **Contact support**, or open the command palette and choose **Contact support**. The support chat opens with a new message.
> 2. Describe what is happening: what you expected, what you saw, and roughly when. Include the project and any identifier you have, such as an issue name or a log source.
> 3. Send the message. Support replies in the same chat, and **Support inbox** in the **Help** menu reopens your past conversations.

> [tab] CLI
>
> Start the conversation from your terminal and continue it in the browser:
>
> ```bash theme={"system"}
> sazabi support ask "Slack alerts stopped arriving yesterday"
> ```
>
> The command creates the support thread in your active project and opens it. Add `--no-open --json` to print the thread's URL instead, or `--project-id` to pick the project. See [`sazabi support ask`](https://docs.sazabi.com/reference/cli/support) for every flag.

## File a ticket

When the answer needs a person, the agent drafts the ticket in the thread: a title, a summary of what you reported, and what has been tried. Read the draft and reply **yes** to file it. Nothing is sent to support until you confirm, and the agent never puts credentials or secrets in a ticket. If you are asking for a capability Sazabi does not have, say so and the agent files it as a feature request.

The agent may also offer a ticket on its own when a conversation runs into a Sazabi-side problem or a missing capability. The offer is made once; declining it ends the matter.

Every ticket carries your organization, the project, and a link to the thread, so support starts with the context. The agent posts the ticket number in the thread once the ticket is filed.

Scripts that need to file without a conversation use the CLI directly:

```bash theme={"system"}
sazabi support tickets create --title "Export issues to CSV" --body "We need a CSV export of the issues list." --feature-request
```

See [`sazabi support tickets create`](https://docs.sazabi.com/reference/cli/support) and, for the API, [File a support ticket](https://docs.sazabi.com/reference/api/support-tickets/create.md). A person can file five tickets an hour and an organization thirty a day; past that, filing is refused with the time to wait.

## See your tickets

List the tickets you filed and check where each one stands:

```bash theme={"system"}
sazabi support tickets list --status open
```

`--status open` shows everything support hasn't closed; you can also filter by `new`, `waiting_on_you`, `waiting_on_customer`, `on_hold`, or `closed`, or add `--feature-request` to see only feature requests. Open one ticket by its number with `sazabi support tickets get 1852`. You see only the tickets you filed yourself, never a teammate's, the same as in the support chat. See [`sazabi support tickets`](https://docs.sazabi.com/reference/cli/support) for every flag.

## Where the reply arrives

Support answers in the dashboard's support chat, opened from the **Help** button in the top bar, where the filed ticket appears as its own conversation, separate from the thread the agent drafted it in. Support's replies land there, not in the thread. If you are not in the dashboard when support replies, the reply is also sent to the email address on your account, and where the support chat is not available the whole exchange happens by email from [support@sazabi.ai](mailto:support@sazabi.ai). Open **Contact support** from the **Help** menu to talk to support directly without starting a thread.

If support cannot take a ticket, for example while the desk is unreachable, the agent gives you the drafted summary and the address to send it to instead, so nothing you wrote is lost. The CLI prints the address; your title and body are still in the command you ran.

## Verify

1. Select **Help** in the top bar, choose **Contact support**, and send a message, or run `sazabi support ask "test"` in your terminal.
2. A conversation opens in the support chat, or the CLI creates a thread in your project where the agent replies within a minute.
3. If you confirm a ticket, the agent posts its ticket number in the thread, and the ticket appears as a new conversation in the support chat.

If the **Contact support** entry is disabled, the support chat is still loading or could not load; reload the page. If `sazabi support ask` prints an authentication error, run `sazabi auth sign-in` and try again.

## Further reading

> [card] [Threads](https://docs.sazabi.com/ask/threads.md)
>
> How threads work, including the support conversation you started.

> [card] [Limits](https://docs.sazabi.com/reference/limits.md)
>
> Every limit that can be raised, and the ones that cannot.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.