Read the Multi-Line Agent Queue Ticket Summary

This article explains reference/subject, updated time, requester, status/priority, routing, assignment, and actions so Agents can triage without opening every ticket.

Where this fits in QC Support Ticket

The Agent Queue is a frontend support workspace, not a shortcut around permissions. Every ticket action is checked against the Agent’s active QCST record and Department scope on the server, including assignment, replies, status/priority changes, attachments, bulk actions, and advanced ticket operations.

Primary location: QC Support Ticket frontend Agent Queue.

Before you begin

  • Use a normal Frontend Agent account for verification. Testing only as Joomla Super User can hide Department-scope or menu-access problems.

What each queue row tells the Agent

Line/dataHow to use it
Reference + SubjectIdentify the case and topic quickly.
Updated timeSpot recently active/stale work.
RequesterKnow who is waiting.
Status + PriorityUnderstand workflow state and urgency.
Department / CategorySee routing context.
AssignmentKnow whether it is yours, another Agent's, or shared Unassigned work.
ActionsOpen/work the authorized ticket.

How to scan a queue row efficiently

  1. Read the ticket reference and subject first to identify the case.
  2. Check requester and Updated time to see who is waiting and how recently the case changed.
  3. Read Status and Priority together; they answer different questions—workflow state versus urgency.
  4. Confirm Department/Category before acting, especially on shared queues.
  5. Check assignment to see whether the ticket is yours, another Agent’s, or still Unassigned, then open the ticket from its action.

Why multiple lines are intentional

The row is designed to expose enough routing and workflow context for triage without opening every ticket. Long subjects/requester data should wrap/read cleanly rather than being compressed into a single unreadable line.

Verify the result

  • The test Agent can open the Agent Queue and see allowed-Department tickets.
  • The same Agent is denied or does not receive tickets outside the configured Department scope.

Community Discussion

For practical QC Support Ticket workflows and discussion with other Joomla site owners, visit the QC Support Ticket Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.