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 your residents connected at move-inOffer the connection at move-in or association onboarding, and reach the same household every time after.02Organize buildings, amenities and the boardSend the shutoff to Building B only, the pool closure to the people who use it, and the packet to the board.03Send a shutoff, an entry notice or an amenity closureGet the notice that generates phone calls onto the right residents' phones in minutes.04Give the office and the board the right accessLet each manager reach their own property while the owner keeps the All Residents sends and billing.05Answer residents 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 community update in advanceWrite a month of updates once and let each one go out on its own day.07Welcome each new resident automaticallyGive every new resident the same first-week orientation, timed from their own move-in.08Carry the annual meeting or the pool openingBuild the announcement, the reminder, the details on the day and the follow-up around one date, once.09Data in, data outCSV import, an inbound webhook, signed outbound events and a Zapier app. There is no property-management connector.10Understand your creditsOne prepaid credit per resident, credits that never expire, and no per-message carrier bill.11Set up ResidentBlasts for your communityGet your community profile, timezone, sending address and resident preferences page ready in a few minutes.
Shared Hub topics
These work the same way on ResidentBlasts as on every other vertical, so they live once, in the platform documentation.
12What the Hub isOne engine behind every Blasts vertical: consent-first connections, audiences people choose, sends, conversations and campaigns.13Blasts and email, side by sidePeople who prefer email still hear everything, from your organization's own address.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.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.
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.