But do you really need a chatbot? Creating design principles that matter.

[ UUID ] c1d2ca29-4554-4d0b-9bdc-b2e3eded720b

[ Session Name ] But do you really need a chatbot? Creating design principles that matter. [ Primary Space ] Digital Inclusion [ Secondary Space ] Openness

[ Submitter's Name ] Hera Hussain [ Submitter's Affiliated Organisation ] CHAYN [ Submitter's GitHub ] herahussain

[ Other Facilitator 1's Name ] Joanna Herman [ Other Facilitator 1's GitHub ] Johanna-hub

[ Other Facilitator 2's Name ] Rebecca Botha [ Other Facilitator 2's GitHub ] rb50

[ Other Facilitator 3's Name ] Olivia Jardine

What will happen in your session?

“It took me 15 clicks to find the information on a local refuge. If you only have 5 minutes alone, that’s at least 10 clicks too many.” This quote from a survivor of abuse prompted Chayn to create a chatbot "Little window" that directs women to the information they are looking for as quickly as possible. It's not a human, and doesn't pretend to be one but not all chatbots are like that.

What should be the design principles for creating "non-tech bro" chatbots that actually add value? We're going to present case studies of chatbots and get participants to rate them on the basis of inclusive design. No coding needed.

What is the goal or outcome of your session?

Coming up with a list of design principles for charities considering chatbots!

Time needed

60 mins