# Escalating and Deescalating w a Ticket System **URL:** https://meta.discourse.org/t/escalating-and-deescalating-w-a-ticket-system/129661 **Category:** Community Building **Created:** [September 27, 2019, 1:25pm UTC](https://meta.discourse.org/t/escalating-and-deescalating-w-a-ticket-system/129661 "2019-09-27T13:25:47Z") **Posts on this page:** 1 **Showing post:** 2
### Author: ![tobiaseigen](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tobiaseigen/32/539204_2.png) [@tobiaseigen](https://meta.discourse.org/u/tobiaseigen) #### Post date: [September 27, 2019, 5:15pm UTC](https://meta.discourse.org/t/escalating-and-deescalating-w-a-ticket-system/129661/2 "2019-09-27T17:15:05Z")
Have you had a look at [Tickets Plugin 🎟](https://meta.discourse.org/t/tickets-plugin/97914)? I use discourse as a ticket system and fundamentally it’s quite solid and well integrated with discourse core functionality like tags, assign, messaging. There is a need still to create a workable dashboard for monitoring ticket resolution and making sure balls don’t get dropped. More on this over here: > [@Using discourse as ticket system, so no balls are dropped woman\_juggling](https://meta.discourse.org/t/using-discourse-as-ticket-system-so-no-balls-are-dropped-woman-juggling/82698): > > I know there are other topics here floating around about using discourse as a ticket system, but I thought I’d start a fresh one to give a fairly complete picture of how we think discourse can be used with the current functionality, known issues, and what fixes/new functionality might help. This might also be faq material. Would be psyched to discuss with others trying to do the same thing and any workarounds you’ve found that I am missing so far. Also quite pleased to discover a whole genre of… --- _[View the full topic](https://meta.discourse.org/t/escalating-and-deescalating-w-a-ticket-system/129661)._