Call screening, done with derech eretz: robocalls, strangers, tzedakah

The telephone's founding assumption — a ring deserves an answer — died somewhere around the ten-billionth robocall, but nobody updated the reflexes. So the household phone still interrupts supper for an extended-warranty recording, the grandmother still answers every call because not answering feels rude, and the one call that mattered — the school nurse, the callback about the apartment — drowns in a sea of spam the family has learned to ignore. Screening is not about answering less. It is about the right calls being answerable at all.

The screening stack, tier by tier

Every tier's foundation: the phone book is the screen. A maintained family contact layer — the four-hundred-name craft — means known callers ring as names, and "unknown" actually means unknown. Screening begins as data hygiene; households with chaotic contacts screen out their own carpool.

Talk-and-text devices screen the classic way, and it works: unknown numbers ring through to voicemail; real callers leave messages; robocalls do not. The craft is a voicemail greeting that invites the message ("please leave your name — we return calls daily") and the callback-window discipline that makes the promise true. The elder generation's version adds the family's speed-dial ladder so that known-and-loved always rings through, per the grandparents' setup.

Secured smartphones add the platform layer: carrier-verified caller identity, the known-spam classes intercepted before the ring, and the household's own rules ("unknowns ring silently during seder hours") — protection in the calling architecture itself, the same built-in-not-bolted-on posture as the rest of the KolBo Phone stack. What the community's platforms rightly avoid is the mainstream apps' trade: crowd-sourced caller-ID services that price their magic in your uploaded phone book — the same data-for-service bargain the household declined everywhere else.

“Screening's goal is not a quieter phone. It is a phone whose ring means something again.”

kolbo.life

The community's special cases

• The meshulach and the tzedakah call. The community's screening dilemma with a neshamah: the unknown evening number is sometimes collection season doing its holy work. Households settle it with policy, not per-ring guilt: tzedakah decisions happen deliberately (the family's giving plan), not under cold-call pressure — so the screening rule stands, the voicemail is warm, and the returned call happens on the household's terms. Screening a call is not screening a mitzvah; it is choosing when the mitzvah gets your full attention.
• The institutional unknowns. The school's office line, the doctor's callback, Hatzolah's return call — the legitimate unknowns that must ring through. The fix is anticipatory contact hygiene: the season's institutions saved before they call, the "A-" emergency prefix pinning the critical ones, and expected-callback windows when you know one is coming.
• The scam classes. The "bank security" call, the code-reading request, the grandparent-targeting emergency impostor — the voice-channel cousins of the recognition guide's scripts, governed by the same three sentences: verify on a channel you already had, urgency is the tell, and no legitimate process needs codes read aloud. Banking's callback rule, per the money-defense playbook, is the screening stack's most valuable single habit.

Screening with menschlichkeit

The etiquette layer keeps screening from curdling into a fortress. The voicemail greeting is the household's front door — warm, brief, honest about the callback window. The returned call comes when promised, which is the entire moral license for not answering live. The known-caller list errs inclusive (the neighbor, the shul office, the kids' friends' parents ring through — community is not spam). And the family teaches its children the same balance it practices: we answer our people, we return real messages, and we owe recordings nothing — a small, complete lesson in guarding attention without hardening the heart.

Frequently asked questions