What "Shabbos-aware" actually means for your automation

Every mosad and frum-owned business I've worked with has a story about the time a system texted a donor at 8pm on Friday. Usually it's a Mailchimp campaign somebody forgot to hold. Sometimes it's a CRM sequence that fired because a form was submitted twenty minutes before candle-lighting. The result is the same: apologies, embarrassment, and a lingering suspicion that this is what happens when you trust software.

What the Shabbos-aware layer does

Every outbound action — email, SMS, phone call, campaign, receipt, thank-you letter, invoice reminder — checks a calendar before it goes out. The calendar includes:

• Shabbos, starting 18 minutes before shkiyah in your zip code and ending at your local Motzei Shabbos.
• Every yom tov, including yontif sheni for the diaspora.
• Any dates the organization marks off — sefiras haomer, tisha b'av, a family shloshim, whatever applies.

A send that would fire during a blocked window is either held for the next kosher time slot, or dropped entirely if it's stale (a same-day reminder for a Shabbos meal isn't useful on Sunday).

How it's built

Nothing exotic. A small service exposes a single function every automation calls before it sends:

// Returns { allowed: boolean, holdUntil?: Date, reason?: string }
const ok = await jewishCalendar.canSend({
  to: recipient,           // recipient's zip / timezone
  at: new Date(),
  kind: "sms",             // "sms" | "email" | "campaign"
});

if (!ok.allowed) {
  return schedule.hold(message, ok.holdUntil);
}
await send(message);

This is included by default in every build for a mosad, school, or frum-owned business. No line item. It's just the right way to run automation in this market — and I've never met an operator who wanted the alternative.