In introducing our "web survey", we're creating a whole new channel for users to answer questions.
It would be relatively straight-forward if our web survey was just a web survey. But we actually like the ability to do multi-part (longitudinal panels) surveys, which means we need some way to follow up with people.
This means users need to be able to start a web survey, but then get notified via chat about a new survey and hop back into the survey. Or, take a web survey, then enter information for payment (i.e. Reloadly) and get a text message later when their payment is successful (or unsuccessful).
For now, we can imagine that the only chat channel is Messenger (can be text/whatsapp in the future).
What, then, would the user flow be for going from Messenger to Web Survey to Messenger ( or Web Survey to Messenger to Web Survey)?
Given that user flow, what do we need to build to support it?
In introducing our "web survey", we're creating a whole new channel for users to answer questions.
It would be relatively straight-forward if our web survey was just a web survey. But we actually like the ability to do multi-part (longitudinal panels) surveys, which means we need some way to follow up with people.
This means users need to be able to start a web survey, but then get notified via chat about a new survey and hop back into the survey. Or, take a web survey, then enter information for payment (i.e. Reloadly) and get a text message later when their payment is successful (or unsuccessful).
For now, we can imagine that the only chat channel is Messenger (can be text/whatsapp in the future).
What, then, would the user flow be for going from Messenger to Web Survey to Messenger ( or Web Survey to Messenger to Web Survey)?
Given that user flow, what do we need to build to support it?