What does the shul publish?

In general, we exclusively send information that is within the majority of our members’ best interest to know within the context of their shul membership.

Some examples of first-party content that goes to our shul distributions:

  • Messages from the Rav, Vaad, Committees, etc.
  • Lifecycle announcements of our members
  • Events/Programming updates organized by our shul targeting our membership
  • Important resources/guides/documents
  • Notices to membership as required by Takanon
  • Updates regarding Tefillot/Security

Some examples of third-party content that is sent to our shul distributions:

  • Messages from the municipality/government authorities (where we deem it needs repeating on our channels)
  • Third party events hosted by the Shul where the vaad/committee has agreed/decided to promote it
  • Lifecycle events of former members or broader community members (where this is relevant enough to our membership to justify sending)

How does the shul communicate?

The shul currently has four main channels for communicating with its members. The first 3 are governed by the shul, while the 4th is a community resource.

  • In-Shul announcements read from the pulpit, after Shabbat/Chag tefillot
  • Email to our distribution list (ad-hoc communications, weekly newsletter)
  • WhatsApp distribution lists
  • Facebook Page/Group (Open for any member to post/comment - with no language or content requirements)

What is our language policy?

We present information in both Hebrew and English. Logistically, this requires that members wishing to post content provide it in both languages, and it may require translation assistance. If things are not provided ‘ready to go’ in Hebrew and English, it may delay delivery while outside translation help is sought out.   

How do I request to share a post/simcha via shul communications?

  • If your post conforms to the guidelines above, send your proposed text (in both English and Hebrew if possible) to comms@ksym.org.il. Requests sent to other people or other addresses are not guaranteed to be included.

  • If you are submitting a flyer for an event, please note the following reqs:

ALWAYS include:

  • A person to contact for more information
  • KSYM logo
  • Language of lecture
  • Time and place of event
  • Customized design for KSYM where both Hebrew and English fit on a single flyer.

What is the policy on life cycle announcements?

Note: Only building fund members and trial members are eligible to have their life cycle announcements published. 

  • Engagement/Wedding/Birth - When parents are the baalei simcha, these are announced once as a standalone email and whatsapp and in the newsletter most closely following the event, and also as an in-shul announcement. If the baalei simcha would like to announce in the newsletter preceding the event instead, e.g., the shabbat before a wedding rather than after, they can request to do so.

NOTE: When grandparents of the simcha are members, these are announced once in the weekly newsletter and as an in-shul announcement.

  • Bar/Bat Mitzvah - in-shul announcement and weekly newsletter the shabbat of/before the simcha (no standalone email/whatsapp).
  • Giyyus - in-shul announcement and weekly newsletter the shabbat before giyyus (no email or standalone whatsapp). NOTE: our policy is that we do not include specifics of the giyyus (branch, tafkid, etc.).
  • BDEs - Email and standalone whatsapp sent upon BDE of 1st-degree relative of member, plus in-shul announcement and weekly newsletter.

What is the policy on event/shiur announcements?

  • Events/shiurim are announced once as standalone email as well as in the newsletters leading up to the event. 

  • If there is a mistake in the original email or the event/shiur is cancelled/postponed, an email and whatsapp is sent.

  • Regarding event reminders: We can send a Whatsapp reminder for an upcoming event within 48 hours of the event’s start. As the typical event will be announced in the initial standalone announcement, as part of the newsletter, and in a reminder, there’s no need to send additional reminders to boost turnout