Greetings, openers, and pings

First messages carry more weight than they deserve. Before anyone has seen your code, they have seen your "hi", and people form fast (and unfair) impressions from it. The good news: greetings are a solved problem. There is a small set of openers, each with a known register, and once you know the table you stop thinking about it.

The greeting ladder

From most casual to most formal:

Rules of thumb:

• When in doubt, "Hi" wins. It is never wrong internally, and rarely wrong externally. "Hey" is fine with peers but can read as overly familiar with executives or strangers; "Dear" inside a company chat reads as odd.
• Use the name. "Hi Sam," beats a bare "Hi," in almost every context. Get the spelling exactly right; misspelling someone's name is a small mistake with an outsized negative effect. Copy-paste it if you are unsure.
• Avoid "guys" for mixed groups. "Hi everyone", "Hi all", "Hi team", or "folks" do the same job without assuming anyone's gender.
• Drop the greeting in ongoing threads. Once a conversation is running, re-greeting every message ("Hello again Sam,") is noise. Just continue.

Don't be confused: "Hey" in professional English is a greeting, not a shout. Some languages use their equivalent of "hey" only to call attention or to complain, so non-native speakers sometimes read "Hey Maria" as aggressive. In an English-speaking workplace it is the friendliest common opener, one notch more casual than "Hi".

The no-hello rule

The single most useful chat rule, so widely shared it has its own site (nohello.net): never send a greeting as its own message and then wait.

Bad (two messages, forces the other person to wait for the point):

  09:14  you: Hi Sam
  09:14  you: (typing...)

Good (one message, greeting and substance together):

  09:14  you: Hi Sam, quick question about the deploy pipeline: is the
         staging freeze still on for today, or can I ship #4132?

Why it matters: chat is asynchronous. A bare "hi" interrupts someone, tells them nothing, and obligates them to respond before they even know the topic. Putting the question in the first message lets them answer once, at a moment that suits them. The same rule kills the standalone "Are you there?", "Can I ask you something?", and "Do you have a minute?" messages: fold the actual ask into the same message ("Do you have a minute today for a question about the retry logic? Async is fine too.").

Opening with a stranger

Messaging someone you have never talked to (another team, another org) has a four-part shape: who you are, why them, the ask, and an easy out.

Hi Priya, I'm Alex from the payments team. I'm told you own the fraud
scoring service. We're seeing 502s from its /score endpoint since about
10:00 UTC and I'd like to rule out a client-side cause. Could you point me
at the right dashboard, or at whoever is on call? No rush if you're heads
down; a pointer any time today helps.

Notes on each part:

• Who you are: one clause. Name and team, nothing more.
• Why them: "I'm told you own...", "Your name is on the ADR for...", "Rafael suggested I ask you." This shows the ping is targeted, not spam.
• The ask: specific and small. Asking a stranger to "help me understand the fraud system" is a big favor; asking for a dashboard link is a small one.
• The easy out: "No rush", "whenever you get a chance", "happy to take this to whoever is the right person." Skip the easy out when it is actually urgent; see Chapter 10 for urgent wording.

Email openers and sign-offs

Email keeps a light formal frame even inside a company. A serviceable internal email:

Subject: Approval needed by Thu: staging DB upgrade window

Hi Dana,

We'd like to upgrade the staging Postgres cluster to 16 this Saturday,
02:00-04:00 UTC. Impact: staging writes unavailable for up to 30 minutes.
Rollback: snapshot restore, tested last week.

Could you approve by Thursday EOD so we can book the window?

Thanks,
Alex

Conventions worth copying:

• The subject line carries the ask and the deadline. Many people triage by subject alone. "Question", "Update", or "Hi" as a subject is a wasted line.
• Sign-offs by register: "Thanks," (when you asked for something), "Best," (neutral default), "Regards," / "Kind regards," (formal, external), "Cheers," (casual, common in UK/Australia tech). Avoid "Yours sincerely" and "Yours faithfully" in tech contexts; they read as a century out of date.
• Skip "I hope this email finds you well." It became a template cliché and now signals boilerplate. If you want warmth, be specific: "Hope the launch week wasn't too brutal." Specific warmth reads as human; generic warmth reads as automated.

Time zones and availability

Distributed teams have their own greeting etiquette:

• Skip time-of-day greetings in chat, or hedge them: "Good morning your time" or just "Hi". "Good morning" sent at the recipient's 9 pm is harmless but sloppy.
• Sending late is fine; expecting a late reply is not. The professional convention: "Sending this now so I don't forget; no response needed until your morning." Many people schedule-send instead, which is even cleaner.
• When you ping someone marked away or focused: "I see you're heads down; whenever you surface:" followed by the ask. It acknowledges the status without waiting on ceremony.

Live and video-call openers

Small talk before a meeting starts is standard in most English-speaking work cultures, and it is shallow by design: weather, weekends, launches, coffee. Two or three exchanges, then work. Useful stock phrases:

• Joining: "Morning, everyone." / "Hi folks." / "Hey, can you hear me OK?"
• Waiting: "Let's give it two minutes for people to join."
• Starting: "Alright, let's get started. The goal for this meeting is..."
• Meeting someone new: "I don't think we've met; I'm Alex, I work on the ingestion side of the pipeline." Then let them introduce themselves.

Don't be confused: "How are you?" / "How's it going?" in passing is a greeting, not a question. The expected reply is short and positive ("Good, you?"), after which real conversation may or may not follow. Answering with an actual status report ("Not great, my build has been broken since...") is a classic register mistake, though with close teammates it can be fine.

Reconnecting after a long gap

• "Hi Sam, it's been a while! Hope things are good on the infra side. I'm reaching out because we're about to touch the quota service again and I remembered you led the last redesign."
• One sentence of warmth, then the reason. Resist apologizing for the gap ("sorry for disappearing"); nobody was keeping score.

A note on emoji and reactions

In chat, emoji do real protocol work: a 👍 or ✅ reaction means "acknowledged, no reply needed", and 👀 often means "I'm looking at it now". Using reactions instead of "ok thanks!" messages keeps channels quiet, and most teams prefer it. Match your team's density: an emoji-free message in an emoji-heavy team reads as cold, and vice versa. In email and docs, keep emoji rare.

👉 The first message opens the door; what you do when someone helps you determines whether they help you twice. Next: how to thank people in a way that actually registers, why "thanks in advance" annoys some readers, and how giving credit in public is one of the cheapest high-return moves available to you. On to Chapter 2.