The company I work at has decided to start building a database of users to extend a current service, but I'm not completely sure how to tackle it.
I believe we should try to make the distinction between registering for a study and registering for our database clear, to be honest to the candidates. But at the same time, I want to avoid bothering the users with excessive forms (and keep the threshold low) and simplify the journey through the process.
Anyway, imagine the following scenario (current flow);
Candidates come to our website to find/participate in clinical trials.
They select a study, and must then fill out a prescreening form to see if they meet the criteria to participate (no contact details involved).
If they pass, the next step is to submit contact details such as name, phone number, address and email address in a contact form.
Done! (But we do not add them to our database as it works right now)
The goal now is, of course, to somewhere in this flow get them to register for the database. So my question is, when and how?
My first thought is to implement a page that users land on if they fail the prescreening form, asking if they want to register to our database to get notified if similar studies (as the one they just chose) come up.
However, I'm puzzled where to propose the registration to our database if they pass the prescreening form, and thought of one of the following:
The form to register for the database includes three fields: Email, password and medical condition of interest.
Ask to registration to the database on the prescreening form as well. This means adding more fields (which I want to avoid).
On the contact form, put in a checkbox and ask if they want to register for the database as well to get further updates.
Upon finishing the contact form, land on a new page asking if they want to register for the database as well.
All of above mentioned option means asking them for their email (again), password and medical conditions of interest.
What to do?