search

i-dot-ai / caddy-chatbot

Caddy is an AI powered co-pilot for customer service functions everywhere.
https://ai.gov.uk/projects/caddy/
MIT License
8 stars 4 forks source link

Improve survey flow #78

Closed AndreasThinks closed 3 months ago

AndreasThinks commented 3 months ago

There is a risk to our current survey flow that we will get duplicate randomisation per call - eg, advisers randomised to not get Caddy might get a second request where they are randomised the other way, or vice versa.

We could fix this by adding an interim step. Suggested workflow below.

  1. We replace the current survey step with a "Please press this button when your call is complete".
  2. If they make another request before that call is completed, we don't change their randomisation - eg, they still do or don't get Caddy
  3. Once they click the "call is complete" button, we store that timestamp and offer the survey at that point.

This should solve the problem so we only have one survey per call.

We could use the random assignment table to stoer the variables - essentially, it now becomes a call table (storing the first caddy query time, random assignmetn and the time the call is closed with survey etc)

@kurtismassey @sdurcan for thoughts? I think this is worth doing before launch, so tagging for MVP.

AndreasThinks commented 3 months ago

Following on from chat with @kurtismassey , we think this is worth doing - we can store the call status (eg, is it open or clsoed) and the random assisgnmetn (eg, random float between 0 and 1) in the caddyEvaluation table, and refer back to it. That should solve our problem.