Ticket panels · team queues · transcripts

Turn Discord questions into an organized support queue.

Create private tickets with custom forms, team routing, clear ownership, service targets, automation, and transcripts. Your team keeps every conversation in Discord.

Everything your team needs

A Discord ticket system your moderators will actually use.

Guardy gives members a clear place to ask for help, staff a queue they can confidently work, and server owners the visibility to improve the whole operation.

Custom ticket panels

Offer buttons or dropdowns for different ticket types, with the right form before each ticket opens.

Private channels or threads

Choose the format that fits your server and keep each conversation limited to the right people.

Clear staff ownership

Claim and close from the pinned header; assign, transfer, prioritize, and tag with /ticket commands that know which ticket you are in.

Queues that show what matters

See unassigned, assigned-to-me, waiting, and breached tickets without hunting through channels.

Service targets and automation

Track response goals, then route, remind, escalate, or close from your own rules.

Transcripts and analytics

Review closed records, measure response times and satisfaction, and find where support gets stuck.

Guardy is a Discord ticket bot for communities that need private support channels or threads, configurable intake forms, staff queues, assignment, service targets, automation, transcripts, analytics, and CSAT. Members and staff handle conversations in Discord; server owners manage the system from the Guardy dashboard.

From request to resolution

Every ticket follows a clear path.

Members get a simple experience. Staff get the context and controls they need at every step.

  1. 01Open

    Start with the right questions

    Members choose a ticket type and complete a form built for that request.

  2. 02Route

    Send it to the right team

    Guardy creates a private channel or thread and routes the request into the right queue.

  3. 03Support

    Keep ownership visible

    The pinned header shows who owns the ticket, its status, and its priority, and every staff action is announced in the ticket.

  4. 04Close

    Finish with a useful record

    Close the ticket, request feedback, and keep a private transcript for authorized review.

Discord-first workflow

Run the whole queue from Discord.

Claim, assign, and transfer tickets. Change status and priority. Add participants, internal notes and saved replies. Your team does it all beside the conversation.

# ticket-042Discord
TICKET #042In progress

Account access

Requester
Maya
Team
Account support
Assignee
Vera
Priority
Normal
First response met
MK

MayaI changed roles and lost access.

VR

Vera · SupportI found the mismatch. I am restoring it now.

TicketsDashboard
OPEN18SLA HEALTH94%WAITING6
Support queueUpdated now
#042 Account accessMaya · VeraIn progress
#043 Report a memberJules · UnassignedNew
#039 PartnershipAri · CommunityWaiting
◎

Configuration healthSet up teams, panels, targets, and automations here.

Built for the whole support team

Simple for members. Powerful for moderators.

Each person sees the tools they need, while the ticket stays connected from opening through retention.

For members

A simple, private way to ask for help.

Choose the right ticket type, provide what staff need, follow the conversation in Discord, add approved participants, and receive a transcript after closure.

  • Buttons and dropdowns on published panels
  • Text, choices, member, role, channel, and file fields
  • Clear feedback for limits, cooldowns, and access rules

For staff

Every ticket has an owner and a next step.

Work from private queues and one pinned ticket header, with the actions and information needed to move a request forward.

  • Claim, assign, unassign, and transfer
  • Status, priority, tags, internal notes, and saved replies
  • Participants, closure with a reason, reopening, and transcripts

For server owners

Shape the workflow without micromanaging it.

Build panels and forms, organize support teams, set response targets, configure routing and automation, choose retention, and understand performance.

  • Guided setup, previews, and panel publishing
  • Manual, round-robin, or least-active assignment
  • Granular ticket permissions without full server admin access

Stay ahead of the queue

Respond on time. Automate what repeats.

Set first-response and resolution targets in business minutes around your working hours, time zone, and holidays. Guardy can pause timing while you wait on the requester and warn the team before a target is missed.

