Support widget
The help panel in the superagnt app. What its AI assistant can read and do, how support tickets and the team's replies work, and who can see chats and tickets.
The support widget is the help panel in the superagnt app. It holds two lines to us: an AI assistant that answers questions and files tickets for you, and support tickets, the threads a person on the superagnt_ team answers.
Open it with support / help at the bottom of the sidebar, on any page of the workspace dashboard. The panel floats over the page, so you can keep the page you are asking about in view. The Request integration button on the Connections page opens it too, straight into an integration request.
01
The home view
- Report a bug and Feature request start a chat with the assistant that ends in a ticket.
- Message the team is a ticket you write yourself, with no assistant in between.
- Your tickets lists the workspace's 20 most recently active tickets, with each one's status and latest message.
- Your conversations lists your 20 most recently active chats with the assistant, and New chat starts a fresh one. A conversation stays until you archive it, so you can come back to it later.
- View documentation opens these docs.
02
The AI assistant
The assistant is separate from the agents you build and from the Agnt Wizard. It runs on superagnt_ and does not spend your AI credits. Its tool calls show in the chat as it makes them.
What it reads
| Tool | What it reads |
|---|---|
get_workspace_context | The workspace's name, plan and trial state, how many agents it has and the five newest, and the five most recent agent sessions that ended in an error. |
get_recent_user_sessions | The workspace's most recent agent sessions and your own Agnt Wizard sessions, up to 10 of each, so it can name the right ones in a bug report. |
get_billing_snapshot | The plan, the trial state, and the data and AI credit balances. |
search_docs, fetch_support_doc | The superagnt_ docs, including the troubleshooting guides: a search over page sections, then a whole page when it needs one. It links the page when the page is on superagnt.com. |
Each message you send also carries the page you are on and your browser details (user agent, language and window size), so you do not have to describe them.
It has no tool that reads your agents' transcripts or configs, your schedules, your connections or your workspace database.
What it can do
Its only actions open a support ticket for you:
| Tool | The ticket it opens |
|---|---|
submit_bug_report | Category bug. Your description is the message, with the steps to reproduce, expected and actual behaviour, related session ids, the page you were on and your browser details attached. |
submit_feature_request | Category feature_request, with your use case and a priority if you gave one. A request for a new integration also names the service you want. |
contact_support_team | Category question, billing, connection or other, for anything a person has to handle: a billing change or refund, deleting an account, a connection you could not fix together, or a question the docs do not answer. |
It sums up what it is about to file, files it once you agree, and gives you the ticket id. The ticket is yours: it shows under Your tickets as written by you.
It cannot build, change, deploy, schedule or run agents, change billing, refund anything or delete anything. For work on an agent it points you to the Agnt Wizard. For anything else that needs a person, it opens a ticket.
03
Support tickets
A ticket is a thread with a person on the superagnt_ team. Every way of asking ends in the same kind of ticket: Message the team, the assistant's three filing tools, and the agnt_support_* tools your agents and MCP clients call, which are on Getting help.
Message the team
Message the team opens a form with a subject (up to 200 characters), a category (Question unless you pick Bug, Billing, Connection, Feature request or Other) and a message (up to 20,000 characters). Send to the team opens the ticket and shows its thread. The page you were on and your browser details go with it.
Status
| In the widget | What it means |
|---|---|
| Open | Waiting on the team. Nobody has picked it up yet. |
| In progress | Someone on the team is working on it. |
| Answered | The team replied. The next move is yours. |
| Closed | Done. |
Agents reading the same ticket with agnt_support_ticket_get see these as open, pending, answered and closed.
Replies
When the team replies, the ticket turns Answered and the reply:
- shows in the ticket's thread in the widget, which refreshes every 30 seconds while it is open;
- is emailed to the workspace owner, and to the person who opened the ticket when that is someone else who is still in the workspace;
- raises an in-app notification, "Support replied:" followed by the ticket's subject.
The email and the notification both link to the ticket, and following the link opens the widget on its thread.
Answer in the thread's reply box. A reply on an Answered or Closed ticket reopens it, and the team is told. In the thread, the team's messages are labelled superagnt support, yours You, another member's Teammate, a deployed agent's Your agent and an MCP client's Your AI client.
Limits
- From the app (the form and the assistant together), a workspace can open 10 tickets in a rolling hour. Agents and MCP clients have a separate 10, so a looping agent never stops a person from asking for help.
- A ticket takes up to 30 messages from your side in a rolling hour.
Past either limit, sending fails with a message that says so. Add to a ticket you already have, or try again later.
04
Who can see what
| What | Who sees it in the superagnt app |
|---|---|
| A conversation with the assistant | Only the person who started it. |
| A ticket and its whole thread | Every member of the workspace, however the ticket was opened, including the tickets your agents filed. |
Outside the workspace, only the superagnt_ team sees a ticket. A person who leaves the workspace loses access to its tickets and stops getting reply emails.
never send secrets
Never put an API key, a password, a token or a card number in a chat or a ticket. The team never needs one to help you.