Weather closure
Sunday services on [date] are cancelled because of [ice / snow / flooding]. Worship will be online at [time] at [link]. Stay safe, and watch here for updates.
Free guide
The ChurchBlasts Rollout Guide
A practical guide to bringing your congregation onto Blasts: where to place the church code, how to build audiences by ministry, who is allowed to send what, and a four-Sunday launch plan. Written for the person who will actually run it.
For the pastor, church administrator or communications director who owns Sunday communication, and for the ministry leaders who will send to their own people.
Este guia está em inglês.
Where the connection lives
Every member connects to your church once, by their own choice; after that your messages reach their phone or computer directly. What you are placing is the church code, your church's enrollment code, typed into the free Blasts app. It also comes as a QR code, a print-ready enrollment kit, and, where your Hub shows one, a standing enrollment link. Put it where the congregation already looks, and keep it there.
- The sanctuary screen before service: the QR code large, the code read aloud once.
- The bulletin, every week, not only launch Sunday. Print the kit for the welcome table and the office.
- The welcome table and new-member class: a greeter who can walk a visitor through the two-minute install.
- Your website and weekly email: the enrollment link or the code, in a standing spot.
- The parent pickup line: a printed card at children's check-out and youth pickup, where Children & Families and Youth fill fastest.
- Ministry leaders sharing the code in their own small group, serve team or choir. A familiar voice asking beats a screen.
Connecting is the member's choice: anyone can mute or disconnect at any time, so the code is an invitation, never a list you add people to.
What a member does, in two minutes
Install Blasts once
The free app on iPhone or Android, or the Chrome or Edge extension on a computer.
Enter the church code and tap Join
In Blasts, under Settings. The enrollment link walks them through the same thing.
Your church confirms, then they choose
Accept each request under People who want to connect, or turn on auto-accept in Settings. The person then picks their ministry audiences, and Blasts, email, or both.
Already have a directory? Upload a CSV on Connections: addresses are checked and previewed first, invitations go out at up to 200 a day, and everyone is invited, never added.
Audiences by ministry
Your Hub starts with Churchwide, which reaches everyone connected, plus a starter pack of ministry audiences. Members pick the optional ones on the preferences page the Hub provides; the church can also assign people to audiences that allow it. A parent of teens follows Youth and Sports; a retired couple follows Prayer and Daily Devotional.
- Churchwide: service updates, weather closures, what everyone needs.
- Prayer: requests and prayer-team updates. With a prayer audience, a confidential prayer lane appears in Conversations for the people assigned to it.
- Daily Devotional: daily scripture and reading plans, the home for your first Content Series.
- Children & Families: nursery, church school, VBS, check-out changes.
- Youth: youth group, trips, permission reminders.
- Small Groups: men's, women's, seniors, Bible studies.
- Serve / Volunteers: greeters, nursery, parking, tech booth, food pantry, missions.
- Sports: practices, cancellations, schedules.
To add your own, open Audiences and create one people will recognize: Choir, Deacons, Young Adults. Choose whether members choose it, the church assigns it, or either. Mark staff and elder-board audiences private. Audiences are preferences, never access.
Who sends what
Roles on the Team screen mean the pastor is not the only person who can send, and the youth director cannot reach the whole congregation by accident. Each person signs in as themselves, so Home shows who sent what.
- Owner: everything, including billing and the church's Blasts account. Usually the pastor or church administrator.
- Admin: every audience, team and integrations, without billing.
- Ministry Leader: sends to, and reads replies from, only the audiences you grant: the youth director gets Youth, the prayer coordinator gets Prayer.
- Viewer: read-only, for an elder who wants to read along.
A Churchwide send asks for a step-up confirmation with a passkey or phone approval, so a big send is never an accident. Settings can also require an administrator's approval before a ministry leader's Blast goes out.
Replies and pastoral follow-up
A reply to any Blast, on Blasts or by email, lands in Conversations as a private one-to-one thread, and everything with one person stays in one thread you can find by name. Staff notes are never shown to the person. This is where a prayer request after a Churchwide message becomes a pastoral conversation. Receiving is free for members; a reply they send uses their own credits, never the church's.
Daily Scripture from the first week
Content Series is included from the start, and Daily Scripture is the one to load first. Open Campaigns, choose New Content Series, pick the Daily Devotional audience, set the schedule (daily at 7am, or weekdays), and paste 30 different verses with a short reflection each. Activate it, and each morning one goes out on its own. Someone who joins in week three gets that day's reading, never the backlog.
A New Member Welcome Journey and an Event Campaign built around one date such as Christmas Eve are Hub Pro, which unlocks at $500 in cumulative credit purchases for any church, verified or not.
The email leg
Not everyone will install an app. Each connected person chooses Blasts, email, or both; people who chose email get each Blast individually or as one weekly digest, from your church's own verified sending address, which the Hub provisions. Replies land in Conversations too. Email is metered separately: every new Hub includes 50 email credits, packs are sold on BlastCredits, and a bounced address switches back to Blasts-only automatically.
Credits and verified church benefits
Credits are prepaid, never expire, and there is no subscription. One typed Blast to one person is one credit, charged only when delivered; the Delivery panel shows the cost before you commit. Credits are bought on BlastCredits, and the Hub activates with your church's first purchase.
Verification is separate from access. A church approved through the nonprofit verification program on BlastCredits receives 20% bonus Blasts credits on everyday packages through $500 and on email credit packs; there is no bonus on the $750 and $1,000 packages. It is optional, not required to buy credits or set up the Hub, and does not unlock Hub Pro: a benefit to apply for once, not a step on the way in.
The four-Sunday launch plan
Set up in one sitting, then build the connection habit one Sunday at a time. One person owns it, usually the church administrator, with the pastor's voice on Sunday 1.
Day 1 Set up your church
Sign in and run the guided setup: church name and website, timezone, the church-controlled Blasts account, and the starter audiences. Invite ministry leaders with the right roles. Click Sync connections once so the church code is published, print the enrollment kit, and send a test Blast to yourself.
Sunday 1 Ask from the front
QR code on the screen, the code in the bulletin, a greeter at the welcome table with the kit, and thirty seconds from the pastor on what people will receive and that they choose. Send a first Churchwide Blast that evening, a thank-you and next Sunday's service times, so every new connection sees the channel work.
Sunday 2 Fill the ministry audiences
Ask each ministry leader to share the code with their own people: the youth director at pickup, small-group leaders in their groups, the volunteer coordinator on the serve teams. Put the enrollment link or the code in a standing spot on the website and in the weekly email. Send one targeted Blast from a ministry leader, so families see that Youth reaches only youth families.
Sunday 3 Turn on Daily Scripture
Load 30 readings into a Content Series for the Daily Devotional audience and activate it. Mention it from the front: anyone who wants a verse each morning can add Daily Devotional on their preferences page. Keep the code on the screen and in the bulletin.
Sunday 4 Review and settle the rhythm
Open Sent & Scheduled and the Reach funnel on Connections: which audiences filled, which sends were read, who chose email. Upload the rest of the directory as a CSV for the people who never scanned. Settle a rhythm: Churchwide no more than twice a week, ministry audiences when there is something to say. Useful beats frequent.
What the Hub does, and what it does not replace
- Sends typed messages with formatting, links, images and up to three attachments: now, scheduled, or repeating weekly.
- Asks for a YES or NO reply and counts the answers, so a volunteer call shows who is coming.
- Delivers the same message by email to everyone who chose email, from your church's own sending address.
- Runs a Content Series from the start; Journeys and Event Campaigns once Hub Pro unlocks at $500 in purchases.
- Takes people in through the church code, QR code, enrollment kit, an enrollment link where shown, CSV import, an inbound webhook, signed outbound events, and a Zapier private app on request.
- Replace your church management software, your directory or your giving platform. The Hub adds a channel, and this guide promises no built-in connector to those systems.
- Take payments or process giving. A giving-statement notice is fine; the giving itself stays on your giving platform.
- Send campaign badges, countdowns, calendar attachments, voice Blasts, polls or self-destruct timers. Those are Blasts-app sender features, not the Hub composer.
- Confirm anything on a member's behalf. A YES or NO reply is the member's own action, which the Hub counts; a read count is not a confirmation.
- Add anyone to a list, or require verification to run. Every member connects by choice and can mute or disconnect at any time.
Blasts, the platform, supports voice messages and other sender features inside the Blasts app itself; this guide covers only what your church sends from the Hub.
Where to go from here
Nothing in this guide is a step you have to complete before you start. ChurchBlasts is open today: sign in, run the guided setup, and put the church code in the bulletin this Sunday. The Hub documentation covers every screen in more depth, and church pricing is on BlastCredits.
See it in action at Harborstone Community Church (uma organização de exemplo fictícia criada para mostrar o produto, não um cliente)
As informações do produto nesta página refletem os dados publicados do Blasts.app em 2026-08-17.