Business hours and holidaysWarnings before a breachWaiting-time pauses
New support ticketActive
  1. WHEN
    When a ticket opensAccount Help panel · any priority
  2. 01
    Route to Account SupportSend the request to the team queue
    Route
  3. 02
    Assign the least-active teammateBalance new work across available staff
    Assign
  4. 03
    Warn before first response is dueNotify the team with five minutes left
    Warn
  5. 04
    Pause the resolution clockOnly while waiting on the requester
    Pause
Every action stays visible in the ticket timeline.

Context that stays useful

Every closed ticket keeps its story.

Guardy turns the conversation into a private HTML transcript and a portable JSON record, including replies, timestamps, reactions, embeds, attachments, and ticket activity. Every record is labeled complete, known gap, or best effort.

  • 01
    Clear transcript statusEach transcript shows whether Discord history was fully captured or whether a known gap remains.
  • 02
    Private, expiring accessHTML is easy to read, JSON is portable, and access links are restricted and expire automatically.
  • 03
    Retention you controlChoose how long content remains available and include ticket data in supported export and deletion workflows.
Read how ticket data is handled

Understand the work

See what your support team needs next.

Track volume, backlog, queue age, response and resolution times, service-target attainment, waiting states, workload, automation outcomes, and requester satisfaction.

Example dashboard · Resolution trendLast 30 days
FIRST RESPONSE P504m 18sRESOLUTION P502h 07mSLA ATTAINMENT94%
4.7/ 5 CSAT

Illustrative requester satisfaction

Optional close feedback, grouped by ticket type and period.

Connect the workflow

Events out. Scoped reads in.

Signed outbound webhooksScoped read-only APIRotatable API tokens

Built for real community work

One ticket system. Every reason to reach your team.

Use the same clear workflow for everyday questions, sensitive reports, applications, access problems, appeals, and community operations.

01

Member support

Give members a private place to ask questions, report account problems, or request help.

02

Moderation reports

Collect the details moderators need before a sensitive report enters the queue.

03

Applications and partnerships

Route structured requests to the right team without mixing them into general support.

04

Purchases and access

Keep order, entitlement, role, and account questions organized and assigned.

05

Appeals and follow-up

Preserve context across closure and an allowed reopen instead of starting again.

06

Community operations

Use tags, priorities, routing, service targets, and analytics across every support workflow.

Ticket system questions

The practical answers.

Clear enough for the member opening a ticket, detailed enough for the administrator choosing the system.

01What does a Discord ticket bot do?

A Discord ticket bot turns a member request into a private support conversation. Guardy also keeps the intake form, team, assignee, status, priority, transcript, and support metrics connected to that request.

02How can members create a ticket?

Members open a ticket from a panel button or dropdown. Servers can provide multiple ticket types so each request starts with the right form and reaches the right team.

03Can I create custom ticket forms?

Yes. Forms can include short and long text, selects, radio choices, checkboxes, member, role and channel selectors, and optional Discord file uploads.

04Can Guardy use private threads as well as channels?

Yes. Each ticket panel can create either a private channel or a private thread, depending on how the server wants support organized.

05How does staff manage tickets?

Authorized staff can claim, assign, unassign, transfer, prioritize, tag, escalate, close, and reopen tickets. Private queues show unassigned, assigned-to-me, and breached work.

06Does Guardy save ticket transcripts?

Yes. Closed tickets can produce private HTML transcripts for reading and JSON records for portability. Guardy also identifies when Discord history contains a known capture gap.

07Can Guardy track response and resolution targets?

Yes. First-response and resolution targets can follow configured business hours, time zones, and holidays. Guardy can warn teams before a target is missed and show breached tickets in a dedicated queue.

08Where does staff reply to tickets?

Staff reply directly in the private Discord channel or thread. The Guardy dashboard is used for setup, queue oversight, records, analytics, and administration.

09How are ticket attachments and messages handled?

Servers choose a retention period that members can see before opening a ticket. Accepted attachments are stored privately, access links expire, and supported data export and deletion workflows include ticket data.

A connected Guardy system

Keep the progress

Turn every request into a better support experience.

Give members a clear place to ask, give staff a queue they can own, and give your server the visibility to keep improving.

Add Guardy to Discord