AquaOps previously had a self-service ticket system (submit, track, and comment on tickets
in-app). It was fully retired in favor of live chat. This page documents current behavior —
if you’re looking for “My Tickets” or a ticket history page, it no longer exists.
Purpose
Use this page to understand how to reach AquaOps support right now: a live chat widget plus a documentation link, both surfaced from a Help page.What changed
The original ticket system let signed-in users submit a ticket, track their own ticket history, and (for org admins) see every ticket their org’s members had filed, gated behind aticket:org permission. Anonymous visitors could also file a ticket from the public marketing site.
That entire system — the support_tickets and support_ticket_comments tables, the ticket-submission actions, the /admin/support-tickets and /settings/support-tickets pages, the anonymous marketing ticket form, and the ticket:own / ticket:org permission keys — was removed in favor of a self-hosted Chatwoot live chat instance. There is no in-app ticket submission form, no ticket history list, and no ticket:org permission in the product today.
Known gap: because Chatwoot doesn’t offer a customer-facing multi-user account/portal, an org admin can no longer see support conversations started by their own teammates the way ticket:org used to allow. Each person’s chat history lives in their own browser session with Chatwoot, not tied to their AquaOps account or organization.
Getting help today
1
Open Help
Signed-in users: go to
Settings > Help. No account: visit the public /help page on the marketing site — same content, no sign-in required.2
Use the chat button
A chat bubble is available in the corner of every page — both inside the signed-in app and on the marketing site — powered by the same Chatwoot widget, loaded site-wide. Click it to start a live conversation with AquaOps support.
3
Check documentation first for common questions
The Help page also shows a Documentation card linking out to AquaOps docs, when a public docs site is configured.
The Help page
BothSettings > Help (in-app) and the marketing site’s /help page show the same simple layout:
- a short message pointing you to the chat button for support
- a Documentation card
The chat widget
The chat bubble is the actual support channel now. It’s a self-hosted Chatwoot widget loaded from every page in the app (not just the Help page), so you don’t need to navigate anywhere special to reach it. Conversations happen directly with AquaOps support through that widget; there is no separate “reply” or “resolve” flow inside AquaOps itself — resolution happens in the chat.Viewing your history / org visibility
There is currently no AquaOps-side view of your past conversations and no org-level visibility into teammates’ support requests. Any history is whatever Chatwoot retains for your browser/session. If you need an org admin to be aware of a support issue, loop them in directly (e.g. have them start their own chat, or share details outside the chat widget) — the app doesn’t do this for you anymore.Marketing site /help
The public /help page is intentionally out of scope for the rest of this guide since it’s aimed at visitors without an AquaOps account — but it’s worth knowing it exists and works the same way as Settings > Help: documentation link plus the same chat widget, no ticket form.
Best practices
- use the chat widget for anything time-sensitive — it’s the only live channel now
- check the Documentation card first for common “how do I…” questions once a public docs site is live
- don’t expect an in-app record of past support conversations — nothing is written back into AquaOps
- if your org needs shared visibility into support conversations, coordinate that manually for now; there’s no
ticket:org-style permission to grant
Suggested screenshots
Settings > Helppage showing the message and Documentation card- the chat bubble in the corner of the app
- an open Chatwoot chat conversation
- the marketing site’s
/helppage