“Send to all” is a number nobody checks.

Sent is not the same as arrived, and neither is the same as allowed

Every messaging tool in this category reports the same number: how many rows it tried. That is the easiest number to compute and the least useful one to read.

Three separate things stand between a person on your roster and a message in their hand, and they fail for completely different reasons.

Some people have no address on that channel at all. No email on file, or no mobile number, or a landline somebody typed into the mobile field years ago. Nothing is wrong and nothing will ever be delivered.

Some people asked you to stop. That is a real, considered request, and it usually happened months ago, quietly, and nobody on staff remembers.

And on a text, most of your roster has never given you permission to text them in the first place, which is a different thing again and the one that gets churches into actual trouble.

A tool that shows you one number has folded those three into a shrug. What you want, before you press anything, is the arithmetic: this many will get it, this many have no address, this many opted out, this many never opted in. If your software cannot tell you that in advance, it is not being simple. It is being quiet.

Email and text are two different features wearing the same button

This is the part most church staff have never been told, and it explains almost every frustrating thing about messaging software.

In the United States, email and text messages are governed by different laws, and the two laws point in opposite directions.

Email runs on an opt-out model. Your church may email the people who belong to it, provided every message gives them a working way to stop. That is why you can write a newsletter on a Tuesday and send it to your whole roster without collecting anything from anybody first.

Text messaging runs on an opt-in model. You may not text a person because you have their number. You may text them because they agreed to be texted, and having their number is not agreement. A phone number on a card at a welcome desk is not a yes, and neither is a number a parent wrote down at a children's check-in counter.

So when a product will happily blast your whole roster by email but shows a much smaller number for the identical audience by text, that is not a missing feature. That is the software declining to expose your church to a class of complaint that carries real penalties, and the products that make it feel effortless are usually the ones that quietly moved the risk onto you.

Where a number came from decides what you may do with it

This is the failure that catches good churches, and it is almost never malicious.

A parent stands at the children's check-in counter with a toddler on one hip and writes a mobile number so the church can reach them if their child needs them during the service. That is a clear, narrow, entirely reasonable permission, and it is about one child, during one hour, in one building.

Eighteen months later, somebody exports the directory, notices that a few hundred more numbers exist than the messaging list has, and helpfully imports the difference.

Nobody made a decision. There was no meeting. But a number given at a children's counter is now on a mailing list, and the first fundraising text will feel to that parent like a bait and switch, because it is one.

The rule worth holding onto is that permission is scoped to the thing that was asked, and it does not widen just because the data ended up in the same database. A number collected for one purpose is not a number you may use for another, and the fact that both purposes are good does not join them.

Which means the question to put to any system is not whether it can import numbers. Of course it can. The question is whether it keeps track of where each one came from, and whether it will refuse.

The shared number, and why one church's mistake silences yours

Some products text your congregation from a phone number shared with every other church on the platform. It is cheaper to run and faster to set up, and it has a defect that no amount of good software can fix.

Opting out of texts is enforced by the phone carriers, and they enforce it against the number, not against the sender.

Follow that through. A member of your church is also on the list of a school, a gym, or another church that shares your platform's number. That other organization sends too much, and your member does the sensible thing and replies STOP.

Your church is now blocked from texting that person, and nobody will ever tell you. Not your vendor, because they cannot see it. Not your member, because from where they stand they stopped one annoying sender. The block lives at the carrier, above the application, and there is no setting anywhere that undoes it.

A number that belongs to your church alone costs more and takes longer to obtain, because the carriers require a real review of who is sending and how people agreed to receive it. That review is the reason it takes days rather than minutes, and it is also the reason the number is worth having.

A number nobody can reply to is not a conversation

The last one is the simplest and the most often skipped.

A church sends a text to two hundred people, and eleven of them reply. Where does that go?

In a lot of setups, nowhere. The number is send-only, so those eleven replies bounce off a wall, and eleven people conclude that the church does not answer. In others, the replies land on one staff member's personal cell, which works beautifully until that person is on holiday, or leaves, or is simply the wrong person to be receiving a message about a hospital stay.

A text is not a broadcast medium. People treat it as a conversation because it is the same thread their sister is in, and they will reply to it with things they would never have put in an email.

So the shape you want is that replies come back to a place the church owns, that more than one person can see, tied to the record of the person who sent it. Not a personal phone. Not a black hole.