Collect assister info for each app

codeforamerica / clean

Apply for CalFresh in SF

http://demo.cleanassist.org

MIT License

20 stars 7 forks source link

Collect assister info for each app #519

Open lippytak opened 9 years ago

lippytak commented 9 years ago

Let's know who our users are so we can get in touch and make sure they have a good experience. Possible future use case is to send FU reminders or something.

Next step is to mockup the flow/information and think through an easy way to implement.

[ ] @alanjosephwilliams create view
[ ] @lippytak will populate current user info
[ ] @daguar does backend for at least
- agency name
- POC name
- poc phone
- poc email
- agency <> case relationship (not necessarily an actual relationship...)
[ ] Setup some alert or monitoring process to make sure we actually see when new assisters register
[ ] QA

daguar commented 9 years ago

Drop some thoughts here!

lippytak commented 9 years ago

v1 sketches with dummy copy:

Simple view before basic info that shows
If user selects 'not on this list' then we reveal a few more questions:

Tasks update in the original comment.

daguar commented 9 years ago

One quick thing re above mockups — I find it confusing for the first "you" to refer to the client, and then the second "you" to refer to the assister.

alanjosephwilliams commented 9 years ago

Seems like we should put this into our backlog. I'm moving it now. Feel free to veto or broach during sprint planning.

daguar commented 9 years ago

Yeah I'm mixed on it - on one side I think low ROI (more due to effort) but I also just saw a case that made me want to know who submitted (the dupes issue, one of which is a Daly City address.)

On May 18, 2015, at 10:27 AM, Alan Joseph Williams notifications@github.com wrote:

Seems like we should put this into our backlog. I'm moving it now. Feel free to veto or broach during sprint planning.

— Reply to this email directly or view it on GitHub.