Key takeaways<\/h2>\n\n\n\n\n- Ask the fork question first:<\/strong> are you looking to support us, or looking for support?<\/li>\n\n\n
- Anyone seeking help reaches a trained person – never a flow, never a form.<\/li>\n\n\n
- Match help-seeking language broadly and err towards routing. A false escalation costs nothing.<\/li>\n\n\n
- Donations automate completely: a working link, where money goes, Gift Aid.<\/li>\n\n\n
- Volunteering automates as far as the facts, then stops at suitability and safeguarding.<\/li>\n\n\n
- Publish your crisis signposting in the flow, accurately, and keep it current.<\/li>\n\n\n
- Do not use urgency or guilt framing in an automated message – you cannot see who is reading it.<\/li>\n\n<\/ul>\n\n<\/div>\n\n\n\n
The Fork, and Why It Comes First<\/h2>\n\n\n\n
Everything in this vertical depends on getting one question right at the top.<\/p>\n\n\n\n
Ask It Before Anything Else<\/h3>\n\n\n\n
\u201cAre you looking to support us, or looking for support?\u201d – two buttons, before any donation content appears. It reads as ordinary signposting and it is the most important routing decision in the whole flow.<\/p>\n\n\n\n
A charity flow that opens with a donation ask, to somebody who messaged because they are in difficulty, is a failure of a different order from a bad support experience.<\/p>\n\n\n\n
Match Help-Seeking Language Broadly<\/h3>\n\n\n\n
Do not rely on the button alone. People in difficulty often describe the situation rather than selecting a category, and they may not use the words your service uses.<\/p>\n\n\n\n
Match broadly and deliberately over-escalate. In every other article in this cluster a greedy keyword is a defect; here it is the correct setting, for the same reason as the allergen list in the restaurant flow<\/a>.<\/p>\n\n\n\nRoute to a Trained Person<\/h3>\n\n\n\n
Not to a general inbox, not to whoever is on, and not into a form. The destination for help-seeking messages should be someone trained for it, with a named fallback and a real response time stated honestly.<\/p>\n\n\n\n
If that is not available out of hours, say so plainly and signpost to a service that is. An honest \u201cwe are not here until 9am, and here is who is\u201d is responsible; silence is not.<\/p>\n\n\n\n![\"Four](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/dm-automation-for-nonprofits-fourgroups.jpg\")
Same inbox, radically different duties.<\/figcaption><\/figure>\n\n\n\nWhat Automates Well<\/h2>\n\n\n\n
Having drawn the line, three of the four groups are genuinely easy.<\/p>\n\n\n\n
Donations<\/h3>\n\n\n\n
A working link, a plain statement of where the money goes, and whatever tax mechanism applies in your country. Those three things answer most donor messages completely.<\/p>\n\n\n\n
The common failure is a broken or outdated link – check it monthly. A donation flow that sends people to a dead page is worse than no flow.<\/p>\n\n\n\n
Volunteering, Up to a Point<\/h3>\n\n\n\n
Which roles exist, what the commitment is, what checks are required, and when the next induction runs. All facts, all asked constantly, all safely automated.<\/p>\n\n\n\n
Then it stops. Suitability, references and safeguarding checks are a conversation with somebody who knows your policy, and the flow should hand over rather than collect personal detail.<\/p>\n\n\n\n
Press, Schools and Partners<\/h3>\n\n\n\n
Usually one named contact each, and a keyword route is enough. The value here is speed – a journalist on a deadline who waits two days writes the piece without you.<\/p>\n\n\n\n![\"Trigger](\"https:\/\/dmpro.brandid.app\/blog\/wp-content\/uploads\/2026\/10\/dm-automation-for-nonprofits-variables.jpg\")
The flow is the same everywhere. Only these change.<\/figcaption><\/figure>\n\n\n\nWhat to Automate<\/h2>\n\n\n\n
The bottom rows are not preferences.<\/p>\n\n\n\n
The Fork, and Why It Comes First<\/h2>\n\n\n\n
Everything in this vertical depends on getting one question right at the top.<\/p>\n\n\n\n
Ask It Before Anything Else<\/h3>\n\n\n\n
\u201cAre you looking to support us, or looking for support?\u201d – two buttons, before any donation content appears. It reads as ordinary signposting and it is the most important routing decision in the whole flow.<\/p>\n\n\n\n
A charity flow that opens with a donation ask, to somebody who messaged because they are in difficulty, is a failure of a different order from a bad support experience.<\/p>\n\n\n\n
Match Help-Seeking Language Broadly<\/h3>\n\n\n\n
Do not rely on the button alone. People in difficulty often describe the situation rather than selecting a category, and they may not use the words your service uses.<\/p>\n\n\n\n
Match broadly and deliberately over-escalate. In every other article in this cluster a greedy keyword is a defect; here it is the correct setting, for the same reason as the allergen list in the restaurant flow<\/a>.<\/p>\n\n\n\n Not to a general inbox, not to whoever is on, and not into a form. The destination for help-seeking messages should be someone trained for it, with a named fallback and a real response time stated honestly.<\/p>\n\n\n\n If that is not available out of hours, say so plainly and signpost to a service that is. An honest \u201cwe are not here until 9am, and here is who is\u201d is responsible; silence is not.<\/p>\n\n\n\n Having drawn the line, three of the four groups are genuinely easy.<\/p>\n\n\n\n A working link, a plain statement of where the money goes, and whatever tax mechanism applies in your country. Those three things answer most donor messages completely.<\/p>\n\n\n\n The common failure is a broken or outdated link – check it monthly. A donation flow that sends people to a dead page is worse than no flow.<\/p>\n\n\n\n Which roles exist, what the commitment is, what checks are required, and when the next induction runs. All facts, all asked constantly, all safely automated.<\/p>\n\n\n\n Then it stops. Suitability, references and safeguarding checks are a conversation with somebody who knows your policy, and the flow should hand over rather than collect personal detail.<\/p>\n\n\n\n Usually one named contact each, and a keyword route is enough. The value here is speed – a journalist on a deadline who waits two days writes the piece without you.<\/p>\n\n\n\n The bottom rows are not preferences.<\/p>\n\n\n\nRoute to a Trained Person<\/h3>\n\n\n\n
What Automates Well<\/h2>\n\n\n\n
Donations<\/h3>\n\n\n\n
Volunteering, Up to a Point<\/h3>\n\n\n\n
Press, Schools and Partners<\/h3>\n\n\n\n
What to Automate<\/h2>\n\n\n\n