QC Support Ticket Production Go-Live and Support Request Checklist

This guide provides a final practical checklist for structure, portal/Agent tests, mail/templates, inbound mailbox if used, tasks/CRON, security, backups, version 1.0.42, and the safe details to include when requesting support.

Where this fits in QC Support Ticket

Primary location: QC Support Ticket frontend and administrator interfaces, depending on the permission or failure being tested.

Production go-live checklist

  • Install/upgrade the complete current package and verify 1.0.42 plus packaged integrations.
  • Confirm Authorized-Domain entitlement, Base/Effective tier and healthy Entitlement Revalidation.
  • Create/publish Departments, Categories, Status/Priority vocabulary and Frontend Agents with deliberate Department scope.
  • Publish/test Support Portal and Agent Queue with normal accounts—not only Super User.
  • Submit, assign, reply, attach and close/reopen a test ticket end to end.
  • Verify Joomla Mail, Email Templates and recent delivery diagnostics.
  • If Max inbound email is used, Test the mailbox, Process Now one controlled message, then verify 5-minute task/CRON.
  • Verify all five Scheduled Tasks and configure server CRON if timing matters.
  • Review attachment/guest/security settings and take a current backup before launch.

What to include in a private support request

  • QCST/Joomla/PHP versions and the affected route/action.
  • Base/Effective tier and sanitized entitlement/task status when relevant.
  • Ticket reference, Department, Agent scope or mailbox title needed to reproduce the issue—without customer secrets.
  • Sanitized delivery/mailbox/task error and exact steps to reproduce.
  • Never include passwords, IMAP credentials, legacy keys, session tokens or unnecessary private customer content.

Go-live checklist

  • Production backup completed and restore path known.
  • Support Portal and Agent Queue menu items published with intended Joomla Access levels.
  • Departments/Categories/Agents/fields/workflow reviewed with a normal customer and normal Frontend Agent.
  • Joomla Mail test passes; QCST outbound email/templates and one controlled notification pass.
  • Five current QCST Scheduled Tasks exist once and have appropriate health/cadence; server CRON is configured where traffic is insufficient.
  • Authorized Domain shows the expected Base/Effective tier and verification state; legacy key entry is not relied upon.
  • Attachment limits/protected downloads tested with allowed and rejected files.
  • If used: verified guest flow, Pro satisfaction/canned/internal notes, Max inbound mailbox/analytics/scheduled report each tested end-to-end.
  • Frontend Design/Text checked at desktop and narrow widths.
  • Status tab shows expected installed version/update-site/task health.

Information to collect before asking for support

Record the exact reproduction steps, affected role, ticket reference only when safe, QCST version, domain, Status-tab entitlement/task/update result and the exact sanitized error. The Support tab provides product/version/product code/domain/status/effective tier/Installation UUID without requiring you to share credentials or customer content.

Verify the result

  • Repeat the test with the least-privileged normal role affected by the feature; do not rely only on Super User behavior.

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.