Appearance
Tickets
Tickets are customer complaints and support cases. Each ticket belongs to one customer and is automatically associated with that customer's owning reseller. Open Complaints from the sidebar to create, track, update, and resolve cases.
Create a ticket
- Select Add Complaint.
- Choose the affected customer from your permitted scope.
- Enter a concise subject and a useful description of the issue.
- Choose a category and priority: Low, Medium, High, or Urgent.
- Save the ticket.
Dream Radius generates the ticket number. Record observations that will help the next operator: the customer username, location, affected service, time of issue, error message, and any troubleshooting already completed.
Work the ticket
Open a ticket to review its details and comments. Update the status as work progresses:
| Status | Use when |
|---|---|
| Open | The complaint has been logged and needs attention. |
| In Progress | Someone is actively investigating or working the issue. |
| Resolved | The reported issue has been fixed or a resolution was provided. |
| Closed | The case is complete and no further action is expected. |
Assign the ticket to the reseller responsible for handling it when that is available. Add comments for diagnostics, customer communication, technician dispatches, and the final resolution. Comments become part of the case history.
Find and review cases
The complaint list is newest first and can be filtered by keyword, status, priority, reseller, and creation date. Search by ticket number, subject, or customer when following up on a call.
The list identifies the customer, owning reseller, category, priority, status, assignee, and creation date. Use the ticket statistics and filtered list to identify recurring faults or overdue high-priority cases.
Visibility and permissions
Resellers can see tickets for their own customers. Upline resellers can see cases within their downline, while Superadmin can see all tickets. A ticket created by an upline for a downstream customer remains visible to that customer's own reseller.
Staff need the matching ticket permissions to read, create, update, comment on, or delete a case. Permanent deletion is limited to authorized administrative roles. Prefer resolving or closing a ticket over deleting it, because deletion also removes its comment history.
Troubleshooting evidence
Link the complaint to the appropriate operational evidence before closing it:
- use Auth Logs for failed logins or rejected credentials;
- use Session History and Usage Summary for session and traffic questions;
- use CoA Logs for a disconnect or reauthorization that did not complete;
- use the customer profile for package, expiry, account status, and live-session checks.
Keep the resolution searchable
End each ticket with what was found, what changed, who performed the work, and when the customer confirmed service. This turns old tickets into useful knowledge for the next similar fault.