SMS marketing for nonprofits: donor appeals, volunteer coordination, and community alerts on one account.

The short definition

What nonprofit text messaging is, and what it replaces.

Nonprofit text messaging is SMS or MMS sent from a phone number your organization controls, to people who agreed to hear from you at that number, and it is nearly always operational before it is promotional. The message that earns its keep is the one carrying a detail only one person needs: the shift you signed up for starts at 8, the ballfield is closed, the match expires at midnight, here is the link that takes your gift in eleven seconds.

Almost every organization we talk to has one list in their head and three lists in reality:

• Donors. People who have given, might give again, and who you are asking for money on a calendar that repeats every year.
• Volunteers and staff. People giving you hours instead of dollars, who need logistics far more often than they need appeals.
• Members, participants, and community. The congregation, the families in the program, the neighborhood that needs to know the distribution site moved.

The overlap between those three is real and it is also where most nonprofit texting programs go wrong. A volunteer who has never given a dollar getting a year-end ask, or a major donor getting a text asking them to cover a shift at the coat drive, both read as an organization that does not know who it is talking to. The platform keeps the programs separate on the composing side and rolls them up together on the reporting side, which is the arrangement that matches how a nonprofit actually operates.

Texting does not replace your newsletter and it does not replace the personal call to a major donor. It replaces the layer underneath both: the reminder, the confirmation, the deadline, the alert. Email is where you explain. Text is where you land a single fact in the ninety seconds before it stops mattering.

Cadence

The giving calendar, and where texting belongs on it.

Nonprofit fundraising runs on a calendar that barely moves year to year, which is a gift, because it means the texting program can be built backward from dates you already know. The mistake is treating SMS as a December tool. A list that hears from you for the first time on November 30 is a list of strangers, and strangers opt out.

1. January to March: repair and record. The quiet quarter is when you fix intake. Every form the organization owns gets clear SMS opt-in language, and every list you are carrying gets audited for where the consent actually came from. This is unglamorous and it is the only work that makes the rest of the year defensible.
2. Spring appeal and event season. Gala RSVPs, ticket reminders, day-of logistics, auction closing times. Event texting is the easiest place to start, because the consent conversation is natural at registration and the messages are obviously useful rather than obviously asks.
3. Summer: programs, not appeals. Camp reminders, distribution schedules, volunteer shifts. This is the stretch that keeps the number familiar. One or two sends a month with no ask attached is what buys you permission in the fourth quarter.
4. October: build the giving-day list. Not the campaign, the list. Grow the opt-in file at every fall event, and get your 10DLC registration finished so throughput is not a question on the day it matters.
5. Giving Tuesday. A whole-list day: a lead-up send, a morning launch, a midday progress update, and a closing-hours message. This is the one day of the year where a broad, well-timed mass texting push is genuinely the right instrument rather than a shortcut.
6. Year-end, December 26 to 31. The densest giving week on the calendar and the one where texting outperforms everything else, because the message is a deadline and the deadline is real. Segment out anyone who already gave in December before the 31st send. Being thanked and then asked in the same week is how you lose a donor who was going to renew anyway.

Matching-gift windows sit outside this calendar and can happen any time a board member or a corporate partner puts money on the table. They are the highest-yield SMS moment a nonprofit gets, because they have all three things a text needs: a reason, a deadline, and a number that goes up while people watch. Write the match send the day the match is confirmed, not the week it expires.

If you want the message-level view (what a donor appeal, a thank-you, an impact update, and a volunteer recruitment text each look like when written well), our guide to SMS marketing for nonprofits and churches walks through donor, congregation, and volunteer messaging with examples you can adapt instead of starting from an empty composer.

The distinction that matters

Donor communication is not the same thing as a fundraising solicitation.

Every text your organization sends falls into one of two buckets, and the ratio between them decides whether your list survives the year.

• Solicitation. Any message whose purpose is to get money: the appeal, the match, the chase, the pledge reminder, the year-end deadline. Useful, necessary, and the only kind of message most organizations ever send by text.
• Communication and stewardship. The receipt confirmation, the thank-you that arrives the same day, the photo from the build site, the note that the program you funded reopened Monday, the shift reminder, the closure alert. No ask attached and nothing to click except, occasionally, nothing at all.

The practical test: if you scroll back through everything the number has sent in the last six months, how many of those messages wanted something? An organization where every text is an ask has taught its list that a message from this number costs money, and people mute or block what costs them money. An organization that sends four useful things for every ask has a list that opens the ask.

This distinction has a second life on the compliance side. The consent someone gave, and the language they gave it under, sets what you can send them. A person who opted in for "service reminders and closures" did not opt in for a capital campaign appeal, and while your counsel will tell you where the legal line sits, the practical line is simpler and stricter: send people the thing they signed up for. That posture is also what keeps opt-out and complaint rates low enough that carriers keep delivering you, which is a business consequence and not just an ethical one.

