Support & Notifications
Report bugs, request features, track your tickets, and stay on top of replies and product updates — all without leaving the dashboard.
What you'll learn
- How to report a bug or request a feature from anywhere in the app
- What the "More details" block captures automatically and why it helps
- How to track your tickets and read replies from the team on the Support page
- How the notification bell, unread badge, and "What's new" updates work
You don't need to leave the dashboard to get help. Open your account menu (the pill with your email at the bottom of the sidebar) and choose Report a Bug or Request a Feature — each opens a slide-over you can fill in without losing your place. Everything you submit shows up on the Support page, where you can follow its status and read replies from the team — clicking a reply notification opens the message right in a popup, with a View full ticket link when you want the whole thread.
Report a Bug
Open your account menu at the bottom of the sidebar and choose Report a Bug. The slide-over walks you through four short fields.
Summary
One line describing what went wrong — the shorter and more specific, the better. "Call drops when I switch the transcriber mid-edit" beats "agent broken."
Details
The full story: what you were doing, what you expected, and what actually happened. Steps to reproduce are gold — if we can follow them, we can fix it faster.
Severity
Pick how badly this is hurting you. The label you choose sets the priority the team triages against:
| Severity | Meaning |
|---|---|
| Critical | P0: Platform down or data loss |
| High | P1: Major feature broken |
| Medium | P1: Degraded but usable |
| Low | P2: Minor, no customer impact |
Attachments
Drop in a screenshot or screen recording — a picture of the broken state is worth a paragraph of description. You can attach up to 5 files, images or videos, at 5 MB each.
Press Submit and the ticket is filed. It appears immediately on your Support page.
What the 'More details' block sends
Every bug report carries a collapsible More details block that fills itself in automatically. Expand it before submitting to see exactly what's attached:
- The page you were on when you opened the report
- Your browser and version
- Your operating system
- Your screen size
- The app version you're running
- Your email
- Your workspace (name and ID)
This is the boring-but-essential context that usually costs a round of back-and-forth to collect. Sending it up front means the team can often reproduce the issue on the first try instead of asking "which browser?" and "what were you doing?" — so your fix lands sooner.
Request a Feature
The Request a Feature button opens the same slide-over, tuned for ideas rather than bugs. A good request leads with the problem, then the behavior you imagine:
- Problem first. Describe what you're trying to accomplish and where the platform gets in your way. "I can't tell which campaigns are paused vs. failed at a glance" tells us more than "add better status colors."
- Imagined behavior second. Then sketch how you picture it working. This is a starting point, not a spec — we may solve the underlying problem a different way, and knowing the why lets us do that well.
The more we understand the job you're trying to get done, the better the thing we build for it.
Tracking Your Tickets
Everything you submit lands on the Support page. Clicking a reply notification shows the message in a quick popup; the View full ticket link inside it takes you to the page, where each ticket shows its current status as a colored pill, full details, attachments, and every reply from the team.
Bugs and features move through different status flows:
| Type | Status flow |
|---|---|
| Bug | Open → Acknowledged → In progress → Resolved / Won't fix |
| Feature | Open → Under review → Planned → Shipped / Declined |
A bug starts at Open, gets Acknowledged once the team confirms it, moves to In progress while it's being worked, and ends at Resolved or Won't fix. A feature starts Open, goes Under review while the team weighs it, becomes Planned once it's on the roadmap, and finishes as Shipped or Declined.
When the team replies, the reply appears on the ticket and you get a notification — so you don't have to keep checking the Support page to know something moved.
Notifications
The bell sits beside the zoxaAI logo at the top of the app. When you have unread notifications, an unread badge shows the count.
- Click the bell to open the notification list. Opening it refreshes the list, and clicking a notification shows the full message in a popup — replies include a View full ticket link for the complete thread.
- Mark all read clears the badge in one click.
- The unread count refreshes every couple of minutes, and again the moment you return to the tab — so a reply that arrives while you're away shows up promptly without a manual refresh.
- The bell keeps your 10 most recent notifications — older ones roll off automatically, and Clear all empties the list for good.
What's New
When there's a new product update, a What's new panel appears once after you log in. Read it, close it, and it won't nag you again for that update.
Want to revisit it later? Open the bell and click the What's new footer at the bottom of the notification popover — it re-opens the latest update any time you like.
The "once after login" behavior is per update: a brand-new announcement will show its panel the next time you sign in, but only that one time. Everything else lives behind the bell's What's new footer whenever you want to catch up.