Increase traffic gate from 25% to 50% from Virtual Agent Chatbot Team

ianpsant commented 2 years ago

Why you're here

Engineering support for:

Redirects that have first been vetted by the Platform Product Support team. If you are requesting a redirect, please submit the Redirect Issue Template
REACT sign-in widgets or feature flags (flipper)
Other engineering support from the Public Websites Team

Note: Apps teams engineers are responsible for flipper implementation related to their products. Our engineers can provide consultation as needed. Read feature toggle documentation

How to submit your request

[X] Complete each area of this intake form that applies to your team's needs. Provide as much detail as you can so we can fully understand your request.
[X] Post a link to this issue: #vsa-public-websites, and in slack tag @brianalloyd, @kelsonic.
[ ] If noted in the guidance below, please schedule any relevant meetings.

When to submit your request

Please submit all engineering requests at least 1 full sprint in advance (so we can work it into our next sprint).

About your app/tool/functionality

Is this request related to a VA.gov tool? If yes, provide a brief description of the tool or functionality:

Previously we worked with the Public Websites to implement a react widget that would display a link to the Virtual Agent Chatbot page (https://www.va.gov/contact-us/virtual-agent/) on the Contact Us page to 25% of unauthenticated traffic.
We want to increase the percentage of people who see the link from 25% to 50% for April 25th release.
The April 25th release is tentative and we'd want to work closely with the Public Websites team to give the Go / No Go on releasing this update for the 25th or whatever the date turns out to be.

Provide links to any available collateral: Please link to existing IA requests, product briefs/outlines, wireframes, prototypes, user research synthesis:

department-of-veterans-affairs/va.gov-team#36319
PR: https://github.com/department-of-veterans-affairs/vets-website/pull/20280

About your support needs

Please select all that apply, and follow related guidance.

Frontend engineering support

[ ] Implementation of REACT sign-in widgets
- Full spec including different states and behaviors:
  - < link to spec >
- Flipper unique id:
  - < unique id >
- [ ] Support for UAT testing or phased roll out of app/tool landing page
- Full spec including different states and behaviors:
  - < link to spec >
- Flipper unique id:
  - < unique id >

Note: Apps teams engineers are responsible for flipper implementation related to their products. Our engineers can provide consultation as needed. Read feature toggle documentation

[X] Other

Increase existing react widget throttle from 25% to 50% of unauthenticated traffic from seeing the link to the Virtual Agent Chatbot. Example of previous implementation: https://github.com/department-of-veterans-affairs/va.gov-team/issues/36319

Desired/target implementation date

What's the ETA for the app/tool launch or the date when you need this request completed? Our team's capacity will determine which sprint the work falls into.

Monday, April 25

Note: As a best practice, PW does not release new products over weekends or holidays. Please plan accordingly.

About your team

Team name: Virtual Agent Chatbot
DEPO product owner: Luciana Morais
Product manager: Ian Santarinala
Designer: Patrick Onesty
FE engineer: Jacob Gacek
Product/team Slack channel: #va-virtual-agent-public

Public Websites internal use

Acceptance Criteria

[ ] Convert this request into a Zenhub epic
[ ] Follow-up with requestor to address any lingering questions/concerns
[ ] Create epic/tickets as needed for the Public Websites team to implement

Definition of Done

Request ticket is closed and implementation tickets created as needed - If you have content requests, please fill out the content intake request form

jilladams commented 2 years ago

@ianpsant & @davidconlon - Sprint 56 started yesterday and Sprint 57 will start 4/25. We'd need to pull this into Sprint 56 (and deprioritize another task), to achieve the requested 4/25 launch date. Should we plan on that priority?

Meantime, I'll check with @ryguyk / @allisonlu on whether our team has the background needed to get this done - since we're new on Public Websites, may require some ramp up, not sure where we are re: the throttling settings on React widgets. Once we know that, can get points assigned.

jilladams commented 2 years ago

Per @ianpsant not required in Sprint 56, can go into 57 and ship asap once complete in that sprint.

jilladams commented 2 years ago

Hey team! Please add your planning poker estimate with ZenHub @ryguyk @allisonlu

jilladams commented 2 years ago

Per sprint planning: may be as simple as flipper access, request in Platform Support (for PW team members)

ianpsant commented 2 years ago

@jilladams Just checking the status of this?

jilladams commented 2 years ago

This is scheduled in our current sprint ending Friday. We are hoping to knock it out early this week and will let you know on ticket once the change is confirmed.

jilladams commented 2 years ago

I have access to Flipper settings as of today. However, this feature isn't easily identifiable in the list.

In issue #36319 the feature is identified as React app data-widget-type="contact-chatbot-cta".
In the PR, https://github.com/department-of-veterans-affairs/vets-website/pull/20280/files, we have show_contact_chatbot as the feature toggle
In vets-website master branch, this appears on line 94: https://github.com/department-of-veterans-affairs/vets-website/blob/master/src/platform/utilities/feature-toggles/featureFlagNames.js#L94
However: in the list of Features for flipper, show_contact_chatbot doesn't appear, or any other reference to contact chatbot:
- Prod: https://api.va.gov/flipper/features
- Staging: https://staging-api.va.gov/flipper/features

I suspect this is just something I'm unfamiliar with how to find. @ryguyk, any chance you can help me poke around and find it today?

Unrelated probably but since I poked at it: There are a few other references to virtual agent things, that seem to be unrelated and are all disabled. https://api.va.gov/flipper/features/virtual_agent_token https://api.va.gov/flipper/features/virtual_agent_auth https://api.va.gov/flipper/features/virtual_agent_bot_a

jilladams commented 2 years ago

Finding: this toggle isn't using Flipper and requires a code change, so reassigning to Ryan.

Slack thread: https://dsva.slack.com/archives/C52CL1PKQ/p1649783390721569

ianpsant commented 2 years ago

@jilladams @wesrowe After speaking with my Product Owner, if this is still going to be ready this Friday, we'd prefer to release it on Monday, May 9th. Let me know if there are any issues with that. Thanks!

allisonlu commented 2 years ago

PR opened and approved: https://github.com/department-of-veterans-affairs/vets-website/pull/21002

I'll merge this first thing on Monday so it can go out with the daily deploy.

allisonlu commented 2 years ago

PR has been merged: https://github.com/department-of-veterans-affairs/vets-website/commit/ec40e182f5ef2bc7914e44d23a8665a9facde363

jilladams commented 2 years ago

FYI @allisonlu that Ian flagged via Slack dm that their team needs this live by EOD Thursday latest, in order to have at least one day to monitor prior to the weekend. (Earlier in the week preferred, if possible, but not critical.) Let me know if that poses issues for us.

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