CRM for charities

Coordinate supporter and service enquiries with purpose, consent and care

For charities, the useful unit of work is a respectful customer or member journey with explicit consent, escalation and human judgement. This design avoids turning sensitive context into an automated decision. Consider this practical starting point: a person may be asking to donate, volunteer, partner or receive help, and those purposes require different handling. A configured CRM can keep the contact, context, owner and next action together, while the business still decides whether the message is routine supporter contact or involves safeguarding, vulnerability, eligibility or specialist services.

Subscribe to 121 CRM Seller, billing and cancellationSee the CRM customer journey

Customer Thread

A visible person-centred enquiry from start to finish

Illustrative example

Purpose identified
a person may be asking to donate, volunteer, partner or receive help, and those purposes require different handling
Consent and minimum data
contact, enquiry purpose, consent, preferred channel, assigned team, next action and retention or review date
Team handoff
whether the message is routine supporter contact or involves safeguarding, vulnerability, eligibility or specialist services
Human decision
Human decision or response
daily by purpose-specific queues, with safeguarding handovers governed by the charity’s approved procedure

Fictional Common Ground Trust example. It demonstrates an operating pattern for charities, not a customer result, professional recommendation or promise that every capability is included.

People, care and membership

See the charities journey as working software

A code-built fictional view connects the customer record, owner and next action without presenting a live charities account or inventing a result.

121 CRM · Customer thread

New enquiry09:12

Northstar Joinery

Website · Commercial enquiry

“We need a clearer way to coordinate enquiries between the office and site team.”

Owner

Amina K.

Next action

Discovery call

Enquiry
Website form
01
Conversation
Reply recorded
02
Owner
Amina assigned
03
Review
Suitability check
04
Next action
Call on Thursday
05

Illustrative exampleFictional customer and activity. Exact fields, channels and stages depend on configuration.

The working building blocks

Use the CRM where it improves the working day.

The same core capabilities can support different sectors, but the data, permissions, professional boundaries and handovers need to reflect the business using them.

Capability 01

Forms

Collects structured visitor details and maps supported responses into CRM records and workflows.

How it works: Publishes or collects information through a configured visitor-facing page, form or content experience.
Why use it: Turns an enquiry into usable data instead of an unstructured email.
Plan for: Generated or templated content is not automatically accurate, accessible, compliant or ready to publish.
Your team owns: A person must review content, test the journey and explicitly publish or change live assets.

Capability 02

Contacts

Stores a person or lead with contact details, activity, ownership and related records.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Gives a team one place to understand who a customer is and what has happened.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 03

Smart lists

Builds reusable contact views from saved filters and relevant record conditions.

How it works: Stores or organises supported business data under configured fields, permissions and record rules.
Why use it: Lets teams focus on a working group without maintaining separate copies of the same contacts.
Plan for: The platform does not make imported, duplicated or incomplete data accurate without review.
Your team owns: A data owner must define the record model and resolve quality, ownership and access exceptions.

Capability 04

Email conversations

Sends and receives supported email messages against the customer conversation and contact record.

How it works: Handles an eligible customer interaction through a configured inbox, number or connected channel.
Why use it: Keeps email context visible to authorised colleagues rather than one private mailbox.
Plan for: Delivery, message types, geographic coverage, approval and charges vary by channel and provider.
Your team owns: A person must own sensitive conversations, failed delivery and any situation outside the approved script.

Capability 05

Users, roles and permissions

Controls whether a user acts at agency or sub-account level and which supported areas they can access.

How it works: Controls agency or sub-account configuration that determines access, packaging, governance or billing.
Why use it: Limits day-to-day access to the work a person actually needs to perform.
Plan for: Availability and control depth depend on agency plan, role and current account configuration.
Your team owns: An authorised administrator must review, approve and audit material changes.

Capability 06

Conditions and branches

Routes a record through different configured steps when relevant data or events differ.

How it works: Runs an ordered sequence only after its configured trigger and conditions are met.
Why use it: Lets one process handle common variations without pretending every customer is the same.
Plan for: Automation follows its configuration; it cannot repair poor data, unclear rules or an unavailable external service.
Your team owns: A process owner must approve, test, monitor and pause or correct faulty automation.

Start with the real enquiry

What charities actually need the CRM to hold

Common Ground Trust is a fictional example used to make the workflow concrete. The aim is not to reproduce a sector package, but to show the minimum useful context for a team that needs identify the purpose, use only appropriate information and route the person to an accountable team.

The customer situation

Imagine a person may be asking to donate, volunteer, partner or receive help, and those purposes require different handling. Common Ground Trust records the customer’s own account before interpreting it. For this charities team, that prevents a short message from becoming a confident but unsupported category, price or promise.

The working record

The useful record contains contact, enquiry purpose, consent, preferred channel, assigned team, next action and retention or review date. At Common Ground Trust, those fields must help a person respond, decide or understand the next handover; extra detail collected merely because a field exists adds risk and maintenance.

The ownership question

Common Ground Trust names the supporter-services lead or another responsible colleague against the next action. The Common Ground Trust shared view is useful only when the team can tell who must act, by when, and what happens if that person is unavailable.

Human decision

The decision that stays human

A person decides whether the message is routine supporter contact or involves safeguarding, vulnerability, eligibility or specialist services. On this charities journey, CRM presents records, reminders and history without turning incomplete information or silence into approval.

A practical customer journey

Move the charities conversation without losing context

A workable starting journey for Common Ground Trust is Purpose identified → Consent and minimum data → Team handoff → Human decision or response → Outcome and review. For charities, each change should mean something observable to the team and customer rather than acting as a decorative pipeline label.

