Working documentation, in your vertical's terms
LeagueBlasts documentation
The Hub is one platform. Its workflows and terminology adapt to the organization running it: on LeagueBlasts, the audience that reaches everyone is called Whole League and the people you reach are participants. The pages below are the how, written in that vocabulary; the shared topics further down are identical for every vertical.
Deciding whether the Hub fits a league? That case is made at leagueblasts.com, not here.
LeagueBlasts topics
01Get your participants receivingStart with the registration contacts you already have. Connecting on Blasts is each person's own choice.02Organize your league's structureBuild an audience for each part of the league a call can land on: divisions, teams, coaches and team contacts, officials.03Give coaches, coordinators and the assignor the right accessOwners and administrators make the league's calls. Leaders send only to the audiences you grant, with approval on by default.04Send the league's callWrite it once, pick the one audience it goes to, and send it from the league.05Answer participants, coaches and officials one to oneEvery reply to the league lands in one shared inbox, visible to the people granted that audience.06Plan the league's regular notes in advanceWrite a season of weekly league notes or the coaches' preseason checklist once, and let the Hub send each on its date.07Welcome each new coach and team contactA Journey runs when a person enters one audience. For a league, the starter welcomes coaches and team contacts.08Run the build-up to opening dayAn Event Campaign times messages around one date the league sets, like opening day.09Where the Hub fits beside your league systemYour league system keeps the schedule. The Hub carries the league's call to the audiences you maintain.10Email first, Blasts when a participant choosesPeople receive by email from the league's own address; delivery moves to Blasts when they connect with the same address.11A communication channel, not a participant recordImport only what communication needs. Player, medical, waiver, payment and eligibility details stay in your league system.12Set up LeagueBlasts for your leagueGet your league's profile, ownership mailbox, sending address and defaults ready before registration opens.
Shared Hub topics
These work the same way on LeagueBlasts as on every other vertical, so they live once, in the platform documentation.
13What the Hub isOne engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.14Campaigns: three ways to send over timeContent Series on the calendar, Journeys relative to each person, Event Campaigns around one date.15Every way people can connectEnrollment code, QR code, printed kit, connect links, invitations, CSV, and a webhook.16Understand credits, refills and Hub ProPrepaid credits from BlastCredits that never expire, a separate email balance, and Hub Pro at $500 in purchases.17Security, ownership, and leavingThe organization owns everything. Leaving takes one confirmation and emails a complete export.18External content and FlowAutomated producers file content through signed ingest; a human reviews it and explicitly publishes.19Manage delivery problems and reconnectionSee why a send did not reach someone, and what, if anything, to do about it.
Ready to work in your Hub?
Sign in at leagueblasts.com or right here. Inside your Hub, Help shows these same articles next to the screen each one describes.