PaulCLI logoPaulCLI

Using it on Discord

Ticket open, staff and close flow.

  1. 1

    Member opens a ticket

    The member clicks the panel button. PaulCLI enforces one open ticket per user per panel; if the saved channel was deleted, the stale row is marked closed and a new ticket can be opened.

  2. 2

    Channel permissions are created

    @everyone is denied View Channel. The opener can view, send, read history, attach files and embed links. Manager roles can view, send, read history, manage messages, attach files and embed links. The bot receives view/send/history/manage channels/manage messages/embed links.

  3. 3

    Staff claims

    A manager clicks Claim. The ticket stores claimedById, the button changes to Claimed by <username>, and the channel gets a claim message.

  4. 4

    Staff locks or unlocks

    A manager clicks Lock to deny the opener SendMessages; clicking again restores SendMessages. Staff access is retained.

  5. 5

    Ticket is closed

    The opener or support staff clicks Close, confirms Close & Archive, then the bot archives the transcript, marks the ticket closed, posts an optional log entry, and deletes the channel after 5 seconds.

Transcripts are built oldest to newest and include message id, author id/tag/avatar, bot flag, content, timestamp, attachments and embed count. The standalone dashboard transcript page renders the stored HTML inside a sandboxed iframe.

Manager access

A support manager is either a member with Manage Channels or a holder of one of the panel manager roles.