Thanking is where texting is underused and where it is unreasonably good. A gift receipt is an email. A thank-you that arrives forty minutes after the gift, from a person, with no link in it, is a text, and it is the single cheapest retention tool a development office has. At $0.06 a message, thanking every donor who gave in December costs less than the stamps on one mail piece.

Congregations

Church texting: service times, closures, prayer chains, and giving.

A church is a nonprofit with a weekly deadline, which changes what texting is for. Most of the volume is not fundraising, it is a congregation that needs to know something before Sunday.

• Closures and schedule changes. The message that justifies the whole account. Ice storm at 5 a.m., service canceled, one send at 6, nobody drives in for nothing. This is the one case where an emergency send outside normal hours is the right call, and it should be rare enough that people trust it when it arrives.
• Service and holiday reminders. Christmas Eve times, a Holy Week schedule, a special service at a different building. Sent Thursday, not Saturday night.
• Small groups and ministries. Each with a tagged sub-list, so the men's breakfast reminder does not reach the whole roll. This is the difference between a church list people stay on and one they mute.
• Prayer chains. Genuinely one of the best uses of SMS anywhere, and the one with the sharpest edge on it.
• Tithing and pledge reminders. A giving link on the first of the month, a pledge follow-up in the fall, an end-of-year note about the giving deadline. Same rule as any nonprofit: the ask lands better when it is not the only thing this number ever sends.

The prayer chain deserves the caution. A prayer request usually contains someone's medical situation, family crisis, or job loss, and forwarding that to a few hundred phones is a disclosure whether or not anyone meant it that way. Two habits fix it: the chain is its own opt-in list rather than everyone on the roll, and nothing goes out without the person's permission and in the detail they chose. "Please pray for the Kim family this week" is a text. The diagnosis is not, unless they asked for it to be.

Multi-site churches and churches with a separate school or food pantry usually want a line per entity at $5 a month. The congregation recognizes the church number, the pantry has its own, and neither list ends up in the other's sends.

Common mistakes

What nonprofits get wrong with texting.

Almost none of these are software problems, which is why a better platform does not fix them. They are decisions, and they are all reversible.

• Texting a list that never opted in. The purchased list, the partner's list, the donor records from 2014. It is the fastest way to turn a cheap channel into an expensive problem, and it is the one mistake on this page with legal consequences attached.
• Over-asking. Six appeals in November from an organization that sent nothing in July. The list does not get annoyed at message seven; it got annoyed at message three and stopped reading before the one that mattered.
• One list for everyone. Volunteers getting capital campaign asks, major donors getting shift requests. Tag on import and the problem never starts.
• Only sending in December. A number that goes quiet for eleven months is an unknown number when it comes back, and unknown numbers get ignored or reported.
• Writing long. The composer counts segments as you type: 160 characters in the first, 153 in each one after, and every segment bills as a message. A three-segment text usually has not decided what it wants. Cutting it to one saves money and reads better.
• Using MMS by default. An image is 2.5 times the cost of a text at pay-as-you-go rates. Worth it for the photo from the build site, wasted on a logo nobody needed to see.
• Nobody watching replies. A send to a donor list produces answers, corrections, and questions within minutes, and an unread inbox turns a conversation into a complaint.
• Two asks in one message. Give and volunteer, in the same 160 characters, reliably gets neither.

The pattern underneath all of them is the same. Texting fails when an organization treats it as a cheaper megaphone, and works when it is treated as the layer that carries one useful fact to one person at the moment that fact is actionable.

Afterward

What to do with the list after the campaign ends.

The most expensive habit in nonprofit data is letting a list built for one campaign go cold and then rebuilding it from scratch the next year. Four things in the week after a giving day or an appeal close:

• Send the thank-you, then send the result. The thank-you goes to everyone who gave, same week. The result ("we finished at $41,200, here is what it funds") goes to everyone on the list, including the people who did not give. The non-donors are next year's donors and this is the only message all year that asks them for nothing.
• Export everything. Message history, consent records, opt-outs, delivery rates, and per-campaign cost, as CSV. That is the board packet, the annual report figure, and the record you want if a complaint ever arrives.
• Keep the opt-out list permanently. The suppression list is worth more than the contact list. Someone who opted out last December and gets texted again this December is a complaint, not a lapsed donor. Opt-outs stay flagged on the account and filter out of every future send automatically, which is exactly the behavior you want and the one you should never work around.
• Keep the number warm. Roughly monthly, something that is not an ask: a program update, a volunteer opportunity, a photo. On pay-as-you-go a monthly non-ask send to 2,000 people is $120 a year, which is the cheapest donor retention line item on the budget.

One caution on organizational change. If the entity changes, the consent question reopens: a merger, a new fiscal sponsor, a chapter absorbed into a national, a program spun out into its own 501(c)(3). Consent given to the organization people knew is not automatically consent given to the one that now holds the file. Treat it as a new program and re-earn the opt-in, which is slower and considerably cheaper than the alternative.

Recurring stewardship (the thank-you sequence, the monthly non-ask, the pledge reminder cycle) is worth setting up once and letting run rather than rebuilding it every quarter. That is what text message automation handles.