Post History

**TL;DR Simply not necessary**

Markdown, and other methods of formatting (Word or similar documents, HTML/CSS, Latex, etc.) are used where the document **is** the product. In this case, the support ticket system is purely a means to an end.

* The messages are "just the facts" and meant to be read *only one time*.
* Formatting to add emphasis is not needed - every support ticket is urgent in the eyes of the sender.
* Formatting to handle long documents is not needed - support tickets are usually, and almost always should be, very short.
* There is no training or long-term usage - a user might submit a ticket a year per web site or even much less than that, so any special formatting would likely get forgotten in between uses.
* Users may be experienced with Markdown, or they may be pure System Administrators who have no experience with it at all.
* While customers may pick a hosting company (or other provider) based on quality of the support, they generally won't know the details of the support ticket system (except to know whether it is primarily phone, email or web form based) before they purchase hosting services, so it is not a selling point. *I really can't imagine switching hosting companies because "We support Markdown in our tickets!", when what I really want is a hosting company (and I found one) where the tickets are rarely needed and when they are needed, they are handled quickly.*

In short, there is little benefit to users or the support staff, so why add this feature.