Why sending just "hi" in chat annoys people

A lone "hi" annoys people because it is expensive. It is not rude, it is expensive: you send two characters, and the reader pays for the rest of your message with their attention.

The greeting arrives, the notification fires, and now they owe you a reply that contains nothing. They cannot answer your question, because you have not asked it. They cannot go back to work either, because you clearly want something.

So they type "hey" and sit there.

What a lone hi costs the person reading it

It puts them in a waiting state: they are on the hook for a conversation whose size and urgency are unknown to them.

Attention at work runs on triage. Every message gets a fast, mostly unconscious judgment: is this now or later, five seconds or forty minutes. A greeting with nothing attached defeats both questions.

Until you say more, here is what the reader cannot do:

• They cannot decide whether this is worth stopping their work for.
• They cannot start thinking about the answer or look anything up.
• They cannot answer it and be finished with you.

You, meanwhile, are fine. Your question is ready, you know it is small, you are just waiting for the door to open. The cheapest message for the sender creates the most expensive pause for the receiver, and that imbalance is the annoyance.

Distance makes it worse. Six hours apart, your hi and their hey and your actual question take a day and a half to land in the same place. I see it on the support inbox for the extension I build: somebody opens with a greeting, waits, and by the time an answer is sitting there they are asleep, so their bug report is a day older than it needed to be. The greeting was a queue ticket.

Why people do it anyway

Most people send the lone hi because they are being polite in the only way speech ever taught them.

In a room you do not walk up to someone and open with "what is the retry limit on the webhook". You say their name, they turn around, then you ask. The greeting is the knock, and knocking is kind.

Chat has no door. The knock and the entry are the same action, so a greeting sent by itself is a knock at a doorway you already walked through.

One version of this is not a habit but a rule. Plenty of teams and cultures treat the greeting as the required opening move, and skipping it reads cold, which is one of the ways the same words land differently across a distributed team. If that is your team, keep greeting. The rule asks for a greeting, not for a separate message. "Good morning Ana, quick question about the invoice numbers" satisfies it and costs Ana nothing.

The other reason is quieter. Sometimes the hi goes out because the sentence after it is not ready, and sending something feels better than sitting with a half-written ask. I built Unvent partly for that stall: it rewrites whatever you are typing, in place, so the clumsy version already in the box becomes a sendable one. The stall is real. Sending the greeting alone does not end it, it just moves it into someone else's afternoon.

Send the greeting and the ask in one breath

Write one message that carries the hello, the thing you want, and how big it is.

Three parts, no ceremony:

• Greet them by name, once, on the same line as the ask.
• Say the actual thing in the first sentence, with its real nouns in it.
• Tell them the size: roughly how long it takes and when you need it.

Shapes you can copy:

• "Morning Ana, quick one: do we have final numbers for the March invoice, or is that still with finance? No rush, tomorrow is fine."
• "Hi Sam, I am stuck on the webhook retry limit and the doc does not say. Two minutes of your time, or point me at whoever knows."
• "Hey Priya, hope the launch went okay. Not urgent: could I get read access to the staging dashboard this week?"

Each of those is a complete transaction. The reader can answer it or park it without ever typing "hey, what's up".

Notice what the size label is doing. "No rush, tomorrow is fine" is the clause people cut for brevity, and it is the one that decides whether your message interrupts a meeting. If you never tell people how urgent you are, they default to assuming the worst case, and eventually they start assuming it before they even open your messages.

If the one-breath version feels abrupt to you, read those three shapes again. Every one of them has a greeting in it.

The "sorry to bother you, are you free?" version

Asking whether someone is free, without saying what for, asks them to say yes to an unknown.

The apology makes it harder rather than softer. "Sorry to bother you, do you have a minute?" leaves the reader two bad options: agree to an unmeasured piece of their day, or refuse a person who has just apologized to them. Most people agree and quietly resent it.

Put the topic and the size inside the question and it becomes easy to answer:

• "Do you have ten minutes today to look at the pricing page copy? Happy to do it in writing if that is easier."
• "Could I grab you before Thursday about the contractor renewal? It needs a yes or no from you, not a discussion."
• "Sanity check when you have a moment: is the staging database safe to wipe?"

"Can I ask you a question?" belongs in the same bin. You are requesting permission for something nobody was going to refuse. Ask the question.

From a manager, a lone hi is a summons

When the greeting comes from someone senior, the empty space does not stay empty. The reader fills it, and they fill it with the worst thing available.

Anyone who has worked for a while knows the feeling. A manager's name appears, the message says "hi", and your stomach runs the list before your brain catches up: the missed deadline, the thing you said in Tuesday's meeting, the reorg rumor. Ten minutes later they ask whether you still have the vendor's phone number.

Managers underrate this because their own hi feels neutral from the inside. It is not neutral from below. Position changes what a blank message means, and a blank message from the person who writes your review means one of a few frightening things.

So here is my position, and I know some managers will hate it: if you lead people, a greeting-only message is a small tax you charge everyone below you, and no amount of "my door is always open" refunds it. The fix costs a few words. Say the topic, and say the temperature.

• "Hi, nothing bad, quick question about the roadmap doc."
• "Morning, I want to talk about your goals for next quarter this week, nothing is wrong."
• "Hey, I need a decision from you on the vendor by Friday, five minutes should cover it."

When someone sends you one

Answer the message they meant to send instead of the one they sent.

The reflex reply is "hey!", which restarts the loop and buys you a second interruption when the real question finally lands. Skip it. Send your availability and an invitation together: "Hi, in meetings till three, send the question and I will answer when I surface."

That line does two useful things at once. It gets you the actual question now, while you are already looking at the screen, and it shows the sender what a whole message looks like without anyone having to be lectured about etiquette.

People copy the shapes they receive, which is the only etiquette enforcement that has ever worked in a chat window. Nobody drops the habit because they were told the lone hi is annoying. They drop it because the person on the other end kept making it easy to say the entire thing at once.