A supporter makes their first donation to a charity. They receive a confirmation from the payment provider, but the fundraising team does not see the donation until someone updates a spreadsheet. A week later, the supporter receives a generic appeal that makes no reference to their recent gift.
Nothing has necessarily gone wrong with the donation itself. The problem is that the different parts of the supporter experience are not connected.
For charities managing donations, events, volunteering and ongoing fundraising relationships, these gaps can become difficult to manage. Teams spend time moving information between systems, communications are delayed and supporters may receive messages that do not reflect their involvement.
Automation can help, but only when it is designed around the relationship rather than the technology.
At Sweet Potato Tec, our Salesforce work with charities and nonprofits focuses on helping organisations improve supporter relationships, reduce administration and make better use of their information.
The aim is not to send more messages. It is to make every appropriate interaction more timely, relevant and useful.
How can charities automate supporter communications and fundraising journeys?
Charities can automate supporter journeys by connecting Salesforce with their donation, website, events and communications platforms, then using relevant supporter activity to trigger appropriate actions. These may include welcome messages, donation acknowledgements, regular-giving updates, event follow-ups and volunteer communications. Effective automation also requires accurate records, appropriate communication permissions, personalisation, human oversight and regular measurement of supporter engagement.
What is a supporter journey, and where should charities start with automation?
A supporter journey is the series of interactions someone has with a charity, from their first enquiry or donation through to an ongoing relationship.
Not every supporter follows the same path.
Someone might discover a charity through a fundraising event, make a donation and later become a regular giver.
Another person may initially volunteer, attend several activities and eventually support a fundraising campaign.
A corporate contact might begin with an event enquiry before developing a longer-term relationship with the organisation.
These interactions often involve different teams and systems.
The first step towards automation is understanding how those relationships currently work.
Map the existing supporter experience
Before choosing Salesforce functionality or an email platform, charities should identify the main stages of their supporter relationships.
For example, a first-time donor journey might involve an initial website visit, donation submission, payment confirmation, acknowledgement, welcome communication and subsequent stewardship.
At each stage, the charity should ask what the supporter needs and what the organisation needs to know.
Is the supporter receiving timely confirmation?
Can the fundraising team see the interaction?
Does the next communication reflect what has already happened?
Is information being transferred manually?
Are communication preferences being respected?
These questions help identify where automation would improve the experience.
They also reveal where a process may need to change before it is automated.
Start with a clear purpose
A charity might want to reduce the time between a donation and its acknowledgement.
It may want to improve the consistency of volunteer information.
Another organisation might need to reduce the administration involved in event registration and follow-up.
Each is a legitimate starting point, but they require different workflows.
At Sweet Potato Tec, we believe technology should follow the organisation’s priorities.
Our Salesforce implementation services begin with understanding existing processes and identifying improvements that will make a practical difference.
For supporter automation, that means deciding what a successful interaction looks like before building the workflow.
How can charities automate welcome messages, donation acknowledgements and regular giving?
Charities can automate routine communications by using reliable supporter activity to initiate the appropriate response, while keeping the content relevant to the individual’s relationship with the organisation.
Some of the most valuable opportunities are also among the simplest.
Welcome and thank-you communications
When someone signs up to hear from a charity, they may benefit from an introductory message explaining its work and what to expect next.
When someone makes a donation, they should receive the appropriate acknowledgement without the fundraising team having to prepare every message manually.
A connected process can record the interaction in Salesforce and initiate the relevant communication through an appropriately configured platform.
However, different interactions need different responses.
A donation receipt or transactional acknowledgement is not necessarily the same as a marketing welcome email.
The charity must distinguish between necessary service communications and optional fundraising or promotional messages, applying the relevant legal requirements to each.
A useful welcome journey should help supporters understand the organisation, not immediately overwhelm them with further requests.
Donation acknowledgements
Donation acknowledgements should be accurate, timely and appropriate to the gift.
A first-time donor may need a different response from someone who has supported the charity for several years.
The information used to create that distinction must be reliable.
If the donation platform and Salesforce are disconnected, the charity may not know whether someone has already donated.
That can result in inappropriate communications or unnecessary manual checking.
A connected process can help ensure donation information reaches the correct supporter record.
The charity can then determine which acknowledgement is appropriate.
For example, an automated workflow might recognise a completed donation, update the relevant Salesforce record and initiate a confirmation or thank-you message.
The exact functionality depends on the donation system, Salesforce configuration and communications platform.
Regular-giving journeys
Regular supporters often have an ongoing relationship with the charity.
Automation can help manage routine stages of that relationship, such as welcoming a new regular giver, acknowledging important changes or providing appropriate updates.
It can also help staff identify situations that require attention.
For example, a failed payment may need to be recorded and routed into an agreed follow-up process.
That does not mean every payment issue should trigger an immediate fundraising message.
The charity needs to consider the cause, the supporter experience and the relevant communication rules.
For higher-value or particularly sensitive relationships, a personal conversation may be more appropriate.
At Sweet Potato Tec, our Salesforce for Charities and Non-Profits services include donor management, recurring giving and fundraising process improvements.
The technology can support these relationships, but the charity still needs to decide how it wants supporters to be treated.
How can charities automate event, volunteer and lapsed-donor communications?
Charities can use connected records and agreed workflows to coordinate communications around events, volunteering and changes in supporter engagement.
These journeys are often managed by different departments, which makes reliable information particularly important.
Event registration and follow-up
An event can involve several communications.
Supporters may need confirmation of their registration, practical information before attending and appropriate follow-up afterwards.
If event information is held outside Salesforce, staff may need to transfer registration details manually.
That can delay communications and make it difficult to connect event participation with the wider supporter relationship.
Integrating the event platform with Salesforce can help the organisation record registrations and participation more consistently.
It can also provide a foundation for event-related communications.
For example, an attendee might receive practical joining information before an event, followed by a thank-you message afterwards where appropriate.
Any subsequent fundraising or marketing communication should reflect the relevant permissions and preferences.
What has Sweet Potato Tec delivered for nonprofit event processes?
Our work with the Charity Retail Association provides a relevant example of connected nonprofit systems.
The organisation previously managed its website and Salesforce separately, while event information required manual administration.
Sweet Potato Tec introduced website synchronisation and Eventbrite integration, allowing relevant event information to move between platforms more consistently.
The project also included membership-renewal automation.
This is evidence of integration and operational automation, rather than a published claim that we delivered a complete event-email journey.
Nevertheless, it demonstrates why connected event data matters.
When registration information is available in Salesforce, the organisation has a stronger foundation for coordinating communications and understanding how events contribute to wider engagement.
Volunteer communications
Volunteers may need confirmations, joining instructions, reminders and updates about their activities.
If volunteer information is maintained in separate spreadsheets, these communications can become time-consuming.
A connected Salesforce environment can help coordinators understand which volunteers are involved in particular activities and what information they need.
For example, a volunteer who has registered for an event may need practical instructions before their shift.
A volunteer who has completed an activity may benefit from a thank-you message or an invitation to provide feedback.
However, volunteer communications should reflect the nature of the relationship.
Important operational instructions should not be treated as interchangeable with fundraising marketing.
Our nonprofit Salesforce services include volunteer coordination, engagement and communication.
We also explore how connected information can support different relationships in our article on animal charities connecting supporters, volunteers and services.
Lapsed-donor engagement
A charity may want to identify supporters who have not donated or engaged for a defined period.
Salesforce can support this by providing the information needed to identify relevant groups, provided the underlying records are accurate.
But charities should be careful about what they consider a lapsed supporter.
Someone who has stopped donating may still volunteer, attend events or support the organisation in other ways.
A lack of recent donations does not necessarily mean the relationship has ended.
Before creating a re-engagement journey, the charity should define what it wants to understand.
Has the person stopped giving regularly?
Have they stopped engaging with all communications?
Have they changed the way they support the organisation?
Are they still eligible to receive the proposed communications?
Automation can help identify patterns and initiate appropriate actions, but the charity needs to interpret those patterns carefully.
A thoughtful re-engagement message may be useful.
Repeated automated appeals to someone who has chosen not to hear from the organisation are not.
How can Salesforce personalise supporter journeys without making them impersonal?
Salesforce can support personalisation by bringing relevant information about supporter relationships together, allowing communications to reflect actual interests and interactions.
Personalisation should go beyond inserting someone’s first name into an email.
A charity may want to distinguish between new donors, long-standing supporters, volunteers, event attendees and people interested in particular programmes.
However, these categories are not always mutually exclusive.
One person may belong to several groups.
That is why a connected supporter record matters.
Use information that is relevant to the interaction
A charity may know that someone recently attended a fundraising event.
That information could help make an appropriate follow-up more relevant.
A regular giver may have a different relationship with the organisation from someone making their first donation.
A volunteer may prefer practical information about activities rather than frequent fundraising requests.
The important question is whether the information improves the experience.
Not every piece of information held in Salesforce should be used for personalisation.
Charities need to consider privacy, appropriateness and the expectations of the people involved.
This is especially important where information relates to beneficiaries or sensitive services.
Avoid treating every interaction as an opportunity to ask for money
A supporter journey should include meaningful stewardship.
That might involve thanking someone, explaining how the charity’s work is progressing or providing information relevant to their involvement.
Fundraising appeals have a place, but they should not dominate every communication.
If automation simply increases the number of messages sent, supporters may become less engaged.
A better approach is to consider the purpose of each interaction.
What does the supporter need at this point?
What information would be useful?
Is there a reason to contact them now?
Would a personal conversation be more appropriate?
These questions help charities build journeys that reflect relationships rather than campaign schedules alone.
Why is a single supporter view important?
Personalisation depends on understanding how someone interacts with the charity across different channels.
If donations, volunteering and event attendance are recorded separately, communications may reflect only part of the relationship.
A supporter who recently volunteered might receive a generic message suggesting they have not engaged with the charity.
Someone who has already donated could receive an appeal written as though they have never supported the organisation.
A connected Salesforce environment can reduce these inconsistencies.
However, creating a single supporter view does not mean every employee should see every detail.
Information should be accessible according to the person’s role and the organisation’s data-protection requirements.
The goal is to provide relevant context without unnecessarily exposing personal information.
How should charities manage consent, preferences and human oversight?
Charities should establish clear rules for communication permissions, maintain accurate preference information and ensure automation does not replace appropriate human judgement.
This is particularly important when Salesforce is connected to several communications and fundraising systems.
Keep communication preferences consistent
A supporter might update their preferences through a website, email preference centre or direct conversation with a charity employee.
If those changes are not reflected across the relevant systems, the organisation may continue using outdated information.
The charity should decide where preferences are maintained and how updates move between platforms.
It should also distinguish between consent, other lawful bases for processing personal data and preferences about particular communication channels.
The requirements for email, text, telephone and postal communications are not identical.
UK charities should follow applicable data-protection and direct-marketing rules, including guidance from the Information Commissioner’s Office and the Fundraising Regulator.
Salesforce can help record and manage relevant information, but technology does not automatically make a communications process compliant.
What has Sweet Potato Tec delivered in this area?
Our work with a UK animal-welfare charity demonstrates the importance of accurate supporter information.
The organisation received fundraising data from more than 50 agencies and channels.
Managing that information required substantial manual processing, and duplicate records created a risk of supporters receiving repeated or inappropriate communications.
Sweet Potato Tec developed an automated supporter-data process that collected, standardised, validated and matched incoming information before bringing it into Salesforce.
The solution included consent and preference management, donation reconciliation through FinDock and integration with CRM Analytics.
The published results included approximately 75% fewer duplicate and error records and an 80% reduction in manual data effort.
This was not described as a complete automated supporter-email programme.
Its relevance is that accurate, connected information provides the foundation on which appropriate communications can be built.
Without that foundation, automation risks distributing errors more quickly.
When should a person take over?
Not every supporter interaction should be automated.
A major donor may need a personal conversation.
Someone making a complaint should be able to receive appropriate human attention.
A supporter experiencing difficult personal circumstances may require sensitivity that a standard workflow cannot provide.
A volunteer raising a safeguarding concern should not be left in an automated communications sequence without appropriate escalation.
Charities should identify which situations require a person to review or manage the interaction.
Automation can help route enquiries and notify the right employees.
It should not remove accountability.
At Sweet Potato Tec, our integration strategy focuses on understanding how information moves between people and systems.
That includes recognising where automation is helpful and where human involvement remains essential.
How can charities connect Salesforce with fundraising and communications platforms?
Charities can connect Salesforce with websites, donation platforms, marketing systems and other applications so that relevant supporter information is available when it is needed.
The exact approach depends on the organisation’s technology environment.
A charity might use Salesforce for supporter records, a separate platform for online donations and another system for email communications.
Without integration, teams may have to export and import information repeatedly.
This creates delays and opportunities for errors.
A connected process can help ensure that an interaction in one system is reflected appropriately in another.
For example, when a donation is completed, the relevant information can be transferred to Salesforce and associated with the correct supporter.
That information may then support an acknowledgement or an appropriate subsequent communication.
Why does data quality matter?
Automated communications depend on reliable information.
If a donation is associated with the wrong supporter, the resulting acknowledgement may be incorrect.
If duplicate records exist, someone may receive repeated messages.
If preferences are inconsistent, a communication may be sent through an inappropriate channel.
Charities should therefore review data quality before expanding automation.
That includes matching rules, record ownership, validation and the processes used to maintain information.
Sweet Potato Tec’s animal-welfare charity project demonstrates the practical value of addressing these foundations.
By replacing more than 170 individual data links with one automated processing solution, the project helped standardise incoming fundraising information and reduce the manual effort required to prepare it.
The resulting Salesforce information became available for campaign selections, insight and stewardship more quickly.
Does every charity need Boomi?
No.
A straightforward integration may be sufficient when two systems need to exchange relatively simple information.
More complex environments may benefit from a dedicated integration platform.
Sweet Potato Tec’s Boomi and Integration services support organisations connecting Salesforce with their wider technology environment.
We also help charities consider whether direct connections or a broader integration strategy would be more appropriate.
The objective is not to connect every available system.
It is to ensure the information needed for useful supporter experiences moves accurately and reliably.
Which Salesforce products can support supporter automation?
The appropriate Salesforce products depend on the charity’s existing environment and requirements.
Salesforce Nonprofit Cloud can support relevant fundraising and relationship-management processes.
Salesforce Flow can support configured workflows and record-based automation.
Salesforce’s marketing products may support audience segmentation and communications journeys, depending on the products and licences in use.
Connected donation and payment platforms may provide additional capabilities.
However, charities should not assume that every communications feature is included in their existing Salesforce subscription.
Before selecting functionality, the organisation should confirm what products it already uses, what integrations are required and which processes need to be supported.
At Sweet Potato Tec, our approach is to understand those requirements before recommending additional technology.
How can charities measure whether supporter automation is working?
Charities should measure supporter automation by the quality of the experience and the operational improvements it delivers, rather than the number of messages sent.
Sending more emails is not necessarily a positive result.
A charity may increase its communications volume while making the supporter experience less relevant.
Similarly, an automated process may save employees time but introduce errors that require additional work elsewhere.
Success measures should reflect the purpose of the journey.
Measure supporter engagement
Relevant measures might include whether supporters complete intended actions, attend registered events, continue regular giving or respond to appropriate communications.
The organisation may also review unsubscribes, complaints and other indications that communications are not meeting expectations.
Email opens alone are not a reliable measure of engagement because tracking can be affected by privacy features and other technical factors.
The charity should therefore consider several measures together.
Measure operational improvements
Automation should also reduce unnecessary administration.
A charity might examine how long it takes to process a donation acknowledgement, how many manual steps are required to manage event registrations or how often staff need to correct supporter information.
These measures can reveal whether automation is genuinely making work easier.
For example, Sweet Potato Tec’s animal-welfare charity project reduced manual fundraising-data processing from more than 200 hours per week to fewer than 40.
That is a measured operational result from the published project.
It should not be interpreted as evidence of increased email engagement or donor retention, because those outcomes have not been published for that project.
Review journeys regularly
Supporter relationships change.
A journey that worked when it was introduced may become less relevant as the charity develops new campaigns, services or fundraising activities.
The organisation should review performance, gather feedback and adjust workflows where necessary.
Our Managed Services offering supports ongoing Salesforce improvements, data-quality reviews, reporting and integration support.
That ongoing attention matters because automation should evolve with the organisation rather than remaining unchanged after launch.
What should a charity automate first?
The best starting point is usually a process with a clear supporter benefit, repetitive administration and reliable information.
A charity could begin by improving donation acknowledgements, event registration confirmations or volunteer activity reminders.
Before implementation, it should agree what the communication is intended to achieve, what triggers it, which supporters should receive it and how success will be measured.
The first journey should be manageable enough to test thoroughly.
Once it is working reliably, the charity can consider expanding into more complex supporter relationships.
FAQs
Can Salesforce automatically send thank-you emails after a donation?
Salesforce can form part of an automated donation-acknowledgement process when the appropriate donation data, workflow and communications tools are configured. The exact approach depends on the Salesforce products and connected platforms being used. Charities should distinguish transactional acknowledgements from marketing communications and apply the relevant rules.
Do charities need Salesforce Marketing Cloud to automate supporter journeys?
Not necessarily. Some workflows can be supported through Salesforce configuration and connected applications. More advanced communications journeys may benefit from specialist marketing products, but the appropriate solution depends on the organisation’s requirements, existing technology and licensing. A charity should define its intended journeys before selecting additional software.
Can supporter journeys be personalised without collecting more personal data?
Often, yes. A charity may already hold relevant information about donations, event participation or volunteering. Improving how that information is connected and used can support more relevant communications without collecting unnecessary additional details. The organisation should still consider whether each use is appropriate and consistent with its privacy obligations.
How can charities avoid sending too many automated messages?
They should coordinate communications across departments, maintain accurate preferences and establish appropriate rules for timing and frequency. Journeys should be reviewed together rather than designed independently by every team. Supporter feedback, complaints and unsubscribe activity can help identify where communication is becoming excessive.
Can automation help charities retain regular donors?
Automation can support timely acknowledgements, relevant updates and appropriate follow-up when giving patterns change. However, it does not guarantee retention. The quality of the relationship, the charity’s communications and the supporter’s circumstances all matter. Retention should be measured over time rather than assumed from the existence of an automated journey.
Should small charities automate their supporter journeys?
Automation can be useful for smaller charities, particularly where limited staff capacity makes repetitive administration difficult. However, the solution should be proportionate. A small organisation may benefit more from one reliable donation-acknowledgement process than from a complicated series of communications that it cannot maintain. The priority should be practical value rather than the number of automated journeys.
Make supporter automation more personal, not less
Supporter automation should help charities build stronger relationships while reducing unnecessary administration.
That means connecting the information behind donations, events, volunteering and other interactions so communications reflect the supporter’s actual relationship with the organisation.
It also means respecting preferences, maintaining reliable data and recognising when a person should take responsibility for an interaction.
At Sweet Potato Tec, we help charities make Salesforce and connected technology more useful through better data, practical automation and reliable integrations.
Our work with the Charity Retail Association demonstrates how connected systems can reduce manual processes, while our UK animal-welfare charity project shows how automated supporter-data management can improve the quality and availability of fundraising information.
Both provide foundations for better supporter experiences.
If your charity is managing communications across disconnected platforms or spending too much time transferring supporter information manually, our Salesforce nonprofit specialists can help identify where automation would make a practical difference.
The right starting point is understanding the journeys your supporters already experience and deciding how to make those interactions more consistent, relevant and useful.
The aim is not to automate every conversation.
It is to give your team more time for the conversations that matter.