How I handle user messages, and why I prefer WhatsApp
Why WhatsApp
Most of our visitors already have it open. A contact form feels like paperwork; a message feels like a conversation. Replies arrive in minutes instead of days, and people send screenshots without thinking about it, which makes debugging far faster.
How I organise messages
Every message goes into one of three buckets: a bug, a question, or a request. Bugs get answered the same day. Questions get a short answer plus a link to the page that explains more. Requests go into a list I review weekly.
Simple rules for replying
Answer in the language the person wrote in. Never send a wall of text. If I cannot fix something, I say so plainly and explain the workaround. A clear "no" is better support than a vague "soon".
What the messages taught me
Users do not describe features, they describe frustration. "The table is confusing on my phone" became pagination and a mobile layout. "I do not know what this score means" became a tooltip and an explainer article.
A practical reply system, step by step
- Set a fixed reply window: for example morning and evening. Consistency beats raw speed.
- Classify the message in seconds: usage question, technical bug, feature request or business offer.
- Lead with the answer: the first sentence solves; the explanation follows.
- Keep short templates for repeated questions, but always personalise the name and details.
- Turn repeated questions into content: asked three times? Add the answer to the tool page or the blog.
- Close the loop: when you fix a reported bug, tell the person who reported it.
Worked example
A visitor wrote: "The appraisal tool gave my domain a low value — why?" Our first reply was a long methodology essay and got no answer. The revised reply was: "It is low because the name has 14 characters and a hyphen; try a shorter variant in domain search." That short answer led to a new test and a thank-you the same day — and we added the same explanation under the appraisal result.
Comparison table: message types and handling
| Message type | Target reply time | Follow-up action |
|---|---|---|
| Usage question | Within 24h | Update the tool explanation if repeated |
| Technical bug | Within 12h | Reproduce and log it |
| Feature request | Within 48h | Add to the idea list with a request count |
| Business offer | Within 72h | Verify the sender before committing |
If you are building something
Put one contact channel where people can actually reach you and answer it yourself for the first year. It is the cheapest research you will ever do.
Comments(0)
…