Learn how to use text messaging responsibly, understand recipient consent, manage replies, protect sensitive information, and recognize the costs associated with SMS communications.

1. Understanding SMS Messaging

SMS stands for Short Message Service. It provides a way to exchange text messages through supported mobile messaging networks.

Ministries may use approved SMS services for reminders, requested updates, or other permitted communications.

Access depends on the ministry's subscription, messaging configuration, sender registration requirements, and assigned permissions.

Learning Objective: Understand when SMS may be appropriate, how to compose and review a message, how consent and opt-outs affect delivery, and why message usage should be monitored.

2. Appropriate Uses for SMS

Text messages are generally best suited for short, timely communication. Their use must still meet applicable consent requirements and ministry policies.

Examples of Potential Uses

An appointment reminder sent through an approved messaging process.
A response to an individual's permitted text inquiry.
An event reminder sent to recipients who have provided the required consent.
An approved operational notification related to a requested service.

Important: Having a mobile phone number in a contact record does not automatically mean the recipient has consented to text messages. Consent requirements can vary with message purpose, technology, and jurisdiction.

3. Composing a Text Message

A well-written text should quickly identify the sender, communicate the relevant information, and avoid unnecessary detail.

Example Ministry Fictional SMS conversation

MINISTRY MESSAGE Example Ministry: Your requested appointment reminder is for tomorrow at 10:00 AM. Reply if you need assistance.

CONTACT RESPONSE Thank you! I will be there.

MINISTRY RESPONSE You're welcome. We look forward to seeing you!

Demonstration only. No actual messages are sent, and no real contact details are used. Production messages require the appropriate sender identification and opt-out disclosures.

Before Sending

Verify the intended recipient.
Confirm the messaging purpose is authorized.
Check the applicable consent status.
Identify the ministry appropriately.
Use concise, accurate wording.
Review links and personal information.
Check messaging time and delivery restrictions.

5. Managing Incoming SMS Replies

When SMS is integrated with the CRM, replies may appear in the Conversations area alongside other supported messages.

Authorized users should review the existing conversation before responding or assigning follow-up work.

Recommended Procedure

Open the relevant Conversations area in your authorized ministry workspace.
Identify the contact and message channel.
Review earlier communications and available contact preferences.
Determine whether a reply is permitted and appropriate.
Respond through the approved channel or escalate the matter when necessary.

CRN SMS Conversations Screenshot A verified, appropriately redacted screenshot from the authorized ministry-user interface will be inserted here during practical training.

6. SMS Usage and Costs

Text messaging may generate usage-based charges. Pricing can depend on the provider, destination, message type, carrier fees, and other billing conditions.

Why One Long Text May Cost More

Long messages can be split into multiple billable segments. Certain characters, including emoji or characters requiring Unicode encoding, can reduce the number of characters that fit in a segment.

Factor	Potential Impact
Message length	May require multiple segments
Emoji / special characters	May change message encoding
Destination	Rates and carrier charges can vary
Bulk messaging	Usage can increase rapidly
Automated workflows	Repeated events may trigger more sends

Recipients may also incur charges under their mobile service plans.

CRN Cost Management Principle: Messaging usage should be attributed to the appropriate ministry tenant and reconciled against provider charges. Avoid unnecessary sends, duplicate automations, and uncontrolled bulk messaging.

7. SMS Security & Responsible Use

Standard SMS is not an end-to-end encrypted communication channel and should not be treated as a secure method for transmitting sensitive ministry information.

Essential Safety Practices

Verify the recipient before sending.
Avoid transmitting passwords, secret credentials, or confidential records.
Never include private details from another ministry's tenant account.
Be cautious about suspicious links, requests, and impersonation attempts.
Do not export contact lists or initiate bulk messages without authorization.
Follow the approved Help Desk and Change Management process for messaging configuration changes.

Security Boundary: Tags, contact lists, and message filters are not tenant authorization controls. CRN permissions must be enforced through the appropriate application and server-side systems.

8. Practice Exercise & Knowledge Check

Complete this exercise using fictional contacts in an approved training environment. Do not send practice SMS messages to real recipients without authorization.

My Learning Checklist I understand when SMS may be appropriate for ministry communications. I know to verify messaging consent and contact preferences. I understand how to recognize and respect opt-out requests. I understand why long messages, special characters, and automated sends can affect costs. I know not to send sensitive information through ordinary SMS.

Knowledge Check

Does having a contact's mobile number automatically authorize text messages?
What should you do when a recipient requests that messages stop?
Why might one long text message generate multiple billable segments?
What should you review before replying to an incoming SMS?
Why should confidential ministry information not be sent by ordinary SMS?

Lesson Complete! You now understand the foundational principles of responsible ministry text messaging, consent, security, and usage awareness.

SMS & Text Messaging