Skip to content
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

[Prod] Research chat bot/conversation best practices #162

Open
smarrison opened this issue Apr 12, 2021 · 0 comments
Open

[Prod] Research chat bot/conversation best practices #162

smarrison opened this issue Apr 12, 2021 · 0 comments
Labels
Product For all product-related issues - good for non-programmer types! UX writing for when we need to write stuff

Comments

@smarrison
Copy link
Collaborator

Description

What does the task entail?

Search for best practices from sources like Twilio to see if there is guidance to improve chat bot user experience. Send them to the team in Slack, and if you feel inclined, do a UX audit of the script to improve usability

Skillsets that would be useful for completing this task?

Research, UX writing

Domain - what area does this issue fall into?

Consider selecting a tag from this list:

  • Wireframing
  • User testing
  • Twilio
  • UX writing
  • Graphics

Lifecycle - where is this task in the grand scheme of things? Who should be consulted?

For reference, product should take a first run at things, share amongst the team, then escalate to BASTA team members.

Share with @arjanvfa @lizard12995 @smarrison

Consider selecting a tag from this list:

  • Product review
  • Dev interfacing
  • Organizer interfacing
  • Ready for SK review
@smarrison smarrison added Product For all product-related issues - good for non-programmer types! UX writing for when we need to write stuff labels Apr 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Product For all product-related issues - good for non-programmer types! UX writing for when we need to write stuff
Projects
None yet
Development

No branches or pull requests

1 participant