Customize QCST Frontend Text and Labels

This guide walks through Frontend Text headings, body copy, size/color controls, and shared interface labels, then explains how to verify the customer and Agent wording without changing business logic.

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 Text.

How to do it

  1. Open the Frontend Text tab.
  2. Edit the intended headings/body text and the available size/color/shared interface labels. Keep wording concise enough for buttons/cards and consistent between customer/Agent concepts.
  3. Save Frontend Text.
  4. Open Support Portal and Agent Queue and verify the wording in real context. Text customization changes labels/presentation; it does not rename database workflow behavior or bypass authorization.

What can be changed

Frontend Text provides separate Customer Support Portal and Agent Queue scopes. It can change optional introductory text and fixed navigation, heading, button, field, table and empty-state wording. Examples in the current definitions include Back to Queue, Ticket/Department/Category/Status/Priority/Agent/Updated column labels, no-results text, conversation/timeline headings, requester/created/updated labels, attachment/message labels and reply-button wording.

Boundary

These text settings are presentation labels. They do not rename the underlying database workflow behaviors, change Status semantics, widen Agent scope or change customer ownership. Keep customized wording consistent with what the control actually does.

Write labels for the control that really exists

Because Frontend Text does not change backend behavior, custom wording should stay semantically aligned with the actual action. For example, renaming a reply button to imply “Close Ticket” would confuse users because posting a reply and changing ticket state are separate operations. Test customized labels on the real customer and Agent screens before rollout.

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.