Learn how to organize ministry contacts using consistent tags and meaningful groups, while protecting information and avoiding unnecessary complexity.

1. Why Organization Matters

As a ministry grows, its contact records may represent a wide variety of relationships, communication preferences and operational needs.

A consistent organization system makes it easier for authorized staff to locate information and support appropriate follow-up.

Learning Objective: Understand the difference between tags and segments, recognize suitable uses, and learn the importance of consistent naming and secure handling.

2. What Is a Tag?

A tag is a label applied to a contact record to indicate a useful classification.

Tags may describe an approved operational category, a relationship type, a relevant interest, or a defined workflow state.

ILLUSTRATIVE MINISTRY TAGS

Event Registration Newsletter Interest Volunteer Inquiry Follow-Up Requested

These are conceptual examples, not instructions to create these specific tags in a production CRN account.

Good Tagging Practices

Use clear, descriptive names.
Follow your ministry's approved naming standard.
Avoid creating multiple tags with the same meaning.
Remove obsolete classifications through approved processes.
Do not use tags as access permissions.

3. What Is a Segment?

A segment is a group of contacts selected according to defined criteria.

For example, a ministry may need to locate contacts who registered for a particular event and requested additional information.

Some CRM configurations support saved or dynamically evaluated filtered contact views, sometimes called smart lists. Exact functionality depends on the available platform features.

EXAMPLE: EVENT FOLLOW-UP SEGMENT

A permitted contact group might require both of these conditions:

Event Registration Follow-Up Requested

The result is a more focused group than either label alone. The exact filter configuration must be verified in the live CRM.

Remember: A tag labels an individual record. A segment selects a collection of records according to criteria.

4. Tags vs. Segments

Feature	Tag	Segment
Purpose	Label a record	Select matching records
Example	Volunteer Inquiry	Volunteer inquiries from a defined period
Criteria	A classification	One or more filter conditions
Security	Not an access control	Not an access control

5. Naming and Governance

Standardized tag names make CRM operations easier to understand and maintain.

A well-governed system documents the purpose, ownership and approved use of each operational tag before deploying it widely.

Questions Before Creating a Tag

What business or ministry purpose does it serve?
Does an approved tag already accomplish this?
Who is responsible for maintaining it?
Will it trigger any automated activity?
When should the classification be removed or retired?

CRN Architecture Principle: Tags that identify workflows should follow the approved naming conventions for the relevant ministry or initiative. Naming consistency helps avoid collisions in shared CRM environments.

6. Tags and Automations

Where configured, a CRM workflow may respond to a tag being added or removed.

This can support operational processes, but changes to automation-related tags must be treated carefully.

Before Changing an Automation Tag

Check whether any workflow relies on it.
Confirm the intended business outcome.
Verify the user's authorization.
Use approved testing and change-management processes.
Consider unintended messages or repeated actions.

Important: A tag is not proof of payment, subscription entitlement, tenant identity or security authorization. Those controls must be verified through the appropriate systems.

7. Practical Exercise

Use a designated training workspace and fictional contact records. Do not modify production data without authorization.

Training Screenshot Area Verified CRN tag and contact-filter screenshots will be added here.

My Practice Checklist I can identify a tag on a sample contact record. I understand how multiple filter conditions can identify a segment. I can explain why standardized naming is important. I know to check automation dependencies before changing tags. I understand that tags and segments do not authorize access to information.

8. Knowledge Check

What is the purpose of a contact tag?
How is a segment different from a tag?
Why should duplicate tags be avoided?
What should be checked before changing a workflow tag?
Can tags or segments grant tenant permissions?

Lesson Complete! You now understand the basic principles of tags, segments and responsible contact organization.