Church-Ops Africa Stewardship with Vision
Home Features Pricing Docs About
Login Create Account
arrow_back Back to documentation
Secretariat and media schedule 6 min read Updated Jun 12, 2026
campaign

Communications

Run WhatsApp-first campaigns, enabled channels, templates, signatures, and pacing workflows responsibly.

Church-Ops Africa Communication Guide

Effective communication keeps the church informed, cared for, and connected. This guide reflects the live Church-Ops communication experience as it exists today: WhatsApp-first outreach, optional additional channels, reusable templates, signatures, pacing controls, and campaign review.

Table of Contents

  1. Communication Channels Overview
  2. Setting Up WA Bridge for WhatsApp
  3. Drafting and Sending Campaigns
  4. Using Dynamic Message Templates
  5. Managing Sender Signatures
  6. Alerts, Reminders & Review Workflows
  7. Best Practices for African Ministry Engagement
  8. Common Mistakes to Avoid

1. Communication Channels Overview

Church-Ops Africa supports multiple delivery channels, but not every church will use every channel at the same time.

Channel Best For Technical Infrastructure Data Cost to Member
WhatsApp Daily devotionals, urgent alerts, group updates, giving receipts WA Bridge / approved WhatsApp route Low
SMS Time-sensitive alerts for members without strong internet access SMS provider if enabled Free to receive
Email Longer announcements and structured updates Email provider if enabled Medium
Push Alerts inside the member portal experience Web push / portal notifications Very low

2. Setting Up WA Bridge for WhatsApp

WhatsApp is the primary outreach surface for many churches, so Church-Ops keeps its WhatsApp controls in one dedicated setup area.

Steps to Configure WA Bridge

  1. Log into the management portal as a church admin or another authorized role.
  2. Open Settings Center > Communications & WhatsApp.
  3. Review and save the church outreach identity:
    • Message Sign-Off
    • Church Message Sender Name
    • Optional Message Header Image
  4. Review the church WA Bridge connection details:
    • Connected WhatsApp Number
    • Device Name
    • Friendly Display Name
    • Base URL if your church overrides the platform default
    • Incoming Webhook URL
    • API Key / Extra Header Fields
    • Default Country Code
  5. Set the default pacing values so large sends do not look abusive:
    • Delay Between Messages
    • Daily Send Limits
    • Any church-specific pause rhythm your setup requires

Note Acceptance by WA Bridge is not the same thing as final delivery on the member's phone. Delivery updates still depend on the connected WhatsApp session and provider behavior.

3. Drafting and Sending Campaigns

Visual note: Create Campaign interface showing channels, text editor, and target audience options

Step 1: Access the Composer

Open Outreach Center and choose Campaign Composer.

Campaign Composer keeps audience, channel, subject styling, reusable campaigns, and reusable templates visible before the message body. Optional CTA and pacing controls stay compact, while the closing signature remains the final message-setting field.

Step 2: Set the Audience

Select your target group in the Audience Scope dropdown:

  • All Members: Broadcast to the entire directory.
  • Cell Group: Send to a specific home cell or small group.
  • Ministry Team: Send to department workers (e.g., Choir, Ushers Team).
  • Selected Members: Multi-select specific individuals.

Step 3: Choose the Preferred Channel

Choose WhatsApp, SMS, Email, or Push. (If WhatsApp is selected, the system will verify the WA Bridge status).

Step 4: Write the Body and Add a Call to Action (CTA)

Write your message content. You can add one primary CTA link and decide where it appears:

  • CTA Label: e.g., Read Devotional or Give Online
  • CTA URL
  • CTA Style
  • Optional inline placement tokens such as @{{cta}}, @{{cta_button}}, or @{{cta_plain}}

Step 5: Save Draft and Verify Recipients

Review the drafted campaign summary. Verify the recipient list size. When ready, click Queue & Send. The campaign will process in the background according to your pacing rules. If a sending worker is interrupted, Church-Ops safely recovers the outstanding message and continues the campaign without requiring the campaign to be queued again.

4. Using Dynamic Message Templates

To make broadcasts feel warm and personal, use dynamic template variables. The system parses these tags at the moment of delivery for each recipient.

Supported Variables:

  • {{first_name}} or @{{first_name}} -> Inserts the member's first name.
  • {{last_name}} or @{{last_name}} -> Inserts the member's family name.
  • {{name}} -> Inserts the full name.
  • {{church_name}} -> Inserts the church's name.

