Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build out a prototype of an updated Contact Us form #289

Closed
3 tasks done
h-m-f-t opened this issue May 7, 2024 · 2 comments
Closed
3 tasks done

Build out a prototype of an updated Contact Us form #289

h-m-f-t opened this issue May 7, 2024 · 2 comments
Assignees
Labels
carryover Carryover from a previous sprint content design

Comments

@h-m-f-t
Copy link
Member

h-m-f-t commented May 7, 2024

Issue description

In #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 this issue, let's build a working prototype of the form and solicit more feedback from the team on whether the approach is viable.

Acceptance criteria

  • Using the FAQs as a guide, build a prototype of a new form using the approach started in the duplicate contact us form (if needed, ask @h-m-f-t to be added as a collaborator on the form).
  • Present an MVP for feedback to @cisagov/gov-designers (needn't account for every permutation but should be functional for several common questions)
  • As a team, decide go/no go. If go, create an implementation issue

Additional context

#288 talked about exploring the sending of emails upon submission. We didn't explore that, but that could also be part of the final implementation.

Links to other issues

🔄 Relates to #288

@vickyszuchin vickyszuchin added the carryover Carryover from a previous sprint label May 22, 2024
@vickyszuchin
Copy link

Per guidance, any "In progress" tickets from sprint 45 will be moved over to Sprint 46 noon EST on Day 1.

@kristinacyin
Copy link
Contributor

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
carryover Carryover from a previous sprint content design
Projects
Status: ✅ Done
Development

No branches or pull requests

3 participants