One of the things I love about Church Community Builder (CCB) is the ability to build and automate “people processes.” You know, like assimilation, serving, spiritual growth and development, etc.
In the post, Workflow Process Implementation, I describe the use of “workflow tools” to implement processes and procedures. At my church, we used two different “tools” for implementing workflow processes. The fundamental split was between “people” and “business” (or non-people) processes.
For business processes, we had The Management System. Read more about that HERE.
For people processes, we used the workflow capabilities of CCB. CCB gave us the ability to make sure nobody got “lost in the shuffle,” so to speak.
Here’s how it worked. We got together and defined the steps one should go through to get connected. We drew a flowchart showing how a new person moved from filling out a communication card to getting connected to a ministry leader if they expressed interest in serving somewhere, getting invited to the next newcomer’s class, getting connected to a group leader if they expressed interest in joining a group, getting contacted by our Connections Pastor if they were interested in learning more about baptism, etc.
We took the flowchart and used it as a guide for implementing a “process” in CCB. The process consisted of a series of “process queues,” all of which had “queue managers” notified when a person was put into their queue. The notification went directly to them via e-mail, prompting them to take some action. In some cases, placing a person into an “in progress” status or even a “completed” status initiated some automation that helped to keep people informed about their next step toward being connected.
So, people were followed up on quickly, and nobody got dropped. Everyone ended up in a queue, and they stayed there until they got connected while being periodically followed up on along the way.