Discord support and web inbox
PulseTickets
Configure ticket panels, staff access, live conversations, transcripts, and analytics.
Open PulseTicketsGetting started
Start with Discord permissions, then create the ticket experience from the dashboard.
Invite the bot
Enable Message Content Intent and Server Members Intent in the Discord Developer Portal before starting the bot.
Choose staff roles
Use the dashboard to select staff and administrator roles. These roles control Discord actions and web inbox access.
Create categories and panels
Define questions, routing, support roles, ticket mode, limits, and the message users click to open a ticket.
Publish and test
Post the panel, open a test ticket, reply from Discord and the web inbox, then close it and verify the transcript.
Ticket modes and access
Each category can use private channels or private threads.
Channel mode
Creates a dedicated private channel with permission overwrites for the opener and configured support roles.
Thread mode
Creates a private support thread and keeps thread membership synchronized when staff roles change.
Category staff
Assign different support roles per category so billing, moderation, and technical tickets reach the right team.
Role cache
Roles, channels, and member roles are cached for fast permission checks and updated through Discord events.
Dashboard pages
The web app mirrors the operational ticket workflow.
Inbox
Read and send Discord ticket messages in real time, claim tickets, change priority, apply tags, and use quick replies.
Panels and categories
Build panel messages, forms, routing rules, limits, staff access, and ticket surfaces.
Transcripts and search
Search past conversations and review message edits, attachments, participants, and closure details.
Analytics and reviews
Track volume, response times, close times, staff activity, ratings, and custom review questions.
Troubleshooting
Most ticket issues come from Discord intents, bot hierarchy, or stale panel configuration.
Messages do not reach the web inbox
Confirm Message Content Intent is enabled and the bot can view the ticket channel or thread.
Staff cannot see a ticket
Check category staff roles, bot role hierarchy, thread membership, and the member role cache.
A panel button fails
Republish the panel if its category was deleted or its configuration changed after posting.
Commands are missing
Restart the bot to run guild command synchronization, then confirm the application command scope was included at invite time.