6
6 Comments

Best way to reach out to new users for feedback?

Hi everyone!

Would you happen to have any tips on reaching out to users that have signed up for beta but didn't use the app?

My main goal is to get some feedback from them and see what they liked or didn't like, did they plan to user the app at some point later in future etc.

So far, I see the following options (or a combination of them):

  • Drop them an email basically with some questions: this is the easiest on my side but then at the same time, the question on "how did you like the app" might be a bit too general. Adding too many questions might be a no reply.

  • Send them a "hello" and quick survey: I usually fill up surveys for product but that's just me. I know that some people hate them.

  • Send them a "hello" and offer some time in my calendar.

When you were reaching out, what approach worked the best for you?
Was there ever an email that you have received from a founder that made you want to spend some time on giving feedback?

on December 12, 2021
  1. 1

    You should first focus on passive feedback. I.E. if you have something akin to fullstory, it's really easy to see what went wrong. You can compare them to users who've adopted your product and see what goes different. Of course this is assuming you've already figured your product-market fit and playing to your strengths.

    After that you can ask for feedback. I don't think emailing them is a good option, though. People who haven't engaged with your product won't bother to respond. Frustrated users might but as far as I've understood you're interested in why they didn't adopt your product. Perhaps a "before you go" survey might work but that risks showing it to every user when they first leave the page.

  2. 1

    My email format is usually something like:

    short honest subject tilte (question about X)
    a) v short intro providing info about me + context + mention anyone who intro-ed us
    b) ask with a clear question mark and one sentence about why I'm asking THEM specifically
    c) add value if possible or just keep it short

    follow-up once then no more

    it's been pretty useful/successful so far in requesting feedback

  3. 1

    I've been running into the same problem and would like to know what everyone does about it. My take is this: most people won't respond to requests for feedback, and I think the trick is to iterate on your approach and not to get discouraged.

    1. 2

      Thanks for replying Draco!

      I do confirm what you just wrote - most people don't respond to requests for feedback unfortunately. Our inboxes are so saturated with people or machines reaching out that it's easy to get lost in all that noise.

      I'll be experimenting with a couple different types of those emails in the next days and will update on how did it go!

      1. 1

        Sounds good. You may find this video helpful.

        https://www.youtube.com/watch?v=y3g5EMmt-xM

  4. 1

    Your first line of feedback should be a tool like https://logrocket.com Then you can see what went wrong directly.

    Next try usage exchanges with other app developers - Uclusion is always up for a feedback exchange if your app is anything we would understand.