Overview

System Tickets are internal task or issue records created by backoffice administrators — not by end users. They are used to track operational tasks, bugs, configuration requests, or anything that needs follow-up within the admin team itself.

🛠️ Internal Tasks

Track operational work items that need to be done by the admin team: data fixes, configuration changes, investigations.

🐛 Bug Tracking

Log observed bugs or unexpected behaviors for investigation, without creating a customer-facing ticket.

👥 Team Coordination

Use system tickets to coordinate work between brand managers, admins, and the engineering team.

System Tickets vs. Customer Tickets

👤 Customer Support Tickets

Who creates them: End users via the app.
Purpose: User needs help with their account, a bug they experienced, or a question about the service.
Communication: Two-way — you respond to the user.

💻 System Tickets

Who creates them: Backoffice admins.
Purpose: Internal task tracking for the ops or engineering team.
Communication: Internal — notes between admins, not visible to users.

Working With System Tickets

System tickets work similarly to customer support tickets but without any user-facing communication:

  • Create — click New Ticket and fill in the title, description, priority, and assignee
  • Comment — add internal notes as you investigate or work on the issue
  • Assign — assign or reassign to appropriate team members
  • Update status — move through Open → In Progress → Resolved → Closed
  • Link to records — if the ticket relates to a specific user, introduction, or other record, include the ID in the description for easy cross-referencing