A powerful feature of Usabilla for Apps are campaigns, which allow you to ask a very targeted questions to a targeted set of users. In this article you will find some example questions that you can run in your app.
Note: these examples mostly serve as a source of inspiration. With every survey that you run it's important to carefully consider whether the survey questions work well in your app and whether they will actually generate valuable input.
The examples in this article can be divided into five different categories by the goal they achieve. For each category you can find an example by scanning the QR code with your phone, using the Usabilla Preview app. Be sure to download the Usabilla Preview app for iOS or Android on your phone before scanning these examples.
1. Get to know your users
Knowing who your user is, what they need and which journey they are on is extremely powerful when optimizing your app. Get to know your users by asking them who they are and what they need from you in order to achieve their goals.
Example questions
- What is your goal in our app today?
- What was your main reason for downloading our app?
- How would you classify yourself?
- In which department do you work?
- Do you use our app for leisure or business purposes?
When to ask
With Usabilla for Apps you can target users that open your app either for the first time after downloading the app or after opening the app a few times. This is a good time to ask a user why they downloaded your app or with which gal they open your app today.
Other questions about your users and their expectations of your app are not as much tied to the behavior and journey in your app. A good practice is defining key moments in your app during which a user could be open to answering questions. Examples of these moments are when opening or right before closing the app, when switching to a new view or scrolling all the way to the bottom.
Try it yourself
2. Gauge your users' satisfaction
Once you know your users you will want to learn how they currently experience your app. Ask them how they feel and what they like or dislike. Your satisfaction can be measured overall or it can be tied to a certain feature or area of the app.
Example questions
- Are you happy with our app today?
- Are you satisfied with your search results?
- What is the one thing we can improve?
- How satisfied were you with your delivery / flight / product?
- How would you rate this feature?
- Post-purchase satisfaction: how happy are your users with the purchase process?
When to ask
If you want to tie customer satisfaction to specific features in your app, you can best ask this question right after they've used this feature, or even while they are using it.
General satisfaction can be measured when the user has had some time to interact with the app, so for instance if they have switched to a view different views / sections in your app.
Try it yourself
Try this example multiple times, selecting different smileys and see how the survey flow changes, depending on your response.
3. Measure your metrics / KPIs
Customer-centric teams / companies include the voice of their KPIs or key metrics. Think about metrics such as Customer Effort Scores (CES), Net Promoter Scores (NPS) or Customer Satisfaction Scores (CSAT).
Example questions
- Net Promoter Score(NPS)
- Customer Effort Score(CES)
- Customer Satisfaction(CSAT)
- Success score / Goal Completion Rate(GCR)
When to ask
Some KPIs or metrics are directly linked to features or certain moments in your app. For instance, if you are measuring a CES, this is typically done after a certain flow had finished. CES is for instance often measured after the user has completed a purchase.
If your KPI / metric is more related to an overall feeling, it's good to define key moments during which you can question your users. Normally, it's good to preserve these questions and only show them once a user has had a chance to form an opinion about your app.
Try it yourself
4. Validate assumptions
Usabilla for Apps Campaigns provide a great way to validate assumptions or certain questions that float around in your company. These examples help you to gather input on newly planned features, evaluate existing features or provide extra insights for your A/B tests.
Example questions
- What do you think of this feature?
- What is the main way in which we can improve our app for you?
- The app just crashed. Could you tell us what you were doing right before the crash happened?
- What do you think of this feature? (As part of an A/B test)
When to ask
When you are testing assumptions there is normally a dedicated feature or area of your app to which those features can be tied. An example is running Usabilla as part of an A/B test. When A/B testing possible improvements, a Usabilla survey can for instance run when your users interact with the feature that your are experimenting on.
Try it yourself
5. Out-of-the-box ideas
Lastly, we also like to get creative with our surveys from time to time. Therefore, we will finish off with some out-of-the-box examples of how to use surveys.
Example questions
- Would you like to participate in an in-person user test?
- Message: Welcome to the app, please have a look around and let us know if you have any feedback.
When to ask
These out-of-the-box surveys can run whenever you want them to. Messages are usually tied to certain moments in your app. You will - for instance - want to use in a certain view or when has just opened your app.
Try it yourself
Any questions? Please reach out to our friendly support team.