GX Technology : Chatbot - Team Discussions/Minutes

Created by Katie Ross, last modified on Oct 05, 2021

Current Discussion/concerns

Topics:
  • Chargeback model
  • On going Launch issues
    • Risk caching issue - future launches that have a breaking change, if so then we should add random queries string to the settings
      • Ask Techops to see if we can get access to Akami to be able to see what is happening
      • test location options in Backstage Pass to see if it is a specific location issue
    • Smoke test seems to need to be run twice before agent can be promoted toProd
  • ABC onboarding - Help site only
    • Next Steps - ABC feedback page
      • Target Launch date: Jan 28, 2021 
  • Movies Anywhere Title search solutions
    • Bifrost dependency
  • Chatbot 2.0 
    • Target Launch date: Feb 3, 2021
Feature Wish List
FeaturePurpose
Product specific URLs for testing (current Bernard URL is all products)To limit Product teams to their own Agents for UAT and ongoing continuous improvement
Assess PII APIs for listed use cases - GSTECH-3118
  1. Many TV Show and movie titles have first and/or last names that could be affected by PII redaction, also some support for shows is given based on host names (e.g. The View).
  2. Sometimes location redaction being triggered (e.g. "hi bot" is redacted)
  3. Error Codes are often 10 digits and being redacted as phone numbers
Way we can do a data dump of Live Chat tickets to target the top topics and ways that guests ask questionsWhen on-boarding we can use existing live product volume to create training phrases for intents



Recent Discussions
  1. Separate servers to scale
    1. probably worth separating out Disney+ and Hulu to their own
    2. possibly launch with ESPN+ using DDEG products
  2. Next onboarding
    1. ESPN+
    2. Hulubot
  3. When to move to web sockets
    1. need head count (work is 50/50 ish server client .. maybe a bit more server) (possibly 6 sprints)
    2. when we have 4-5k concurrent sessions we will benefit from moving to web sockets
    3. could have a cost benefit to move earlier, possible easier scaling 
  4. Documentation of
    1. Updates - in readme files (server)
  5. review Chatbot 2.2/2.X


Attendees: Kevin, Darryl, Marc, Curtis, Katie

Overview:

  • Title search will be triggered from Dialogflow/server to the client – Action Darryl/Katie to add in intents and triggers
  • Design discussion:
    • This will let the conversation continue in Dialogflow
    • Confirm will send title as text into Dialogflow for next steps
    • Go back  will return to carousel will allow the viewer to view their initial search again
    • Images can be a bit smaller
    • Keep year visible
    • Add info icon that will open to show full text that can be ‘x’ed out to close
    • Remove looping to encourage viewers to scroll through options first
    • Remove left scroll from initial card (prevent viewer from seeing the Movie not found card prior to scrolling through all the surfaced cards)
    • Add end add Movie not found card
    • Selecting a movie will trigger a request to Confirm the title OR Go back option


Was there anything missing from this list? If not I’ll go ahead and update both Confluence and Jira tickets.

Context for future designs: we are looking to handle as much as possible through the server and Dialogflow and keep the Client as simple as possible.

Question for future discussion: Does the background of the carousel impact Accessiblity? Do the thumbnails need an outline for readers to be more effective?

Archived Discussion