Reply to an Existing QCST Ticket by Email

This article explains ticket identification, authorized customer/Agent sender checks, storing the reply/attachments, and confirmation after successful storage.

Where this fits in QC Support Ticket

Inbound email is a Max/All Access feature. Each enabled mailbox connects to an ordinary IMAP account, routes new tickets to one Department, can accept replies to existing tickets, and can process attachments and supported Agent commands according to the mailbox settings.

Inbound processing is intentionally defensive: it checks sender authority, ticket identity, deduplication, loop/bounce/automatic-message signals, attachment policy, and mailbox state before it changes ticket data.

Primary location: Joomla Administrator → Components → QC Support Ticket → Email Templates → Inbound Mailboxes.

Before you begin

  • Confirm the site currently has Max / All Access effective access before expecting the controls described here. A preserved configuration may still exist after downgrade even when the feature is locked.
  • Confirm Joomla Mail works before diagnosing QCST template delivery. For inbound mail, confirm PHP IMAP is available and keep one controlled test message available.

How to do it

  1. Open a QCST notification for an existing ticket or compose a reply that preserves the ticket identification format QCST expects.
  2. Send the reply from an address authorized for that ticket (customer/verified identity or an authorized Agent for the supported Agent-email path).
  3. The inbound processor matches the ticket, rechecks sender authority, stores the public/internal message as allowed, and validates attachments.
  4. Open the ticket in Support Portal/Agent Queue and confirm the new message appears once. If it is rejected, check ticket identification and sender policy rather than weakening authorization.

Verify the result

  • Mailbox Test succeeds before unattended processing is relied upon.
  • Process Now handles one controlled message exactly once and records a safe result without duplicate ticket/reply creation.

If it does not work as expected

  • If connection fails, verify PHP IMAP, host/port/encryption/certificate settings and credentials before changing routing.
  • If connection succeeds but processing fails, inspect sender policy, ticket reference matching, duplicate/loop checks, mailbox capabilities, and attachment policy.

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.