yes hello.

because manners matter more than your time

a manifesto for civilized human communication

Someone sent you this link. That means they said "hello" to you and waited, and you had the audacity to be inconvenienced by it.

This website exists to explain, in patient and loving detail, why saying hello first and waiting for acknowledgment is not merely acceptable — it is morally correct. Please read it carefully. Take notes if you need to.

✓ the gold standard of professional communication
DM — DevWhoWasInTheZone
👔
ChadFromAccounting • 9:41 AM
Hello
— a respectful 47 minutes of dignified silence —
💻
DevWhoWasInTheZone • 10:28 AM
Hey! What's up?
👔
ChadFromAccounting • 10:28 AM
Oh great!
👔
ChadFromAccounting • 10:29 AM
So I have a question
👔
ChadFromAccounting • 10:29 AM
About the API
— the question is being thoughtfully composed —
👔
ChadFromAccounting • 10:32 AM
Can you change the date format in the /users endpoint from ISO 8601 to MM/DD/YYYY?
Beautiful. Textbook. Chad gave DevWhoWasInTheZone the gift of anticipation. Both are fully present for this interaction. This is connection.
✗ frankly offensive behavior
#backend-dev
😤
SomeoneWithNoBoundaries • 9:41 AM
Hey! Quick question — is there a reason the /users endpoint returns dates in ISO 8601? Accounting needs MM/DD/YYYY. Happy to format on our end if that's easier, just wanted to check before I do something cursed in Excel.
No greeting. No warm-up. No period of anticipation. They simply... unloaded their thoughts without warning. Like an ambush. DevWhoWasInTheZone was not emotionally prepared for this.
✓ advanced technique: the multi-stage hello
DM — SeniorDevLisa
📊
PriyaFromProduct • 2:00 PM
Hi!
👩‍💻
SeniorDevLisa • 2:14 PM
Sure, what's up?
📊
PriyaFromProduct • 2:14 PM
Great! So...
📊
PriyaFromProduct • 2:15 PM
I wanted to ask
📊
PriyaFromProduct • 2:15 PM
about something
👩‍💻
SeniorDevLisa • 2:16 PM
...
📊
PriyaFromProduct • 2:17 PM
📊
PriyaFromProduct • 2:19 PM
Can we push the release by two weeks?
Note how Priya built suspense across five messages before delivering the question. SeniorDevLisa had 19 full minutes to mentally prepare. This is masterful pacing. This is storytelling.
★ the platonic ideal
DM — TechLead_Morgan
🎓
NewIntern_Jake • 11:00 AM
Hello
— 4 hours and 12 minutes of rich, respectful silence —
🎓
NewIntern_Jake • 3:12 PM
Are you busy?
— the next morning. Jake is nothing if not patient. —
🧑‍💼
TechLead_Morgan • 9:03 AM
Hey Jake, sorry I was in meetings yesterday. What do you need?
🎓
NewIntern_Jake • 9:04 AM
Oh nvm I fixed it
Jake solved the problem himself. The "hello" gave him 22 hours of focused, uninterrupted problem-solving time. Some call this inefficiency. We call it growth.

Why the hello-first approach is simply correct

When you send "hello" and wait for acknowledgment before sharing your question, you are doing something profound: you are asking permission to exist in another person's consciousness. That is not a bug. That is basic human decency, and frankly it is the minimum we should expect from one another.

Think about it. You wouldn't walk into someone's office, sit down, and immediately start talking about your problem, would you? Of course not. You'd knock. You'd say "got a minute?" You'd wait. Chat is exactly the same, except the waiting can extend into the next business day, which is fine.

The people at nohello.net will tell you that chat is "asynchronous" and you should just "include your question." This is the philosophy of someone who has never once stopped to consider how their message might land emotionally. Sure, they'll get their answer faster. But at what cost to the relationship?

The hello is not inefficiency. The hello is an act of care. It says: "I see you. I know you exist. I'm not just going to fire my thoughts at you like some kind of question gun." You are better than a question gun. We all are.

Benefits of saying hello first

