Learn how to respect communication preferences, recognize valid permission, handle unsubscribe requests, and prevent unwanted messages across ministry communication channels.

1. Why Communication Preferences Matter

Ministries communicate with people for many reasons, including event information, appointments, newsletters, requested support, and administrative matters.

However, a contact's presence in the CRM does not automatically establish permission to send every type of message.

Responsible communication means recognizing the recipient's choices, applicable legal requirements, and the purpose of each message.

Learning Objective: Understand the differences between contact information, communication preferences, consent, and opt-out status—and know what to verify before sending or automating ministry messages.

2. Understanding Consent

Consent refers to permission given for a particular communication activity. Applicable requirements depend on the channel, purpose, technology, jurisdiction, and circumstances of collection.

Permission Is Context-Specific

Someone registering for an event may provide information needed to administer that event. This does not necessarily authorize unrelated promotional text messages.

Likewise, a person who subscribes to an email newsletter has not necessarily agreed to receive marketing SMS messages.

Information	What It Tells Us
Email address	A possible destination for email, not proof of universal sending permission.
Mobile number	A possible SMS destination, not automatic SMS consent.
Documented opt-in	Evidence of a specific agreement, subject to scope and applicable rules.
Opt-out request	A communication restriction that must be respected and processed.

Important: Do not assume that consent for one ministry, purpose, or channel automatically transfers to another ministry, purpose, or channel.

3. Understanding Contact Preferences

Communication preferences help a ministry understand which types of contact a person wants to receive.

Preferences may vary by topic, communication channel, or type of message. Some platforms offer subscription-management features, but their actual capabilities must be confirmed before implementation.

Example Communication Preferences Fictional training illustration — not connected to GHL

Email Newsletter Periodic ministry news and updates

Opted In

Promotional SMS Text messages about promotions and events

Not Opted In

Appointment Reminders Requested scheduling communications, subject to applicable requirements

Enabled

General Ministry Announcements Broader announcements and updates

Unsubscribed

These statuses are invented for instruction. They do not represent actual GHL fields, verified consent, or a functioning preference center.

Important Distinction

A preference shown in a contact profile must reflect the actual authorized system of record. Users should not invent, guess, or manually fabricate consent.

4. Recognizing Unsubscribe & Opt-Out Requests

An opt-out occurs when a recipient communicates that they do not want certain messages to continue.

Different channels can use different opt-out mechanisms. For example, marketing email commonly provides an unsubscribe mechanism, while SMS programs often support STOP and other recognized requests to discontinue messages.

Scenario A — Email

A newsletter subscriber clicks Unsubscribe. The request must be processed according to the applicable email and platform requirements.

Scenario B — SMS

A person replies, "Please stop texting me." This must be treated as an opt-out request where applicable, even though the person did not use the exact word STOP.

Scenario C — Conversation

A contact asks to stop receiving event promotions but still needs information about an existing appointment. The request should be handled according to its scope and the rules for each message type.

Critical Safeguard: Never work around an opt-out by changing contact information, creating duplicate records, or sending from another ministry account. Escalate uncertainty before sending.

5. Verifying Eligibility Before Sending

The safest communication workflow includes a pre-send review of the proposed recipient, message purpose, and applicable communication status.

Identify the message purpose Determine whether the communication is promotional, operational, transactional, or a response to an inquiry.

Identify the channel Confirm whether email, SMS, or another supported channel will be used.

Check documented permission Review the applicable consent, preferences, and suppression information.

Check the selected audience Confirm that recipients belong to the correct ministry tenant and authorized audience.

Resolve uncertainty before sending Pause the send when the required permission or audience eligibility cannot be established.

CRN Operating Principle: When the necessary permission cannot be established, do not guess. Refer the matter to the authorized administrator or compliance process.

6. Preferences & Automated Messaging

Automation can send messages repeatedly and at scale. This makes correct recipient eligibility especially important.

Before an automated messaging workflow is activated, its owners should verify applicable consent and suppression checks, triggering conditions, audience boundaries, and the procedure for responding to opt-outs.

Examples of Risks

Sending a newsletter to someone who has unsubscribed.
Triggering promotional SMS without the required consent.
Sending duplicate messages because multiple workflows share a trigger.
Using an outdated or incorrectly imported contact list.
Ignoring a suppression status because a contact has a particular tag.

CRN Contact Communication Settings A verified, redacted screenshot of the actual GHL contact preferences and messaging controls will be added during platform testing.

Change Management: Modifying consent handling, opt-out suppression, or bulk-message eligibility is a controlled operational change. Use authorized testing and the approved CRN Change Management process.

7. Records, Privacy & Accountability

Ministries should maintain appropriate records of consent and communication restrictions according to their policies and applicable requirements.

Evidence may include the agreed scope, collection method, date, relevant disclosure, and subsequent changes or opt-out requests, as appropriate.

Responsible Recordkeeping

Use authorized systems for recording communication permissions.
Preserve accurate information about consent and restrictions.
Limit access to those with a legitimate ministry responsibility.
Do not treat tags alone as proof of a complete consent history.
Do not delete or override an opt-out merely to enable a campaign.
Keep tenant information segregated under server-enforced authorization.

Governance Boundary: This training lesson introduces operational safeguards. Specific legal requirements, retention periods, and required consent language must be determined by the ministry's applicable laws, approved policies, and qualified compliance guidance.

8. Practice Exercise & Knowledge Check

Use fictional contact records in an approved training environment. Do not alter real subscription or consent settings as part of this exercise.

My Learning Checklist I understand that possessing an email address or phone number does not establish universal consent. I can explain why consent may differ by channel and purpose. I know how to recognize an unsubscribe or opt-out request. I understand why automations must respect suppression and eligibility requirements. I know to escalate unclear permissions rather than guessing.

Knowledge Check

Does a contact's presence in the CRM automatically authorize marketing communications?
Can permission to receive a newsletter automatically establish permission for promotional SMS?
What should you do when someone requests that messaging stop?
Why are consent and suppression checks important for automations?
What should you do when the required permission is unclear?

Lesson Complete! You now understand the foundational principles of contact preferences, communication consent, opt-out handling, and responsible audience management.

Contact Preferences, Consent & Opt-Outs