Event setup
Describe it once. Everything follows.
One plain description of the event. EzzyWorks drafts the calendar listing, the registration page, the reminder emails and texts, and a flyer from your template library. You review, approve, and it goes out.
The problem
The same event, typed six times.
The calendar listing. The registration form. The email. The text reminder. The flyer. The note to the caterer. In most synagogue offices each of these is built by hand, in a different tool, from the same facts. When one detail changes, someone has to remember all six places.
EzzyWorks starts from one description and drafts every piece from it. Change the time once and every piece updates. Nothing sends until a person approves it.
What you get from one description
Six things drafted for you.
A listing and a registration page
Title, date, location, description and ticket options, drafted from your words and ready for your edits. Public, unlisted, or visible only to registered guests. You choose.
Reminders, written and scheduled
A short sequence of emails and texts, from the first announcement to the day-before reminder, drafted in your voice and placed on the calendar. Edit any of them before approving.
A calendar that knows the Jewish year
Hebrew dates, candle lighting and holidays are built in. Nothing is scheduled to send on Shabbat or chag, and clashes with clergy availability are flagged before you publish.
Catering and headcount, handled
Set who the caterer is and how many days ahead they need numbers. EzzyWorks sends the working headcount on that day, and again when you ask. Add setup and service notes in plain text. No food? Skip it.
A flyer from your templates
Pick a template from your library and the event details fill in. Download it for the lobby, the bulletin or social media.
One approval, then it runs
Submit for approval and the event locks. One approver, one email, one click. After that, the listing is live and the reminders run on schedule.
How it works
From a sentence to a live event.
Describe
Write what the event is, when, where and who it is for, in plain words.
Review the drafts
Listing, registration, reminders and flyer appear. Edit anything.
Approve
One approver signs off. Until then, nothing is public and nothing sends.
It runs
Registration opens, reminders go out on schedule, the headcount reaches the caterer.
Good to know
Before you ask.
You stay in control.
Every draft is editable and nothing goes out without approval. EzzyWorks writes the first version; your team decides the final one.
Shabbat and chag are respected by default.
Quiet hours are on from the start. Anything that would land during Shabbat or a holiday moves to after Havdalah.
It is not a CRM.
EzzyWorks runs the event. Your membership system stays where it is and keeps doing what it does.
Related: Planning Team, the EzzyWorks blog, and on ShulWorks, why we built EzzyWorks
Bring one event. Watch it get built.
A 30 minute walkthrough. We describe your next event together and you see every piece appear.