Learn how to turn ministry inquiries into accountable follow-up actions, assign responsibilities, track progress, and understand how approved workflows support communication without replacing human judgment.

1. From Conversation to Action

Ministries receive messages that require more than an immediate answer. A person might request event information, need help with registration, or report a problem that requires follow-up.

A conversation provides communication history. A task assigns responsibility for a particular action. A workflow organizes a process that may coordinate or automate authorized steps.

Component	Purpose
Conversation	Records supported communications with a contact.
Task	Identifies an action, an owner, and an expected follow-up.
Workflow	Coordinates defined actions based on configured triggers and conditions.
Help Desk / Change Management	Provides a controlled process for support incidents, requests, and system modifications.

Learning Objective: Understand when a message requires a task, how to assign and complete follow-up, when automation is appropriate, and when an issue must enter an authorized support or change-management process.

2. Understanding Follow-Up Tasks

A follow-up task helps ensure that an important request has an identifiable person responsible for completing it.

Depending on the enabled GHL functionality, authorized users may be able to create tasks, assign owners, select due dates, and mark work complete.

What Makes a Useful Task?

A clear description of the action required.
An authorized person responsible for the work.
An appropriate due date or priority.
Enough context to understand the request.
A defined way to recognize completion.

Example Ministry Follow-Up Board Fictional training data — not a live task board

Respond to sample event inquiry To Do

Owner: Example Coordinator Due: Next scheduled workday

Review sample volunteer request In Progress

Owner: Example Volunteer Lead Due: Per ministry procedure

Confirm fictional registration response Completed

Owner: Example Administrator Completed: Training example

This is an instructional illustration. The status labels, assignment fields, and layout are not a verified GHL task interface.

3. Assigning Responsibility & Tracking Progress

Assigning a task should establish accountability without granting unnecessary access to private ministry information.

The task owner should understand what needs to happen, when it is expected, and when to request assistance.

Identify the required action Turn the request into a clear, actionable description.

Choose an authorized owner Assign the work to the appropriate person or ministry role.

Set an appropriate deadline Consider urgency, service expectations, and operational needs.

Track the outcome Record progress according to the authorized process.

Confirm completion Mark work complete only when the required action has actually been performed or appropriately resolved.

Accountability Principle: Assigning a task is not the same as completing the work. A follow-up remains open until the required outcome is confirmed or formally resolved.

4. Understanding Communication Workflows

A workflow is a configured sequence of actions that begins when a defined trigger or event occurs and applicable conditions are satisfied.

For example, an approved ministry process might respond to a new inquiry by creating a task for an authorized team member.

Illustrative Follow-Up Process

FICTIONAL COMMUNICATION WORKFLOW

New Ministry Inquiry Received Authorized event triggers a review

Check Contact and Ministry Context Confirm tenant, record association, and permitted handling

Is human follow-up required?

YES Assign task to the authorized ministry team

NO Continue approved processing without creating an unnecessary task

Review Outcome & Close Confirm the action was completed or appropriately escalated

Conceptual diagram only. This does not create, activate, or demonstrate a configured live GHL workflow.

Workflow Boundary: A workflow should never be treated as permission to bypass required human review, consent restrictions, tenant authorization, or ministry operating procedures.

5. Responsible Automation & Follow-Up

Automation can reduce repetitive administrative tasks, but only when its triggers, conditions, audience, and outcomes have been reviewed.

Appropriate Automation Examples

Creating an internal follow-up task when a qualifying inquiry is received.
Notifying the assigned ministry team through an approved internal channel.
Recording a defined operational event for authorized follow-up.
Sending a permitted appointment reminder when applicable consent and configuration requirements are satisfied.

Automation Risks

Duplicate triggers creating repeated tasks or messages.
Incorrect conditions selecting the wrong contacts.
Messages being sent after an opt-out or suppression event.
Follow-up being assigned to someone without appropriate permissions.
An automation continuing after the original request is resolved.

CRN Design Principle: Processes that create records, billable activity, or external side effects require duplicate-event protection. Webhook retries and repeated triggers must not produce unintended duplicate work, sends, or charges.

6. When to Escalate or Use the Help Desk

Some requests are ordinary ministry follow-up tasks. Others require formal technical support, approvals, or controlled system changes.

A conversation or simple CRM task should not replace the approved Help Desk and Change Management procedures when those procedures apply.

Situation	Appropriate Next Step
General event inquiry	Respond or assign normal ministry follow-up.
Routine callback request	Create an appropriately assigned follow-up task.
System access problem	Use the approved technical support process.
Request to modify a live workflow	Follow authorized Change Management procedures.
Possible security incident	Escalate promptly through designated incident procedures.

Important: A ministry user's request does not, by itself, authorize a configuration change. Requests affecting security, entitlements, automations, billing, or other platform controls must follow the appropriate approval and testing procedures.

7. Security, Monitoring & Accountability

As ministry operations grow, follow-up processes should remain clear, auditable, and appropriately restricted.

Responsible Operating Practices

Assign work only to users authorized for the relevant ministry and information.
Avoid exposing sensitive details in task titles or broad notifications.
Review overdue tasks through the ministry's approved procedures.
Test workflow changes in an approved environment before production activation.
Confirm automated messages respect recipient preferences and opt-out restrictions.
Monitor messaging and other usage-based costs where services are enabled.
Maintain appropriate records of approvals and changes.
Reconcile workflow outcomes with the actual work completed.

CRN Tasks & Workflow Screenshot Verified screenshots from the authorized ministry-user training environment will be inserted after practical configuration testing. Personal data must be excluded or appropriately redacted.

Security Boundary: Task assignment, contact tags, and workflow filters do not replace server-enforced tenant authorization. Users must only access records and operations permitted by their CRN roles and entitlements.

8. Practice Exercise & Knowledge Check

Use fictional contacts and an approved training environment. Do not activate live workflows, send real communications, or change production assignments during this exercise.

Practice Scenario

A fictional contact sends a ministry inquiry requesting information that must be reviewed by an authorized event coordinator.

Consider what the team should do to ensure the question receives an appropriate response.

My Learning Checklist I can explain the difference between a conversation, task, and workflow. I can identify an appropriate task owner and follow-up deadline. I understand that assigning a task does not mean the task is complete. I recognize why automated messaging requires audience, consent, and duplicate-event checks. I know when to use the Help Desk or Change Management process instead of a routine task. I understand that workflow configuration does not replace CRN tenant or role authorization.

Knowledge Check

What is the difference between a conversation and a task?
What information makes a follow-up task actionable?
Why should duplicate workflow triggers be prevented?
When must a request be escalated through the Help Desk or Change Management?
How should a team verify that follow-up is truly complete?

Lesson Complete! You have completed the foundational Communications training sequence. You now understand how conversations, email, SMS, reusable responses, communication preferences, tasks, and workflows work together to support responsible ministry operations.

Follow-Up Tasks & Communication Workflows