This post originally appeared on Medium .
In June, Slack announced that they had added buttons to their developer kit. From the moment we saw the announcement, we knew that buttons were going to be a game changer forTroops.
Buttons open up a world of possibilities to make interactions simpler for users in Slack. Commands that require typing two, three or four words can now be replaced with one press. Action URLs can be packaged in a user-friendly button.
Some of the mocks of how buttons were going to be used by other products recreated button experiences that existed in their web-apps. Others allowed users to take discrete actions on the dashboard from Slack.
Immediately, we had a unique idea for using buttons in our onboarding:
Onboarding is a crucial part of the customer journey. Users want to give your product a shot, but they aren’t fully aware of the world of awesome features awaiting them. You want them to use everything because you know it’s awesome, but how can you possibly educate your user on all theuseful things they can do? Not to mention, many modern approaches to this problem, like “guided” product tours, don’t translate to mobile.
Slack buttons give us a unique way to expose each feature, one at a time based on what they found most interesting, across devices . Instead of conforming users to an onboarding process we thought they’d find most interesting, the interactivity buttons enabled a “choose your own adventure” experience.
We think this is just the beginning for how bots will teach users to use them, and develop a path to creating more engagement later on. By placing CTAs to configure Troops in the correct places, we knew we could achieve two goals:
1. Detail each features
2. Get people set up to actually use them
For reference, here’s what our onboarding message in Slack looked like at the time (with two features):