Collaboration Cycle for VA Notify, Digital Notifications Terms and Conditions, Content Updates

VFS product information

VFS team name

VA Notify

Product name

VA Notify

Feature name

Digital Notifications Terms & Conditions page on VA.gov

GitHub label for product

vanotify

GitHub label for feature

No response

Kickoff questions

Toggle kickoff questions

### When did/will you start working on this product/feature? We were recently given additional requirements for SMS notifications from AWS Pinpoint (our provider) that require some minor text changes to the existing page. We are able to send "intent" of changes to continue our work, but would like to get this scheduled over the next quarter so there are no complications with existing or new notification use cases. ### Will your work result in visible changes to the user experience? Yes ### Are you doing research with VA.gov users? No ### Will your work involve changes to... Static pages ### Does your product/feature have Google Analytics tracking and a KPI dashboard in Domo? VA Notify has a Domo dashboard for notification statistics and URL/landing page tracking. The T&C content change we are requesting will not affect GA or Domo. ### Do you need to capture any additional analytics or metrics? No ### Product outline N/A, this is just a couple minor text adjustments/additions to https://www.va.gov/privacy-policy/digital-notifications-terms-and-conditions/ We were recently given additional requirements for SMS notifications from AWS Pinpoint (our provider) that require some minor text changes to the existing page. Without these changes we would be unable to send new SMS (text) use cases and it could impact existing ones should the carriers audit them. 1. Section header "Delivery and messaging rates" must be changed verbatim to "Message and data rates may apply". This is a carrier requirement for SMS notifications on the terms and conditions page. 2. We are required to provide at least one method of help/contact on the page. After talking to our SMS provider, they told us it would be ok to link to our current contact us page somewhere within terms and conditions. https://www.va.gov/contact-us/ 3. Please add additional reference of “T-Mobile” in the list of participating service providers under the section, "Delivery and messaging rates". Please note, “Metro by T-Mobile” is already in the list and must remain as is. ### Verify all relevant materials provided to Governance Team - [X] I have provided all relevant and up-to-date links, screenshots, images, designs, etc. of the as-is version of the product ### Notify the Collaboration Cycle team of this ticket in the vfs-platform-support Slack channel. - [X] I acknowledge that I must notify \#vfs-platform-support after submitting this issue. Kickoff Slack Thread with VFS team: (https://dsva.slack.com/archives/CBU0KDSB1/p1681392085280869)

Recommended Collaboration Cycle touchpoints

Sitewide Content and IA Intake Request

Toggle Sitewide Content and IA Intake Request

##### VFS actions - [ ] Complete the [sitewide content and IA intake request process](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Sitewide-Content-and-IA-intake-request.2124906551.html) - [ ] Link to the Sitewide Content and IA Intake Request ticket below

Staging Review

Toggle Staging Review

#### Before meeting ##### VFS actions - Navigate to reference link: [Staging Review Guidance](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-review) - [ ] Schedule your Staging Review when ready: - Open the [Calendly staging review calendar](https://calendly.com/collaboration-cycle/staging-review) - Select a date and time and click “Confirm” - Add your name and email - Click "Add Guests" and enter the VFS meeting attendees email addresses - Invite all relevant VFS team members, including accessibility support, product owners, and other VA stakeholders - Click "Schedule Event" - [ ] If this product contains any [experimental design](https://design.va.gov/experimental-design/), add the `experimental-design` label and schedule a meeting with DSC to present the research findings. - [ ] Link all artifacts **ONLY** in the Staging Review artifacts section below at least four days before the scheduled Staging Review. **Do NOT add artifacts to Comments section** - [ ] I confirm the environment is available and test users have been provided. - [ ] Please verify your product information in the [Product Directory](https://depo-platform-documentation.scrollhelp.site/getting-started/vfs-product-directory). **Staging Review artifacts** Links to [Staging Review artifacts](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/Staging-review.1810137181.html#Stagingreview-Artifacts) must be added to this ticket 4 business days ahead of the scheduled meeting. Please do not make changes to the product or artifacts during the 4-day review period. #### Required artifacts - [ ] **URL(s) to review the product** - The product should be available on an [approved staging environment](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/staging-environment-guidance-for-vfs-teams). - List pages, sections of pages, and/or user flows impacted by this work. - [ ] **Drupal or Staging URL for updated primary entry point**: the main way Veterans will access the tool through site navigation (not search) - [ ] **Test users and scenarios (when applicable)** - Store [test user information](https://github.com/department-of-veterans-affairs/va.gov-team-sensitive/blob/master/Administrative/vagov-users/staging-test-accounts-accessible-example.md), passwords, and tasks in a `.md` file in the va.gov-team-sensitive repository. - Make sure all user scenarios can be tested, i.e.: in-progress form, submitted form, new form. - [ ] **Link to Sitewide CAIA intake ticket, if applicable.** - [ ] **Completed accessibility testing artifact**: [see instructions and link to accessibility testing template](https://depo-platform-documentation.scrollhelp.site/collaboration-cycle/prepare-for-an-accessibility-staging-review). - [ ] **QA Artifacts**: artifacts that correspond to each of the [QA Standards](https://depo-platform-documentation.scrollhelp.site/developer-docs/quality-assurance-standards). - [ ] Regression test plan - [ ] Test plan - [ ] Coverage for References - [ ] Summary (Defects) reports - [ ] E2E tests - [ ] Code coverage - [ ] Endpoint monitoring playbook #### Not required, but nice to have artifacts - [ ] **Content source of truth**: link to CAIA Content feedback, such as a content source of truth. - [ ] **Information Architecture spec**: link to CAIA IA feedback, such as an IA spec. ##### Platform actions - [ ] Update this ticket with the Zoom recording - Recording URL: - Password: ##### VFS actions - [ ] Review the findings tickets and comment on the ticket if there are any questions or concerns - [ ] Close individual findings tickets when the issue has been resolved or validated by your Product Owner. If a team has additional questions or needs Platform help validating the issue, please comment on the issue ticket. - [ ] After launch, [request an accessibility audit from the VA 508 Office](https://depo-platform-documentation.scrollhelp.site/developer-docs/request-support-from-the-va-508-office#RequestsupportfromtheVA508office-AuditRequest). This is required even if no accessibility issues were found during the Staging Review. - [ ] Share ServiceNow ticket number here: ______ - [ ] Close ticket once Privacy, Security, Infrastructure Readiness Review has been completed, VA 508 Office audit is requested, and all other post-Staging actions are complete

department-of-veterans-affairs / va.gov-team