3 channels you can use for user onboarding
User onboarding is a process that has no fixed rules for implementation and its success is how creative and how well you know the product and the users (their habits, experience etc). Below, I will talk about 3 most know channels used for user onboarding and what’s are the pro and cons for each one.
Old fashioned school email
Probably most well-used method to implement the onboarding process.
Consists of a series of emails sent automatically 1, 3, 5 days after registration and can be implemented with any email marketing tool.
Most of them communicate a general message with text instructions, rather boring and often sent at the wrong time (when already I gave up the idea of using the product or when it shows me something I already tested).
Easy way to implement
Everybody does it, so users begin to ignore this kind of messages.
New hype: content marketing
The type of channel with a fulminant growth lately but still rarely used for onboarding process. The basic purpose of this channel is bringing traffic and create awareness but with a strategy well planned, you can benefit from the attention of visitors to enter in the process of onboarding, considering that there are already users of your product (even if they’re not) .
You have a lot of space to describe anything you want to get them to the “AHA moment” (screenshots,videos, podcasts etc).
It is possible that at some point, content no longer is relevant (your product has new features / UI changes etc.).
The newest in town: segmented in-app messages
Though used in prehistoric, messages in the app were considered difficult to implement, given the fact you had to talk to a fellow programmer for any small change. Ability to configure a tooltip only for users who have not entered into the application for 10 days or just for those who have some type of subscription, was almost science fiction.
With onboardX for example, the implementation consists of a single action, namely the introduction of a piece of code on all pages. After that, even if you’re not a coder, you can configure walkthroughs or hints on any page of you app and publish immediately.
Not say you can see statistics about each step of the walkthrough.