1. Capture purpose identified

For Common Ground Trust, capture starts with the source, the customer’s words and enough contact detail to reply. The first response should set a realistic expectation and ask only for information needed now; it should not imply that whether the message is routine supporter contact or involves safeguarding, vulnerability, eligibility or specialist services is resolved.

2. Establish consent and minimum data

Common Ground Trust asks the owner to check duplication and fill the smallest important gaps. Identify the purpose, use only appropriate information and route the person to an accountable team becomes the operating goal, rather than sending every charities enquiry through one sequence regardless of context.

Human approval point

3. Record team handoff

At Common Ground Trust, the team records the human decision, its basis and the promised next action. If information is missing, the request names it and its reviewer; if work should stop, a clear reason is more useful than leaving this charities record open indefinitely.

4. Complete human decision or response and outcome and review

For Common Ground Trust, later stages preserve the customer commitment, operational handover and outcome. Its charities team closes or defers work deliberately, records why, and gives future follow-up a date and purpose instead of keeping an undifferentiated list of old leads.

Reviewable by design

Make the decision and the exception visible

The second view shows how Common Ground Trust could expose handovers, missing information and the point where a person must decide what happens next.

121 CRM · Control responsibilities

Control questionOwnerNext check

Who can export customer data?CustomerConfirm

Who changes workflow permissions?Agreed scopeRecord

What happens at account closure?SharedDefine

Which suppliers process data?SharedCheck

Illustrative exampleIllustrative governance pattern. It does not assert that a specific technical control or certification is in place.

Fictional working example

How Common Ground Trust could use the pattern in a normal week

This example uses fictional people and activity. It demonstrates how a configured CRM might support a charities team while keeping account availability, detailed configuration and service scope subject to agreement.

The first response

Common Ground Trust receives the initial enquiry described above. The record is assigned to the supporter-services lead, the customer receives an acknowledgement that matches the actual response process, and the owner sees the missing information and a dated action rather than a vague notification.

The awkward case

The same week, a disclosure involving safeguarding, crisis or vulnerability that must bypass promotional workflows. At Common Ground Trust, the ordinary sequence pauses while a person reviews the context and records the decision. For this charities workflow, the failure route matters because automation should expose exceptions rather than quietly continuing.

The handover evidence

At each handover, Common Ground Trust keeps the source, time, owner, status change and next commitment. Common Ground Trust attachments or sensitive details remain only where the approved design permits them. A completed charities task proves that an action was recorded, not that the underlying judgement was correct.

The weekly view

The team reviews contacts with unclear purpose, consent gaps, handovers not accepted, promotional suppression failures and records due for retention review. For charities, those measures prompt investigation rather than promise performance. They help Common Ground Trust only when stages are updated consistently, exceptions remain visible and someone corrects stale or misleading records.

Controls, limits and review

Keep the charities workflow useful after launch

The safest charities design is modest: a small number of meaningful fields, an owner, an observable next action and a review rhythm. Common Ground Trust would test the ordinary path and the exception path before relying on either.

Human responsibility

Professional and operational boundary

The CRM can support coordination, but it cannot decide eligibility, safeguarding action, service priority or how a vulnerable person should be supported.

Exception handling

A disclosure involving safeguarding, crisis or vulnerability that must bypass promotional workflows should be visible to a named person. Common Ground Trust needs a stop, escalation or manual route so that delay, missing data or unusual circumstances do not produce an inappropriate automatic message.

Access, data and communication

Use the minimum information required for this charities journey. Confirm Common Ground Trust roles, channel consent, retention, export access and connected suppliers in the customer’s own account. Keep sensitive or formal charities records in the approved system for their purpose rather than copying them into CRM notes.

Review rhythm

Common Ground Trust reviews the workflow daily by purpose-specific queues, with safeguarding handovers governed by the charity’s approved procedure. The Common Ground Trust review checks a representative journey, stale records, failed actions, user access and whether fields still support a real decision. Any material charities change should be tested before it reaches ordinary customer communication.

Questions about this page

Useful answers, without the sales fog.

1. What is the most useful first CRM workflow for charities?

For charities, start with one common enquiry from capture to a recorded outcome: Purpose identified → Consent and minimum data → Team handoff → Human decision or response → Outcome and review. Keep Common Ground Trust’s first version narrow enough that the team can name the owner, test exceptions and see where a customer is waiting.

2. What should charities avoid automating?

The CRM can support coordination, but it cannot decide eligibility, safeguarding action, service priority or how a vulnerable person should be supported. Charities should also avoid automatic follow-up where consent, urgency, safety, suitability, a complaint or a vulnerable person needs a considered response.

3. Which information belongs in a charities CRM record?

Use information that supports the current relationship and next action: contact, enquiry purpose, consent, preferred channel, assigned team, next action and retention or review date. At Common Ground Trust, detailed or sensitive information is not collected simply because a custom field exists, and an authoritative professional or operational record is not duplicated without a defined reason.

4. How should a charities team know the workflow is working?

Review contacts with unclear purpose, consent gaps, handovers not accepted, promotional suppression failures and records due for retention review. Then inspect examples behind the figures. For charities, a dashboard can expose patterns but cannot prove service quality, causation or correct professional judgement without reliable data and human review.

Read all CRM questions

Continue the journey

Solutions Forms and lead capture Security and data CRM governance for small teams Travel businesses Membership organisations

Delegate the work. Keep the human.

Ready to organise the customer journey?

Subscribe through the approved secure checkout, or review pricing and responsibilities before you decide.

Subscribe to 121 CRM Seller, billing and cancellationCompare pricing