# Can incoming Discourse email support replace old ticket portals?

**URL:** https://meta.discourse.org/t/can-incoming-discourse-email-support-replace-old-ticket-portals/43522
**Category:** Support
**Created:** [April 30, 2016, 9:24pm UTC](https://meta.discourse.org/t/can-incoming-discourse-email-support-replace-old-ticket-portals/43522 "2016-04-30T21:24:21Z")
**Posts on this page:** 1
**Showing post:** 2

<div class="post-metadata">

### Author: ![steko](https://avatars.discourse-cdn.com/v4/letter/s/c77e96/32.png) [@steko](https://meta.discourse.org/u/steko)
#### Post date: [April 30, 2016, 10:04pm UTC](https://meta.discourse.org/t/can-incoming-discourse-email-support-replace-old-ticket-portals/43522/2 "2016-04-30T22:04:22Z")

</div>

Have you looked at this topic:

> [@Discourse as a private email support portal](https://meta.discourse.org/t/discourse-as-a-private-email-support-portal/34444):
>
> Purpose We would like to set it up so Discourse can act as a private email support portal for a team. In this mode a single email address will be mapped to a category, all incoming mail will create new messages in that category that can be viewed by all the users with permission on the category. Users will be automatically provisioned as emails come in. Advantages over central email box Historically we have used a central email box for our team “support” this has proven to have quite a few draw…

I don’t think there is a native way of attaching priorities to topics (in your case, tickets) but it could be easily implemented using the [official tags feature](https://meta.discourse.org/t/tagging-support-is-now-part-of-discourse/43334).

---

_[View the full topic](https://meta.discourse.org/t/can-incoming-discourse-email-support-replace-old-ticket-portals/43522)._