The community's texting etiquette: the unwritten rules, written down

Every community has an etiquette book nobody wrote — you learn it by getting it slightly wrong once. The mazel tov text sent to the wrong sibling's simcha; the levaya notice forwarded with a cheerful emoji left over from the previous message; the 6 a.m. text that woke a night-shift nurse. None of these were malice; all of them were the absence of a written page. This is that page — the community's texting norms, collected from how the considerate actually behave.

The occasions, and their forms

The simcha text. Warm, prompt, and specific — "Mazel tov on Rivky's engagement!" beats a bare "MT" the way a handshake beats a nod. The form scales down gracefully for the acquaintance and up for the close friend (who deserves a call — texting a best friend's simcha is itself a small etiquette miss, per the generational-channel wisdom). The one hard rule: verify before congratulating — the community's rumor speed occasionally outruns its accuracy, and the premature mazel tov is an awkwardness that lingers.

The levaya and nichum text. Gravity in form as well as words: no emojis, no abbreviations, nothing forwarded with residue from prior messages. The levaya notice is logistics and belongs on the official rails; the personal condolence is its own message, brief and sincere — "thinking of your family, BDE" — with the real nichum happening in person. And the timing dignity: condolences text in daylight hours; grief does not need a midnight notification.

The logistics text — carpool, appointment, the address — is the medium's native genre and has one rule: complete in one message. Time, place, and the answerable question together; the four-message drip ("You there?" … "Question" …) spends four notifications on one thought.

“Texting etiquette is one principle wearing many forms: the message costs the receiver something — attention, sleep, feelings — and the considerate sender prices it first.”

kolbo.life

The reply-time question, settled honestly

Half of texting friction is mismatched expectations about response speed. The sane community norms:

• Texting is asynchronous by design. The default expectation is "today," not "now" — a person davening, learning, driving, or parenting is supposed to be unreachable. The device tiers this community chooses enforce that wisdom architecturally; etiquette extends it to everyone else.
• Urgency escalates channels, not volume. Truly urgent means call — the triple-text with question marks is urgency theater that trains everyone to ignore it. The channel ladder (text → call → call again) is the community's actual protocol, and the emergency stack formalizes its top rung.
• The read-without-replying grace. Between households, the read message answered hours later needs no apology; the standing assumption of busy, frum, family life is the etiquette's foundation. (Within a marriage or a carpool rota, agree your own tighter norms — group coordination runs on them.)

Timing, and the calendar

The community's texting clock has zones mainstream etiquette never mapped: erev Shabbos afternoon is logistics-only territory — the philosophical question and the long story can wait for Sunday; Motzaei Shabbos opens with the post-Havdalah burst, and the considerate sender waits for it rather than stacking messages to land at once; Yom Tov adjacency follows the same rhythm, longer; and the daily edges — before seven, after ten — are call-worthy-only hours unless the recipient's schedule is known. None of this is law; all of it is the texture of a community that runs on a shared calendar, and whose messages should honor it.

For the next generation, these norms are curriculum: the teen's first messaging season deserves the etiquette conversation alongside the safety one — the safe-texting foundation covers who and what; this page covers how, and households that teach both raise texters other families bless.

Frequently asked questions