Acknowledgments, accepts, and micro-replies

Most of a chat day is not composed messages; it is one-liners. "On it." "Will do." "Makes sense." "SGTM." These micro-replies are the connective tissue of a team, and non-native speakers often own exactly one of each kind and repeat it until it wears thin, or reach for a textbook phrase ("I have understood your request and will comply") that reads like a robot filing a form. This chapter is the full inventory: every band of one-liner, what it signals, and the one trap that matters more than all the vocabulary.

Accepting a task

Someone asks you to do something. The accept-replies, casual to formal, with tone notes:

The upgrade over any of these alone is to echo the task and add a when: "On it; PR up before lunch." That one clause converts a vague yes into a plan the asker can stop thinking about, and it is the single biggest tell of a reliable teammate.

Don't be confused: acknowledging receipt and committing to act are different messages, and collapsing them is the most expensive micro-reply mistake there is. "Ack", "seen", "noted", "got it", and a 👀 reaction mean I received this and nothing more. "On it", "will do", and "consider it done" mean I am now responsible for making this happen. Saying "on it" when you cannot actually start for four hours teaches people to expect a result that is not coming; the honest version is "Seen; can't start till after the incident call, will pick it up around 2." When you only mean to acknowledge, use an acknowledge word; when you mean to commit, add the when. The gap between "I saw your message" and "I own your problem" is where most quiet let-downs live.

Declining or deferring, in one line

You cannot or should not take it right now. The micro-replies that say so without a wall of apology (the costed no, compressed):

• "Can't right now; free after standup. Urgent, or can it wait?"
• "Not my area; Yuki owns that. Want me to loop her in?"
• "Swamped today; I can get to it tomorrow AM. Works?"
• "I'd rather not half-do it; give me till EOD to do it right?"
• "Out of bandwidth this sprint. Happy to pair for 20 min so you can run it yourself."
• "Short answer, not me. Longer answer, ask in #search-infra."

Each does the same two things: a clean no or not-yet, plus a route (who else, when instead, what path). A bare "can't, sorry" leaves the asker exactly where they started.

Confirming you understood

Someone explained something; signal that it landed:

• Neutral: "Got it." / "Understood." / "Makes sense." / "Clear."
• Warmer: "That tracks." / "That lands." / "Yep, with you." / "Following."
• Precise: "Got it: pin the epoch, then exchange. Right?" (the echo-back, which proves understanding instead of claiming it, Chapter 22)
• Honest partial: "Following up to the epoch part; lost you after. One more pass?" (far better than a false "got it")

The false "got it" is the quiet cousin of the false "on it": it buys a comfortable moment and sells a Thursday of rework. Use the partial-honesty version whenever the "got it" would be a lie.

Agreeing with a proposal

Someone proposed a plan; you approve:

• "+1." / "SGTM." (sounds good to me) / "LGTM." (of code, Chapter 7)
• "Works for me." / "Fine by me." / "No objections." / "I'm good with that."
• "No notes." (jokey-strong: it is so good you have nothing to add)
• "Ship it." / "Send it." (enthusiastic go-ahead)
• Qualified: "+1 with one nit in the thread." / "Yes, assuming the flag defaults off." (agreement with a named condition, which is more useful than a bare +1)

Non-committal, honestly

Sometimes the true answer is "not yet." Say that instead of a fake yes:

• "Let me get back to you." / "I'll come back to you by EOD." (add the when, or it reads as a soft no)
• "I'll see what I can do." (genuine effort, no promise; do not use it as a polite refusal, which some hear it as)
• "No promises, but I'll try to squeeze it in."
• "Tentatively yes; confirming once I've checked the calendar."
• "Leaning yes; give me an hour to be sure."

Reacting to news

The human one-liners that keep a channel warm (Chapter 27):

• Good news: "Nice!" / "Love it." / "Huge." / "Congrats!" / "🎉" / "That's a relief."
• Bad news: "Oof." / "Ugh, sorry." / "That's rough." / "Yikes." / "Well, that's not ideal." (British understatement, Chapter 39)
• Impressed: "Slick." / "Clean." / "Nicely done." / "Chef's kiss."
• Commiseration: "Been there." / "The worst." / "Solidarity."

A reaction emoji often does this job with zero words, and on a busy channel that is a kindness; the rule is only that some acknowledgment beats silence when someone shared something that cost them to share.

Closing the loop

The task is done; report it in one line, in the same thread:

• "Done." / "Shipped." / "Merged." / "Deployed." / "Handled." / "Sorted." / "All set." / "Good to go." / "Wrapped."
• With the receipt: "Done, PR #812." / "Deployed to staging; watching the graphs." / "Fixed and verified; closing the ticket."
• Handing back: "Done; over to you for the review." / "Ready for QA whenever." / "Unblocked; you're clear to proceed."

Closing the loop is the most underrated micro-reply in the set. The asker has been holding an open question about your task; one word ("done") lets them put it down. Silence after "on it" leaves that question open for days and quietly erodes the trust that "on it" was supposed to build.

Reading them, not just sending them

The receiving half: these one-liners carry information you should decode. "Will do" is a softer, later commitment than "on it now." A bare "ok" (no thanks, no next step) from someone usually warm can signal irritation; a "sure." with a period sometimes reads colder than "sure!" (punctuation is tone in chat). And "seen" or a 👀 with no follow-up for hours is your cue to send the gentle bump (Chapter 3), because it acknowledged receipt without committing to action. You do not need to over-read every message, but knowing that "ack" ≠ "on it" ≠ "done" tells you exactly how much you can stop worrying about.

👉 Micro-replies run the middle of the chat day; presence messages run its edges. Next: how to introduce yourself when you are the new one and how to welcome someone when you are not, plus the whole grammar of Slack and Teams status (stepping away, heads down, out sick, on leave, signing off) in both directions. On to Chapter 43.