Yesterday I asked a few questions about who the new users are and how they will be stored.

Today we look at what it means to bring them over. There are quite a few factors that go into who the new users/customers/clients are, where, and how they are stored. At the end of the day, they will need to be integrated into your ecosystem.

There are two approaches with how this can be done. The first is through an initial bulk upload. The second is to bring over “just enough” data to add them to your business applications, and have the users recreate their login account.

With the first scenario, this would ensure the smoothest interaction for your new users where it could just be as simple as providing them an email with a link to regenerate a password as an example. It is also great for small number of inter-related systems. My recent example of having a home loan acquired by my bank is one example.

A second example would be if your business has multiple applications stretching into multiple different areas, but a common login experience. In this scenario, the data already exists in one silo, however it must be associated with the common login. To do that, you would need to create a new account, and then associate it with the data that was conveyed. I did this a few years ago with my medical insurance provider when my plan was sold from the state exchange to the provider.

There are two things that you will need to keep in mind:

  1. Communication with the new user/customer is key so they know what to expect and the process is as seamless as possible.
  2. You must account for the burst in traffic.

This applies not just the users creating accounts for the first time within a short period, but also whether or not you can send out the communications at the same time. Without a plan in place, your system will either fall under the load or your initial communication emails will get flagged as spam and not reach their intended audience.

cab