How to handle your first bug reports from users
George · 2 min read
The short answer: reply quickly, thank the person, and ask only for what you need to reproduce the problem. Fix what affects the most people first, and when it is fixed, tell the person who reported it. Early users who see their report handled often become your most loyal ones.
Your first bug reports are a gift. Most people who hit a bug simply leave. The ones who write to you are telling you they want the product to work.
Reply fast, even before you have a fix
A short reply within hours matters more than a perfect one days later:
"Thanks for telling me, that should not happen. I am looking into it now. Could you tell me which browser you were using?"
This tells the user they were heard and gets you the detail you need.
Ask only what you need
To reproduce a bug you usually need:
- What they were trying to do.
- What happened instead, ideally with a screenshot.
- Their device and browser, or app version.
- Roughly when it happened, so you can find it in your logs.
Do not send a long form. Check your error tracker and logs first; you may already have the details.
Reproduce before you fix
Try to make the bug happen yourself. If you can not, look at what is different about the user's setup: another language, a very long name, a slow connection, an old account created before a change. Many "impossible" bugs come from data you did not expect.
Prioritize
Not every bug is equal. Fix first:
- Anything that loses or exposes data.
- Anything that stops people paying or signing up.
- Anything that affects many users.
Cosmetic issues can wait, but write them down.
Close the loop
When it is fixed, write back:
"Fixed, thanks to you. It was a problem with long names on mobile. Let me know if you see anything else."
Mention it in your changelog, and credit the user if they are happy to be named. This turns a bad moment into a good story.
Make reporting easy
Add a visible way to reach you: an email address, a feedback button, or a reply to your onboarding email. The easier it is to report a bug, the more you hear about and the fewer users quietly leave.
The short version
- Reply quickly and thank them.
- Ask only for what you need, and check your logs first.
- Reproduce before you fix.
- Fix data, payments and widespread issues first.
- Tell the reporter when it is fixed.
