The moment users have to decide where to begin, they are already postponing the reply.
A lighter way to get a response from users who signed up, but never started using the product.
This page is less of a product pitch and more of a note about the feedback mechanism itself. The premise is simple: the more effort it takes to write a reply, the fewer replies you get. If the user can choose inside the email instead, the chance of getting a response goes up.
So the channel stays the same, email, while the interaction changes from a free-form reply to a simple choice inside the message.
Purpose
Test whether we can collect more reasons from inactive signups with less effort required from the user.
Channel
Keep email as the familiar touchpoint, but change the user's action from writing to choosing.
Hypothesis
For the same question, asking someone to tap once inside the email will get more response than asking them to compose a reply.
problem framing
The problem is not the question itself, but the way the answer is requested.
Inactive users usually do not have enough energy to leave a long retrospective about a product. “Why didn't you use it?” is a fair question, but the interface that delivers that question is often too heavy.
The user has to think, phrase the reason, fix the wording, and finally decide to send it.
For someone who only just signed up, closing the message is much easier than leaving feedback.
same question, different interface
Both are emails, but one asks the user to write, while the other asks them to choose.
The key difference is not “better copy.” It is the action the recipient actually has to take.
Please reply and tell us why you did not use it.
An open-ended question can be useful, but the user has to create the structure of the answer themselves.
message draft
|
Please pick one reason you did not use it.
Instead of writing a reply, the user can choose the closest reason directly inside the email.
Setup felt too complex
I do not need it right now
I forgot about it
Other
reply-cost ladder
The point is not to change the question, but to lower the cost of answering.
Users rarely describe this cost out loud, but they calculate it very quickly. The more they need to think, write, or leave the flow, the less likely they are to respond.
harder to answer
A free-form reply requires the user to create the answer themselves.
They need to find a reason, turn it into a sentence, and decide whether it is worth sending.
01
Figure out what reason to give
The user has to create a structure before writing anything down.
02
Turn that reason into an actual reply
Even vague hesitation has to become a readable sentence.
03
Hesitate once more before sending
The final doubt is often whether the reply is worth the effort at all.
easier to answer
A single click inside the email ends with a response already submitted.
The user does not have to compose new text. They only need to choose the closest reason and send it.
01
Open the email and understand the prompt
From there, the user reaches the choices immediately.
02
Choose the closest reason
Instead of inventing a sentence, they select from prepared wording.
03
Submit and finish in place
No reply screen, no extra explanation, no separate form.
interaction proof
The proof this concept wants to show is that the flow can actually stay this simple inside the message.
In abstract, it can sound theoretical. Once you see the sequence of open, choose, and finish inside the message, the lower effort becomes much easier to understand.
A short demo showing how the interaction can appear and behave inside an actual Gmail inbox.
signal shape
What you get is not only more replies, but reasons that are easier to work with afterward.
The value is not just response volume. It is that the reasons start arriving in a more structured form, which makes the next product or onboarding decision easier to make.
Plain replies
-
Reasons arrive as different sentences each time
Even when users mean the same thing, the wording varies and still needs to be grouped manually.
-
Extra reading and categorizing comes later
After collecting the replies, someone still has to turn them into usable patterns.
Choice-based replies
-
Reasons are collected directly as selectable categories
You can see repeated patterns and rough counts much earlier.
-
It is easier to act on what you learn next
Changes to onboarding, positioning, and reminder timing become easier to decide from the same set of inputs.