Communities

Writing
Writing
Codidact Meta
Codidact Meta
The Great Outdoors
The Great Outdoors
Photography & Video
Photography & Video
Scientific Speculation
Scientific Speculation
Cooking
Cooking
Electrical Engineering
Electrical Engineering
Judaism
Judaism
Languages & Linguistics
Languages & Linguistics
Software Development
Software Development
Mathematics
Mathematics
Christianity
Christianity
Code Golf
Code Golf
Music
Music
Physics
Physics
Linux Systems
Linux Systems
Power Users
Power Users
Tabletop RPGs
Tabletop RPGs
Community Proposals
Community Proposals
tag:snake search within a tag
answers:0 unanswered questions
user:xxxx search by author id
score:0.5 posts with 0.5+ score
"snake oil" exact phrase
votes:4 posts with 4+ votes
created:<1w created < 1 week ago
post_type:xxxx type of post
Search help
Notifications
Mark all as read See all your notifications »
Q&A

Welcome to Software Development on Codidact!

Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.

Why most hosting providers support ticket systems allow text only (no formatting)? [closed]

+0
−8

Closed as off topic by Alexei‭ on May 15, 2021 at 18:48

This question is not within the scope of Software Development.

This question was closed; new answers can no longer be added. Users with the reopen privilege may vote to reopen this question if it has been improved or closed incorrectly.

Through the years I have "tasted" several website hosting companies; none of them had Markdown available in their support-ticket-systems (if all any formatting method available).

Why is it? What's so problematic for hosting providers to let their customers comfortably format their support tickets (which is extremely important in cases of complicated problems and can save time and energy for both sides)?

Is there some information security reason for such a support-ticket-system development paradigm?

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.
Why should this post be closed?

1 comment thread

General comments (5 comments)

1 answer

+3
−6

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.

History
Why does this post require attention from curators or moderators?
You might want to add some details to your flag.

1 comment thread

General comments (5 comments)