Feedback Mechanism - Contact Center Review

[ATMiddleton]

Issue Description

Ensure Veteran Support representatives are prepared to answer questions and help Veterans troubleshoot new tools or services on VA.gov.

Tasks

• [ ] _Complete the Contact Center Review form
• [ ] Analytics request
• [ ] Security Review
• [ ] Contact center reviewers provide feedback on your artifacts and training documentation
• [ ] Implement User testing feedback

Acceptance Criteria

• [ ] Scenario 1: Complete the Contact Center Review form

  • The user has the Contact Center Review form.
  • The user fills out all the required fields in the form.
  • The user submits the form.
  • The system saves the form data successfully.

• [ ] Scenario 2: Analytics request

  • The user needs to request analytics for the Contact Center Review.
  • The user provides the necessary information for the analytics request.
  • The user submits the request.
  • The system acknowledges the request and processes it.

• [ ] Scenario 3: Security Review

  • The user needs to initiate a security review for the Contact Center Review.
  • The user provides the required documentation and artifacts for the review.
  • The user submits the review request.
  • The system acknowledges the request and assigns it to the appropriate team for review.

• [ ] Scenario 4: Contact center reviewers provide feedback on artifacts and training documentation

  • The user has submitted artifacts and training documentation for review.
  • The contact center reviewers review the artifacts and documentation.
  • The reviewers provide feedback on the artifacts and documentation.
  • The system captures and displays the feedback to the user.

• [ ] Scenario 5: Implement User testing feedback

  • The user has received user testing feedback on the Contact Center Review.
  • The user reviews the feedback and identifies necessary changes.
  • The user implements the changes based on the feedback.
  • The system verifies the implementation of the feedback and updates the Contact Center Review accordingly.

• [ ] Scenario 6: Configure this issue

  • The user needs to configure the issue for completion.
  • The user attaches the issue to a milestone indicating the completion date.
  • The user attaches the issue to an epic to indicate its association with a body of work.
  • The user labels the issue with the appropriate team(s) (e.g., product support, analytics-insights, operations, service-design, Console-Services, tools-fe).
  • The user labels the issue with the relevant practice area(s) (e.g., backend, frontend, devops, design, research, product, ia, qa, analytics, contact center, research, accessibility, content).
  • The user labels the issue with the appropriate type(s) (e.g., bug, request, discovery, documentation, etc.).
  • The system updates the issue configuration accordingly.

[clantosswett]

@ATMiddleton @starlow00 @UXCamG where are we on this? Is this something that we plan to do soon? If not, let's put in the backlog. Thanks!

[ATMiddleton]

This is the last step in the collab cycle. I will move to backlog.