What this helps you do
Blasts gives your community a direct line to the people who live there, with their consent, for as long as they live there. The simplest start is an email address: a resident who joins at move-in, from the welcome email, at the office or on your website becomes an email subscriber and receives the office's messages by email from day one. When that resident later connects on Blasts, the Hub notices the connection and moves their delivery to Blasts on its own; nothing has to be re-sent or re-entered. Someone who already uses Blasts can enter your enrollment code instead, which creates a connection request for the community to accept.
When to use it
Put the invitation at the moments a residential community already owns: move-in and the key handoff, the closing or association onboarding packet, the welcome email, the management office, the community notice board and your community website. Where the community has a lobby, a mail area or amenity doors, the printed kit belongs there too. Then repeat it whenever a resident is in front of you with a question, because enrollment does not have to happen at move-in to count.
How to do it
- Open Residents in your Hub and click Sync connections once so your enrollment code is published.
- Print the enrollment kit for the office counter and the notice board, and put the enrollment code or QR code in the move-in packet, the welcome email and the association onboarding packet. You add one line to your own templates; nothing connects to your property software for you.
- Add a resident by email at the office, or point your move-in form or community website form at the inbound webhook on Integrations or the Zapier app, so each new resident joins as an email subscriber the day they ask.
- If your property system gives you an opted-in resident or owner export, use Add many at once or upload the CSV. Tick the opt-in box for people who already agreed to hear from the office and they join as email subscribers right away; everyone else is invited, checked on Blasts and spread out at up to 200 a day.
- When a resident enters your code in the Blasts app, a connection request arrives. With auto-accept on in Settings they are connected the moment they join; with it off, accept them under People who want to connect on Residents.
- Send everyone to the preferences page (the link is in Settings) to pick their topics, and use Bulk assign to place them in their building, phase or street once you know where they live.
Example
A 240-home community with three buildings and a row of townhomes puts the code in the move-in packet and the kit on the office counter, adds one line to the welcome email, and uploads the opted-in resident list the office already keeps. Six weeks later most households are on the list, half of them already on Blasts, and the office has placed each one in Building A, B or C or Townhomes. When a riser fails, the shutoff notice goes to Building B and the townhomes never hear about it.
Good to know
- Connecting is consent-based: a resident can change their topics, mute the office or disconnect at any time, and the office is not told. A lease or an association membership is not consent to message someone here; the resident joins.
- Entering the enrollment code does not connect a resident by itself. It creates a connection request that the community accepts, unless auto-accept is on in Settings, in which case they are connected right away. Leader approval is a different setting: it holds a manager's Blasts for an administrator, and has nothing to do with who is connected.
- Import columns: your file needs an email column. The Hub also recognizes name, first name, last name, phone, address, birthday, household, and interests (a column headed audiences, tags, groups or lists works too). Files are limited to 5,000 rows and 2 MB, with a preview before anything is sent.
- There is no property-management, work-order, payment or access-control connector. Your resident list reaches the Hub as a CSV export, through the inbound webhook, or through Zapier, and the Hub does not learn where anyone lives until you or the resident place them in a place audience.
- Two people in one home are two connections, each on their own phone. Group them as a household on the person page so a mailing can be held to one copy; there is no shared household login.
- The Reach funnel on Residents shows where every resident stands (known, invited, requested, on email or connected) and how they arrived: code, import, webhook, request or Zapier.
- This is Blasts, not SMS: no per-message carrier fee, and no mobile numbers to collect or refresh at every move-out.