Support
Collect useful evidence and contact PulseHA support.
Use the Support page in the console to raise a ticket, follow its progress and reply to the PulseHA team. Open it when a guide and the console’s own error states do not explain a problem.

The Support list with priority, status and SLA for each ticket, and the All, Active and Resolved filters.
Before you start#
- Any signed-in user can open the page, but the control plane gates the calls behind it. Listing and reading tickets needs
support.read; creating tickets, replies and attachments needssupport.create. Under the built-in roles those belong to Owner, Admin and User, not Readonly. - Tickets are tied to your email address. The first ticket creates a support contact for you in PulseHA’s case system.
- The Help & Support link under Resources in the sidebar opens the PulseHA contact page on the website. The in-console ticket list is at Support (
/support), also linked from the documentation pages. - Gather evidence first: the display name of the affected device, gateway, service or policy; the time range and timezone; the visible error; and agent or gateway versions for connectivity issues. Search Security → Audit for related events.
- Never send private keys, enrollment codes, client secrets, access tokens or unsanitised tenant data. Check screenshots for names, addresses and user information.
Create a ticket#
- Open Support and choose New Ticket.
- Under Contact Information, confirm your Name, Email and Organization. These are read from your account.
- Under Category & Priority, pick a Category and a Priority. The sidebar shows the SLA Commitment for that priority with Response and Resolution targets.
- Under Issue Details, enter a Subject and a Description. Both are required. Include what you tried, what happened, error messages and steps to reproduce.
- Under Attachments, drop files or click to browse. Max 50MB per file. Accepted types are images, PDF, text, CSV, JSON, ZIP, gzip and tar.
- Choose Submit Ticket.

New Support Ticket: contact details, category and priority, the subject and description, and the SLA Commitment panel for the chosen priority.
You land on the ticket’s Case Details page. The subject is stored with the category in square brackets, for example [TECHNICAL] VPN drops on wake. Critical is recorded as High in the case system, which has three priority levels.
Follow and reply to a ticket#
- On Support, filter with All, Active or Resolved, or search by subject or ticket number.
- Open a row to see Case Details: ticket number, Status and Priority chips, the SLA panel, your original description and the message thread.
- Type in the reply box and choose the send button. Use the paperclip to attach one file per message (50MB limit).

Case Details: the ticket number, status and priority chips, SLA Tracking, the original description, and the message thread with the reply box.
Your messages appear on the right under your name. Support replies appear on the left. Once a ticket is Resolved or Cancelled, the reply box is replaced by “This ticket is closed. Create a new ticket if you need further assistance.”
Reference#
Categories: Technical Issue, Billing & Account, Feature Request, Security Concern, Integration Help, Other.
Priorities on the form:
| Priority | Description shown | Stored as |
|---|---|---|
| Low | General questions or minor issues | Low |
| Normal | Standard support requests | Normal |
| High | Critical issues affecting production | High |
| Critical | Complete service outage or security incident | High |
Ticket statuses:
| Status | Meaning |
|---|---|
| Active | Open and being worked. |
| On Hold | Paused by support. |
| Waiting | Support is waiting on you. |
| Resolved | Closed as fixed. Replies disabled. |
| Cancelled | Closed without resolution. Replies disabled. |
The SLA column shows time remaining to first Response until support replies, then to Resolution. A negative value with a red marker means the target has passed. An Escalated badge appears when the case is escalated.
Allowed attachment types: PNG, JPEG, GIF, WebP, PDF, plain text, CSV, JSON, ZIP, gzip, tar.
Troubleshooting#
- “Support center is temporarily unavailable”. The console could not reach the case system for your contact. Choose Retry. If it persists, use the website contact page.
- “Support system is temporarily unavailable” on submit. Same cause at creation time. Your draft stays on the form. Retry shortly.
- “file_too_large” or “invalid_file_type”. Files over 50MB or outside the allowed types are rejected. Compress logs into ZIP or gzip.
- A file was silently dropped from the attachment list. The form filters out files over 50MB before upload. Check the size.
- “Case not found” or “forbidden”. The ticket belongs to a different contact. Open it from your own Support list.
- The ticket list fails to load with a permission error. Your role lacks
support.read. Readonly users should ask an Owner, Admin or User to raise the ticket. - The reply box is gone. The ticket is closed. Open a new one and reference the old ticket number.