Customize the Agent Queue Design

This guide walks through the Agent Queue visual scope and how to verify that KPI cards, ticket lists, ticket detail/timeline forms, and bulk controls remain usable after customization.

Where this fits in QC Support Ticket

Frontend Design and Frontend Text change presentation and wording only. They do not bypass customer ownership, Agent Department scope, ticket workflow, or server-side permissions, so functional testing should be completed before and after appearance changes.

Primary location: Joomla Administrator → Components → QC Support Ticket → Frontend Design.

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.

How to do it

  1. Open Frontend Design and choose the Agent Queue scope.
  2. Select Customize and adjust the intended visual controls.
  3. Save.
  4. As a normal Frontend Agent, verify KPI cards, multi-line ticket list, filters, ticket detail/customer context, timeline/reply forms and bulk-action controls remain usable.
  5. Test a narrow viewport and a ticket with long subject/requester text before accepting the styling.

Agent-queue checks after styling

  • KPI cards and the multi-line ticket list remain readable.
  • Queue filters, assignment/workflow controls and bulk-action controls remain visible.
  • Customer context, timeline, reply/Internal Note controls and attachments remain distinguishable.
  • Long subjects/requester names wrap without covering action buttons at narrow widths.

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.

Design changes must preserve dense Agent workflows

The Agent Queue contains more controls and denser information than the customer portal: KPI cards, multi-line rows, filters, customer context, assignment/workflow controls, conversation entries, attachments and bulk actions. After changing width, font, padding or button settings, test a busy ticket and a long queue row so the design is proven under realistic content rather than an empty-state screen.

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.