Wowzers, you're missing all the good stuff!

Your feedback form is very weak, so it's time for an overhaul.
Your users are the easiest source of innovation available to you; Most of them have used other telematics platforms, and they probably have some opinions about which systems were good, and which ones were not (and importantly… why). The success of many front-line workers is limited by the design of the software, but a robust feedback loop can close the gaps in what they need vs what you offer.

Unfortunately (in its current state) your feedback form isn't really up to the task:

1. It lacks the structure and depth to fully capture an idea
2. There is no support for text formatting, file attachments, etc.
3. It keeps a very low profile, and is intended primarily for one-way communication. Any follow-up correspondence is done via email, which is easy to get buried in a busy inbox (especially when it's a shared inbox)
4. There are (at least) 2 different versions of the form (my.geotab.com, support.geotab.com)
5. It is a modal (pop-up) form, which among other things, makes it easy to accidentally close and lose any written ideas

At a minimum, the feedback page should resemble the overall design and capability of the community posts, except that it should be a more intimate exchange with Geotabbers instead of a largely public discussion thread.

In a best-case scenario, your redesign should (in my opinion) include the following features:

1. Identical text formatting options as the community posts
2. Improved file sharing options
   1. Fix error when uploading .txt file [You do not have enough privileges for this action.]
   2. Make [All files *.*] the default option in the file picker by removing the list of …….It looks very messy, and will get messier as you recognize other useful filetypes (of which, there are many)
   3. Allow multiple selections in the file picker
3. Make the form a full-size page in a new tab
4. Automatically save (like an email draft) the user's work. This will:
   1. Allow time to research an issue more thoroughly before 'publishing' the feedback (gather reproduction steps of a bug, etc.)
   2. Prevent accidental loss of work due to browser crashes or similar events
5. Fix the obvious issue with nested 'ordered lists'... It should have been 2a, 2b, 2c and then 4a, 4b
6. Maintain access to previous feedback and responses. Sometimes the original post might seem too confusing or lack enough information, so it's essential to continue the conversation (much like the community posts)
7. Include guidelines + recommendations (writing prompts) for creating high-quality feedback. Fixes will occur faster if all the relevant information is available at the beginning. Do not put them as 'hints' inside the text box that users will type into. They should be visible after writing begins.

Please and thank you