Commitment

Synago’s main scheduling algorithm is based upon the commitment of the users. Instead of having large calendars with attendance scheduled long into the future, Synago only looks at 1 week intervals, and plans attendance in accordance with that.

Plan

Imagine a week has been scheduled, and in the first three days, two already has achieved a minyan.

DaysAttendeesMinyan?
Sunday9
Monday11
Tuesday10
(...)

Persona

Then David signs up.

Guy

David looks a bit like the guy who founded Synago.

Commitment

He’s pretty busy and has an unpredictable calendar, so he only signs up for 1 day each week.

Commitment

Plan (before)

Synago then looks at the plan as it is currently:

DaysAttendeesMinyan?
Sunday9
Monday11
Tuesday10
(...)

Scheduling

Magic happens.

Plan (after)

And in this case, places David the only obvious place, which is Monday.

DaysAttendeesMinyan?
Sunday9
+ David
= 10
Monday11
Tuesday10
(...)

That’s all?

For the sake of simplicity, the above example is pretty straight-forward. But a real world example is not much different. It only gets a bit more complicated when you calculate in 3 services each day, yahrzeits, preferred days and concurrence, when multiple users are updating their commitments at the same time, to mention a few.

This means that the schedule can update and change during the week, when users create or change their committed days.

In the above example, the 9 other people assigned to Monday would receive the following notification:

Conversation

synago.io

Dear Yoshua, we are happy to inform you that a user has signed up for a service on Sunday, meaning that minyan on this day is now guaranteed. We look forward to seeing you in the Synagogue. Best regards, Synago.

Would you like to know more?

A more thorough example is available in the About-section.

Help & Support