SP SMMPanelz Docs

Tickets is client support: every conversation a client opened from their own dashboard. Live admin: smmpanelz.com/go-admin/tickets.

Reading the screenshots. Blue boxes mark a data value, blue numbered badges mark what you click, client names and subjects read as user1 and Ticket subject 1

Page anatomy

Tickets page with Pending, Answered and Closed tabs, Add ticket, Show unread and the ticket table
The ticket queue. State tabs, then Add ticket, Show unread, the search block and the table.
#ElementWhat it does
1Add ticketOpens a ticket on a client's behalf — use it when they wrote to you elsewhere.
2Show unreadFilters to the tickets you have not read. This is the switch to leave on.
3SearchFinds a ticket by Ticket ID, Subject, Message or User.
4Search fieldChooses which of those the search matches.
5Answered tabTickets you replied to. Pending is the one that means work.
6OptionsThe per-ticket menu — open it, and close or reopen it.

Ticket states

TabRead it as
All (n)Every ticket, with the total in brackets.
Pending (n)The last message is the client's. This is your to-do list.
Answered (n)You replied and the ball is in their court.
Closed (n)Finished. A new message reopens it.

Leave Show unread on and work the Pending tab. Those two together are exactly the tickets that are waiting on you, and nothing else.

Column reference

ColumnMeaning
IDThe ticket's number. Quote it when you talk about the conversation.
UserThe client who opened it.
SubjectThe one-line summary the client wrote.
StatusPending, Answered or Closed.
CreatedWhen the ticket was opened.
Last updateWhen anything last happened on it — sort by this to see what is going stale.

Working the queue

  1. Open Pending. Newest first is fine for speed; oldest-first is fairer to clients who have waited.
  2. Read the whole thread before you answer. Half of the "not delivered" tickets are answered by the order's own Remains value.
  3. Get the ID. Ask for the Order ID when it is missing — it turns a guessing game into one search.
  4. Answer, then close. An Answered ticket that never gets closed inflates the queue and hides the real backlog.
  5. Fix, don't just reply. If the cause is a provider or a service limit, fix it before you write back — otherwise the same ticket returns tomorrow.

On a phone

The tickets page on a phone
Phone view. Leave Show unread on and work the Pending tab; the table scrolls sideways to reach the Options menu.

Troubleshooting

The queue is full of Pending tickets

  1. Work them oldest-first, and close the ones already resolved.
  2. Group them: if many are about one service, fix the service and answer them together.

A client says they never got a reply

  1. Check whether the ticket is Answered but not Closed — the reply exists.
  2. Check the client's email on Users; ticket notifications go to that address, and a typo means they never see them.

The same client opens ticket after ticket

  1. Read the history — a repeated complaint is usually one unfixed root cause.
  2. If it is abuse rather than support, Suspend from the client's row actions; it is reversible.