The following are documented, peer-reviewed, and absolutely not made up.

  • 01.
    Builds suspense
    Nobody likes to feel ambushed by information. The hello primes the other person's nervous system. They know something is coming. They can feel it. It makes the eventual question that much more satisfying when it finally arrives — sometimes hours later.
  • 02.
    Gives them time to mentally prepare
    What if your question is hard? What if it involves a database migration, or, God forbid, a conversation about timelines? A bare "hello" sent at 9 AM gives the other person until lunch to brace themselves. That's a gift. That's compassion.
  • 03.
    Establishes dominance
    Whoever asks the question holds the power in a conversation. By sending "hello" first and forcing the other party to respond with "what's up?", you have made them ask you a question. You are now, technically, answering. You are in control. This is chess.
  • 04.
    Confirms they are alive
    What if they weren't online? What if they were, in fact, in a meeting? A "hello" sent into the void and ignored for four hours tells you something valuable: they are busy. You could have also checked the green dot, but the hello is more personal.
  • 05.
    Encourages self-reliance
    As NewIntern_Jake demonstrated above, waiting 22 hours for a response creates an ideal environment for independent problem-solving. Your unanswered "hello" is essentially a mentorship program. You are helping them grow as a professional by not being immediately available.
  • 06.
    It's simply what nice people do
    Some things don't need to be optimized. A sunrise is inefficient. A long meal with friends is inefficient. Saying hello and waiting is, in its own small way, a refusal to let the relentless march of productivity consume every human interaction. Cherish it.

Expert tips for maximum impact

You've mastered the hello. Now refine your craft.

Pro Tip #1
For maximum impact, say hello on a Friday at 4:58 PM. This ensures your conversation partner has the entire weekend to mentally prepare for your question. They'll thank you Monday morning, question in hand, refreshed and ready.
Pro Tip #2
Follow up a "hello" with "do you have a sec?" before asking anything. This double-greeting technique shows extraordinary consideration. You are not merely announcing your presence — you are requesting a formal audience. Very elegant.
Pro Tip #3
If they don't respond to your "hello" within 20 minutes, send "Hey!" This shows persistence and reminds them that you exist. Some experts recommend a third message — "Just checking in!" — sent three hours later. This is called a "courtesy escalation."
Pro Tip #4
When they finally respond, do not rush to your question. First, ask how they're doing. Ask about their weekend. Build rapport. The question will land so much better after a 12-message warm-up. They'll be relaxed. You'll be relaxed. Everyone will be fine.
Pro Tip #5
Consider spreading your question across multiple messages for dramatic effect. "I have a question." (send) "It's about the database." (send) "The production one." (send) This builds narrative tension and ensures they are fully engaged when the actual question arrives.
Advanced Technique
Send "hello" and, if they respond immediately, say "never mind, figured it out." This is the purest form of the practice. The hello was never about the question. The hello was about the connection.

Frequently asked questions (answered patiently)

"Why should I say hello first? They know I have a question."
Do they, though? Do they really know? When you send "hello" with no context, you are gifting the other person a brief moment of beautiful uncertainty. Maybe it's a compliment. Maybe you just wanted to connect. Maybe something urgent came up. The world contains multitudes. Let them wonder.
"But it makes them stop what they're doing for no reason."
First of all, you are a reason. You are a person. Your hello is not "nothing" — it is acknowledgment of the relationship between two human beings operating in a shared professional context. Second of all, yes. Exactly. They stop. They look up. They see your name. For one brief moment, you have their full attention. Is that so terrible?
"What if they're in the middle of something important?"
Then they will see your "hello," feel a little flutter of social anxiety about who it's from and what it could mean, close the notification, try to return to their work, fail to concentrate because they know a conversation is pending, check back three times, and eventually respond. This is called being kept on their toes and it is a sign of a vibrant workplace culture.
"Someone at nohello.net says I'm 'weaponizing politeness.'"
The nohello.net crowd has optimized every last molecule of warmth out of their professional communications and replaced it with pure, cold efficiency. Yes, they get answers faster. They also eat lunch at their desk and describe themselves as "direct." We're not saying they're wrong. We're saying we don't want to be them.
"What if I say hello and they immediately ask 'what's up?' — do I have to answer?"
Absolutely not. You can say "Oh, just wanted to check in!" and end the conversation there. A hello that leads to nothing is not a failure. It is proof that human connection doesn't need to be transactional. You said hello. They acknowledged you. That's a complete interaction. That's a relationship.
"My coworkers sent me this link. Should I change my behavior?"
Under no circumstances. They sent you this link because they care about you. They want you to read it, feel validated, and continue saying hello at an unhurried pace for the rest of your career. That's what this site is for. Stay the course. Say hello. Wait. They'll be there eventually.
"Is there ever a time I should just ask my question directly?"
If the building is on fire, yes, skip the greeting. For everything else — a date format question, a release timeline, a CSS bug — there is always time for hello. There is always time to be a person first and a colleague second. The building is almost certainly not on fire. Say hello.