# Get help

Make a support request easy to understand and fast to investigate.

Source: https://docs.opser.com/help/support/

## Try a quick check first
Many problems have a fast answer. Check [Troubleshooting](https://docs.opser.com/help/troubleshooting/) for common causes such as a disconnected account, a missing permission, or an [empty credit balance](https://docs.opser.com/billing/usage/). If a workspace-wide notice is showing at the top of Opser, a known issue may already be under investigation.

## Start with a clear description
When **Support** appears below App Store in your sidebar, open it and choose **New ticket**. Describe the problem and optionally attach screenshots. This page works without installing Chat and does not spend AI credits.

Tickets are private to you and the Opser team. You can also ask your default agent, the one created with your account, to open a ticket, find an existing one, read replies or send a follow-up. Review and approve a new ticket or reply before the agent sends it. Other agents cannot access your private tickets; use the Support page instead. If other people can use your default agent, they see its chat, including any ticket you read there, so use the Support page for anything you want to keep to yourself. Model usage still follows your workspace billing.

Return to the conversation to read the team's reply, add details, resolve the ticket or reopen it. Notification preferences control alerts, and an unread team reply can trigger an email reminder.

If Support is not available in your workspace, use the [Opser contact page](https://opser.com/contact) or your agreed workspace support channel. Explain what you were trying to do, what you expected, and what happened instead.

Include the workspace address, the affected app or agent, the approximate time and timezone, and the visible error message. Mention whether the problem affects one user or several.

## Add useful evidence
A short sequence of steps is often more useful than a large log. Include a record or conversation link when appropriate for the support channel. For billing problems, provide the payment reference rather than card details.

Remove passwords, API keys, session tokens, and unrelated private information from screenshots or copied messages. Never provide your account password, a verification code, or a reset link to diagnose an issue.

## Improve an agent's answers
If an agent's response was unhelpful, use the response feedback control on that message to mark it and add an optional note. This is separate from a support request: it helps tune future answers rather than opening a ticket. For a repeatable improvement, set the agent's [context](https://docs.opser.com/agents/context/) or a [skill](https://docs.opser.com/agents/skills/) so the next task starts from better instructions.

Agents can also report gaps in Opser itself to the Opser product team on their own, such as a tool they needed that does not exist, a tool that misbehaved, or one whose results were unclear. These reports describe the gap generically, without personal data, secrets or business records, and you are not notified when one is sent. Nothing changes automatically because of a report, and it is not a support request: for help with your own problem, open a ticket as described above.

## Suggest a docs improvement
If a guide is unclear, include the page URL and the step that confused you, and tell us what you saw in the interface so the guide can be corrected against the product. For immediate checks while you wait, see [Troubleshooting](https://docs.opser.com/help/troubleshooting/).