Workflows & analytics
Workflows turn a basic ticket system into a repeatable support operation. Configure service targets, automatic actions, reusable replies and tags in Workflows, then use Analytics to measure whether the process is working.
SLA policies
An SLA policy defines how quickly staff should provide a first response and how quickly a ticket should reach resolution. SLA targets can be associated with a ticket panel so different support areas can have different expectations.
Time between ticket creation and the first qualifying staff response.
Time between ticket creation and ticket closure/resolution.
Advance warning before the SLA is actually breached.
Discord role that can be notified when configured warning/breach behavior requires escalation.
Use targets that reflect your staff coverage. A five-minute target looks impressive but becomes meaningless if your community has no 24/7 support coverage.
Ticket automations
Automations react to ticket events. A rule can be scoped to a particular panel and/or priority so it does not affect every support workflow.
Supported actions include adding a tag, changing priority, sending a message and pinging a configured role. Keep automation chains simple; if several rules respond to the same event, document why each one exists so staff are not surprised by multiple actions.
Saved replies
Saved replies are reusable staff responses for common situations. Examples include requesting evidence, explaining expected response times or providing a standard troubleshooting checklist. Staff can select them directly in the ticket workflow instead of copying from an external document.
Write saved replies as a starting point rather than a robotic final answer. Staff should still personalize details that matter to the member's case.
Ticket tags
Tags help organize tickets without changing their priority. A ticket might be tagged Billing, Bug, Staff Report, Awaiting Evidence or Escalated. Use a controlled tag list so analytics and staff searching remain meaningful.
Analytics overview
Open Dashboard → Analytics and select a licensed server. Submitt aggregates operational records from tickets and applications into a set of performance indicators.
Ticket health metrics
Priority distribution
Priority distribution shows how support volume is spread across Low, Normal, High and Urgent cases. If nearly every ticket becomes Urgent, the priority system has lost meaning. Adjust staff guidance or automation rules so priorities continue to represent actual urgency.
Staff performance
Staff metrics can include claims, first responses and closures. Use these figures alongside schedules, role responsibilities and ticket complexity. A reviewer who handles fewer but more difficult escalations should not automatically be considered less productive than someone closing simple requests.
Application outcomes
Application reporting summarizes acceptance/denial and other outcome states. Track trends over time to understand whether a recruitment form is too permissive, too restrictive or attracting the wrong applicant audience.