The short version every vertical site gives is: your people connect once, choose what they care about, and one send reaches all of them. Here is the whole machine, and each card links to the full article in the Hub documentation.
Consent-first connections
Nobody is ever added to a list. A person connects through your enrollment code or a connection request, and the Hub detects the right path automatically: on Blasts already, they get a request in their app; not yet, they get your invitation email with the code. Invitations from lists are spread at up to 200 a day so they never look like cold mail.
Read: Get your people connected β
Audiences people choose
Open audiences are published to your enrollment code as interests; each person picks theirs in their own Blasts app and can change them any time from their preferences page. You can group people inside an interest (a camp inside youth), and closed audiences for staff or leadership are yours to assign and never shown. Tags are preferences, never access.
Read: Organize who receives what β
Compose, campaigns, journeys
One Blast reaches everyone in an audience who can be reached. Schedule it, repeat it weekly, run a Content Series on the calendar, a Journey relative to each person, or an Event Campaign counting down. Rich text, images, up to three attachments, RSVP tallies, a test-to-yourself button, and optional administrator approval before a leader's Blast goes out.
Read: Send a Blast βCampaigns: three ways to send over time β
Two-way conversations
Replies land in a shared inbox with lanes (including a confidential prayer lane where a prayer audience exists), "who is replying" presence for teams, per-person history, staff notes, and STOP/START handled automatically on every rail.
Read: Handle replies and one-to-one conversations β
The email leg
People who prefer email still hear everything: each Blast is mirrored by email from your organization's own sending address (we provision the subdomain at activation), one by one or as a weekly digest. Email credits are separate and cheap: $10 for 2,500 up to $100 for 50,000, with a 20% bonus for verified organizations and 50 free to start.
Read: Blasts and email, side by side β
Every way in
Enrollment code, QR code, a printable kit, one-person invitations, pasted lists and CSV import with cleaning (bad addresses, duplicates, dead domains) and a preview before anything is sent, plus one inbound webhook URL any form, CRM or Zapier can post a new person to.
Read: Every way people can connect β
Data in, data out
Signed webhooks tell your systems when someone connects, opts out or replies, and when a Blast goes out. A private Zapier app (available on request) wraps both directions. Named connectors per vertical, starting with Planning Center People for churches. A Reach funnel shows exactly where everyone stands: known, invited, requested, connected, by channel and by source.
Read: Data in, data out β
Team and roles
Owners, admins, leaders limited to the audiences you grant, and read-only viewers. Everyone signs in as themselves; sending to everyone, changing roles and leaving ask for a passkey or phone confirmation. Members who sign in through Blasts can request Hub access, and nobody gets in until you approve.
Read: Give your team the right access β
Portals, households, birthdays, calendar
A members portal and an employees portal, each activatable and renameable, give people a place to manage their choices: Blasts or email, each update or a weekly digest, name and language. Group families so a mailing reaches one person per household. Members can share birthdays and anniversaries and the Hub sends your greeting at 9:00 local, once a year. Point the Hub at your public calendar and upcoming events appear on Home with one-click announcing.
Read: Organize who receives what βData in, data out β
External content and Flow
Automated producers (an alert engine, a publishing system) file content through signed HMAC ingest. Each item waits in a review queue rendered exactly as it would go out. A human approves it and explicitly publishes; ingest can never send on its own. Producer credentials are issued by BlastsHub staff today.
Read: External content and Flow β
Ownership and safety
Sign-in by email code, passkey, or through Blasts itself, with step-up approval for dangerous actions. The organization owns everything: leaving takes one typed confirmation plus a step-up, revokes our authority, and emails the owner a complete JSON export. Recovery material is held sealed. No hostages, ever.
Read: Security, ownership, and leaving β