What the Hub is

One engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.

What this helps you do

The Hub is the console an organization uses to communicate through Blasts, a permission-based channel where every recipient chose to connect. The same engine runs behind a dedicated front door for each kind of organization: a church signs in through ChurchBlasts, a nonprofit through NonProfitBlasts, an employer through DirectToEmployees, and so on. The vertical changes the vocabulary and the starter presets, never the machinery.

  • Home: your balance, connected people, what is scheduled, what needs attention, and recent activity.
  • Connections and People: who is connected, who has been invited, and each person's history, notes and household.
  • Audiences: the groups people choose for themselves, plus the closed ones you assign.
  • Send, Templates, and Sent & Scheduled: compose a Blast, reuse one, and see what went out, what is queued, and what is waiting for approval.
  • Conversations: replies and one-to-one threads, shared across your team.
  • Campaigns: Content Series, Journeys and Event Campaigns.
  • Team, Integrations, Settings and Help: roles, data in and out, your profile and branding, and these articles.

When to use it

Read this first if you are deciding whether to run a Hub, or if you just signed in and want the map before the details. Each capability has its own article; this one explains how they fit together.

How to do it

  • Sign in at your vertical's front door, or at blastshub.com, with an email code or through the Blasts app.
  • Run the guided setup: organization profile, the Blasts account your organization uses, audiences, a test Blast.
  • Share your enrollment code so people connect; each person picks the audiences they want.
  • Send your first Blast to everyone connected. People who prefer email receive the same message by email.
  • Grow from there: invite your team, add a Journey for newcomers, connect your calendar or CRM.

Example

A neighborhood association sets up a Hub on Tuesday. On Wednesday the enrollment code is on the newsletter and the lobby sign. By the weekend forty residents are connected and have picked the audiences they care about, and the first Blast about a street closure reaches every one of them on their phones, with the two who chose email getting it in their inbox.

Good to know

  • Everything is one engine. What a church calls Churchwide, a nonprofit calls All Supporters and an employer calls All Employees: the same protected audience that reaches everyone connected.
  • There are no seats, tiers or contracts. Sending uses prepaid credits from BlastCredits; the Hub unlocks with your first credit purchase.
  • The organization owns everything. People can mute or disconnect at any time, and the organization can leave with a complete export.

Do it in your Hub

Inside your Hub, Help covers the same ground in your vertical's own vocabulary, next to the screen it describes.