All guides
Admin

Support

Create customer tickets, reply, update status and manage support categories, types and labels.

Step-by-step guide

Before you start

Use an administrator account for this feature.

Open this feature

Open /admin/support on your application domain, or use the matching item in the application menu.

Steps

Sign in with support-management access. Before creating a ticket, identify its user and choose the category/type that will help your team route it.

Create a ticket for a user

  1. Open Support at /admin/support. Open the new-ticket form at /admin/support/create.
  2. In User, search by name, username or email and select the matching result. Check the selected person; typing a search term alone does not choose the owner.
  3. Enter a short Subject, for example Download link does not open. In Message, write the page, steps, visible error and expected result.
  4. Choose Category and Type from the available choices when relevant. Leave them unset if they are optional and no suitable choice exists.
  5. Set Status to Open for a new request that needs a reply. For Priority, choose Normal or Pinned; Pinned highlights the ticket rather than defining an urgent/high scale.
  6. Add useful Labels, then select Create ticket. Check the owner and conversation on the ticket page.

Find a ticket and reply

  1. On /admin/support, enter a search term and use Status, Category or Type to narrow the queue. Select Filter.
  2. Select View for the matching ticket. Read the earlier messages and check who the reply will reach.
  3. Enter the response in the reply editor below the conversation. Include an action the customer can follow; do not paste credentials.
  4. Select Send reply. Wait for the response to appear in the conversation before sending another message.

Change routing or resolve a ticket

  1. Open the intended ticket and locate its settings for Status, Category, Type, Priority and Labels.
  2. Select the new values. Choose Resolved only when the request has been answered; use Closed when you intend to close it.
  3. Select Save changes for the ticket settings. Reopen the ticket or refresh the queue to check the new state.
  4. To continue a resolved or closed request, set the intended status back to Open in these settings and save.

Manage categories, types and labels

  1. Open /admin/support/categories, /admin/support/types or /admin/support/labels, depending on the list you need to maintain.
  2. In the create form, enter Name, for example Installation. Set Status to the active choice if the entry should be offered for new selections.
  3. Set optional Icon class and Color when the form provides them. These change presentation, not ticket ownership or permissions.
  4. Select Create. To change an entry, use Edit on that entry and select Save changes.
  5. Return to a ticket form and check that the active entry is available in the relevant selector.

Fields and choices

Field or problemWhat to do
UserRequired. Search and select an existing person; verify their name and email before creating the ticket.
Subject / MessageSubject is required, up to 255 characters. Message is required; follow the length limit shown by this installation.
Category / TypeOptional on the administrator create form. Choose an existing active entry when it helps routing.
StatusOpen, Resolved or Closed. Choose the state that reflects the request; do not enter a numeric status code.
PriorityNormal or Pinned. Pinned is the queue’s pin flag, not a separate response deadline.
LabelsChoose existing labels from the selector. Remove an unintended selection before saving.
ReplyRequired when sending a reply, up to 5,000 characters. Empty rich-text formatting does not count as a message.
Taxonomy Name / StatusName identifies a category, type or label. Use the active status when it should be offered for new selections.

Check the result

  • Open the same ticket and check its owner, original message and new reply.
  • Refresh the queue after saving status or routing and check the selected filters.
  • Create a practice ticket only for a controlled account; keep the conversation and notifications separate from real customer requests.

Common problems

Field or problemWhat to do
No selected userChoose a result from the User search. A typed name without a selection is not sufficient.
Category, type or label is absentOpen its management list, check that the entry is active, then reload the ticket form.
Reply is rejected as emptyEnter meaningful text; an empty formatted paragraph can fail validation.
Ticket disappears from the queueUse Reset to clear filters, then search its subject again. A saved status may no longer match the previous filter.
A customer reports no emailCheck the conversation first to avoid duplicate replies. Email delivery must be investigated separately from a successful ticket save.

Technical reference

Role-scoped source references

Pinned commit: ca125291cce57358ac4842e50928bc31fc6eab07

Source-only route information
MethodSource-default route
GET/admin/support
GET/admin/support/create
GET/admin/support/categories
GET/admin/support/labels
GET/admin/support/types
GET/admin/support/{ticket}
Unmapped fields — not user instructions

These fields belong to this role’s source handler, but their screen labels were not confirmed.

Source keyHandler
uidmodules/AdminSupport/Livewire/SupportCreate.php
pinmodules/AdminSupport/Livewire/SupportCreate.php
labelIdsmodules/AdminSupport/Livewire/SupportCreate.php
pinmodules/AdminSupport/Livewire/SupportShow.php
labelIdsmodules/AdminSupport/Livewire/SupportShow.php
editingCommentContentmodules/AdminSupport/Livewire/SupportShow.php
iconmodules/AdminSupport/Livewire/SupportTaxonomy.php
colormodules/AdminSupport/Livewire/SupportTaxonomy.php