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.
I did a post on “Workflow” Process Implementation a while back. In the post, I described the use of “workflow tools” to implement processes and procedures. Here at CCV, we’re using two different “tools” for implementing workflow processes. The fundamental split is between “people” and “business” (or non-people) processes.
For business processes, we have The Management System. Read more about that HERE.
For people processes, we’re using the workflow capabilities of CCB. CCB gives us the ability to make sure nobody gets “lost in the shuffle,” so to speak.
Here’s how it works. We got together and defined the steps one should go through to get connected here at CCV. We drew a flowchart showing how a new person moves from filling out a communication card to getting connected to a ministry leader if they express interest in serving somewhere, getting invited to the next newcomer’s class, getting connected to a group leader if they express interest in joining a group, getting contacted by our Pastor of Pastoral Care if they are 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 consists of a series of “process queues,” all of which have “queue managers” notified when a person is put into their queue. The notification goes 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 initiates some automation that helps to keep people followed up upon and getting connected.
So, people are followed up on quickly, and nobody gets dropped. Everyone ends up in a queue, and they stay there until they get connected, being periodically followed up on along the way.