Ticketing Dashboard Health and Attention Queues
Use the Ticketing dashboard to spot payment retries, refund work, disputes, near sell-out tickets, draft events, sale-window blockers, abuse signals, and operational health issues.
Article guidance
The Ticketing dashboard is the cross-event operational view. It is not just a sales summary. It pulls together current ticketed events, orders, refunds, disputes, sale-window blockers, operational health, and first abuse signals so the team can decide what needs action before customers or gate staff find the problem.
Attention queues
- Failed payment retries show orders where the buyer may need a fresh payment link or support follow-up.
- Pending or failed refunds show finance actions that are not finished.
- Open disputes show chargebacks that need evidence or outcome tracking.
- Near sell-out ticket types help teams watch capacity pressure.
- Draft events show setup work that has not launched.
- Sale-window blockers flag ticket types that may not be available when expected.
- Abuse watch highlights repeated failed payments, high same-email paid-order volume, repeated promo use, and open dispute pressure.
Operational health checks
- Stripe readiness for paid ticket sales.
- Stripe webhook signal for payment, refund, and dispute updates.
- Ticket PDF generation health.
- Recent scan activity for live gate confidence.
- Queue depth warnings for stale queued work.
- Scheduled ticketing command freshness, such as unpaid-order expiry, no-show marking, issued-order repair, ticket PDF repair, and scheduled report generation.
How to use it
- Start with red or warning states: Open the queue item rather than treating the dashboard as a passive report.
- Follow the link to the event record: Most rows link to the order, refund, dispute, event, or report area that needs action.
- Record the action: Use notes, refund recovery, dispute response, or setup changes so the audit history explains the resolution.