by In February of 2010, I wrote about a small but symptomatic failure in our digital manners. Young people, then aged eighteen to twenty, would send you a message, receive your reply, and disappear. No acknowledgement, no “Ok,” no “Got it,” just the digital equivalent of someone slamming the door after asking you a question through the mail slot. The piece was called “How to Ack Back,” and the argument was that the etiquette of the early internet, the discipline of acknowledging every transmission, had been lost on a generation that grew up assuming delivery was guaranteed and silence was a defensible reply.
Sixteen years have passed. Those eighteen to twenty year olds are now thirty-four to thirty-six. They run departments, hire staff, negotiate vendor contracts, and raise children who are themselves the new eighteen to twenty year olds. And the Ack, the small confirmation that closes a communicative loop, is in worse shape than it was in 2010.
What I want to argue here is something I did not say sharply enough the first time, because in 2010 the technical metaphor was about InterNIC and email forms. The deeper truth is this: the entire infrastructure of the internet, every protocol that carries your email and your photographs and your bank transfers, is built on acknowledgement. The TCP three-way handshake, the foundational ritual of the connected world, runs as SYN, SYN-ACK, ACK. A machine asks to speak. The receiving machine answers that it heard the request and is ready to speak back. The first machine acknowledges that it heard the acknowledgement. Only then does the connection open. Every packet of data that follows is itself acknowledged by the receiving machine, or it is retransmitted. The network insists on confirmation, packet by packet, billions of times a second, around the globe, every second of every day. No packet counts as delivered until its acknowledgement returns.
The infrastructure is more polite than its users.
Someone will object that machines need explicit acks because they lack context, while humans have shared context that makes most acknowledgements redundant. The answer is that we are no longer operating in conditions of shared context. The contexts we used to share, of small newsrooms, common time zones, single inboxes, and stable working hours, have fractured. We communicate across platforms, time zones, languages, and generational dialects with strangers and near-strangers most of the day. We have become more like packets ourselves, which is the reason the packet-level protocol scales better than human courtesy does.
Read receipts, which arrived as a consumer feature after my original article, did not solve the problem. They made it worse in a way I want to be clear about. A read receipt is the opposite of an Ack. An Ack is a chosen act in which the responder decides to close the loop with the other party. A read receipt is involuntary surveillance. It tells the original sender that the recipient saw the message and chose not to respond. Effective communication requires the agency of the responder. Read receipts strip that agency and replace it with evidence. The result is a communicative culture organized around the suspicion of being ignored rather than the practice of being heard. That outcome is not effective because it converts a courtesy into a forensic procedure.
The emoji reaction is a debased middle case. When you send a colleague three paragraphs about a budget revision and the only reply is a thumbs-up reaction stuck to your message, you have received something that resembles an Ack and is not actually one. A real Ack confirms reading and confirms reception. A thumbs-up confirms tap. Reactions are effective because they are faster than typing “Got it.” They are not effective because they do not commit the responder to anything, including the proposition that they actually read the message. A reaction emoji is the cognitive minimum required to make the dot disappear from a notification tray. The Old Internet Ack, even when it was just the letters “Ok,” contained a small grain of accountability. The thumb does not.
Now consider what has happened in the workplace since 2010. Slack and Teams and their imitators have built whole economies around channels of unread messages. The competent employee of 2026 is supposed to be present, responsive, available, and also focused, deep, and uninterrupted. These demands are incompatible. The compromise that most workers have reached is the silent read. You open the channel, you scan, you absorb what you must, and you close the tab without responding to anyone. The thread dies. Its question hangs unanswered. By morning, someone repeats it and is met with the same silence. I have watched entire product decisions collapse from sheer lack of acknowledgement, even when no one in the room disagreed with the proposal. The room agreed, and the silence killed it anyway. Silence in a workplace functions as a vote against the speaker, with the convenient cover of looking like neutrality.
Job applicants and hiring managers have constructed an even more disturbing economy of non-acknowledgement. Applicants send hundreds of resumes into systems that never reply. Hiring managers schedule interviews with candidates who never confirm and then never appear. Companies extend offers to recruits who accept verbally, sign nothing, and vanish for weeks. The HR field has invented a term for this, “ghosting,” that politely names the failure to Ack while excusing it. Ghosting is the language we now use for what used to be called rudeness, and its migration out of millennial dating culture and into every professional interaction shows what happens when an entire generation has been taught that messages do not require closure. It is effective for the ghoster because it removes the small social cost of saying no. It is not effective for the system as a whole because it converts every communication into a probabilistic gamble in which the sender must construct backup plans for the case in which the recipient simply does not exist.
Any working professional who looks honestly at their own thirty day email volume can run a version of this experiment. Count the messages that go out and never come back, with no reply, no auto-responder, no read receipt. The number is almost always higher than the sender wants to admit, and a large share of those non-replies are to people with whom the sender has active, ongoing, billable relationships. The economic cost of the missing Ack is enormous and almost entirely invisible because it is distributed across millions of small re-asks. Every follow-up email anyone has sent in the last twelve months is a tax that the original recipient imposed on the original sender by refusing to spend three seconds confirming receipt.
The generation now coming up, the actual eighteen to twenty year olds of 2026, present a more complicated problem than the cohort I described in 2010. They know what acknowledgement is. They have replaced the old form of it with a system of platform-specific micro-signals that they understand and that almost no one outside their cohort can read. A typed “k” with no period means received and acknowledged. The same letter capitalized to “K” means annoyed but acknowledged. Double it to “kk” and you have warm acknowledgement. The skull emoji indicates that the previous message was funny enough to register. The grammar is real, and within the cohort it functions. The failure is that this grammar is invisible to the rest of the working world, and the cohort has not yet been required to translate. When they enter the workplace, they are read as rude, when in fact they are speaking a dialect that the workplace has not learned. I will say this in their defense. They are doing something. The thirty-five year olds who learned email in 2010 and never developed any acknowledgement habit at all are doing nothing.
The artificial assistants that now draft replies on our behalf complicate the picture in a way I find worth examining honestly. When a suggested smart reply offers “Sounds good!” or “Thanks, will do,” and the recipient taps it without reading the original message, what has actually happened? A signal has been transmitted that resembles an Ack. The sender will receive it and will probably treat it as one. The recipient has performed the appearance of acknowledgement without performing the cognitive work that acknowledgement traditionally implied. This is effective in the immediate sense, because the loop closes and the next email can proceed. It is not effective in the larger sense, because the trust that the Ack was meant to establish has been hollowed out. If the original message contained a deadline, a constraint, or a question that required actual reading, the smart reply ack is a lie. It is the digital equivalent of nodding through a conversation you stopped following ten minutes ago. The infrastructure that runs on real packet-level ACKs has produced a software layer that fakes acks at the human level. This is funny in a dark way and dangerous in a practical way.
The deeper argument I want to make in 2026 that I did not make sharply enough in 2010 is this: the Ack is a question of relational accountability, and to file it under etiquette undersells what is at stake. To Ack is to say, “I am still here, I am still in the conversation with you, and I have received what you sent.” Each of these claims is a small act of social commitment. The refusal to Ack is the refusal to commit, and the refusal to commit at scale is the cultural condition we are now living in. People do not want to say no. They do not want to say yes. They want to leave themselves the option of having never received the message at all, so they can act, later, as if the question was never asked. The non-Ack is a tactical erasure of the other party’s request from the social record.
This is corrosive because it converts every relationship into a relationship of low trust. If I send you a question and you do not Ack, I must assume that you may answer, may not answer, may never have received the message, may have read it and decided to ignore it, may be waiting for me to follow up, or may be testing how badly I want a response. The cognitive load of that ambiguity is a tax on the sender that I am paying, you are paying, and most of the working professionals I know are paying every day. Old Internet hands paid this tax less because the Ack culture distributed it across both parties. A recipient did a small amount of work to Ack, and a sender did not have to do a larger amount of work to chase. Under the new culture, the cost concentrates on the sender, who pays it forever.
There is a generational defense of the non-Ack that I want to address head on, because it gets offered to me by my younger colleagues all the time. The defense is that the volume of digital communication is so high now that responding to everything is impossible, and that the Ack is therefore a luxury we cannot afford. I find this argument honest and wrong. The volume is high because we have stopped acknowledging. The decline of the Ack has not lightened anyone’s inbox. It has weighed every inbox down with follow-ups, ambiguous threads, re-asks, and orphan questions. A culture of fast, terse, reliable acknowledgement would reduce communicative volume, not increase it. The Old Internet hands cleared their queues by closing loops, which made them faster than we are, contrary to what the volume argument assumes. We are slower because we leave loops open and hope they evaporate.
I want to offer three practical positions for the reader to consider, and I will tell you which I recommend.
The first position is to abandon the Ack entirely and accept the new norm. This is effective because it reduces friction with people who have already abandoned it. It is not effective because it accelerates the social condition I have just described and contributes to the very erosion it adapts to.
The second position is to insist on the Ack from others and to enforce it by repeating yourself until acknowledged. This is effective because it gets results. It is not effective because it makes you exhausting to communicate with and signals that you do not trust the other party, which over time produces a self-fulfilling lack of trust.
The third position, and the one I recommend, is to Ack everything yourself and to model the behavior without demanding it. Acknowledge every meaningful email you receive within twenty-four hours, even if only with one word, with spam and bulk mailings obviously excepted. The same goes for every text message, even when it comes from people who never Ack you. Small confirmations matter too: meeting holds, document receipts, calendar acceptances. Make yourself the kind of correspondent that other people learn from. This is effective because it produces a small visible standard in the conversations you participate in, and because over a long enough stretch of time the people who communicate with you regularly begin to mirror it. It is not always effective because some recipients will never reciprocate, and you will have to make peace with the asymmetry. I have made that peace. The cost of acking strangers who never ack me is much smaller than the cost of becoming the kind of person who has stopped acking.
When I wrote the original piece in 2010, I closed with the line that to refuse the Ack is to refuse to communicate a proper end to a never-ending beginning. I will close this one differently. The Ack is the smallest possible act of citizenship in a digital society. It costs almost nothing. It commits the sender to almost nothing. And yet its absence is the single most reliable indicator I know that a relationship, a workplace, or a generation has stopped taking its own communications seriously. The internet itself, at the layer of packets and protocols, refuses to operate without acknowledgement. We should at least try to be as decent to one another as our routers are.
Leave a Reply