Support

Get help with a Tavory ticket

Send a focused support request with enough context for the Tavory team to help efficiently.

Describe what you expected and what happened.

Do not include API keys or passwords.

Include screenshots only when they do not expose private data.

How Workspace fits together

One place for the decision, the context and the next step.

Choose the issue path

Bug reports, billing questions and feature requests each need different context from the start.

Protect the request

Support messages must never contain passwords, API keys or private payment details.

Know the current boundary

The existing form sends a protected support email; persistent ticket history needs a future authenticated backend.

Ticket desk

Create a request and keep its thread visible.

Tickets are authenticated and scoped to your account. Never include passwords, API keys or full payment details.

Ownership is checked server-side. Other users cannot load your tickets or messages.

Checking your sign-in...

A simple workflow

Move from prompt to useful work.

The workspace keeps the important decisions visible without forcing every request through the same model or process.

Describe the issue

State what you expected, what happened and where the issue occurred.

Send through support

Use the current support form, which validates and forwards the request server-side.

Track the next step

Ticket IDs, status history and threaded replies remain a planned backend dependency.

Controls that stay visible

Useful control without unnecessary complexity.

The current support form does not fabricate ticket IDs or statuses.
Support email delivery is server-side and hides provider credentials from the browser.
Persistent ticket history requires authenticated ownership checks.
Do not include passwords, API keys or full payment details.

Open support Back to Tavory