strelichl
commented
5 months ago Noting from Slack convo: since team is sticking close to what's in CST for MVP launch of this skill, and on a tight timeline, CAIA will save our content collab for the post MVP version that may have more significant content work.
Content, accessibility, information architecture (CAIA) new initiative collaboration request
Use this ticket to start collaboration on a new initiative with the sitewide content, accessibility, and information architecture (CAIA) team.
Note: If you’re already partnering with us on an initiative, you don't need to fill out this request form. If you don’t have access to your initiative’s CAIA epic, post a message in the #sitewide-content-accessibility-ia slack channel and tag
@Terry Nicholsand@Lily Strelich.About your team
Chatbot Benefits-MicroservicesLuciana MoraisChatbotLeah SpixGrace Goodenough, goodenoughgraceVAInsert name and/or GH handleAbout your initiative
Which of these descriptions best fits the work we’ll partner on?
Select all that apply.
insert descriptionWhat's the nature of your initiative and desired outcomes?
Tell us briefly about your work and the outcomes you’re aiming to achieve.Design and build an updated Disability Claims Status Flow as part of the VA.gov Chatbot. The new Claims Flow will include: Bot can provide a) a definition of the phase, b) a general claim timeline, and/or c) details within the phase (micro-transaction). The bot can direct users to other VA tools (ex. Claims Status Tool, VA.gov pages) where information can be found.At this time, this chatbot can only show a Veteran status information on disability compensation claims. The chatbot will provide the date the claim was filed and the current phase that the compensation claim is in. All other details of the in-progress claims and other claims must be found via the Claims Status Tool or through an agent. To provide a seamless experience across VA platforms and channels, the Chatbot should have the same capabilities in this area as other tools on the VA platform, such as the Claims Status Tool. Responding to select claims status details and not providing details to the veteran could harm the veteran's confidence in the bot over the long term.
Collaboration timeframe
Note: We work on nearly every OCTO product and manage all unauthenticated content on VA.gov, so we will need to prioritize intake requests based on overall workload and VA and OCTO priorities.
Is this work tied to a Congressional mandate, change in law or policy, or upcoming event with a specific deadline?
Where are you at in your timeline?
Tell us briefly about what you're working on now (such as initial discovery, wireframing, or usability research planning) and add any known dates for upcoming milestones or deadlines.
Collaboration cycle
Which phases of the collaboration cycle have you completed?
Select all that apply.
Collaboration cycle ticket
If you’re going through the collaboration cycle, provide your ticket number and link:
Supporting artifacts
Provide links to any supporting artifacts that can help us better understand your initiative and begin collaboration. Include artifacts like your product outline, user flows, mockups and prototypes, or any draft content.
Next steps
@Terry Nichols. We’ll reply within 24 hours to acknowledge receipt. We'll then review the artifacts in more detail and work with you to determine timing for collaboration. Depending on the work, we may schedule a kickoff meeting to better understand how we'll partner together.Tasks