nohello is shorthand for one of the most common chat mistakes: typing “Hi” or “Hey, you there?” and then stopping, waiting for the other person to respond before you say what you actually need. In email or a phone call, a greeting first is polite. In chat, it just creates a wait. By the time the other person replies “hi, what’s up?” and you type out your real question, you have burned several minutes and their attention for nothing.
Why “hi” alone is costly
Chat is asynchronous. When you send only “hello,” the receiver sees a notification, switches context, replies, and then has to wait again for the real message – two interruptions where one would do. Sending the whole thing at once lets them read it when they have a moment and answer in a single reply.
Before
You: Hi
[reader sees a ping, replies] Them: Hey, what’s up?
[several minutes later] You: Do you know how to fix a merge conflict?
After
You: Hi! I’ve got a Git merge conflict in
app.jsthat I can’t resolve – I rangit merge main, gotCONFLICT (content), and I’m not sure which side to keep. Could you point me in the right direction?
One message, everything they need. They can answer the moment they read it.
The rule of thumb
Greet and ask in the same message. The original explainer lives at nohello.com. For how this fits into asking good questions everywhere – Slack, Discord, forums – see our guide on how to ask better questions online.