How to write a feature request a product team can act on
A wish tells a team what you want. A good request also tells them what happened, how often, and what it costs you.
Product teams read a lot of feedback, and much of it arrives as a wish: add dark mode, fix the app, make it faster. A wish says what someone wants. It rarely says enough for a team to decide whether to build it, how to build it, or who it is for. The requests that move forward are the ones a team can act on without writing back to ask what you meant.
This guide takes one request from a vague wish to something a team can use. It works for any product, whether you post on Suggst, leave an app store review or type into a support chat.
Start with what happened
Open with the moment the problem showed up, before any solution. "I was booking a Tatkal ticket on IRCTC, the payment page timed out, and when I got back in the seats were gone" gives a team a scene they can picture and try to reproduce. "Please improve the payment page" gives them nothing to test. (IRCTC here, and every app named in this guide, is a made-up example of how to write a request, not a report about the app.)
Leading with a solution feels helpful, which is why so many people do it. The trouble is that the team may know a better fix than yours, or a reason yours would break something else. If they understand the problem, they can choose the fix. If all they have is your fix, they have to guess at the problem.
Say who it affects and how often
Every team has more requests than time, and two questions come up each time they choose: how many people run into this, and how often. You cannot answer the first one alone. That is what votes are for. You can answer the second one for yourself.
Say what kind of user you are when it happens: a commuter ordering lunch at the office, a parent paying school fees, a shop owner checking UPI payments at closing time. These details tell the team whether you are one of their everyday users or an edge case, and both are worth knowing.
On Suggst, every post asks How often does this happen to you? with four answers: daily, weekly, monthly or rarely. Answer it honestly. A problem that happens rarely but costs a lot each time is still worth posting, and saying so plainly is more useful than making it sound bigger than it is.
Describe what you do today
The workaround is the most overlooked part of a request. If you screenshot every order because the app loses it, or keep PNR numbers in a WhatsApp chat with yourself because the booking history is hard to search, say so. A workaround shows the problem is real enough that you already spend effort on it, and it shows the team exactly where their product falls short.
Add what it costs you: time, money, a missed train, an awkward call with a customer. Keep it factual. "I lost the seat and paid more for a bus" is stronger than "this is the worst app ever", and it is much easier for someone on the team to repeat in a planning meeting.
The same request, written two ways
A wish
Swiggy should have a better way to split bills. Please add this, it is very much needed!!
Ask for one thing
Once the problem is clear, suggest a fix if you have one. Keep it to one change per request. A post asking for split bills, dark mode and faster delivery collects votes from people who want any one of the three, and nobody on the team can tell which one the votes were for.
If you have three ideas, post three requests. Each one is easier to vote on, easier to answer and easier to mark shipped.
Then write a title that makes sense on its own in a list, because that is where most people will first see it. "Send UPI requests to split a group order" works. "Suggestion" or "Big problem!!!" does not.
Quick question
Which title is most likely to get votes from the right people?
Check it before you post
Before you post a request
0/8If writing in English slows you down, write in Hindi or whatever language you think in. Suggst AI lays the post out in English for the team and keeps your original words with it. You can also start a post from a screenshot of the screen where things went wrong, which is often the quickest way to show what happened.
What to do after you post
A request does better with company. Share it with people who have the same problem, especially people who use the product often. On Suggst they can vote with I want this too, add I use this product, and mark I'd pay for this if a fix would be worth money to them. Each of those tells the team something a bare count cannot.
If the product's team has claimed their page, they can reply to your post and set a status: planned, in progress, shipped or not planned. When a team picks a post up, it shows Picked by with the product's name, and the author earns impact points toward levels and badges on their profile. If the team has not claimed their page yet, the post is still public and still collecting votes, and they can claim it whenever they like with a work email at their domain.
Every post also gets a public record: a timestamp proof made with OpenTimestamps, so if your request is the one that ships, anyone can check who asked first. And if you follow the product, its new posts come to you in a Monday email, so you can vote on related requests instead of writing the same one twice.
For more on why some requests get answered and others do not, read why product teams ignore feedback. If you are not sure your post belongs to a product at all, this guide to suggestions, problems and ideas will help you pick.
Post a request for a product you use, then share it with people who have the same problem.
Write a requestWritten by the Suggst team. Example requests about real apps are made up to show how to write them, not reports about those apps.