Verify a Guest Ticket by Email

This article explains the expiring verification link, what verification authorizes, and what to do when a link is expired or does not match the ticket.

Where this fits in QC Support Ticket

The Support Portal is ownership-scoped. Registered users work their own tickets; verified guests use a signed, expiring verification/access path for the specific guest ticket. Department choice also controls which scoped Categories and Ticket Fields are offered during intake.

Primary location: QC Support Ticket frontend Support Portal.

Before you begin

  • Use a normal customer/guest test flow as well as administrator checks so ownership and verification behavior are tested under the same permissions customers use.

How to do it

  1. Open the QCST guest verification email for the submitted ticket.
  2. Click the signed verification link before it expires.
  3. QCST validates the signature/token against the intended guest ticket. A link for one ticket must not authorize another ticket.
  4. After success, bookmark/use the resulting permitted ticket route as appropriate.
  5. If expired or invalid, request/use a fresh valid verification flow rather than modifying the token/URL.

Important behavior and limits

  • A guest verification/access link is ticket-specific and must not be treated as a general public ticket URL.

Verify the result

  • A guest receives the verification message and can access only the intended ticket after verification.
  • The access path expires or fails safely when its signed verification is invalid or no longer eligible.

If it does not work as expected

  • If the guest cannot continue, check guest-ticket enablement, email delivery, verification expiry, and whether the exact signed link is being used.

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.