The gabbai role sits at the intersection of pastoral care, logistics, and financial accountability. Gabbaim track who has received aliyot, manage requests from families observing yahrzeits or simchahs, record kibbudim, and — critically — ensure that pledges made at the bimah actually flow through to billing. When these workflows are managed on paper or disconnected spreadsheets, pledge revenue leaks and gabbai context doesn't transfer between terms.
In many shuls, aliyah requests come in through phone calls, emails, text messages, and in-person conversations — all to different gabbaim. There is no central queue, no way to see all pending requests at once, and no way to confirm that a request was received and will be honored.
When a congregant makes an aliyah pledge at the bimah, that pledge needs to be recorded, connected to the member's household billing record, and followed up on. In shuls without a structured pipeline, a significant portion of aliyah pledges are never invoiced — because the gabbai who recorded it isn't the one who manages billing, and there is no handoff mechanism.
Gabbaim develop institutional knowledge about which families have received specific kibbudim, how recently, and what considerations apply. When a gabbai's term ends and that knowledge is in their personal notes, the next gabbai starts from scratch. Families notice the loss of this context.
Yahrzeit-driven aliyah requests are time-sensitive and emotionally important. Without a connection between yahrzeit records and the aliyah queue, gabbaim cannot proactively plan for known upcoming yahrzeits — they only see demand when a family member calls.
Congregants submit aliyah requests through the member portal, providing the occasion, any relevant context, and their contact information. All requests flow into a single gabbai-managed queue — no more tracking requests across multiple channels.
When a pledge is recorded at the bimah, it is attached to the household's billing record in the system. The billing team sees the pending pledge without requiring a separate communication from the gabbai. Revenue that would otherwise be lost stays in the pipeline.
Each kibud given — aliyot, hagbah, gelilah, pesicha, leading services — is recorded with the recipient, the date, and the service. Gabbaim can review history before calling someone up, ensuring that kibbudim are distributed with appropriate consideration and that context survives leadership changes.
Gabbaim can view upcoming yahrzeits in their planning interface and anticipate aliyah demand before it arrives. Families with yahrzeit records in the system who have also submitted an aliyah request appear with the full context attached.
Gabbai users have access to the aliyah queue, kibbudim records, and yahrzeit planning views without access to financial records or administrative settings that are outside their role.
When a family submits an aliyah request, the gabbai sees their member profile, yahrzeit records, recent kibbudim history, and any relevant household notes — all in one place, without switching between systems.
The aliyah request portal is included on all GabbaiPro plans. The aliyah pledge-to-invoice pipeline, kibbudim history and reporting, and yahrzeit-to-aliyah planning views are included on Growth and Pro plans.