Working documentation, in your vertical's terms
ResidentBlasts documentation
The Hub is one platform. Its workflows and terminology adapt to the organization running it: on ResidentBlasts, the audience that reaches everyone is called All Residents and the people you reach are residents. 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 community? That case is made at residentblasts.com, not here.
ResidentBlasts topics
01Get the people who live here connectedStart each resident with an email address at the moments you already have, and let the Hub move them to Blasts when they connect.02Where they live, and what they want to hear aboutTwo kinds of audience: the places you create by name, and the topics residents choose. The shutoff goes to the building; the pool reopening goes to Amenities.03Send it to the part of the community it concernsGet the notice about one building, one phase or one topic to the residents it affects in minutes, from the person who knows.04Give the office, maintenance and the board the right accessLet each manager reach their own places and topics while the owner keeps the All Residents sends and billing. A team role is not a resident audience.05Answer residents about where they live, one to oneReplies to a notice land in one inbox, and the office picks each one up. A reply is not a work order.06Plan the weekly update or a season of property notes in advanceWrite a month of updates once and let each one go out on its own day, to the place or the topic it belongs to.07Welcome each new resident, and let them chooseGive every new resident the same three-week welcome, timed from the day they connect or you add them, ending with the choice in their hands.08Carry a community project from the announcement to the update afterBuild the announcement, what residents should know, the reminders, the day itself and the follow-up around one dated piece of work, once.09Where the Hub fits beside your property systemYour property system keeps the lease, the ledger and the work order; your access system keeps the gate. The Hub adds the channel, and four generic doors connect the two.10Set up ResidentBlasts for your communityGet your community profile, timezone, sending address and the resident preferences page ready before the first move-in packet goes out.
Shared Hub topics
These work the same way on ResidentBlasts as on every other vertical, so they live once, in the platform documentation.
11What the Hub isOne engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.12Blasts and email, side by sidePeople who prefer email still hear everything, from your organization's own address.13Campaigns: three ways to send over timeContent Series on the calendar, Journeys relative to each person, Event Campaigns around one date.14Every way people can connectEnrollment code, QR code, printed kit, connect links, invitations, CSV, and a webhook.15Understand credits, refills and Hub ProPrepaid credits from BlastCredits that never expire, a separate email balance, and Hub Pro at $500 in purchases.16Security, ownership, and leavingThe organization owns everything. Leaving takes one confirmation and emails a complete export.17External content and FlowAutomated producers file content through signed ingest; a human reviews it and explicitly publishes.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 residentblasts.com or right here. Inside your Hub, Help shows these same articles next to the screen each one describes.