Professional Ticket Openings & Handling
First impressions matter. When a user opens a ticket, they are looking
for clear communication, professionalism, and swift assistance.
How to Greet a User (The Standard Opening)
Whenever you claim a ticket, always begin with a polite, structured
greeting. Never just say "hey" or "what do you need."
For standard tickets you can solve:
"Hello [Username], thank you for reaching out to support! My name is
[Your Name], and I will be assisting you today.
Could you please provide a bit more detail about the issue you are experiencing?
(Screenshots or error codes are highly appreciated!)"
For tickets that require a higher-up (Payment, Boosts, or unresolved complex issues):
Greet the user professionally first, state that you are looping in the
right person to help them, and tag them directly in the same message.
"Hello [Username], thank you for reaching out! [Tag Owner or
Higher-up] will be with you as soon as they are available. Thank you for your patience!"
Handling Common Cases
Case A: The user opens a ticket but says nothing (Blank Ticket)
What to do: Ping the user with a friendly greeting and ask them how you
can help. If they do not respond within 24 hours, send a follow-up warning text before
closing the ticket due to inactivity.
Case B: You are unsure what the underlying problem could be
What to do: Never sound unsure or guess in front of the user. Do not say
"I don't know" or "Maybe try this?" Instead, confidently tell the user
you are looking into it (e.g., "Thank you for the details, let me investigate this
for you right away"). Then, immediately ask for help in the staff chat to get
the correct solution.
Case C: The user is angry or frustrated
What to do: Remain calm and professional. Acknowledge their frustration
without taking it personally ("I understand this is frustrating, let's get this
sorted out for you"). Focus strictly on the facts of the problem. Never argue
back.
Ticket Management & Triage (Trainee Protocol)
Trainees are expected to help manage the ticket queue actively.
However, permissions vary depending on the ticket type. Never guess on restricted or
specialized tickets.
1. General & Technical Tickets
Trainee Action: Full clearance to handle.
These are your primary responsibilities. Answer these to the best of your ability
using our standard troubleshooting steps and FAQ guidelines.
2. Premium Tickets
Trainee Action: May only reply if 100% sure of the answer.
If you have even a slight doubt about a premium feature, perk, or issue, do not
reply. Leave it for a higher-up to handle.
3. Specialized Tickets
| Ticket Type |
Action |
Instructions |
| Payment & Billing |
Escalate Immediately |
Tag the Owner. |
| Server Boosts |
Escalate Immediately |
Tag @Sanji. Sanji handles all boost rewards, perks, and issues. |
| Collaborations / Partnerships |
Freeze Ticket |
Do not write anything. Leave the ticket completely blank and let the
higher-ups handle the conversation from the start. |
Support Chat Guidelines
The main support chat is meant for fast-paced help and triage. It keeps
the community moving without overloading the ticket queue, but it must be managed
efficiently.
1. The Quick Resolution Rule
If a user asks a question in the support chat that can be answered in 1 to 2 messages,
resolve it right there. Always remain helpful, polite, and brief.
2. When to Direct to a Ticket
If an issue requires troubleshooting, looking at account details, or extensive
back-and-forth conversation, do not try to handle it in the support chat. Move it to a
ticket immediately to keep the chat clear and ensure privacy.
Examples of ticket-worthy issues: Tech bugs, billing/payment problems,
premium perk issues, or anything requiring logs/screenshots.
How to direct them:
"Hey [Username], since this requires a bit of
troubleshooting/sensitive info, please open a ticket in [#channel-name]. We'll get
this sorted out for you right away!"
The Chain of Command & Tagging Protocol
To maintain order and professionalism within the team, all staff
members—especially Trainees—must respect the Chain of Command. Never jump ranks
unnecessarily or tag high-level staff for minor issues.
Who to Tag When? (Strict Rules)
-
Tag a Higher-Up
For collaboration inquiries, partnership proposals, or complex bugs that have
been verified but remain unresolved after checking the staff chat.
-
Tag the Owner
Strictly and exclusively for Payment & Billing issues (failed transactions,
subscription issues, refund requests) or catastrophic server emergencies. Do not
tag the Owner for anything else if you weren’t told to do so.
Respect the Process
Before tagging a Higher-Up or the Owner on an unresolved general issue, always post your
question in the staff chat first. Give your team members a chance to help you before
escalating up the chain.
