Presence, status, and welcoming a new joiner

Distributed teams cannot see each other, so they broadcast: "back in 10", "heads down till standup", "OOO Friday". These presence messages are a real genre with real rules, and the biggest is counterintuitive: telling people you are unavailable is a courtesy, not an excuse, because it stops them waiting on a reply that is not coming. This chapter covers the presence grammar of Slack and Teams in both directions, and the bookend moments of belonging: introducing yourself when you are the new one, and welcoming someone when you are not.

Introducing yourself as the new joiner

Your first channel message is read by everyone and remembered by a few; the social layer chapter has the anatomy, and here is the range, by team culture.

The standard version (safe anywhere):

Hi all 👋 I'm Noor, joining the Checkout team today as a data
engineer, coming from a fintech background (mostly payments
pipelines). I'll be picking up the recommendations work with
Alex. Still drinking from the firehose this week, so expect
some basic questions; pointers to docs I should read are very
welcome. Based in the Berlin office, usually online 9-6 CET.

The lighter, casual-team version:

hey team 👋 Noor here, new data eng on Checkout, ex-payments.
excited to be here! will be lurking and learning this week.
what's the one doc everyone wishes new folks read first?

The remote-first version (leads with logistics):

Hi everyone! I'm Noor, starting today as a data engineer on
Checkout. I'm fully remote from Lisbon (WET, so an hour ahead
of most of you), best reached here or async; I check messages
morning and late afternoon. Working with Alex on recs to start.
Genuinely no question too basic for me right now, so I'll be
asking a lot. 🙂

The three share a spine: name, role, one line of background, what you will work on, an explicit license for beginner questions, and logistics (location, hours, best channel). The beginner-question line is doing real work; it pre-frames a month of "where does X live?" as expected, not incompetent. Spend that license while it lasts (Chapter 32; the new-joiner card expires after a quarter).

When you are new and someone else introduces you, a one-line reply closes the loop warmly: "Thanks Dana! Excited to be here; I'll intro myself properly in the team channel in a sec." Then do.

Welcoming a new joiner (when it is not you)

The receiving side takes ten seconds and compounds; teams where every joiner gets three warm replies onboard measurably faster.

  • The channel welcome: "Welcome, Noor! I own the deploy tooling; ping me any time, no question too basic." (name your area, open a door)
  • The buddy offer: "Welcome! Want to grab 20 min this week? I can give you the map of who-owns-what, which saves you a lot of guessing." (a private DM for this is often better than the channel)
  • The specific hook: "Welcome, fellow ex-payments person! We should compare war stories about reconciliation." (finds common ground, Chapter 27)
  • The practical gift: "Welcome! Two links that took me a month to find: the arch diagram (go/arch) and the on-call runbook (go/oncall). You'll want both."

Whether to welcome in-channel or by DM: channel for the public "glad you're here" (it signals the team's warmth to everyone), DM for the substantive offer (a private "here's how things really work, ask me anything" lands more honestly than a public one). Doing both is ideal and still cheap.

Presence: stepping away and coming back

The everyday grammar of "I'm briefly gone." Precision saves people from waiting:

  • Short break: "brb" (be right back, minutes) / "grabbing a coffee, back in 5" / "afk 10" (away from keyboard).
  • Lunch: "lunch, back by 1" / "🍽 out for lunch, back ~13:00."
  • Errand or appointment: "at the dentist this afternoon, back around 3; ping my phone if it's on fire" / "stepping out for an hour, back by 2."
  • Deep focus: "heads down on the migration till standup; will miss messages, DM or @ me if urgent" / setting a 🎧 status.
  • Coming back: "back" / "back online" / "back at my desk, catching up on threads now."

Two rules make these work. State the return, not just the departure: "back by 1" lets people plan; "brb" alone does not. And name the escape hatch for urgent things when you will be unreachable for a while ("DM if urgent", "call my phone"), so your focus block does not become someone else's outage.

Don't be confused: the precision ladder of "I'm not here." brb = minutes, at my desk shortly. afk = away from keyboard, could be a while, not reading messages. heads down / focus = at my desk but deliberately not watching chat. OOO (out of office) = away from work entirely, hours to days. on leave = the long structured absence (vacation, parental, medical), days to months, and you should be dropped from day-to-day threads, not cc'd "just in case" (Chapter 20). Using "brb" for a two-hour absence, or "OOO" for a coffee, both mislead; the whole point of the vocabulary is that the word sizes the gap.

Start and end of day

The bookends, especially valuable across time zones:

  • Arriving: "morning all 👋 online now, catching up on the overnight threads." / "Good morning! Starting on the vault edge cases today."
  • Signing off: "logging off for the day; PR #812 is with Sam, nothing else blocking. Back tomorrow ~9." / "EOD for me; have a good evening all." / "Calling it; picking up the backfill first thing."
  • Signing off with a handoff: "Off for the day. On-call is Ravi tonight (thanks Ravi). The one thing to watch: queue depth on the demo tenant; runbook is go/queue if it climbs."

The sign-off with a state-of-play ("what's parked, what's blocking, what to watch") is the mark of someone who thinks about the people in the next time zone. It costs one sentence and prevents a morning of "wait, where did Alex leave this?"

Sick, and the OOO handover

The chat versions of Chapter 20's templates, since these often live in Slack now:

  • Sick, same day: "Out sick today, hopefully back tomorrow. Nothing of mine blocks anyone; the #812 review can go to Ravi. Off Slack." (availability + coverage, zero medical detail)
  • Sick, setting status: 🤒 with "out sick" so it shows on every message, plus the one channel post so nobody has to hunt.
  • Planned leave, the early flag: "Heads-up, I'm off next week (14th-18th). Flagging now so planning can route around it; handover to follow Friday."
  • Planned leave, the handover note: the day before, a runbook for your absence (in-flight state, who covers what, which decisions can wait, bias to "pause" over "improvise").
  • The OOO status itself: set the Slack/Teams "out of office" so auto-responses fire, and make the message useful: "OOO until the 21st, back the 22nd. For urgent Checkout issues, Sam (@sam). I won't be checking messages."

Responding to others' presence closes the loop warmly and is half the etiquette:

  • "No rush, enjoy lunch." / "Feel better!" / "Have a great time off, we've got it covered." / "Thanks for the handover, super clear." / "Go, we're fine here."

The one to avoid: pinging someone who set 🤒 or 🌴 with "quick question when you're back?" The status is the answer; hold the question, or route it to their listed backup.

The async principle underneath all of it

Every message in this chapter serves one goal: let people act without waiting on you. Presence broadcasting is not surveillance and not excuse-making; it is the distributed-team version of glancing up and seeing whether someone is at their desk. Broadcast enough that nobody blocks on a reply that is not coming, and no more (nobody needs a play-by-play of your bathroom breaks). The test for any status message: does it save someone a wasted wait? If yes, post it; if no, skip it.

👉 The presence layer covers the day's edges; one bank remains, for its most uncomfortable moments. When you did not catch the question, cannot understand the speaker, or fully drifted off, the recovery is a set of practiced sentences, and the only wrong move is the silent nod. On to Chapter 44.