Guest follow-up assignment templates also support:

  • {{assignee_name}}, {{guest_name}}, {{visit_date}}, {{service_attended}}
  • {{decision_made}}, {{follow_up_status}}, {{membership_interest}}
  • {{deadline}} and {{task_link}}

Sensitive guest placeholders such as {{guest_phone}}, {{guest_whatsapp}}, {{guest_email}}, {{guest_address}}, {{invited_by}}, and {{prayer_request}} are deliberately rendered as protected in the outbound assignment. The assigned caregiver sees their real values only after accepting the authenticated portal task.

Example Devotional Broadcast Template:

Shalom {{first_name}}!
Here is today's devotional reflection:
"The Lord is my Shepherd, I shall not want." (Psalm 23:1)

Take time to meditate on God's goodness today. Join us at this evening's fellowship gathering if you are available.

5. Managing Sender Signatures

Official signatures add credibility to outgoing messages and tell members exactly who sent them.

  1. Open Communication Hub > Signature Studio.
  2. Create or edit a reusable signature.
  3. Define the identity:
    • Label
    • Usage Scope
    • Ownership Scope (shared, personal, or role-specific where allowed)
    • Signature Body
  4. Choose whether to make it the Default Signature.

Church-Ops uses one shared Signature Studio across direct outreach, campaigns, workflows, and guest follow-up. Signatures are managed in Communication Hub, subject to channel, ownership, and usage scope. Signatures with Manual or All usage appear in direct outreach, while Campaign or All signatures appear in campaign composers. Signatures are always placed last in the final sent message.

5A. Managing Reusable Templates

  1. Open Communication Hub > Template Studio.
  2. Save the message structures your team uses often, such as prayer updates, event reminders, giving receipts, and follow-up notes.
  3. Keep each template ready with:
    • Title
    • Body
    • optional CTA label and CTA link
    • the preferred signature
  4. Reuse the same tenant-scoped templates from the Outreach Composer, message campaigns, guest follow-up assignment, and supported workflow actions.

Church-Ops now uses one shared Template Studio for church communication templates. Older outreach-template records remain readable for existing queue links and history, but new composer choices and edits should happen in Template Studio.

5B. Conversations and Delivery Reports

The Inbox / Conversations page receives WhatsApp replies through the configured WA Bridge webhook and refreshes an open conversation automatically. Automated companion keywords are also preserved in the conversation history so staff can see the complete exchange.

Open Outbox & History to review outbound messages. Every tracked message shows one of these delivery states:

  • Sent: WA Bridge accepted the message.
  • Delivered: WhatsApp confirmed delivery to the recipient device.
  • Read: WhatsApp confirmed the recipient opened the message.
  • Failed: Delivery failed; the provider reason is shown when available.

6. Alerts, Reminders & Review Workflows

Church-Ops includes reminder and alert surfaces, but churches should still review how outbound communication is actually being sent before depending on automation alone.

Practical Uses

  • Birthday reminders once birthdates are present and the church has enabled that workflow.
  • Follow-up awareness for care teams through alerts, tasks, or reviewed campaign sends.
  • Reusable templates for recurring announcements that still need a human review step before broad delivery.

7. Best Practices for African Ministry Engagement

  • Optimized Timing: Send morning devotionals between 5:30 AM and 6:30 AM when members wake up. Send meeting reminders 24 hours prior to save data costs.
  • Keep WhatsApp Campaigns Brief: Avoid sending messages longer than 3,800 characters to prevent WA Bridge timeouts.
  • Data-Free Alternatives: Use SMS for critical announcements (such as funeral alerts or sudden service shifts) so members without internet remain informed.

8. Common Mistakes to Avoid

  • Spamming WhatsApp numbers: Sending 500+ messages without a delay timer will get your church's SIM card blocked by MTN/Orange or flagged by WhatsApp. Always keep per-message delay active (minimum 3 seconds).
  • Using Raw Copy-Paste Links: When adding CTA links, verify they begin with http:// or https:// otherwise the CTA treatment will not work correctly.
  • Unregistered Members: Dynamic templates like {{first_name}} require correct directory inputs. If a member's name is blank, the system displays a fallback (e.g., "Shalom Beloved!").