I suppose the name gives it away: In-app feedback<\/a> is customer feedback that you collect directly within your product. <\/p>\n\n\n\n So, when we collect in-app feedback, we basically ask customers to share their experiences and opinions while using the product. <\/p>\n\n\n\n Here\u2019s an example of an in-app feedback widget from one of our customers. <\/p>\n\n\n The image shows just the welcome screen, of course. Once the user agrees to complete the survey, they see questions asking about the person\u2019s attitude towards AI plus information about how they use a feature currently available in the product.<\/p>\n\n\n\n Here\u2019s another example of a company asking customers to vote on new features.<\/p>\n\n\n Once again, this is the intro screen, and once the person clicks on the call to action, they\u2019re taken to the next section with the actual feedback mechanism.<\/p>\n\n\n\n There is quite a number of reasons, actually. If you don\u2019t mind, I\u2019m going to leave out the goals for collecting in-app feedback. I\u2019ve discussed them at length in my dedicated guide on the topic<\/a>, and I recommend that you check it out for more info. <\/p>\n\n\n\n Here, I want to focus on why in-app feedback is not an option for a SaaS company. <\/strong><\/p>\n\n\n\n As I said, there are several reasons for focusing on in-app feedback, and they all come down to one thing: <\/p>\n\n\n\n Everything users share will be in context of their actual and present experience. <\/p>\n\n\n\n The person doesn\u2019t recall past experiences, nothing is clouded in their memory, and certainly, they aren\u2019t distracted by anything else. <\/p>\n\n\n\n They are using the product, and they are telling you about it. <\/p>\n\n\n\n The problem?<\/strong> Well, as I mentioned in the introduction, getting results from in-app surveys takes more than just firing up the widget the moment someone logs in. <\/p>\n\n\n\n (In fact, THAT is the last thing you should do, but I\u2019m getting slightly ahead of myself\u2026<\/em>)<\/p>\n\n\n\n You need to optimize the survey, and ensure that it can engage a person while NOT interrupting their flow at the same time. <\/p>\n\n\n\n Let\u2019s see how to do that. <\/p>\n\n\n\n I do appreciate that this advice may sound vague. What does it mean to \u201ctime a survey well,\u201d<\/em> after all. <\/p>\n\n\n\n Bear with me, please as this is important. <\/p>\n\n\n\n You see – Your in-app feedback tool, most likely, offers a whole range of targeting options, including trigger events. <\/p>\n\n\n\n Trigger events let you define at what moment the survey is shown to users in your Target Audience. <\/p>\n\n\n\n In my tool, Refiner, you can choose between time delay, page visits, or event-based triggers, or launch surveys manually.<\/p>\n\n\n This means that you have a full control over when to display in-app surveys, and you should avail of it fully. <\/p>\n\n\n\n Now, some in-app surveys are fine to trigger immediately after the person begins their session. But others aren\u2019t. Sometimes, it\u2019s better to wait a while before triggering the survey, or even, launch it only when the person reaches a particular feature in the app. <\/p>\n\n\n\n This helps boost the performance of your in-app survey in several ways:<\/p>\n\n\n\n Finally, timing helps you make the survey relevant.<\/strong><\/p>\n\n\n\n Let me share a negative example to illustrate this. <\/p>\n\n\n\n I just signed up for a new tool to help promote my content. I created the first asset with the tool – a short video. The task took 5 minutes to complete, and the process was easy and pretty much automated. <\/p>\n\n\n\n But this wasn\u2019t the only thing I could do with the tool. In fact, apart from creating the asset, I haven\u2019t done anything meaningful with the app. <\/p>\n\n\n\n And yet, just when I completed the (pretty much automated process,) the app displayed an in-app NPS survey\u2026<\/p>\n\n\n\n Needless to say, I haven\u2019t even had the time to make any lasting opinions about the app, let alone be able to decide whether I\u2019d recommend it to anyone. <\/p>\n\n\n\n I\u2019m going to explain this best practice with some data we\u2019ve collected. <\/p>\n\n\n\n In 2022, we analyzed 500 in-app surveys<\/a> that generated 7,963.216 views and 1,344.251 responses. <\/p>\n\n\n\n One of the factors we evaluated was the effect of the survey\u2019s length on the completion rate. Unsurprisingly, we discovered that the longer the survey, the lower the response rate becomes. <\/p>\n\n\n As you can see from this data, one-question surveys (like NPS or CSAT) generated the highest response rate. <\/p>\n\n\n\n Surveys with 2 – 4 questions held roughly at the same level. <\/p>\n\n\n\n Anything longer, and the response rate started to drop. <\/p>\n\n\n\n What\u2019s the lesson here?<\/strong> Response rates drop with every new question added to the survey. So, be mindful that every new question you add to your in-app feedback widget is likely going to reduce the results you\u2019re going to get. <\/p>\n\n\n\n This doesn\u2019t mean that you should launch only short surveys. Far from it. But keep in mind that if you want to generate meaningful results from a long survey, you need to deliver it to a large enough audience segment. Only this way, you can get such feedback with a lower response rate. <\/p>\n\n\n\n Tell me, which of these two surveys you\u2019d be more likely to take?<\/p>\n\n\n Yeah, me too\u2026<\/p>\n\n\n\n Both surveys ask the same question. <\/strong>And yet, that answer box in the first example looks so intimidating, doesn\u2019t it? <\/p>\n\n\n\n So, when designing in-app survey, make sure that you choose a question type that:<\/p>\n\n\n\n That\u2019s exactly what I did in the other example. I\u2019m asking the same question, and it matches my objective for this particular campaign. <\/p>\n\n\n\n But I\u2019m also making it ridiculously easy for the person to respond. All they need to do is select one of the available options and they\u2019re done. <\/p>\n\n\n\n This in-app feedback best practice ties in with what I discussed above. Sometimes, the easiest way to get someone to complete a survey is to make it idiotically simple to do so. And when it comes to surveys, the best place to simplify the survey is the response field. <\/em><\/p>\n\n\n\n Again, look at the two examples from the previous point to see it. The comment box is big, empty, and intimidating. The list of options looks so much simpler in comparison.<\/p>\n\n\n\n Depending on your survey, you could simplify it even further and use a rating. Nothing\u2019s more simpler than choosing a number or an icon. <\/p>\n\n\n The point here is to make providing feedback effortless. So, whatever you can do to simplify the response field, do it. <\/p>\n\n\n\n\n Every in-app feedback tool let\u2019s you launch a survey in two ways – Start from scratch or use a template. But it\u2019s only natural to want to design a custom survey from scratch. <\/p>\n\n\n\n But equally much can be said about using a template:<\/p>\n\n\n\n TIP: <\/strong>Refiner comes with a whole library of in-app survey templates<\/a> optimized for every scenario: CSAT template<\/a>, UX, growth, product, and more. <\/p>\n\n\n Any kid will tell you that the magic word is please<\/em>.<\/p>\n\n\n\n Every copywriter will disagree\u2026<\/p>\n\n\n\n Please might be a power word in every day life. True. But when you\u2019re trying to convince someone to stop what they\u2019re doing and offer you their time, the actual power word to use is\u2026 <\/p>\n\n\n\n BECAUSE<\/em><\/p>\n\n\n\n In his book, \u201cInfluence: The Psychology of Persuasion<\/em>\u201d Robert Cialdini explains it:<\/p>\n\n\n\n \u201cA well-known principle of human behavior says that <\/em>when we ask someone to do us a favor we will be more successful if we provide a reason<\/em><\/strong>. People simply like to have reasons for what they do.\u201d<\/em><\/p>\n\n\n\n This advice applies to collecting in-app feedback, too. <\/p>\n\n\n\n If you tell users why you\u2019re asking them for help, and provide a valid reason, they\u2019ll be more likely to offer you their time and insights. <\/p>\n\n\n (An example of in-app feedback clearly explaining the reasons for asking for insights.)<\/em><\/p>\n\n\n\n I admit that in-app surveys (and surveys in general) are harder to A\/B test than landing pages or websites. We can\u2019t split test our audience, and so on.<\/p>\n\n\n\n But it doesn\u2019t mean that it can\u2019t be done. Far from it, and there are two ways to do it, actually.<\/p>\n\n\n\n In this option, your goal is to test how well the audience responds to the survey overall. You\u2019re not looking to test anything in particular, just validate if the survey is relevant. <\/p>\n\n\n\n To do that, create a small subsegment of your target audience, and trigger the survey for them. <\/p>\n\n\n\n Monitor response rate, and the quality of the feedback to see if the audience finds your survey clear to understand and complete. <\/p>\n\n\n\n Running split tests on surveys a little more tricky but can also be done. In this case, you need to create two small segments of your target audience – the control group and the test group. Then, you need to create two versions of your survey, differing by the factor you want to test – the question, question type, survey type, etc.<\/p>\n\n\n\n Then you run both surveys for their respective segments for a limited time, and compare results. <\/p>\n\n\n\n As I said, it\u2019s tricky and a little time-consuming but it can be done. <\/p>\n\n\n\n Naturally, you need the entire customer base to see some surveys. Not all of those people will complete those, of course. But the survey is relevant to all users. <\/p>\n\n\n\n But that\u2019s actually a rare occurrence. In most cases, the trick to getting highly-relevant audience insights is to trigger the survey to the most relevant people only. <\/p>\n\n\n\n PRO TIP:<\/strong> Create custom audiences based on specific criteria like activity, events, and so on. <\/p>\n\n\n\n For example, this segment includes customers who have engaged with our support in the past 7 days, and allows me to survey them about the experience. <\/p>\n\n\n A common challenge with surveys is that you can\u2019t make the widget too big. It just wouldn\u2019t look too well.<\/p>\n\n\n\n At the same time, there is often quite a lot you might want to tell the customer about the survey. <\/p>\n\n\n\n One hack that works really well is to embed a video as the survey\u2019s introduction. <\/p>\n\n\n\n The video player will ensure the widget is small, but at the same time it will boost engagement AND help you communicate all what you need to tell the customer. <\/p>\n\n\n Another common challenge I hear companies face is deciding where to place the widget in the app:<\/p>\n\n\n\n All seven placements have its pros and cons, so let me revert to our research<\/a> once again to explain how each works. <\/p>\n\n\n In our study, the centre of the screen placement performed the best. Surveys placed at the centre of the top of the screen came second, with the rest of the placements performing pretty much similarly, <\/p>\n\n\n\n But there is something worth noting – The second-best performing placement \u2013 top-center slide in \u2013 was also the least used survey placement in our data set. This fact may have attributed to its higher performance.<\/p>\n\n\n\n This is perhaps more of a personal preference than a best practice but I still do believe that it has merit. <\/p>\n\n\n\n You see, I always prefer when the company sounds, well, human in their surveys. Instead of just asking me a dry question, they communicate with me the goals of the survey, and address me directly. <\/p>\n\n\n\n I am a customer, after all. They are not sending a random survey to a list of contacts purchased form who knows where. We have a relationship already. And so, it only makes sense that they communicate with me accordingly. <\/p>\n\n\n\n It certainly make me more likely to respond to their survey. <\/p>\n\n\n Refiner is in-app survey tool<\/a> for web and mobile apps, built specifically for SaaS and digital products that want high-quality contextual feedback inside the product, not in random email blasts.<\/p>\n\n\n\n With Refiner, product and CX teams are able to run targeted microsurveys in their web app or native mobile apps, and collect feedback to make better product decisions and improve customer experience based on what their real users are doing.<\/p>\n\n\n\n The whole idea is simple. You drop Refiner into your app, show beautifully branded surveys at the perfect moment, and get highly valuable insights instead of noisy, low-intent feedback. Refiner focuses on perfectly timed in-product micro surveys and gives you advanced targeting so you can always ask the right question, to the right segment, at the right time.<\/p>\n\n\n\n What you can do with Refiner<\/strong><\/p>\n\n\n\n If you are running a SaaS or mobile app and want serious, in-app survey infrastructure for product feedback and customer experience, Refiner might just be the solution you’re after.<\/p>\n\n\n\n These are 11 absolutely best best practices for collecting in-app feedback. <\/p>\n\n\n\n Naturally, you don\u2019t have to implement them all. Not at the same time, at least. But keep them in mind as you\u2019re launching the next in-app survey. <\/p>\n\n\n\n Good luck!<\/p>\n\n\n\n\n In this guide, I’ll show you the best practices for collecting in-app feedback. Before we get to that, though, let\u2019s run through some basics quickly. What is in-app feedback? I suppose the name gives it away: In-app feedback is customer feedback that you collect directly within your product. So, when we collect in-app feedback, we […]<\/p>\n![\"Example](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-1024x542.jpeg\")
<\/figure><\/div>\n\n\n![\"Another](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image.png\")
<\/figure><\/div>\n\n\nBut why bother? Why launch in-app surveys at all?<\/h3>\n\n\n\n
\n
11 Best Practices for Collecting In-app Feedback<\/strong><\/h2>\n\n\n\n
#1. Time your in-app feedback right<\/h3>\n\n\n\n
![\"Setting](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-1.jpeg\")
<\/figure><\/div>\n\n\n\n
#2. Optimize survey length for your objectives<\/h3>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-1.png\")
<\/figure><\/div>\n\n\n#3. Use relevant question types<\/h3>\n\n\n\n
![\"In-app](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/Example1.jpg\")
<\/figure><\/div>\n\n![\"In-app](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/Example2.jpg\")
<\/figure><\/div>\n\n\n\n
#4. Use visual clues to collect feedback faster<\/h3>\n\n\n\n
![\"In-app](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/Example3.jpg\")
<\/figure><\/div>\n\n\n#5. Don\u2019t try to reinvent the wheel. Use a proven template.<\/h3>\n\n\n\n
\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-2.jpeg\")
<\/figure><\/div>\n\n\n#6. Tell users why you\u2019re asking for feedback<\/h3>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-3-1024x542.jpeg\")
<\/figure><\/div>\n\n\n#7. Test your surveys<\/h3>\n\n\n\n
Run a small test survey to evaluate response<\/h4>\n\n\n\n
A\/B test the survey<\/h4>\n\n\n\n
#8. Segment the audience<\/h3>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-2-1024x593.png\")
<\/figure><\/div><\/div><\/div>\n\n\n\n#9. Use video to keep the widget small but generate greater engagement<\/h3>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/04\/image-1.jpeg\")
<\/figure><\/div>\n\n\n#10. Placement<\/h3>\n\n\n\n
\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-3.png\")
<\/figure><\/div>\n\n\n#11. Be personal<\/h3>\n\n\n\n
![\"\"](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/image-4.png\")
<\/figure><\/div>\n\n\nBest tool for collecting in-app feedback: Refiner<\/h2>\n\n\n\n
![\"In-app](\"https:\/\/refiner.io\/blog\/wp-content\/uploads\/2024\/05\/Refiner-in-app-1024x406.png\")
<\/figure>\n\n\n\n\n
And that\u2019s it\u2026 <\/strong><\/h2>\n\n\n\n