Report a bug, suggest a feature, or ask us anything. We reply within one business day, and every status change shows up here as it happens — no browser tab required.
Support lives at the same address as your work — no browser tab, no email thread, no guessing whether your report landed.
Somewhere else
You file a ticket in a browser portal, receive an auto-reply by email, and periodically check back hoping something changed. Context lives in five different tabs.
Inside Actionist
You raise the ticket from the app, attach a screenshot or recording, optionally include the day’s diagnostic log in one click, and watch status advance in a structured pipeline — right here, as it happens.
The response SLA shown in the app is “within one business day.” This is the current UI string — confirm with the team if you need a contractual guarantee for your use case.
Pick the type when you raise a ticket. The pipeline you see on the detail view then matches how that type of report actually moves through the queue. Select a type to watch its stages animate:
Received and under review
Bug confirmed as reproducible
Resolved — ships in next update
No further action needed
SubmittedYour report has been received and is under review.
VerifiedThe team has confirmed the bug is reproducible. Not yet fixed — but acknowledged.
FixedThe issue has been resolved. Usually shipped in the next update.
ClosedNo further action needed.
Received and being considered
On the roadmap — committed
Feature has shipped
Complete
SubmittedYour request has been received and is being considered.
ApprovedThe feature is on the roadmap. Not yet built — but committed.
ImplementedThe feature has shipped.
ClosedComplete.
Question received
Team has replied — check the Activity thread
Resolved
SubmittedYour question has been received.
AnsweredThe team has replied. Check the Activity thread.
ClosedResolved.
Bug reports include repro steps and ideally a screen recording so the team can reproduce the exact failure path before investigating.
Feature requests work best as problems. “I need bulk CSV import because I manage 50+ agents” gives the team far more than “add CSV import.”
Approved ≠ Implemented. Approved means on the roadmap. Implemented means shipped. Do not mistake the earlier stage for completion.
Look for the lifebuoy in the bottom section of the left sidebar. It is always visible — no need to scroll or open a settings panel.
Read the stats banner
Three cards load immediately: Bugs, Feature requests, and General support — each showing counts at each pipeline stage. This gives you a live snapshot of your open reports before looking at any individual ticket.
Browse your submissions
Below the stats is the All submissions table. Columns show type, title, status, and last-updated time. Tickets with new admin activity carry a New badge; that badge clears the moment you open the ticket.
Help & Support
Bug reports
Submitted 2Verified 1Fixed 0
Feature requests
Submitted 3Approved 1Implemented 2
General support
Submitted 1Answered 2
AllBugsFeaturesGeneral
Search title…
TypeTitleStatusUpdated
BugLogin button unresponsive after 2FA on Safari iOS NewVerified2 hr ago
FeatureBulk CSV import for skillsApprovedYesterday
GeneralHow do I share an agent with a teammate?Answered3 days ago
BugWorkflow editor freezes on large branching diagramsSubmitted4 days ago
Filtering and searching
Use the filter pills — All, Bugs, Features, General — to narrow the table to one type. To find a specific ticket by title, type in the Search title box. The search fires after you have typed at least 3 characters (a hint appears for shorter input) with a short debounce so results update as you type. The list is paginated at 20 tickets per page.
The New badge
A New pill appears on any ticket that has received a new admin reply or a status update since you last opened it. Opening the ticket clears the badge. It reappears the next time new activity arrives.
Click Raise a Ticket in the banner to open the wizard. Two steps: pick a type, then fill in the details. Below is what each step looks like:
Step 1 — Pick a typeStep 2 — Fill in details
Something isn’t working the way it should. Reports include repro steps and ideally a recording.
A question, an account issue, or a how-do-I. Anything that doesn’t fit the other two.
A new capability or an improvement to an existing one. The more “why” the better.
Step 1 — Pick a typeStep 2 — Fill in details
Title *
Login button unresponsive after 2FA on Safari iOS
45/120 characters · keep it specific
Description *
After completing 2FA on iPhone Safari, tapping Login does nothing. Refreshing the page clears the session. Repro rate: 9/10 attempts.
Related area
Account
Include diagnostic logs to help us debugView
Bug tips
Describe the exact steps to reproduce, not just the result.
Include the OS, browser, and app version.
A screen recording is worth a thousand words.
One bug per ticket — easier to track and close.
Step 1 — pick a type
Three cards appear: Bug report, General support, Feature request. Click one to advance to the form. Each card includes a one-line description to help you choose the right channel.
Raise a new ticket✕
Pick a type
Something isn’t working the way it should. Reports include repro steps and ideally a recording.
A question, an account issue, or a how-do-I. Anything that doesn’t fit the other two.
A new capability or an improvement to an existing one. The more “why” the better.
Step 2 — fill in the details
The form opens. A tab bar at the top lets you switch type without losing your draft. Fill in the required fields:
Title — 8 to 120 characters. The placeholder changes per type.
Description — at least 20 characters.
Related area — choose the area of the app: Actions, Apps, Agent, Skills, Workflows, Account, Billing, or Other.
A contextual tips sidebar on the right shows per-type writing guidance.
See the Step 2 wizard mock rendered above — it shows the exact fields and tips layout described here.
Attach screenshots or recordings
Drag files onto the attachment drop zone or click to browse. You can attach up to 5 files, each up to 10 MB. Accepted formats: .png, .jpg, .jpeg, .mp4, .mov. Remove any file individually before submitting.
Video files (.mp4, .mov) upload successfully and are visible to support admins. The in-app lightbox shows a placeholder — download the file to play it.
(Bug only, desktop only) Opt in to diagnostic logs
On bug tickets in the desktop app, tick Include diagnostic logs to help us debug to bundle today’s app log with the ticket. Click View first to preview what will be sent before you consent.See Diagnostic log consent below for full detail.
Submit
Click the submit button — Report this bug, Ask a question, or Suggest a feature depending on type. If you try to close the wizard with unsaved input, a confirmation dialog appears: Discard to abandon the draft, or Keep editing to return to it. On success the modal closes and the list refreshes automatically.
If you close the wizard before submitting, you will see a “Discard this ticket?” confirmation. Click Keep editing to go back to your draft — it is not saved once you confirm discard.
One checkbox bundles the day’s app log with a bug ticket. No log-hunting, no copy-paste. Entirely opt-in.
What gets sent
Today’s app log (app-YYYY-MM-DD.log). The log is admin-only — it does not appear in your ticket attachments list.
Preview and consent
Click View to read the last 256 KB before you tick the box. If the file is larger, the preview is truncated but the full file is always uploaded. The label “Showing last 256 KB of [size]. Full file is uploaded.” appears when truncation occurs.
When it's unavailable
Desktop-only feature. On the web app the option is hidden. On desktop, logs only exist in packaged production builds — development builds show “No log file found for today.” in the preview, which is expected.
app-2026-06-11.log (preview)
[2026-06-11 09:14:02] INFO scheduler:start agents=4 interval=60s
[2026-06-11 09:14:03] INFO ipc:ready channel=main-renderer
[2026-06-11 09:14:11] INFO auth:clerk status=signed-in user=[email protected]
[2026-06-11 09:22:51] ERROR workflow:run id=wf_8Bx2 step=send-email error=“SMTP_TIMEOUT after 4000ms”
[2026-06-11 11:45:12] INFO mcp:connect server=gmail status=ok
App logs are only written in packaged, production builds of the desktop app. In development or beta environments the preview may show “No log file found for today.” — this is normal. Nothing is uploaded in dev mode.
Click any row in the submissions table to open the full ticket. The detail view shows everything in one place: your original description, the pipeline stage, the full conversation thread, and the reply composer. Watch the thread build:
ticket · #1042 · Login button unresponsive after 2FA
New
SubmittedVerifiedFixedClosed
YouToday at 09:31
After completing 2FA on iPhone Safari, tapping Login does nothing. Refreshing clears the session. Repro rate: 9/10 attempts. Diagnostic log attached.
status changed: Submitted → Verified
AdminToday at 11:14
Thanks for the detailed report. Reproduced the exact flow on Safari 17.4.1 / iOS 17.4. The issue is a race condition in the session cookie write after TOTP validation — we have a fix in review. Will update you once it ships.
YouToday at 11:22
Appreciate the quick turnaround. Any workaround in the meantime? Trying Chrome on iOS seems to work, but we have users who only use Safari.
AdminToday at 11:48
Chrome on iOS is a safe workaround for now — you’re right that it avoids the issue. The fix targets the next patch release, which we aim to ship within 48 hours.
Reply to thread…
Send reply
The status progress bar reflects the pipeline for that ticket’s type. Bug tickets show the four-stage bug flow; feature requests show their own four stages; general tickets show their three. The current stage is highlighted.
The Activity section is chronological. You will see your own messages, replies from the Actionist team labelled Admin, and synthesized status-change events when the ticket moves through the pipeline. Type in the composer at the bottom and click Send reply to add a message at any open stage.
Once a ticket reaches Closed status, the reply composer is disabled and the message “This ticket is closed.” appears. If the same issue recurs, click the inline Raise new ticket button that appears in the closed-ticket view — it opens a fresh wizard.
You don’t have to open the wizard. The Actionist helper can guide you through ticket creation conversationally — useful when you spot an issue mid-workflow and don’t want to break your flow.
chat · Actionist helper
helperHi Sina! I’m here to help. Are you facing a bug, or do you have a question or suggestion for us?
youI found a bug with the login flow on Safari iOS.
support skill matched — collecting details
helperGot it — bug report. Can you describe what happens and the steps to reproduce it?
youAfter 2FA the login button does nothing. Repros 9 out of 10 times on iPhone Safari.
helperWould you like to include today’s diagnostic log? I’ll show you a preview before attaching anything.
When you navigate to the Help & Support page, the helper greets you:
Click Start chat to begin — or type directly in the chat at any time from anywhere in the app.
Describe the issue or request
Say something like “I found a bug” or “I want to request a feature.” The helper identifies the intent and loads the support skill automatically — it is not visible in your skills list and activates transparently.
The helper guides through required fields
It collects title, description, and related area through conversation. For bug tickets it asks for steps to reproduce before proceeding.
Consent for diagnostic logs and attachments
The helper asks whether you would like to include the diagnostic log and any attachments before submitting. Nothing is sent without your explicit agreement.
The helper submits on your behalf
On your approval the ticket is created and immediately appears in your Help & Support list — the same ticket you would have raised through the wizard.
Type “I found a bug with [area]” or “I have a question about [topic]” in any Actionist chat to raise a ticket without leaving your current workflow. The helper handles the rest.
I spotted the issue mid-workflow, typed two sentences to the helper, ticked the log checkbox, and the ticket was in the queue before I’d even switched tabs. The whole thing took under a minute.
Priya — support lead, managing 120+ inbound tickets a week
If the submissions table seems unresponsive to typing, check that your input is at least 3 characters. Shorter input is silently ignored — the hint “Type at least 3 characters to search” appears below the field for shorter input.
Preview the diagnostic log before ticking the box
Click View next to “Include diagnostic logs to help us debug” before enabling the checkbox. The preview shows the last 256 KB of the log file so you can confirm the content before consenting. The log is admin-only and does not appear in your ticket attachments.
Diagnostic logs only exist in production builds
If the preview shows “No log file found for today.”, you are likely on a development or beta build. App logs are only written in packaged production releases. The diagnostic feature is simply unavailable in that environment.
Switch ticket type without losing your draft
While on Step 2 of the wizard, use the tab bar at the top to change the ticket type. The title, description, and area fields are preserved when you switch — only the type label updates.
Video files upload but don't preview in-app
.mp4 and .mov attachments are accepted, uploaded, and fully visible to support admins. The in-app lightbox shows a placeholder message. Download the file to play it locally.
Closed ticket? Use the inline button
When a ticket is Closed the reply composer is disabled. If the issue persists, click the inline Raise new ticket button in the closed-ticket view to open a fresh wizard.
Frame feature requests as problems, not solutions
The in-app tips sidebar says: “Frame the problem you’re trying to solve, not just the solution.” A request like “I need bulk CSV import for skills because I manage 50+ agents across clients” gives the team far more to work with than “Add CSV import.”
Approved and Implemented are two different stages
Approved means the feature is on the roadmap — the team has accepted it but has not yet built it. Implemented means it has shipped. Similarly, Verified confirms a bug is reproducible; Fixed means it has been resolved. Do not mistake the earlier stage for completion.
