Before publishing
Name the panel and write its public description. Choose the channel where the button or menu should appear under Panel publication destination, then choose the Staff team role and add an intake question. Private ticket category (optional) chooses where new ticket channels are created. Leave it at No category to create them without one. You can also require an eligible role, limit each member’s open tickets from that panel, and set an availability window. Choose the Discord message channel where the entry point belongs, then publish the saved draft. Publishing creates a new message from pup. Moving a panel posts it in the new channel and disables the old button or menu. An interrupted publication is recorded automatically when someone uses the panel in Discord. Failed sends show an error and can be retried.Safe changes
Disable pauses new requests. Repair restores a disabled or broken button or menu. Retire permanently closes that panel. Replace retires it and directs new requests to another published panel. Existing tickets keep the request type, destination, staff team and questions they opened with. Editing, moving, replacing or retiring a panel does not change those tickets. Choose a lowercase prefix for private channel names and a maximum number of open tickets. These settings are saved with each request; later edits do not rename existing channels or change how existing tickets are handled.Automatic follow-ups
A panel can send an acknowledgement, follow up with the requester, escalate to staff, respond to inactivity and send a closing message. Configure the steps you need before publishing. Each ticket keeps the steps, request type, answers, priority, staff role, availability and deadline chosen when it opened. If an escalation’s staff role is unavailable, pup shows that the step was skipped. It does not choose a different team. Each step shows whether it completed, was cancelled or failed. Retrying continues the same ticket without opening a duplicate or changing a completed ticket’s destination. Discord’s limits and the server’s access rules still apply.Submit a ticket
Panels can ask for up to five answers: short or long text, a configured choice, a member or channel reference, or a date. Required answers must be completed. Complete the form and submit it to open a private ticket. The opening message includes your questions and answers, including tickets waiting for staff review. Post any files in the ticket channel. Staff and the server owner can read the request and files. pup saves the displayed field labels and answers with the request, so later panel edits do not rewrite it. Keep private questions out of the public description. pup checks a panel when someone clicks it and restores changed formatting. A confirmed missing Discord message marks the panel as needing repair. Panels always have a safe default destination and staff role. An administrator can add routing rules for a request type, selected answer, eligible role and priority. Matching rules route directly to their staff role. Otherwise, the panel uses its default destination.
