10. Vertical modules

Modules: Support, Events, Recruitment, Donors, Pastoral care

Five modules for five kinds of work. Each is small on its own — that is the point. They are not separate products bolted on; they are thin layers over the same contacts, sharing the same activity log, the same relationship health, the same automations.

Switch on the ones that describe your work and ignore the rest.

10.1 Support

Tickets against contacts, with a status (open, in progress, resolved, closed) and a priority (low, normal, high, urgent).

The reason to keep tickets here rather than in a dedicated helpdesk is that a support history is part of a relationship. When you open a contact and see four urgent tickets in two months next to a won deal, you know something a separate helpdesk would never have told you.

Reports → Support shows volume and resolution mix.

10.2 Events

Events with a date, a location and a capacity. Attendees move through registered → confirmed → attended, no-show or cancelled.

Attendance history stays on the contact, which is the real value: you can see that someone came to four things last year and nothing this year, and that is a signal no amount of email tracking would give you.

Invitations can target an event — a tokenised invite that emits invitation.accepted when someone says yes, which automations can act on.

Reports → Events aggregates attendance.

10.3 Recruitment

A candidate pipeline: applied → screening → interview → offer → hired or rejected, with notes per candidate.

Candidates are contacts. This is deliberate and it is the whole reason to do recruitment here rather than in an ATS: the person you interviewed and did not hire is still someone you know, still in your network, and still there next year when a different role opens. An ATS forgets them. A CRM does not.

10.4 Donors

Fundraising campaigns and individual donations recorded against contacts, with top-donor rankings and a giving report at Reports → Donors.

This module pairs unusually well with chapter 3. Donor relationships are exactly where the two failures show up hardest: the major donor nobody has spoken to in eight months, and the loyal small giver who receives every appeal you send and has started deleting them unopened.

10.5 Pastoral care

Two things.

Small groups with members and roles.

Pastoral needs with an urgency level — low, normal, high, urgent — recorded against a person.

Needs can also be raised from outside. Another platform of yours can push an alert through the API, which creates the need and emits alert.raised onto the event bus. That means a form on a church website, or a button in another app, can put someone in front of a pastor without anyone re-typing anything.

This module is the clearest example of what the product is for. Nobody in pastoral care has a pipeline. What they have is eight hundred people, a finite amount of attention, and no way of knowing who has quietly slipped through — which is the problem described on the first page of this manual, in its purest form.