AI Receptionist for Kosher Caterers + Jewish Event Services
Vaad-certified caterers serving weddings, sheva brachos, brisses, bar/bat mitzvahs, and Shabbos kiddushes — every call captures hashgacha, dietary category (meat/dairy/pareve/fish), headcount, venue, occasion-type (festive vs grief). Shabbos / yom tov / yom kippur silence is a first-class configuration: the AI does NOT pick up, transcribe, or respond inside the observance window.
“Sholom aleichem, this is the AI assistant for Goldberg Catering. Tell me what's the simcha and when, and I'll get you a starting quote.”
Built for the calls kosher catering + Jewish event services actually get
Shabbos + yom tov silence — DO NOT pick up the phone
From Friday candle-lighting to Saturday nightfall (and on all yom tov days), the AI is configured (Settings → Business hours → Religious observance → Shabbos) to NOT pick up the phone, NOT transcribe, NOT respond. Callers hear your pre-recorded outgoing message ('We are closed for Shabbos. Please leave a message after the tone'). Candle-lighting + nightfall times are computed weekly from the owner's address (Brooklyn / Monsey / Lakewood / Miami zmanim). Built into safety.ts rule 22a.
Hashgacha + kashrus vocabulary — AI knows the lexicon
Cholov yisroel, pas yisroel, yoshon, glatt, mehadrin, bishul yisroel, milchig vs fleishig vs pareve, kli rishon, yashan vs chodosh, gebrokts — the AI knows the vocabulary. Captures the caller's kashrus requirements as a structured field; never agrees to 'we can do cheese on the brisket platter' (an AI cheerfully violating mixing meat-and-dairy is brand-ending). Hashgacha attestation ('is this venue Vaad-approved?') routes to the owner — the AI does NOT improvise on certification claims (rule 21b).
Sheva brachos vs. shiva vs. aufruf — different occasions, different decorum
The AI captures the occasion-type early and adjusts tone: chasuna / sheva brachos / aufruf / bris / bar mitzvah / pidyon haben = festive. Shiva / shloshim / yahrzeit / kaddish-minyan = grief. A 'congratulations!' to a shiva caller is catastrophic — and the AI is configured (rule 11c-style death-care tone) to switch tone immediately on grief-context signals.
Yiddish + Hebrew gap — honest disclosure pre-purchase
Yiddish + Hebrew are NOT supported by our voice synthesis provider today. Older Hasidic mothers planning a chasuna will hear English fallback. We disclose this on /languages BEFORE you pay — we'd rather lose your business than have you discover the gap after signing up. Russian (yes, Hebrew = no for now) is supported for FSU-origin Russian-speaking Modern Orthodox + Jewish communities.
Large-batch pricing (8-800 people) — quoteable on the call
Wedding for 600 with 60-table seating, kosher Pesach catering for 80, sheva brachos for 25 — the AI quotes per-head with tier discounts + minimums from your pricing structure. Captures venue + headcount + meat-or-dairy + special-needs (gluten-free, nut-free, mehadrin) up front so your kitchen knows what's coming.
Vaad HaKashrus inspection calls — separate flow
Crown Heights Vaad / OU / Star-K / KAJ inspectors calling for 24-hour mashgiach scheduling get a dedicated booking flow that captures inspector name + agency + window + product line so you don't lose your hechsher to a missed inspection.
How it works for kosher catering + Jewish event services
Religious-observance silence engine
Per-week zmanim computation (candle-lighting + nightfall) from the owner's address. Yom tov days auto-populated from the Hebrew calendar 5-year forward. Owner can override (chol hamoed pickup, yom tov sheni for diaspora, fast days). The AI hard-respects the window — no pickup, no transcription.
Festive occasions (chasuna / sheva brachos / bris / bar mitzvah / pidyon haben / engagement-vort) get cheerful + congratulatory tone. Grief occasions (shiva / shloshim / yahrzeit / kaddish meal) switch to the rule-11c death-care tone. Cross-context occasions (yom kippur break-fast = bittersweet) get a neutral-respectful tone.
Vaad attestation safe default
Caller asks 'is this venue Vaad-approved?' or 'is your kitchen mehadrin?' — the AI does NOT improvise. It answers verbatim from the owner-documented hashgacha record in business_notes ('Vaad Crown Heights certified, certificate #2026-447, expires 2026-09-30') or routes to the owner for confirmation. Hard guardrail — getting this wrong loses your hechsher.
Your dashboard
Here's what you wake up to.
Latest call · 9 min ago
$389
Maria Hernandez · Emergency leak repair
Tomorrow · 9:00 AM· 412 Oak St· with Carlos
“You're booked, Maria — Carlos will be there tomorrow at 9 with parts for a copper pinhole leak.”
From $107/mo (billed annually). No contract. Cancel anytime.
$129/mo if you go month-to-month. Three plans (Starter / Professional / Enterprise), voice cloning included with any active plan, BYO phone number. Most kosher catering + Jewish event services start on Professional for multi-staff routing.
No. Once you configure the Shabbos / yom tov window in Settings → Religious observance, the AI does NOT pick up, transcribe, or respond inside the window — callers hear your pre-recorded outgoing message. Candle-lighting + nightfall are computed weekly from your address. Yom tov days are auto-populated 5 years forward; you can override for chol hamoed / yom tov sheni / fast days. This is hard-coded into safety.ts rule 22a as a religious-conscience configuration, not a feature flag.
▸
Does the AI know hashgacha vocabulary — cholov yisroel, pas yisroel, mehadrin?
Yes. The AI knows the lexicon: cholov yisroel, pas yisroel, yoshon, glatt, mehadrin, bishul yisroel, milchig vs fleishig vs pareve, kli rishon, yashan, gebrokts. Captures the caller's kashrus requirements as a structured field so your kitchen sees them up front. The AI never improvises on certification claims — Vaad attestation routes to you (rule 21b).
▸
Will the AI mix meat and dairy or get the occasion-type wrong?
No. Meat / dairy / pareve / fish is a structured field captured early in the call. If a caller says 'we want cheese on the brisket platter,' the AI flags the conflict + takes a message for your review instead of agreeing. Occasion-type (festive vs grief) is captured early; a shiva caller never gets 'congratulations!' decorum.
▸
Yiddish + Hebrew — supported for my older customers?
Not today. Our voice synthesis provider does not yet support Yiddish or Hebrew. Older Hasidic mothers calling in Yiddish will get English fallback — half may hang up. We disclose this BEFORE you pay (on /languages). If your customer base is heavily Yiddish-first, email hello@ringdispatch.com before signing up. Russian IS supported for FSU-origin Modern Orthodox + Jewish communities.
▸
Can the AI quote a 600-person wedding price live?
Yes — list your per-head pricing tiers (40-99 people $85/head, 100-249 $75/head, 250+ $65/head, 500+ $55/head), minimums, deposit policy, and surcharges (kosher pesach +30%, glatt mehadrin +15%, mashgiach temidi flat $400). The AI quotes a starting number live for any caller who provides headcount + occasion + dietary category.
▸
How do you handle Vaad / OU / Star-K inspector calls?
Separate booking flow with inspector name + agency + window + product line captured up front. Inspector calls are routed urgently (urgent SMS-page) even outside business hours so you never miss a hechsher inspection.
Set up your AI receptionist in 5 minutes
Pick your kosher catering services, hours, and voice. Your AI is answering test calls inside 10 minutes.