In https://github.com/cisagov/get.gov/issues/288, we experimented with modifying the Contact Us form to guide users to the right answers so (perhaps) they don't need to submit the form at all. In https://github.com/cisagov/get.gov/issues/289, we tested out the viability of updating the form with a prototype. In #300, we finalized the content updates. Now, let's implement the changes!
Acceptance criteria
[x] Reformat the contact form prototype with updates from the content doc
[x] Test out prototype with existing contact form submissions (acting as the past submitter, would you have been able to find answers and/or reach out at the end using the new form?)
[ ] reach out to Cameron for some examples
[ ] Test out accessibility (Microsoft Forms has accessibility issues, particularly with tabbing through multiple choice options. Accessibility issues will not be addressed in this ticket, but should take note)
[x] Share prototype with team for final feedback
[ ] Replace existing contact form with prototype
[ ] See how new contact work affects helpdesk volume, address any potential issues that come up a week after implementation
Note; This effort will update the Microsoft Form, but will not replace it. We will work on replacing the contact form with our own customized solution in #2011 and #2099
Issue description
In https://github.com/cisagov/get.gov/issues/288, we experimented with modifying the Contact Us form to guide users to the right answers so (perhaps) they don't need to submit the form at all. In https://github.com/cisagov/get.gov/issues/289, we tested out the viability of updating the form with a prototype. In #300, we finalized the content updates. Now, let's implement the changes!
Acceptance criteria
Additional context
Link to Google doc Link to prototype
Links to other issues
Steps for updating the form:
288
289
300
303 (📍 YOU ARE HERE)
Note; This effort will update the Microsoft Form, but will not replace it. We will work on replacing the contact form with our own customized solution in #2011 and #2099