If you build church management software, give each church its own sub-account, registration and number, so texts come from that church and its opt-outs stay its own. Then send service reminders, volunteer schedules and event notices through one REST API, with consent captured when a person joins a list.
Churches text a lot, and mostly to people who asked for it: service times, small group changes, prayer chains and volunteer swaps. The risk for a platform is the opposite of the use case. Many churches means many senders, each with different habits. Our guide to multi-tenant SMS architecture covers the general design. For church-side basics, see church texting service.
What churches send
| Message | Audience | Notes |
|---|---|---|
| Service time or location change | Whole congregation | Time-sensitive |
| Volunteer schedule and swaps | A ministry team | Two-way replies |
| Event reminder | People who registered | Transactional |
| Prayer request or care message | A small group | Personal, keep out of bulk |
| Giving receipt or reminder | Donors who opted in | Registered use case matters |
The platform design
- Create a sub-account per church with
POST /v1/sub-accounts. See the sub-accounts docs. - Register each church as its own business. Ready registers businesses with an EIN, so a church without one can't register. Decide what your product tells it. Most approvals take 2 to 7 days.
- Give each church a number at $2 a month, and send with
POST /v1/messagesfrom that sub-account. - Model groups in your own database. A ministry, a class and a volunteer team are lists you manage. Send with
POST /v1/messages/bulk, at most 100 numbers per call. - Route replies by number to the right church. Routing inbound SMS to the right tenant shows how.
Consent and care
Capture agreement on a connection card, a sign-up form or a text-to-join keyword, and store when and how in your own data. Ready keeps no per-contact consent record for API sends, so that record is yours. See church connection cards and opt-in wording that passes registration.
Pastoral and care messages are personal. Don't send a sensitive health or family detail by text, and let a person choose to receive them. A STOP always blocks that number in the sub-account that received it. Show church staff a clear way to see who has opted out.
Cost per church
A congregation of 400 people texted weekly with a one-segment reminder sends 400 segments a week, so 400 × ($0.0075 + $0.0045) per weekly send, plus the registration and number fees. The figures are assumptions: swap in your own size and frequency. See metering SMS usage per customer.
Ready's all-in prices per segment include the carrier fee but not screening: Scrub lists and Number validation, the two switches in Settings under Compliance, each add $0.003 per segment when switched on, shown as screening on your bill, and both are off by default. Unless you turn the opt-out footer off, the first text to each contact, and one again from time to time, also gets "Reply STOP to opt out" and your business name if the message does not already have them, so a text close to the segment limit can bill one more segment.
Accounts opened before November 12, 2026 keep their signup prices, shown under Billing.
Frequently asked questions
Can a church share one number across campuses? It can, but separate numbers per campus help recognition and routing. That's a product decision.
Are church texts exempt from the rules? No. Consent, opt-out and registration apply to churches too.
Can volunteers reply to confirm? Yes. Replies land on your inbound webhook, and each received segment is billed at $0.0075 plus the $0.003 received carrier fee.
Next step
Prototype one church end to end in a test account: sub-account, number, a reminder to a volunteer list and one reply.