Flow Example - Product Feedback
Feedback from your users is a key component of knowing whether you're heading in the right direction with product updates and new features. A feedback flow should be:
- Explicit and one-topic in the content you're asking for feedback about
- Contain an easily understood rating or open-ended question
- Respect the user's time (they came to your product to do something else) by being concise
Let's walk through building a simple feedback flow. We'll cover:
The final product of your slideout will look something like this when we're done:
Building the slideout
Let's begin by creating the actual content.
First, launch the Flow Builder to create a new flow
There are multiple ways to create a new flow, one is from the flows page in your dashboard by clicking the green Create a Flow button:
Create a Slideout step
Once in the Flow Builder, start by creating a Slideout:
Add a text block
Give the flow some context. Because we have event targeting we are able to say "Looks like you recently built a flow", and you can give short context in the same way.
Add a Ratings form
This will contain both the question you want to ask the user as well as the numerical rating block.
Set the numerical limit to your preference and add a label.
You can also edit the rating text under the numbers.
Change the button text
Setting a Theme
See the Themes page if you haven't already set a theme for your Appcues content.
If you have a Theme you're ready to use, make sure this modal is using it:
Targeting the correct users
To be able to target you'll need the applicable User Properties being sent to Appcues. You can see what you're sending on the "Events and Properties" tab of the Settings section. And recommended User Properties to send are in the User Properties Overview doc.
The targeting below is for example purposes, yours will be different. For this flow, we wanted to target a very specific set of people.
- They needed to be customers
- They needed to have completed their Onboarding (we don't want new users seeing it)
- They needed to have recently completed the action we're asking about
- And, we didn't want to show it to everyone (because we're running multiple surveys and that might inundate a user with flows)
Here's how we did it, explained below.:
First and second, we used our Segments for Customers and Steadystate users ( creating a Segment).
Third is the Session Randomizer property, which each user gets during each session and it changes with each new session. It's on a 100-point scale, so we're trying to target about 40% of users that meet all the other criteria.
Fourth, we'll show this flow if the user has "Clicked create new flow" in the past 4 days. This is an event we send to Appcues from a button click in our application and is how we know the did the activity we're asking about.
Lastly, and this is icing, we didn't want to show a user multiple surveys in a short period of time. We created a specific Segment so users won't see more than one survey per day. It looks like this:
When you're ready you can use Test Mode to see what your modal will look like and publish your flow when you're ready. And remember, you don't need to wait to build all the content you're hoping to build to set this flow live; and you can always iterate on each flow once you know how your users are interacting with them.
Have an awesome feedback form or survey to share? Need some extra support? Shoot us an email at firstname.lastname@example.org and we'll be happy to help.