Working documentation, in your vertical's terms
BlastsFlow documentation
The Hub is one platform. Its workflows and terminology adapt to the organization running it: on BlastsFlow, the audience that reaches everyone is called All Subscribers and the people you reach are subscribers. 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 organization? That case is made at blastsflow.com, not here.
BlastsFlow topics
01Set up your publicationsA publication in BlastsFlow is an audience readers choose, plus the editions you send it. Build one per publication.02Get your readers receivingStart with the opted-in email addresses you already have. Connecting on Blasts is each reader's own choice.03Publications are audiences readers chooseOne open audience per publication, named the way readers know it. Groups you fill yourself stay hidden from readers.04Publish an editionSend an edition to one publication's readers now, on a schedule, or every week.05Run a publication's schedule as a Content SeriesWrite a publication's next editions once, and each is released on its schedule to that publication's readers.06Give each editor their publicationsAn editor publishes to, and reads replies from, the publications you grant. Approval is on by default.07Answer readers one to oneA reader's reply to an edition becomes a private conversation with the editors of that publication.08Welcome each new reader of a publicationA short sequence that starts when a person enters one publication's audience.09Communicate around one dateThe week before, the day and the follow-up for a date that matters to your readers.10Editions from your own systems: the review queueA system you run can file an edition. It waits in the review queue until a person publishes it.11Data in, data outYour sign-up form through the inbound webhook, signed events out, and Zapier. No newsletter or payment connector.12Email first, Blasts when readers connectReaders receive editions by email with nothing installed. When they connect on Blasts with the same address, editions move there.
Shared Hub topics
These work the same way on BlastsFlow 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.18Manage 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 blastsflow.com or right here. Inside your Hub, Help shows these same articles next to the screen each one describes.