-
Notifications
You must be signed in to change notification settings - Fork 212
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
Prepare for Contact Center Review | Appoint a Representative MVP #92148
Comments
I have a good outline in place, will focus on adding in screenshots next week. |
I think I've done as much as I can for now, waiting on the following updates in Staging to wrap this up. Authenticated experience:
I may also need a dev's help to confirm the error message for PDF generation is in place and getting a screenshot from a local build (as it may be more accurate than Figma). |
My draft of a Contact Center guide is ready to review! product-guide-appoint-a-representative-1.0.docx Some notes:
@jfinnerty13 would you mind reviewing this by Friday EOD and let me know if there's anything else you think I should call out that may help our Contact Center team assist users with the Appoint MVP experience? 🙏 |
Copy in GDrive for comments and feedback Left my first round of comments @oddball-lindsay |
Thanks so much @jfinnerty13! Here is the updated guide with addressed comments:product-guide-appoint-a-representative-1.0.docx Also uploaded to Github: https://github.com/department-of-veterans-affairs/va.gov-team/tree/master/products/accredited-representation-management/product-documentation/appoint-a-representative/contact-center Going to move on to submitting the Contact Center Review ticket. |
Contact Center Review ticket: #99679 Closing this out, and will use that ticket ^ to track progress and confirm this touch point is good to go. |
Issue Description
As part of the collaboration cycle, we will need to go through a Contact Center Review. The full Contact Center Review process.
Tasks
Acceptance Criteria
The text was updated successfully, but these errors were encountered: