Create account without actually creating an account

I'm building a website where users may interact with the company (It is the real estate business) to request a budget, ask for information or other type of interactions. The interactions are made via contact form or other type of request, ex. button to request budget about an specific product.

Note I'm not talking about a simple contact to ask for information about the website, a phone number, etc. It's a more concrete contact about schedule a visit, more information about a specific property and so on.

It isn't an obligation to have the user logged in to start these interactions, but once he got engaged it will be necessary to have a login to proceed or either to buy a product. We have a dashboard where users who already have a login can access all these contacts, supports, history, etc..

To create a better fluid introduction for the user into the web site, I'm thinking about creating the user's account progressively without actually clicking on a button "Create account" (this option will also be available), but, of course, with the user doing all the process. Let me try to explain:

• User access the website and send a message through the form, or other interaction we may have - Need to provide an e-mail.


• The web site will automatically create a "Pending" account for that e-mail address where the user can access the dashboard but with a very limited access, only able to access the "Support" area, for example.


• In the meantime an e-mail will be sent to that e-mail address asking users to access an specific link to add an password and some basic information, such as name, and actually create an account on the web site.

Is it acceptable to create such a process? What would be the bad user experiences by doing this? Or is it a good alternative?

The intention is to auto introduce the user on the environment and already show what he can have, how we are organizing our interactions, provide a good feedback we will keep an history of that conversation or possible purchase on the user "future" account.

Answer

From a user perspective, it is by default clearer if the options are simply:

a. Not have an account
b. Have an account

If you want to create an in-between option, it has to be clear to the user what the distinction is between the new option and options a. and b.

For instance:

• If I get some access to dashboard with pseudo-account, what additional features do I get when I upgrade to real account?


• Do I need to opt-in to some Terms & Conditions for pseudo-account? What additional Terms & Conditions are there for full-account?


• If I get access to dashboard with pseudo-account, without password, how do I login? Or how do I identify myself to get my dashboard?


• Does "pending" mean temporary? How temporary is that?

I am not suggesting a pending account is a bad idea, but it all depends on the design of the in-between option whether

• the additional benefits: smoother transition, less barriers to next step, more choice, etc


• outweigh the additional costs: an additional step to sign on, possible confusion about options.

PS: There may also be some legal barriers to a pseudo-account, depending where you operate (most European countries are quite strict this regard - e.g. Dutch law requires explicit opt-in and forbids any pre-filled check boxes with "I have read and understand terms") and the kind of personal/ contact data you have in your database.